Please keep in mind for servo you also need to apply 5V to B0, connect the servo to E0
I thought that the power from the USB plug would supply the 5v of the E0.
So, if I power the 5v of the B0 (with the B.EC.), I would have 5v in E0?
I admit that I do not understand well the functioning of the different plug B0/E0 and B1/E1.
For ordinary users, would it be possible to have a small video explaining the interactions between these elements, this could avoid damaging the RX (2 burned with a 5.2 V power supply)
Thank you very much.
It is explained a bit in the schematic
The arrow like symbol is a diode, it will only let electricity through in the arrow direction
As you can see, USB can supply power to the processor, also E0 and B0 can do that, but never back
The idea is:
If the ESC already makes 5V itself (e.g. all VESC) you connect it to E0 and it will power everything
If the ESC does not do that, you also need a BEC that inputs power in B0 and that power is internally forwarded to E0 and the processor
For the B1 and E1 it is the same, it has some isolated electronics that also need an independent power supply.
1 Like
ok for the supply of the servo in B0 and not through the usb port; I understood.
On the other hand, the ESC has battery power so, in principle, we can only connect the black (GND) and white (SIG) wires to port E0 and power the RX via USB; should that work? (tricky question, it doesn’t work with me)
NB: I’m afraid of powering the RX with a source other than USB because I have already burned 2 RX, it’s silly, I know, I won’t take my PC on my tow boogie…
In any case, thank you for the pedagogy
This will only work for E0, not E1
Hello,
This morning, I decided to power the Rx with the BEC.
As a precaution, I measured the output voltage of the BEC, result, 5v on B0 and 5.43 V on B1.
(GND bridge closed)
Is it normal to have 5.43 V in B1, is there a risk of overvoltage for the RX?
Yes that is normal and within the usual limit of +/- 10%
Hello Ludwig,
This means that the short circuits on my first 2 RX are not due to the 5.2 volts of my ESC instead of 5 Volts: correct?
I think it’s the welds of the headers that are causing the problem.
The aspects of the welds are good and there are no weld bridges (checked with a multi-meter).
I noticed short circuits (sparks and fumes) on my first 2 RX and on the BEC.
I am therefore thinking of overheating during welding.
Can this explain the short circuits and the lack of signal sent to the ESC?
Thank you
Not really
Damage this big can only be with voltage that is way too high or incorrect polarity somewhere
Hey together,
I’m currently assembling everything. I’ve already soldered everything, but now I have the problem that nothing happens on the screen when I turn it on.
What could it be and what can I check?
Samuel
Check flex cable, plug in USB once to activate
It still doesn’t work
Check if you can upload firmware or get serial output
Otherwise contact openfoil for replacement
That means Rx firmware is uploaded to a Tx board
Please upload Tx firmware according to the video I made
Sorry, I made a mistake in the line.
I’ve now updated TX again and now it works.
2 Likes
Was just trying to find some information about the progress on that. I am about to assemble my V2 remote and realized I do not have the TX GPS.
I have not followed the development during the winter since I mainly focus on snow activities. But now spring is coming and dreams of water start to flow. My current tow boogie do not yet support steering but I guess any kind of unit that can be steered and the RX can be connected to would work for debugging/developing the Follow Me feature?
Hello,
My bremote is finally operational, the short circuit problems were supposed to be caused by an overly aggressive stripping flow.
A question: how to visualize the battery charge on the remote control screen when I connect the + of the battery to the “Meas UBAT” pin ? i dont see anything.
thank you.
You need to set data_source in Rx confog to analog and num_cells to the amount of cells you have (e.g. 14S pack = set 14)
Then the battery SOC will be in the bottom bargraph
Update:
Logger tested and working fine
As promised, the BREmote V2 Rx has the potential to log data
I have implemented and tested this.
How it works:
- connect BN-220 GPS module to Rx
- connect a VESC via UART
- send the command
?dbit4to enable auto-logging permanently - with
?dbit0you can toggle VESC debug data,?dbit1for GPS and?dbit2for logger debug data - as soon as GPS fix is made, the logger will record data
- when the Rx has no connection to Tx for some time, it will start a WiFi-AP you can log into
- go to 192.168.4.1 and donwload the logs to your phone
Compatible with logtrc
@Kian and his dad made this awesome log viewer you need to check out: LINK
It works with VESC and other log files too, as well as the BREmote logfiles.
Here an example of one of my logs: LINK
All files on GitHub, Rx software V2, so you can simply update without losing any settings. Upload the .ino.bin to 0x10000 like usual.
Download here: LINK
Enjoy and let @Kian and me know your feedback 
3 Likes