History of MembersPage/HankMoody/CAN
Older Newer
2026-08-11 01:16:27 . . . . 152.115.183.206 [Solved... kind of...]
2026-08-08 15:13:33 . . . . 89.239.208.134.dhcp.fibianet.dk [Problem with CAN_Dash adapter]
2026-08-08 02:17:51 . . . . 89.239.208.134.dhcp.fibianet.dk [Problem with CAN_Dash adapter]
2026-08-07 03:59:19 . . . . 89.239.208.134.dhcp.fibianet.dk [Problem with CAN_Dash adapter]
2026-08-06 03:25:06 . . . . 89.239.208.134.dhcp.fibianet.dk [Added info]


Changes by last author:

Changed:
I just cannot read the CAN-ID's from the AiM2CAN adapter. Does anyone have an actual dump of the CAN Data from the Aim2Can Adappter, or do I need to buy a CAN logger/sniffer to get this working?
I just cannot read the CAN-ID's from the AiM2CAN adapter. Does anyone have an actual dump of the CAN Data from the Aim2Can Adapter, or do I need to buy a CAN logger/sniffer to get this working?
Added:

EDIT:

I got this working.

The issue is that the Aim2Can adapter somehow communicate with the V3 and this stops the AiM stream, from the V3. So, the sollution for me was to only connect the RS232-TX from the v3 and not the RS232-RX. This prevents the adapter from stopping the AiM stream.

Another issue is with the DBC file published here:

https://www.vems.hu/wiki/index.php?page=AimCanBusMessages

It's not working.

My findings so far: The CAN ID's are correct, however the protocol is BIG-ENDIAN byte order and not Little Endian.

I will post my DBC, once everything is setup correctly.