search

betaflight / betaflight-tx-lua-scripts

Collection of scripts to configure Betaflight from your TX (currently only supported in OpenTx)
GNU General Public License v3.0
604 stars 142 forks source link

Empty PWM page #157

Closed simogere closed 6 years ago

simogere commented 6 years ago

FC: Airbot Fireworks V2 (with Betaflight 3.4.1) RX: FrSky R9 Mini (with last firmware) Radio: FrSky Taranis Q X7 (with OpenTx 2.2.2)

Lua and luac enabled. I can manage all the screens of the lua script excepting the PWM page that is empty. With last Butterflight release, the PWM page works.

mikeller commented 6 years ago

@simogere: Can you try again with Betaflight 3.5.0?

simogere commented 6 years ago

Tried, but no values again. If possible let's focus to 3.4. 3.5 is not good enought for my quads. Hope you understand. Is there any code patch I could try?

mikeller commented 6 years ago

No. And development on 3.4 has finished, so there will be no more fixes for it. We have only so much free time to invest in developing this, I hope you understand.

simogere commented 6 years ago

Ok. Anyway, it sounds strange it's affecting only me and on butterflight works like a charm

simogere commented 6 years ago

Hi @mikeller, which version should I try with betafligh 3.5?

mikeller commented 6 years ago

@simogere: Yes please - 3.5 is the current release, and if there is a bug in it it will be fixed.

simogere commented 6 years ago

Ok, but which release should I use? 1.0.2?

mikeller commented 6 years ago

Yes, 1.0.2 should work.

RipperDrone commented 6 years ago

empty PWM page on FPORT+R-XSR was fixed with firmware 1800827_Beta from FrSky, however this version had timing issues on Omnibus F4 target (EMAX F4 Magnum Mini v2). Therefore it's a catch 22!

It seems that with the older firmware 180615_Beta, PWM page is not shown but 'sensor lost' issue shows up. Older firmware had issues with bytestuffing, see https://github.com/betaflight/betaflight-tx-lua-scripts/issues/151

mikeller commented 6 years ago

@RipperDrone:

Can you supply more information about the timing issue please, so we can look into fixing it?

RipperDrone commented 6 years ago

@mikeller - I was just able to narrow it down to a point that the new 180827 firmware seems to be running fine on an Omibus F4SD, including showing the PWM page properly. I think somebody had the suspicion that bad bytestuffing in the previous firmwares <=180615 might have lead to the whole PWM page not being shown once there is a 125 or 126 data value entry on it somewhere (not sure in which fields there should be such values, though...)

On an Omnibus F4 (EMAX Magnum F4 v2), though, the 180827 firmware does not work properly. But this time it's not about showing or not showing the PWM page, now it's timing issues with FPORT telemetry:

When I watch the asterisks on my Taranis indicating sensor values coming in, there are a few fast blinking values like RSSI and RxBat. Other values seem to get updates a lot more slowly, like once in 1-2 seconds. When continuing to run the radio connection, updates come in more and more slowly, up to a point that the RC times out and throws a 'sensor lost' message. Sometimes it recovers, but after ~1min the data connection seems so fragmented that for some sensors, they don't come through at all anymore and blink on the RC's telemetry screen (=dead). CPU usage (which I suspected first) is at 8% only, I tried both 8k/8k and 4k/4k, no change. I deleted all but 6 sensors on the Taranis, but still the same phaenomenon persists.

Particularly VFAS, A4, Hdg and Accx/y/z seem to be dying first, RSSI+RxBat seem to survive a little longer.

I have connected the FPORT pin of the R-XSR to the B10/TX3 pin of the MCU since there were no more free external pins to access. TX6 is hard connected to the backpack VTX for SmartAudio, UART1 is free - supposed for SBUS/SPEKTRUM connections. So unfortunately I cannot easily rewire the connections to try out another free UART on this stack.

However, once flashing the R-XSR back to 180615 firmware, all timing issues are gone - frequent updates on all sensors whatsoever, no 'sensor lost' messages anymore. Only little drawback is the missing entries/values on the Lua PWM page.

What else could I do to help diagnose...?

mikeller commented 6 years ago

@RipperDrone: What firmware version are you running on the OMNIBUSF4 that is showing this problem?

RipperDrone commented 6 years ago

@mikeller 4.0 #1091

mikeller commented 6 years ago

@RipperDrone: Ok, this is odd - I can't quite see what's going wrong there.

RipperDrone commented 6 years ago

@mikeller yeah, strange indeed. New R-XSR FW seems to be an improvement on most FCs, so maybe this is a very special case. I will go with the old FW for now, accepting the missing PWM Lua page. Over time, we'll see whether or not there are other reports about timing issues on some targets...

@simogere How is progress on your end?

klutvott123 commented 6 years ago

@RipperDrone do this: https://github.com/betaflight/betaflight-tx-lua-scripts/issues/151#issuecomment-413305190

Still any combination of values that makes the CRC 125 or 126 will make it stop working again.

fanderko commented 6 years ago

Hi, the same problem here. FC: Omnibus F4 V3 PRO OSD (omnibusf4sd) betaflight 3.5.1 RX: FrSky R9 Mini TX: FrSky Taranis Q X7 (with OpenTx 2.2.2) Only PWM page is blank.

chadmbrown commented 6 years ago

Hi, the same problem here. FC: Kakute F4v2 betaflight 3.5.1 RX: R-XSR FPORT: R-XSR_FPORT_FCC180615_Beta TX: FrSky Taranis Q X7S (with OpenTx 2.2.2)

Only PWM page is blank. Everything else works great.

klutvott123 commented 6 years ago

@chadmbrown it's a rx firmware issue. Try the new 180827 beta firmware from frskys website.

@fanderko rx firmware issue for you too. Frsky haven't released a fix for the R9 mini yet. "set gyro_calib_duration = 128" in CLI should bring the PWM page back, but doesn't fix the issue.

chadmbrown commented 6 years ago

Thanks. That fixed it. Didn’t notice the second beta directory. I thought I had the latest.

Chad

From: Hans Christian Olaussen notifications@github.com Sent: Wednesday, September 26, 2018 5:41 PM To: betaflight/betaflight-tx-lua-scripts Cc: Chad Brown; Mention Subject: Re: [betaflight/betaflight-tx-lua-scripts] Empty PWM page (#157)

@chadmbrownhttps://github.com/chadmbrown it's a rx firmware issue. Try the new 180827 beta firmware from frskys website.

@fanderkohttps://github.com/fanderko rx firmware issue for you too. Frsky haven't released a fix for the R9 mini yet. "set gyro_calib_duration = 128" in CLI should bring the PWM page back, but doesn't fix the issue.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/betaflight/betaflight-tx-lua-scripts/issues/157#issuecomment-424916995, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ApmtqPGe_1CskIkkTl0JOCEbpeZa-BrXks5ufB67gaJpZM4WFZw8.

stale[bot] commented 6 years ago

This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

stale[bot] commented 6 years ago

Automatically closing as inactive.