History of MembersPage/HankMoody/AIM
Older Newer
2020-05-14 08:49:57 . . . . 188-143-66-163.pool.digikabel.hu [triggerframe notes]
2020-04-30 14:10:11 . . . . leasedline-static-080-228-061-181.ewe-ip-backbone.de [User Question]
2014-02-27 17:57:16 . . . . 195-240-176-40.ip.telfort.nl [removed some outdated info, Race Technology VEMS Ecu interface works]
2014-02-26 15:12:59 . . . . catv-80-98-222-153.catv.broadband.hu [Race Tech can help to configure the receiving side]
2013-03-04 09:45:39 . . . . 188-180-179-186-static.dk.customer.tdc.net [Race Technology reflash added!]
2013-03-04 09:44:42 . . . . 188-180-179-186-static.dk.customer.tdc.net [Race technology reflash provided!]
2013-03-01 18:10:57 . . . . netacc-gpn-5-27-108.pool.telenor.hu [ GPS-SPEED is sent via AIM channel 133 (5+128)]
2013-03-01 17:50:56 . . . . netacc-gpn-5-27-108.pool.telenor.hu [Race-Tech]
2013-02-26 09:47:12 . . . . 188-180-179-186-static.dk.customer.tdc.net [Race Technology interface now working correct!]
2013-02-20 15:38:07 . . . . 188-180-179-186-static.dk.customer.tdc.net [I also see action on channel 133, what is that used for?]
2013-02-20 15:35:52 . . . . 188-180-179-186-static.dk.customer.tdc.net [cleanup]
2013-02-20 14:49:40 . . . . netacc-gpn-4-128-214.pool.telenor.hu [note on channel 224-229.]
2013-02-08 19:42:40 . . . . cpe.ge-1-3-0-179.mdnqu1.dk.customer.tdc.net [v3 output does not match AIM protocol!!!?!]
2013-02-08 15:08:47 . . . . 188-180-179-186-static.dk.customer.tdc.net [v3 output does not match AIM signal!!?]
2013-02-08 15:04:16 . . . . 188-180-179-186-static.dk.customer.tdc.net [v3 output does not correspond to AIM signal?]
2013-02-07 15:30:13 . . . . 188-180-179-186-static.dk.customer.tdc.net [need confirmation about AIM-signal??]
2013-02-06 11:05:13 . . . . 188-180-179-186-static.dk.customer.tdc.net [confirmation that race-technology stuff does not use AIM signal when "working"]
2013-02-05 12:30:10 . . . . catv-80-98-222-153.catv.broadband.hu [Found no Race-tech serial interface that reads aimstream. RaceTech firmware upgr]
2013-02-05 11:58:46 . . . . catv-80-98-222-153.catv.broadband.hu [Race-Tech can likely be firmware upgraded]
2013-02-01 09:03:25 . . . . catv-80-98-222-153.catv.broadband.hu [everything works that reads AIM stream. AIM dash works. Racetech looks confusing]
2013-01-28 18:15:48 . . . . 0x4dd4207a.adsl.cybercity.dk [still need to know which Mo-Tec interface works?]
2013-01-18 09:29:57 . . . . catv-80-98-222-153.catv.broadband.hu [examples show that vems v3 sends RPM correctly in channel1 as in the specs]
2013-01-17 19:44:12 . . . . cpe.ge-1-3-0-179.mdnqu1.dk.customer.tdc.net [added info. further questions regarding RT interface]
2013-01-17 17:32:05 . . . . catv-80-98-222-153.catv.broadband.hu [v3 sends RPM in AIM protocol ch1 as in the protocol, round displays it well]
2013-01-17 08:57:25 . . . . 188-180-179-186-static.dk.customer.tdc.net [added info]
2013-01-16 22:40:32 . . . . PeterJensen [Please add som more data]
2013-01-16 12:58:09 . . . . 0xbcb4b3ba.cpe.ge-1-1-0-1109.hsnqu1.customer.tele.dk [info added]


Changes by last author:

Changed:
loging AIM-Data-Stream from VEMSRound V2
"logging AIM-Data-Stream from VEMSRound V2"
Changed:
i want to log the data comming from my VEMSRounD V2.

i don't have a VEMS-ECU i just bought the VEMSRoundV2 and i like to log both afr and egt values to a storage in my ESP32 driven boardcomputer

I want to log the data comming from my VEMSRounD V2.

* must be a misunderstanding , since VEMS round v2 does NOT output AIM. It understands AIM stream coming from other source, typicelly v3 RS232 or 2nd RS232 see BroadcastDatastreamAim

* I don't have a VEMS-ECU i just bought the VEMSRoundV2 and i like to log both afr and egt values to a storage in my ESP32 driven boardcomputer

Added:

Triggerframe protocol: "Unescape HDLC 7E between frames", 7D 5D => 7D and 7D 5E => 7E check modbus CRC and the bytes are there ("type" is NOT at the beginning, but type is the last byte just before CRC). Sniff some short VemsTune - Round communication to see some valid request response frames:

* 0xA0 short request

* and 0x20 response (with all runtime and analog data)