search

FrSkyRC / RF_Feedback_Group

Regarding to the RF issues.
1 stars 0 forks source link

X20R with TD-ISRM 1.1.14 three times same telemetry value and error messages #4

Open glipski50 opened 3 months ago

glipski50 commented 3 months ago

Using X20R with TD-ISRM FW 1.1.4 Ethos 1.5.13 TW R12 with FW 1.0.9 Neuron II 60A with FW 11_5

TW R12 Pin 12 is set to S.Port Yellow wire of the Neuron II (S.Port/FBUS) is connected to Pin 12

In telemetry I get ESC Voltage and ESC Current shown three times as three pairs with three different addresses. All other telemetry values are shown as normal only one time.

screenshot-2024-08-23-82169

the upper pair has address 0D 0B50 the middel pair has address 0A 0B50 the lower pair has adress 17 0B50

the upper pair Voltage / Current and the lower pair Voltage Current frequently get lost and come back. The middle pair is shown constantly like in the examples below. When they disappear or come back it is always as a pair Voltage / Current

screenshot-2024-08-23-82150

screenshot-2024-08-23-82130

That goes along with constant messages Sensor Lost when one pair gets lost or Sensor Conflict when one pair comes back

glipski50 commented 3 months ago

I have done more testing, now with a TWIN X14 transmitter, receiver and ESC as above. With the old TW-ISRM firmware v1.0.6 all telemetry values are shown as normal. I then updated the X14 with TW-ISRM v1.0.7 which should fix

  1. Fixed the issue of the repeat telemetry data of the same sensor source.
  2. Fixed the issue of alarming “Telemetry Lost” while staying in ETHOS’s [Info] tool.

I now have ESC Voltage and ESC Current twice and the same behavior now twice with the adresses

17 0B50 - getting lost and recovered frequently 0A 0B50 - shown stable constantly

Since this time ESC Voltage and ESC Current is shown only twice and not three times as with my X20R as above my theory is that with the latest update of the firmware TW-ISRM for the X14 and TD-ISRM for the X20R the values are transmitted per HF band, three times at the X20R as it has three bands and two times for the X14 as it has two bands.

Reporting this on GitHub may have no sucess as this seems not to be an Ethos issue. How can this bug be reported to the RF team?

glipski50 commented 3 months ago

Here a video https://youtu.be/_ztjJG411Yo?si=QN3Z7KutXEXNb9hy

SmartTommy commented 3 months ago

Hi @glipski50 , i repeated the phenomenon you described if only connect the S.PORT line, could you please try to also connect the PWM/SBUS line to your receiver when you test ?

glipski50 commented 3 months ago

Hi SmartTommy, I connected the PWM line to the throttle pwm out put, deleted all sensors and discovered sensors agin. Now ESC voltage and ESC current are shown correctly only once. But I got one sensor conflict message within 3 minutes, only once, none within the next tem minutes I had the configuration switched on. I only have the Neuron II 60 connected to the TW R12 receiver, no other sensors.

SmartTommy commented 3 months ago

We attempted to reproduce the phenomenon you described, but everything worked properly when connected the throttle pwm to the ESC. do you have anther ESC or can you start the motor to run?

Alex00101 commented 3 months ago

@SmartTommy , I believe this is relates to the below, copy from the Ethos gothub. Please note I have to other telemetry sources rather that standard ArchevPlus SR6 mini

I do believe this is ISRM firmware issue rather than Ethos issue), in any case I'm reporting here as I'm not sure if there is a better register. Updated my X20ProAW with TD-ISRM Pro 1.1.14 and Ethos 1.5.14. On two models where I tested the update the symptoms are consistent. Note that both models have Archer Plus stab receivers (SR8 and SR6 Mini) updated to the latest FW (v1.0.11), new stabs lua 3.0 installed, both receivers reset and recalibrated as per instructions. Both in ACCESS mode.

Shortly after powering up and connection established, started getting "Sensor lost" messages. Went to model telemetry screen and all sensors except the basic (RSSI, RX Batt) - i.e. stab related, such as AccZ, P.angle are red. Deleted and rediscovered the sensors and only got 2 or 3 basic, nothing stab. specific. Tried to open the rx in the lua stab 3.0 script (thought I might need to reset it) - pressing Open caused nothing, i.e the script could not read the rx. cleared the rx in the FR menu, went through re-bind, got all sensors white and active initially but after a short while they all went red and I started getting "Sensor lost" messages again. Downgraded TD-ISRM to 1.1.13 and all symptoms are gone.

