openrcforums

Ok, the latest version has the extra options and the channel mapping is steady and locked, but it begs the question on how you manage options between all the different receivers. I see you have a Ch5/6 Sbus/port option as well, which I presume is mapping Sbus onto PWM pins on receivers that have it....

As I was taking the logs, I noticed that the receiver options screen was showing slightly different data from before. I attributed this to the fact that I was experimenting with a homemade S-Port sensor, so the telemetry data was different. When this sensor was removed, I then saw the same display a...

Yes, the Receiver Options screen is still garbled, with some overwritten characters. The characters change when you scroll through the lines, but they always go back to invalid numbers. Also, on the Internal Protocol Options screen, it shows the Power as -1. I don't know if that is supposed to be th...

I received my multi-module today and it appears to work fine in the Q X7. I only tested D8 and D16 mode and some obscure protocol but it all seemed to work ok. I believe I have enough of a working version to start integrating the radio into my models. The only outstanding things I can think of is su...

I think you did find the problem! After an hour or so, have not seen any losses yet.

I just tested that version and the telemetry losses are still occurring. Sometimes it can go for a while with no loss, and then when it occurs, it can occur rapidly, one after another, with or without servo movements.

Logs from recent losses:

Hmm, as I play more with it, I'm noticing that there are times when it looses telemetry in ACCESS mode. I've managed to catch some of those occurrences in the attached log file. It's set for 0.5 s sampling. I have not seen the same issue in ACCST/D16 mode.

Well, Happy New Year!

I've enclosed a pic of what the Receiver Options screen looks like, as well as the log file. There is about 10 seconds of log at 1 per sec.

Yes, on performing a Register and bind on a newly flashed receiver, it bound as expected and I am now getting telemetry in ACCESS as well. I will play around with the telemetry a bit more. I can go into the receiver options for the bound receiver and can turn telemetry on/off, but the CH pin mapping...

Version 9 now works for Internal! I was able to bind in D16 mode to both your D16 code, as well as an R-XSR 2.1.0 (both ACCST and ACCESS mode). The LEDs also appear to work correctly now. I've only done a cursory check on D16, but it seems to work fine. The erskytx telemetry is different from my old...

If it's of any use, I've managed to flash one of my old D4R-II receivers with your D16 code, so if you need to write any debug binding code from the receiver's perspective, that is an available option.

The count down timers appear to counting be down correctly, with the right timing. On the debug menu, the 6th line is as follows: xxxx 0000 0000 0042 202C, with only the first value counting. Internal module was set up as ACCESS/ACCST(D16) Selecting ACCESS in the External module still results in a W...

I have never seen TelRxCount counting. First value is always 0000 and the 2nd value is 0000 when nothing is selected, and 0101 for the Internal RF, and some other values for the External. Since it is not counting, no need to set up logging? If you do need it, then you'll have to give me a bit more i...

The QX7 ACCESS board appears to be fairly different from the ACCST version. For one, it doesn't have the extra connectors. See picture below. In considering adding the extra switches and pots, erskyTx appears to support several inputs: Switch PB1/2 = JTMS, JTCK, EXT 1, and EXT 2 Pot 3/4 = PC5, PB1 A...

These are the values of rows 3-6 00 00 00 00 00 00 00 00 00 00 7E 10 01 03 00 00 C7 D3 40 02 xxxx 4645 001D 4267 xxxx 0042 On re-power, it DID NOT reboot, and the BOOT REASON is the normal POWER ON. You probably don't need that value on the right since it didn't watchdog, but it's 9062. Also, for wh...

Mike, you are indeed a man of many talents! We appreciate all the work you contribute to this hobby. I am already designing a custom mini PCB for your arduino based SBUS-PWM converter code. So many amazing things have happened in this hobby in the 5 years that I've been out! I've got updates and pro...

Presumably you meant to look at it after trying to bind? Unfortunately (for me), I somehow managed to fry my only D16 receiver this afternoon. Everything else I have is old D8 stuff, so I currently don't have anything that can bind with the X7 Access. I ordered a new receiver but it won't be here ti...

Ok, 5th version bootloader now indicates Version 3.3 and works as you intended, which I think is: Power on with trims inward = Bootloader menu Power on with trims outward = Maintenance menu The EEPROM read/write function with eepSkye also now works, although I've only tried a few items. Obviously th...

Ok, so: Press power switch WHILE holding trims apart = Bootload menu (Flash, App, EEPROM) Hold trims apart AFTER pressing power switch = Maintenance mode I can now load the bootloader via erskyTx from the latest file (4th), but despite that, I STILL see V3.1 on my bootloader menu and still can't rea...

Tested 4th version, no change unfortunately. Still can't read or write EEPROM memory via eePskye and can't bind with Internal RF module in either D16 nor ACCESS mode.

When I select Backup or Restore EEPROM, the respective line just stays highlighted, doing nothing, and I cannot scroll anymore until I hit exit. So I've tested the new version and Switch C is fixed, but I still cannot read the EEPROM to or from the radio properly. Just so I'm not missing anything in...

I flashed the erskyTX bootloader from the x7Acc bin file using the OpenTx SDcard function, then booted into the erskyTX Bootloader (V3.1) to flash the x7Acc bin file. I am still getting familiar with the various USB modes of both FW so hopefully this method works as well. I am definitely running the...

Wow, that was fast! Thanks! Here are my initial observations after 20 minutes of playing around. Please bear in mind that the X7 and erskyTX are new to me so if I made some stupid assumptions, please be kind... 1) Switch C indicates the top and middle position, but does not show the lower position. ...

I just got hold of a Taranis Q X7 ACCESS unit and I see there doesn't seem to be erskyTx support for it yet. I've tried loading the standard X7 ACCST FW, but it just complains about Bad EEprom Data when it starts. When it then goes through the EEPROM Formatting process, the unit just resets and goes...