History of MembersPage/Kamuto/AimtoCan
Older Newer
2023-06-23 21:03:03 . . . . 88.119.113.145 [info for my friend Dave]
2022-07-08 14:39:02 . . . . 86.38.152.111 [mazda can stream]
2017-08-11 04:41:58 . . . . 93.190.5.121 [minor: formatting]
2017-08-07 20:13:48 . . . . 185.154.38.86.mobile.mezon.lt [final]
2017-07-03 11:18:17 . . . . 19.222.38.86.static.lrtc.lt [thanks]
2017-07-03 11:01:54 . . . . static.kpn.net [pointed to AIM CAN message format, annotated id assignment]
2017-07-03 10:11:49 . . . . 88.119.113.145 [question]
2017-07-03 06:47:51 . . . . catv-80-98-142-196.catv.broadband.hu [CAN notes]
2017-07-02 11:07:42 . . . . 88.119.113.145 [question]


Changes by last author:

Added:

------

hello, lately I have an issue with external devices when working with vems, dash pdm has can bus but vems has only one way can, so I cant get any data to vems from can bus, I have a simple but very efficient request to sort this integration nightmare, as we know aim2can can send physical analog inputs to vems. I need an override for it. lets say, if aim2can device see ID 0x640 on can bus it stops sending first 4 actual physical analog inputs and replaces them with can bus data received on 0x640 or 0x641 that way it would be possible to get analog inputs, switches or any other stuff to vems over can bus from other devices and that means that it would be possible to control boost from keypads, or antilag or any other stuff could be controled over can bus. it would be kinda modern ecu, cause it's now really really lacking in this departament.

so, 0x640 on can bus stops broadcasting first 4 aim2can analogs to vems and replaces them by 4 16 bit big endian values from that can ID

0x641 would do next 4, and that's all I need I guess.

thank you.

-------