Once again I believe this is a serious ISRM firmware issue but this is the only place to raise it that I'm aware.

glipski50 commented 3 months ago

@SmartTommy, I do not have another ESC to test. Also I cannot start the motor since ESC / Motor are not mounted in my model yet. I am still in the process of building up the model. So far I used the ESC Neuron II 60A only to power up the receiver TW R12 and to see telemetry data for voltage and current, specifically BEC of Neuron II, while I am installing the 10 servos wing and tail and testing power current / consumtion load of the servos.

Could you reproduce to get the telemetry data ESC voltage and ESC current three times when the PWM line of the ESC is not connected? As I wrote above in my initial posting why is the ESC voltage and ESC current show three times with three different PhysIDs one time 0D 0B50 unstable display with sensor lost and sensor conflict messages one time 0A 0B50 stable one time 17 0B50 unstable display with sensor lost and sensor conflict messages

I do not know where the Phys ID sensor adresses are generated, ESC, TW R12 or TD-ISRM-Module. Why would the PWM input of the ESC, if connected or not connected, have impact on the telemetry data?

This strange behavior did not happen with the initial TD-ISRM version of my X20R. It only came up after I have updated the TD-ISRM to the new version 1.1.14. Unfortunately I cannot go back to the previous TD-ISRM version since it is not available to download on the Frsky-rc webpage.

I believe that there is an issue with the latest TD-ISRM firmware update. This issue https://github.com/FrSkyRC/RF_Feedback_Group/issues/36 also might be related to the issue I reported.

SmartTommy commented 3 months ago

FW-TD-ISRMPro_v1.1.13.zip here:https://www.frsky-rc.com/tandem-x20-pro-aw/

SmartTommy commented 3 months ago

@SmartTommy, I do not have another ESC to test. Also I cannot start the motor since ESC / Motor are not mounted in my model yet. I am still in the process of building up the model. So far I used the ESC Neuron II 60A only to power up the receiver TW R12 and to see telemetry data for voltage and current, specifically BEC of Neuron II, while I am installing the 10 servos wing and tail and testing power current / consumtion load of the servos.

Could you reproduce to get the telemetry data ESC voltage and ESC current three times when the PWM line of the ESC is not connected? As I wrote above in my initial posting why is the ESC voltage and ESC current show three times with three different PhysIDs one time 0D 0B50 unstable display with sensor lost and sensor conflict messages one time 0A 0B50 stable one time 17 0B50 unstable display with sensor lost and sensor conflict messages

I do not know where the Phys ID sensor adresses are generated, ESC, TW R12 or TD-ISRM-Module. Why would the PWM input of the ESC, if connected or not connected, have impact on the telemetry data?

This strange behavior did not happen with the initial TD-ISRM version of my X20R. It only came up after I have updated the TD-ISRM to the new version 1.1.14. Unfortunately I cannot go back to the previous TD-ISRM version since it is not available to download on the Frsky-rc webpage.

I believe that there is an issue with the latest TD-ISRM firmware update. This issue #36 also might be related to the issue I reported.

The ESC switch between S.PORT/FBUS until find the throttle PWM, so it will report the telemetry randomly.

glipski50 commented 3 months ago

Thanks for the quick response. I will continue later since I am not at home for the next couple of days.

SmartTommy commented 2 months ago

TD-ISRMPro_1.1.15_20240828_Beta.zip

please test this Beta firmware.

glipski50 commented 2 months ago

I will test the betafirmware this weekend

glipski50 commented 2 months ago

I did some tests on the bench with the TD-ISRMPro_1.1.15 beta firmware. There is no more a sensor conflict message at power up of the receiver and no sensor lost message. Telemetry works fine which anyway was a probllem of not having connected the pwm input of the esc.

I assume there will be a ISRM firmwara update in the near future. Should i use the beta firmware for flying or should I wait for the official update?

Thanks for your support

SmartTommy commented 2 months ago

I did some tests on the bench with the TD-ISRMPro_1.1.15 beta firmware. There is no more a sensor conflict message at power up of the receiver and no sensor lost message. Telemetry works fine which anyway was a probllem of not having connected the pwm input of the esc.

I assume there will be a ISRM firmwara update in the near future. Should i use the beta firmware for flying or should I wait for the official update?

Thanks for your support

The release version software need about two week to test.