After I got a report of a bit strange behavior of GPS-sensor I thought I could maybe have a look on the actual programming of it. After all it has a few years on it’s back and maybe could get an overhaul. It was not meant to be fully re-written but you know how it goes…
It’s now EX-bus
Sensor now works with full EX-bus. There’s pro’s and con’s on this, the main function of a sensor is to be fast to deliver values to system and EX-bus truly comes through on this. Old sensor connected to receiver with 9600baud and new version is now 125000baud, also there is no issues with differences on R- or REX-receivers. Update speed on transmitter is up to 4-5 times per second, so this is fast!
Downside is that hardware Jetibox does not work with EX-bus sensor, same goes for expanders, unfortunately. But in my minf the pro’s wins con’s by a big margin so this is how it is now.
What about my old GPS-sensor?
Best news ever: Just update! New firmware is fully compatible with old hardware and connections. You do not need to re-solder any wires!
RCT Jeti GPS-sensor release
You will find the new firmware on the re-worked GPS-page HERE. I released it as version 2.b meaning it’s a beta until I get some feedback from you guys! So let me know HERE in case of any issues, thanks in advance!
Hello, Tero,
Use multiple self-built GPS sensors with Nightflyer88 software. This sensor uses the same hardware and wiring as the RC-Thoughts GPS sensor. This hardware and software works without any problems.
The reason I use the Nightflyer88 software is because it registers the distance travelled (trip).
Now that the new RC-Thoughts GPS software for the EX-bus is available I wanted to test it.
Initially the EXT port on the receiver was set to EX-bus. Then with the RC-Thoughts Firmware Uploader I sent the GPS EX-bus software to the GPS sensor. The Firmware Uploader confirmed that sending the firmware was successful. Now connect the GPS sensor with the new software directly to the EX-bus of the receiver. Nothing happens.
– The sensor is not visible through the Jetibox emulator in the transmitter.
– After pressing the "Auto" button in the Sensors/Logging Setup screen, nothing of the GPS sensor is displayed.
The EX-bus software for the GPS sensor is also sent again with X-Loader to the GPS sensor. The successful transmission is confirmed, but the sensor does not work.
Then the EXT port of the receiver is reset to Jetibox & Servo, the Nightflyer88 software is sent to the GPS sensor and everything works again.
Have no idea what the cause of this is, but send these experiences in response to your request for feedback. Maybe there are more users with the same problem.
Kind regards,
Nico
Translated with www.DeepL.com/Translator (free version)
Nightflyer88's GPS is originally done on from my older version GPS, that is true.
If you uploaded my new GPS-hex to your GPS and it was in the Nightflyers version before I would imagine one issue right away and that is the settings stored in Arduino. I haven't gone through Nightflyers code but since he has put all sort's of stuff in it I would imagine that EEPROM-addresses and values are not the same and it's possible there's something messing the start of sensor.
There's a way around this, you could flash a .hex that reset's some of the EEPROM-addresses and then use my GPS .hex. Since you can't get the Jetibox-menu to show up in your transmitter there is no way of resetting it either.without flashing. I think it could be cool to investigate a reset-function, it's easy to build a "short these pins to reset"-function in there, could be fun to do.
Another possibility is of course that your EXT set as EXBus just didn't work for some reason. We know for a fact that my hex works as EXBus, I have a few GPS-sensors working with it and there's test-report's saying the same, all with the exact same .hex-file.
Vielen danke fur dich feedback, danke vielmals Nico!!
Hello, Tero,
Thanks for your reaction. Have tested the EX bus of the receiver with another EX bus sensor and the EX bus is fine. The sensor is visible Device Explorer. Now get started with your remark about a reset of the arduino.
Kind regards,
Nico
Since you have verified EXbus only possibility is the different EEPROM values. I’ll have a look on the reset at some point :)
Hello, Tero,
I have copied your EX Bus GPS sensor published in Jetiforum.
Today was the first test in flight. Contrary to your statement of 4-5 values per second
I see only about 2 values per second in the log.
Does the update rate of the GPS module ( Beitan 220 ) in the Ublox Center have to be set to 5Hz? Maybe the baudrate has to be adjusted then?
My Setup:
DS 16
Rex 10 Assist
RCT GPS sensor
HOTT ESC with HOTT2Duplex converter.
Greetings Jürgen
If you use anything else than NEO-6M or NEO-8M you need to set your GPS-module update-speed yourself. Keep the serial speed in 9600baud. My code does this automatically for UBlox NEO-6M and NEO-8M. While the RCT GPS may support any GPS module with 9600baud and NMEA the guide is for NEO-modules with GPS from UBlox. Any other module-type is untested and function is not guaranteed.
Actually the update-speed between NEO GPS and Arduino is 10Hz, the update speed from receiver to transmitter have been 4-5Hz at best :)
Hello, Tero,
thank you for your quick response.
I tested it again today with the GPS sensor with 10Hz rate.
In extended mode I reach about 2Hz update rate, in basic mode between 4 and 5 Hz.
Another thing I noticed is that the REX 10 Assist, after switching on with the GPS sensor
only bound says, reinforced and initialized are no longer necessary. Sensor disconnected, all 3 announcements
back.
Greetings Jürgen
I have no idea what this means? "reinforced and initialized are no longer necessary"? Translation error? I don't have/use Assist so no help there either.