Thread Tools
Jan 03, 2017, 02:15 PM
Registered User
Thread OP
Thanks Marc ! You've solved the problem before people have run into it
Sign up now
to remove ads between posts
Jan 03, 2017, 02:47 PM
Registered User
Dancy's Avatar
Well,
I am surprised! I truly expected more difficulty and problems. This seems almost too easy.
Narrative:

I have been working assembling my platform for my long range powered glider. Getting the Pixhawk wired in correctly to all of the "goodies" I intend on using. Pretty much a full house. I want to be able to perform complete flights autonomously while I enjoy the view via video googles and head tracker. The pixhawk servo rail caused my first problem. I am using 6v servos. Pixhawk wants to be powered via the power module but if you have greater than 5.5v on the servo bus, well, their docs are not real clear. They site 5.7v as max for normal operation and max voltage tolerance as 20v and then some greek about a zener diode that looks like a source of smoke to me so I just isolated the power buss for the servos. Next problem I encountered was a "gotcha" on Sami's board. He has a vertical connector specified for the telemetry/serial port on the RX board and when he assembled them for me he used a horizontal (Pins reversed! Dead short, killed power to the Pixhawk) I simply made a custom cable to remedy that.

I was beginning to wonder if the RX board had any software loaded yet. No led's when power was applied via usb nor the main power port. Got stuck here as ULRS had expired. Ben fixed that. I have encountered a slight bug in the program though. Sometimes when I start ULRS, it shows no com ports and hitting refresh causes it to freeze. Unfortunately, I have not been able to identify a repeatable sequence to reproduce this. Now came the easy part. I connected to the Sami RX via USB and fired up ULRS and connected to it. Tried the spectrum analyser. Had a graph of activity. Keyed my shortwave radio on 444mhz and bang! The SA reported it perfectly. Next I turned on Sami's TX via my JR 10x and (grin!) I had lights! On both modules I could see the send and receive led's going. I had verifiable changes to each transmitted channels on the ULRS servo display.

Next I went to the Firmware Upgrade tab and well, did not know which radio button to check for Sami's board with the USB connection so I just tried the mini button. Well off it went and just did it! Wow! Too easy! Thank you Sami and Ben!


01-03-2017 09:57:34.807 Run avrdude in folder c:\WinAVR-20100110\bin
01-03-2017 09:57:34.807 Firmware is in folder ULRS_HK_1W.hex
01-03-2017 09:57:34.807 -Cavrdude.conf -patmega328p -carduino -P\\.\COM5 -b57600 -D -Uflash:w:"C:\Users\Keshka\AppData\Local\Temp\ulrs\ avrdude\firmware.hex":i
01-03-2017 09:57:36.512 avrdude.exe: AVR device initialized and ready to accept instructions
01-03-2017 09:57:36.528 Reading | ################################################## | 100% 0.02s
01-03-2017 09:57:36.528 avrdude.exe: Device signature = 0x1e950f
01-03-2017 09:57:36.560 avrdude.exe: reading input file "C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\f irmware.hex"
01-03-2017 09:57:36.565 avrdude.exe: writing flash (20108 bytes):
01-03-2017 09:57:42.060 Writing | ################################################## | 100% 5.50s
01-03-2017 09:57:42.060 avrdude.exe: 20108 bytes of flash written
01-03-2017 09:57:42.060 avrdude.exe: verifying flash memory against C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex:
01-03-2017 09:57:42.076 avrdude.exe: load data flash data from input file C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex:
01-03-2017 09:57:42.081 avrdude.exe: input file C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex contains 20108 bytes
01-03-2017 09:57:42.081 avrdude.exe: reading on-chip flash data:
01-03-2017 09:57:46.111 Reading | ################################################## | 100% 4.03s
01-03-2017 09:57:46.111 avrdude.exe: verifying ...
01-03-2017 09:57:46.111 avrdude.exe: 20108 bytes of flash verified
01-03-2017 09:57:46.142 avrdude.exe: safemode: Fuses OK
01-03-2017 09:57:46.142 avrdude.exe done. Thank you.


OK! now on to the TX. I unplugged the USB connection to the RX and plugged in the TX. ULRS refresh did not work but it did not hang either. I had to leave the TX plugged in and restart ULRS. Now it sees Sami's JR TX. (I am running the newest release of Windows 10 Ben). Spectrum analyser, working. Firmware update, Check!

