That’s not ideal. Have you done a capacity check? I still feel you shouldn’t fly it, I’m just curious.
13mOhms at 100A is 1.3W of heat inside the cell. That’s best case, it’s likely to get much worse under load.
At that point the charger was on the discharge cycle, the capacity was declining accordingly. However when I got the battery out of the two LiPo safes I’d put them in over night it was still reading 100%. While there was no loss of capacity over night I’m more concerned about the resistance within the cells, not that one is high, although that’s enough of a worry on it’s own. More about the disparity of the six cells, they’re not even close!
Nothing changed, it’s still going back!
If I hadn’t already decided to return it, that would swing the balance, for sure.
Edit: Ironically, the cells are all about even in volts now, during the discharge cycles
@SimonDale @GVG_Air @Njoro @jpmreece
All, my build still does not ‘See’ the Receiver, which as you know is a major part of getting this thing in the air. I have tries everything I can think of from removing ALL other components from the FC stack, just leaving the PD and FC connected with the Receiver attached. start up and wait…
…nothing receiver still not registering within the FC or BetaFlight! Now bear in mind this is another receiver, not the original. Listed is what I’ve done to resolve this (that I can remember)
Connect with ELRS app to flash - connection failed
remove all other components - failed
Check, double check the wiring - all appears correct
checked ports page of BetaFlight - Serial RX enabled on port 2 - all settings for port left as default
Checked soldering for dry joints, reflowed all to be sure
Any ideas would be greatly appreciated. I’m thinking of the option to delete the config and start again - drastic measures are required!
1 Like
Hi Steve,
Have you tried binding it with a radio before connecting to betaflight?
If it’s failing ELRS flash connection, it’s unlikely it will not connect to anything. I’m on FrSky which requires that the RX is on the same Firmware as the TX.
Have you YouTubed the issue? regarding the fail to connect to the App? Is the App the latest release?
I spent the last three day trying to get my TX to run Lua scripts and getting old I kept missing the common denominator in my attempts. lol.
It eventually dawned on me that every time I deleted the sound pack, it killed a path to ETHOS configurator also YouTube has out of date clips for what I was looking for, a right confusion.
Yes, mate, tried that nothing…
The replacement ELRS module comes with V3.3.0 according to the web page of the online shop.
The TX is RadioMaster TX15 MAX - which is on V3.6.0 EDIT: I’m reluctant to install/flash the TX with an older version - V3.3.0 to match the module
I do suspect the version mismatch has something to do with the issue of the TX/RX not talking/connecting, but with the failure to connect, I’m somewhat at a loss as to how to upgrade/flash the module…
I’m going to search YT for a solution to both issues, they may be one in the same, but I doubt it. The RX Module should be ‘Seen’ in the FC/BetaFlight even if it doesn’t talk/bind to the TX.
Or am I getting things wrong?
1 Like
Use the WiFi method I defined above and set a binding phrase. It should connect.
Other things to note:
If you’re using model match that would cause the effects you are seeing
I’ll have another go after lunch, but have to upgrade the RAM in the wife’s laptop before lunch or I don’t get to eat!!!
In BetaFlight have you set the protocol to CRFS?
Yes, it’s strange that they wouldn’t talk to each other because they’re only a few minor revisions apart. But you have to try the easy options first.
Turn on wifi in the ELRS script, that turns the radio into a wifi hotspot. Connect to that and you should be ready to flash.
But, obviously, you have to do the good hubby bit first, lol.
1 Like
Yep, double checked
WELL! Some measure of success!
Managed to WiFi into the receiver, flashed the latest version/same as the TX V3.6.0
After much trial and error, managed to get the TX/RX to bind!
However, I still cant see the receiver in the FC, thus RX_Failsafe mode is enabled!
Bugger!
Next steps are TBD…
I’m open to suggestions, I did not do a reset, found the ‘Match Model’ option was enabled in some places but not others, corrected and connected.
2 Likes
@SimonDale @GVG_Air @Njoro @jpmreece
Just as a quick update, I’m talking to the supplier support team about the issues with this build. I’ll update again once I get a resolution…
BTW - @SimonDale have you received your components for the 13" build you’re going to do? How’s it doing?
2 Likes