You are here

Data logging for dual VESC on Android VESC-tool

5 posts / 0 new
Last post
elmardus
Offline
Last seen: 3 months 2 weeks ago
VESC Free
Joined: 2020-05-11 11:07
Posts: 3
Data logging for dual VESC on Android VESC-tool

I am using VESC Tool 3.00 on Android to connect over bluetooth. My board is running a dual vesc setup (connected over CAN) with a Flipsky NRF51 bluetooth module connected to the slave VESC.

However I am unable to get logging data from both VESCs. When enabling 'RT data logging' in the developer settings, the resulting CSV file only contains data from the slave VESC. Is it possible to log data for both VESCs?

frank
Offline
Last seen: 5 hours 10 min ago
VESC BronzeVESC FreeVESC GoldVESC OriginalVESC Silver
Joined: 2016-12-27 20:19
Posts: 802

It needs to sit on the master side. Not all data from the slave is logged.

elmardus
Offline
Last seen: 3 months 2 weeks ago
VESC Free
Joined: 2020-05-11 11:07
Posts: 3

So if I understand correctly, the data from the slave is passed through to the master? For some reason flipsky recommends that the module is connected to the slave:

https://flipsky.net/blogs/vesc-tool/having-trouble-using-flipsky-bluetooth

Notes:

  • If you’re using a Dual ESC, we suggest you plug in bluetooth module on the slave side that you set.

Not sure why they recommend this though...

 

EDIT:

I've just driven with the bluetooth module connected to the master VESC, and the result is still the same. For example, the Ah used total is still only for one VESC.

frank
Offline
Last seen: 5 hours 10 min ago
VESC BronzeVESC FreeVESC GoldVESC OriginalVESC Silver
Joined: 2016-12-27 20:19
Posts: 802

I guess you have to ask Flipsky support. Their product, their customer support duty.

elmardus
Offline
Last seen: 3 months 2 weeks ago
VESC Free
Joined: 2020-05-11 11:07
Posts: 3

I can try to ask, but this behaviour is 100% controlled by the VESC firmware and VESC-tool software, the flipsky module is only a specific hardware implementation of the NRF51 bluetooth chip.