01-03-2017 11:34:52.303 Run avrdude in folder c:\WinAVR-20100110\bin
01-03-2017 11:34:52.303 Firmware is in folder ULRS_HK_1W.hex
01-03-2017 11:34:52.304 -Cavrdude.conf -patmega328p -carduino -P\\.\COM5 -b57600 -D -Uflash:w:"C:\Users\Keshka\AppData\Local\Temp\ulrs\ avrdude\firmware.hex":i
01-03-2017 11:34:54.005 avrdude.exe: AVR device initialized and ready to accept instructions
01-03-2017 11:34:54.005 Reading | ################################################## | 100% 0.00s
01-03-2017 11:34:54.005 avrdude.exe: Device signature = 0x1e950f
01-03-2017 11:34:54.036 avrdude.exe: reading input file "C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\f irmware.hex"
01-03-2017 11:34:54.052 avrdude.exe: writing flash (20108 bytes):
01-03-2017 11:34:59.511 Writing | ################################################## | 100% 5.46s
01-03-2017 11:34:59.511 avrdude.exe: 20108 bytes of flash written
01-03-2017 11:34:59.511 avrdude.exe: verifying flash memory against C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex:
01-03-2017 11:34:59.511 avrdude.exe: load data flash data from input file C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex:
01-03-2017 11:34:59.531 avrdude.exe: input file C:\Users\Keshka\AppData\Local\Temp\ulrs\avrdude\fi rmware.hex contains 20108 bytes
01-03-2017 11:34:59.531 avrdude.exe: reading on-chip flash data:
01-03-2017 11:35:03.553 Reading | ################################################## | 100% 4.02s
01-03-2017 11:35:03.553 avrdude.exe: verifying ...
01-03-2017 11:35:03.553 avrdude.exe: 20108 bytes of flash verified
01-03-2017 11:35:03.577 avrdude.exe: safemode: Fuses OK
01-03-2017 11:35:03.579 avrdude.exe done. Thank you.

Slick! I love it! Now I see the red led on port PD6(AIN0) flashing after the update. Seems I read about that in one of Ben's posts as a revision. Also the led for Sami's bluetooth module is flashing. Nice!

Updates to follow as I get more time to continue. Very happy with the results I have seen.

Thank you all so much for each contribution to this thread. Learning from each post as I go. Special thanks to Ben and Sami for making this smooth as silk.

Keshka
(aka: Dan)
Jan 03, 2017, 03:59 PM
Registered User
Thread OP
Hi Keshka,

Thanks for the nice report ! It's true that one of the objectives was to stay simple to use. That's why it's the same firmware for TX and RX, in the beginning it was even able to detect if it was installed on a TX or RX (but that proved unreliable with some RC transmitters).

After all it has to be as simple as possible, it's just the invisible wire between the pilot and the plane : if you don't notice it then it plays his role.
Jan 03, 2017, 04:07 PM
Registered User

14 second Delay in MAVLink data?


After a lot of trial and error I got the Wolf Box tx hooked op to my pc and th rx to a navio2 running arduplane. I am running Ultimate LRS 2.33.

APM Planner and Mission Planner connected. Yay!

But: there is a bad and increasing delay in the MAVLink. How can I improve this? Ultimate LRS seems to have too big a buffer. And there can be a 14second (!) delay between moving the plane and the artificial horizon moving on APM Planner.

What can I do to decrease the latency?
Jan 03, 2017, 05:19 PM
Registered User
Thread OP
Hi and welcome to rcgroups !

Normally there's practically no visible delay, it should move on screen as fast as you move the flight controller.

I don't think this is related to buffering in the atmega, because it only has 2k RAM, which would be filled up in 1 second at 19200 bauds, and the buffer is limited to much less than 2k.

Pay attention to the fact that only MP 1.3.37 works fine, not a more recent version.

Could it be an issue with the FTDI driver, this one has a large serial buffer.

I'm not aware of other users of Navio2, so your feedback is very important.
Jan 03, 2017, 06:02 PM
Registered User
Hi, is there a way to reduce power for the 1W boards in ULRS to lets say 100mW?

I'm about to build a dolphin board and I would prefer to be on 100mW. Can I do it with RFM23BP?
Jan 03, 2017, 06:39 PM
RC fanatic

New Teensy telemetry solution v2.0-rc1 now available for testing


Guys, I have been continuing my development of the Teensy telemetry solution over the last few weeks and finally I can announce that v2.0-rc1 is now available for testing here: https://github.com/athertop/MavLink_...-opentx2.1-dev

