You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isnt an issue with this plugin, more like just some behaviour I noticed. I recorded the can bus using Savvycan and then when I played it back (off the car) it seemed like the adapter wasn't able to handle all the messages being sent and was slowing down/messing up the timings of the frames (when using keep original interval timing between frames option on Savvycan). Could it be due to the plugin or is it the hardware (USB canable dongle) that cant handle it?
The text was updated successfully, but these errors were encountered:
To be honest, I cannot answer the question. I have not tried connecting the adapter to the car CAN network. Actually, STM32F042x/STM32F072xB (ARM Cortex M0-based) are not very powerful microcontrollers. But you can always check this in practice by replacing Savvycan + plugin software with, for example, Cangaroo. You can also try changing the firmware of the CAN adapter to the original one that uses the Lawicel SLCAN protocol and then use the adapter with Savvycan. I provided the links here.
This isnt an issue with this plugin, more like just some behaviour I noticed. I recorded the can bus using Savvycan and then when I played it back (off the car) it seemed like the adapter wasn't able to handle all the messages being sent and was slowing down/messing up the timings of the frames (when using keep original interval timing between frames option on Savvycan). Could it be due to the plugin or is it the hardware (USB canable dongle) that cant handle it?
The text was updated successfully, but these errors were encountered: