Hi Jan12,
We’re excited to confirm that this new receiver is currently in the final testing phase . If everything continues to perform as expected, we plan to start production and make it available around November.
As always, we won’t release the product until we’re completely satisfied with its reliability and performance. Once testing is complete, we’ll move directly into production and begin accepting orders.
Stay tuned for more updates.
Jasmin RM
OpenFoil Team
Hi All,
I’m keen to update my rx and tx to the latest version. I’m currently on 2.2.4 and will go to 2.2.6. I don’t do this frequently so forget exactly how to do it. I know that I should use the offset i0x0 for firmware with .merged and 0x10000 for firmware without .merged. Which one allows me to continue to use my existing configuration? I think it is the without .merged one.
Many thanks,
James
Basically always use this for updates
Check this video for the exact steps (39:45 or last chapter)
Easier to download from the releases page, not like shown in the video from the “Source” folder
Hi @ludwig_bre , the updates have worked. Thanks for reminding me of the video.
I downloaded the v2-2.2.8 zipped folder. Inside that the rx bin file is labelled 2.7.1 and the tx bin file is labelled 2.7.2. Is that definitely the latest? Just asking as the file names differ to the folder name.
The key feature I wanted was battery %. Is that a setting I need to now turn on in the c-structure as when I turned on the remote, the battery level display is still the bar running horizontally along the bottom of the display screen.
Thanks,
James
Latest files are:
Yes, you have to select the “speed source” in the Tx config, set to 4
uint16_t speed_src; //0: GPS RX kmh, 1: GPS RX knots, 2: GPS TX kmh, 3: GPS TX knots, 4: Battery %
Great. That is all working now. Thanks.
Is there a reason you keep the non-log version instead of just having one? just because it is less tested?
or is there any practical reason?
I guess because Log Version ist Beta
I want to offer one stable version that everyone can rely on, and the LOG version does not have my full trust yet 
Had some intermittent problems with what I think was a I2C race condition / access problem, probably fixed, but I wanna be certain. Also the LOG version will need some cleaning up.
Hi All,
I am having trouble getting my battery percentage displayed. Occasionally it will read correctly for a few moments, but then always goes back to reading full bars or now with the latest release displaying 99.
When I run ?printBat on the Rx it shows the correct battery voltage. I have put in the battery calibration. My setup is connected as shown for ‘VESC with UART’ with just a single VESC and no GPS.
These are my configurations:
Tx: AgACABQAAQBkACg1yiIcLQ41Yjz0AR4A9AGIE9AHZADoAwoA0AcAAAAACgADAAAAUAAyADIAMgBDrkI5AAAAAAEABAAoAwEAvgSEFVqAAAA=
Rx: AgACABQAAAAyAAAAAADcBdAH3AXQB+gDDAAAAAEAAAACAAAAAAAAAAAAyEEAACBBAAAgQQAAoEAAAAxCAAA0QgAANEJBjhw8AAAAAOgDAAABABVagL4EhA==
Do I have something setup or configured wrong? Thanks.
Assuming you have set the amount of series cells correctly, the error must be with the batcal. Can you also post your batcal string? It will be displayed in the terminal when the receiver reboots.
i am having this issue also.
Encoded Data Read: AgABABQAAQAyAAEAAABMBNAHTATQB+gDDAAAAAAAAAACAAAAAAAAAAAAyEEAACBBAAAgQQAAoEAAAAxCAAA0QgAANEJBjhw8AAAAAOgDAQABAEbOKF14SA==
Struct successfully read from SPIFFS
… Done
Getting bat conf from SPIFFS…
Encoded Data Read: j9zBvbu6ubi3trW1tLOysrGwr66trayqqainpqWko6KhoJ+enZycm5qZmJeVlJOSkZCPjo2Mi4qJiIeGhYSDg4KBgH9+fn18e3p5eHh3dnV0c3Jwb25sa2lnZWJgXVpXU09KRDwz
batcal: noload_offset: 0.29V, 100% rem. @ 4.20V, 0% rem. @ 2.51V.
And what exactly is the problem? Do you experience these problems having the motor run at land without load? Or in the water too?
my issue is on the controller, when not doing anything i see the correct battery SOC, about 10 seconds ish after starting up the motors the displayed SOC will change to 99% and i noticed that through the session this number dropped, at the end of my session the battery was at 20% and when under load this other number read 60% or there about.
i dident see this issue when i was on the land, only when on the water but i was not really looking for it then
will also see if the Rx logger saw anything
What the system does in the background:
Check if you are commanding throttle or not, then add or remove voltage from the actual measurement depending on the configuration you gave it
If it is reading higher than expected you have too much noload-offset
Or chose a battery curve for the wrong current
Which battery curve did you choose? TENPOWER 50ME@10A?
and what setup (s/p) do you have?
Hi, I finished the assembly of the tow boogie but it doesn’t work. I have a ESC and not a VESC (Flipsky FT85BD). Can the remote work with this ESC ? With Flipsky ESC Tool, I can see the motors turning, so wiring is OK… Thanks
Edit : I connected in UART mode, I have to try with PPM
Please check the connection examples on GitHub, from there you will see that only PPM is accepted for throttle. The UART is additional for VESC telemetry
interesting,
my battery setup is 12s10p
My issue is similar to ecpow in that it has read the correct battery percentage for a short amount of time (10-30s) before displaying 99. Mine does not decrease during a riding session, stays at 99 the whole time. The times I have gotten it to display the correct battery percentage have been after I updated the configuration or SW version. I don’t recall if I had pulled the throttle and the displayed changed, I don’t think so, it has always been on dry land when setting up and testing. I can try and recreate it and get a video this weekend.
Info for my battery:
12s14P - Samsung INR 18650-30Q 3000mAh
I used 2A - current per cell and 0 offset for battery voltage, as it matched the measured voltage.
Encoded Data Read: KtzRzs3My8rJycjIyMfHxsbFxcXEw8PCwcC/vry7urm4uLe2tbS0s7KysbCwr66trKyrqqmop6alpKOioaCfnp2cm5qZmJeWlZSTkpGQj46NjIqIh4WDgH58eXd0cm9tamZjXllS
batcal: noload_offset: 0.08V, 100% rem. @ 4.20V, 0% rem. @ 2.82V.