Sorry to troll the ULRS forum, but I appreciate that there are a few ULRS users in here who take advantage of the teensy telemetry solution with its ability to work with ULRS (which has been discussed in this forum previously). So though't I'd make a shout out and provide some details.

The solution uses a Teensy LC or 3.x board to convert the Mavlink output at the ULRS Tx into FrSky SPort data. Once fed into the Taranis radio this provides 25 discoverable telemetry sensors - some with regular and some with custom data. This is all made sense of with a custom telemetry screen. Actually there are two separate telemetry scripts, plus two optional mixer scripts provided by the project. main.lua which as the name suggests is the main telemetry screen for the project provides the regular flight screen (some images are shown below) The other telemetry script is called txtmsg.lua allowing Mavlink status messages to be read (although this is experimental just now and not so reliable). The two mixer scripts if installed - one provides LiPo voltage voice warnings, and the other manages service intervals.

The main telemetry screen looks like this:
Name: v2telem-main.jpg
Views: 81
Size: 63.9 KB
Description:

and pressing the MENU button loads the scripts configuration page which looks like this:
Name: v2telem-main-cfg.jpg
Views: 78
Size: 61.0 KB
Description:

Configuration settings are stored on the SD card and specific to the active model.

This is of course just a release candidate at the moment and even though my own limited tests have proven successful, please don't use this in critical situations just now, but I'd be grateful to anyone willing to give it a go for testing.

Just some background:
Discussion on the project has been happening on diydrones forum since its beginnings in January 2014 here: http://diydrones.com/forum/topics/am...port-converter. There have been several developers working on the project since the beginning. My involvement in the project has been over the last year, and in that time I have added the ULRS compatibilities, and advanced the LUA screens for the Taranis (making them compatible with OpenTx 2.2 now as well as 2.1). I have also updated the wiki (here: https://github.com/Clooney82/MavLink_FrSkySPort/wiki) which presently covers only up to release v1.8 - once this new v2.0 goes on general release, I will then update the wiki to reflect the changes in this version. For the time being, if you have any questions, please consult the release notes on the releases page here: https://github.com/athertop/MavLink_...s/tag/v2.0-rc1 and also feel free to ask questions on the diydrones forum - or feel free to PM me here. I will be shooting some videos in the longer term also to show how to set it all up.
Cheers, Paul
Jan 03, 2017, 06:45 PM
Registered User
Brilliant. If you have a Taranis and use Ardupilot this is a must.
Jan 03, 2017, 07:42 PM
FPV Melbourne
yak-54's Avatar
Nothing to see here move along all
Last edited by yak-54; Feb 22, 2018 at 04:29 AM.
Jan 03, 2017, 09:23 PM
FPV Melbourne
yak-54's Avatar
Nothing to see here move along all
Last edited by yak-54; Feb 22, 2018 at 04:29 AM.
Jan 04, 2017, 03:10 AM
RC fanatic
Quote:
Originally Posted by yak-54
This Ok for some but there's a lot people that cant compile it or when they try its missing this or that why not share the Hex and the telemetry script
i bet i lot of people will start using it
There are many different combinations of configuration options in the teensy code, which is why you need to compile it. If you tell me your specific config options then I can provide a hex for you. You will still need the teensy writer app to apply the sketch.
Jan 04, 2017, 03:53 AM
FPV Melbourne
yak-54's Avatar
Nothing to see here move along all
Last edited by yak-54; Feb 22, 2018 at 04:29 AM.
Jan 04, 2017, 06:23 AM
RC fanatic
Quote:
Originally Posted by yak-54
i am good i have used Arduino for years
Ah cool, no worries then! Just for info I rewrote most of the wiki since being involved in the project so the build and install instructions are pretty accurate now - so to install, its just a case of following the wiki :-)
Jan 04, 2017, 06:45 AM
Durability Tester
Quote:
Originally Posted by gregd72002
Hi, is there a way to reduce power for the 1W boards in ULRS to lets say 100mW?

I'm about to build a dolphin board and I would prefer to be on 100mW. Can I do it with RFM23BP?
You would have to use an rfm22b
Jan 04, 2017, 07:15 AM
Arrière pays Niçois
salience's Avatar
Quote:
Originally Posted by athertop
Guys, I have been continuing my development of the Teensy telemetry solution ...
MUCH appreciated Paul.


Quick Reply
Message:

Thread Tools