Yes there is a way to export unencrypted logs. Once you upload your file to the cloud api, you can download it as JSON. I made a fetch interface where you input the upload ID and it returns a response. http://api.wavrx.com/fetch.php?r=c9
I’m going to improve this further in the future as I’m working on an online account system, where you can log in and find/download all your logs.
Still having a tough time getting a consistent connection to the module itself. When saving edits to settings and then going back to main screen it shows disconnected. Once connected again, going to the telemetry page it shows as no module is connected.
This was on V0.06
Just upgraded to V0.07 to check connection stability but now just gotta wait for the TestFlight drop.
On other good and bad news, gps IS detected now but not connected, just continues searching forever.
Meant to type this out earlier but been busy with work!
Can you check with the current TestFlight app? Before that make sure to unpair/forget the module to start a new pairing.
If it’s detected but still searching, it means it still didn’t get a satellite lock, did you try it with the GPS antenna having an open view to the sky?
Actually this is the normal behavior. Whenever settings are changed, the module auto-restarts to make sure the new changes are in effect, resulting in a disconnect.
Seem to have had some trouble updating to 0.07 firmware.
It would not do an OTA update (tried it three times and after downloading and telling me to wait 2-5 minutes it just never progressed.)
I downloaded the bin file to the SD card and the blue light flashed as expected (green light came on on its own without waiting for me to push the button)
Now all I se is this.
Is there a repository of previous firmware updates to try?
This means it did the upgrade successfully, green LED means it connected to your WIFI AP.
Did you unpair/forget the ilogger from the Bluetooth menu before trying to connect? This update brings a major change to the BLE stack, so a re-pairing is necessary.
That appears to have got it connected.
New problem is that it is no longer reporting the VESC firmware version. It just shows up as -1.-1
Are you using CAN or UART port?
CAN.
CAN now requires baud rate to be set to 50k instead of 500k, have you tried changing that yet?
Any other CAN settings need to be adjusted?
Changing the baud rate lets it read the firmware version but it does not appear to read anything else.
Which Vesc are you using and what FW? Also is it a single or dual setup?
Was it working before the update?
Dual cheap focer 2’s FW 5.1
Just getting it fully setup today so I have not previously had it displaying data.
Do you know if they are still using custom firmware on it or is it running the official vesc fw?
Apparently. Should only be related to the drive portion of the controller. Might be worth messaging @shaman if you think that could be causing problems.
Any way to see what the ilogger is seeing over CAN to tell if that is the issue?
Thats a good question, I have that planned for the next version to be able to log and view debug information including CAN messages. I’m going to look over the Github source code and get back to you.
Also it is worth noting that the reason I reduced baud rate to 50k is that the Vesc seems to be having trouble sending over all the requested CAN messages.
What I noticed is that when I request a COMM_GET_VALUES message from the vesc, it should reply with a series of CAN_PACKET_FILL_RX_BUFFER messages that contains the telemetry data, it is divided into multiple messages because it can’t fit into one. Then once all of them are received, there is a final command CAN_PACKET_PROCESS_RX_BUFFER that instructs the iLogger to process the filled buffer.
The issue I’m currently noticing with the Vesc FW is that it does not reliably send those messages and sometimes it is cut short, causing the telemetry data to be truncated.
I have seen other people from other forums reporting the same issue when they were trying to interface the Vesc CAN for other projects.
If someone working with CAN is experiencing the same behavior please let me know, we can probably open an issue and forward it to vedder to check it out.
My current assumption is that the vesc needs some kind of small delay when transmitting consecutive commands like here https://github.com/vedderb/bldc/blob/master/comm_can.c#L330
Rearranged things to give UART a try.
Same behaviour can read the firmware version but nothing when I go to real-time data.
Just to make sure that things are set correctly:
Change port to UART from the settings page.
Make sure that you have swapped RX and TX on the cable (vesc 6 variants have it swapped).
Set UART baud rate to 115200.
For some reason I -still- can’t see the telemetry page. I’ve forgotten the device and repaired it with the code. Have my baudrate for can on 50k and also status message 1. On the settings page it reads that everything is correct but it isn’t so I am confused.
I’ll open enclosure later today and check everything.
Does it show the vesc version on the settings page?
