openrcforums

Did it stay operating all the way from -128 to +127? Usually, you go one way until the Rx stops working, then go the other way until it stops working, and pick the value in the middle of these two positions. This may be what you did, of course. With my AVR module and my STM module, one needs about ...

Well, so far so good and not had any issues with the frsky receiver. Not got any RSSI obviously but everything stays nice and smooth (when the AFHDS2A Rx is playing up the servo movement stutters). I've actually found that the option seems to be spot on set at 0 but I've only done basic range testin...

I think the frsky "V" series receivers do not have telemetry, even if they can be bound in D mode. João Ahh, that's where I was getting confused I think. I read on the spec that it can be bound in V8 mode (non-telemetry) or D mode (telemetry) and assumed it was going to be passing some ba...

Just need to have a read up on the module setting for the receiver I think.
Receiver bound ok but not getting rssi back in D mode which I thought I should be able to.

I'll hang fire for now if you're going to make a modification to the firmware.
I've got an FrSky receiver to test (VF8R-II) that has arrived today so be interesting to get a comparison on how it behaves using another protocol.

You could also try to tune the A7105 frequency for your module and see if it helps. (AFHDS2A is using the A7105 RF component) In the latest multi code and in _config.h, locate the line #define A7105_FREQ_OFFSET 0 Change the offset value and see if it's better, sadly you need to reprogram the module...

Have just ordered a new module so will.do some more testing when that arrives. Went for the new irange-x cased version with usb from banggood this time so no messing with getting the 3d printed case just right this time hopefully. Always possible something went awry with the installation initially a...

It's tempting to order another one to try. Given the chance it could be a build issue on the board or something else unrelated that's made it foul up it makes sense to try and rule it out at least.

I've just posted r221 "g1" test version. This may fix your AFDHS2A telemetry problems. It may fix your link problems! Mike. Flashed and tested. Telemetry now seems fine whether the internal module is on or off - that is all working fine now. I have managed to get a failed link up though (...

OK so tests have been performed and the results are in... still plays up :( Did a methodical test this time so I could record the results. Went through a specific process of Rx on/off, internal on/off etc but have noticed since the changes to f9 the debug screen shows a bit more data so I've recorde...

If you could try the "F9" test version, and also look over on the RCG thread where I posted about a possible problem with the module code. Please check to see if you have "SPORT_POLLING" enabled, and also comment out the line: USART3_BASE->SR &= ~USART_SR_TXE; in telemetry.i...

Doesn't seem to show anything in there. Unless it's just the way the AFHDS2A data stream comes though that it frames ok but the data is duff?

OK, a bit of progress. This is an example of a telemetry packet from your log file: aa f5 00 00 f3 01 fe 00 01 00 fc 00 3c 00 fb 00 64 00 fa 00 28 00 00 01 90 04 ff ff ff ff aa is the start. f5 is the Tx RSSI. Then we have up to 7, 4-byte values: 00 00 f3 01 fe 00 01 00 fc 00 3c 00 fb 00 64 00 fa 0...

Please confirm it is the bottom left figure on the DsmDiag screen that changed to FF04. I'll see if I can do a special test version for you to try to pin down the RxV problem. If you could generate a raw log file when the RxV value is going wrong, I could check to see if it is the received serial d...

Link unstable test done. DSM diag literally had the top left value of 0003 and everything else at 0000. Same when the voltage is going all over the place. However I have just noticed the bottom left figure in the debug screen has gone to FF04. I've tried a few things and it went back to 0000 after a...

Quick update - I have been from T-rate 50 all the way to option 127 and I still get the same effects when the link to the Rx doesn't stabilise. Repairs the link by changing from PWM_IBUS to PWM_SBUS and back.

Still get the random RxV results if I switch off the internal module too.

I can't think of a reason why enabling the internal module should have any effect on the external one. I'm beginning to wonder if your module has a problem, or needs "tuning". When using the FrSky protocols, we generally need to adjust the frequency in the RF chip (in that case by using t...

Well after much searching it seems the firmware for the receivers is very very elusive and the only one I can find is 1.0.6 which is a few years out of date and requires a few more bits to get the update applied. So, if this problem can't be solved with the AFHDS2A receivers I may consider switching...

Finally managed to get it to show some errors in the voltage telemetry long enough to see what the value is so I've got it on video. This was with the internal module disabled with the receiver freshly bound with only the connection to the 4xAA battery pack. https://youtu.be/dzZ-QISYhAY And this was...

OK, according to my i10 there's no upgrade to the two receivers I'm using which means they're at least at firmware version 1.0.8 which is the same as the i10 transmitter. I don't have a way to confirm exactly which firmware they are running though as the only reference I have is whether they will fl...

I'll check the bind options (1-8 and telemetry), these should only be showing if the protocol is XJT! The PWM_IBUS/PWM_SBUS options are just passed to the module, so it seems the module firmware may have a problem. Possibly some timing related to switching from transmit to receive is not quite righ...

Hey, looking into the issue. First the problem with the afhds2a receivers is that they run different firmwares which makes it really difficult. (You can update the RX firmware from the orginal TX). The weird thing I see reported is that it does work/not work by just turning on/off the RX a couple o...

Update... After the 8th power down and re-power of the Rx I had the bad link again. However, as a test I went into the module menu and switched from PWM_IBUS to PWM_SBUS and the link instantly stabilised. Is this a setting that is controlling the module setting or something internal to the Tx firmwa...

So, being as I'm up at stupid o'clock this morning (other half had work) I decided to do a bit more work on the link issues. I've figured out the telemetry stream items thanks to dissecting the code from the multimodule so I now have more of an understanding on that front. The stream seems to come i...

OK so I've been trying to decipher the raw log with a little success. Reason being is it now seems to want to play around with the RxV and it is flipping between the actual voltage (Ext.V if I plug that sensor in) and something around 600 but it flips so quick I can't make anything more out. I've lo...

When the link is not working well, there are many fewer telemetry packets arriving. The status packet (starting with 'M', 0x4D), is sent at regular intervals. You can see many more of these compared to the telemetry packets. A packet with FFs in it simply has no telemetry data to send at that point...

OK, so after a few days away due to the usual Xmas fun and 3D printing a new plane I've got back onto things. Looking at the logs, when the system is working fine it does it's startup then after the initial AA frame entry there seems to be quite a lot of FF filling in the data frames. This doesn't s...

Thanks Mike that's great.
I'll see if I can make head of tail of the logs then and maybe be able to help.out with the diagnosis easier.

To give me a comparison, please create a log file when the telemetry is working OK. Mike. Here's one I just took. Same process though - Power on Tx, start raw logging, power up Rx and allow log to build. Power off Rx then stopped log. Would you be able to give me some pointers on how to read the ra...

I found my voice pack I made was quite low in volume so I downloaded this program... https://neon1.net/prog/normalizer.html And ran it across my wav files and they're now plenty loud enough. I downloaded it and extracted it into my voice pack home directory where the modelNames, system and user dire...