AEMNet Connections Other Than EGO?
#1
AEMNet Connections Other Than EGO?
I've recently installed a nice CAN wiring harness in my 95' with an MSLabs MS3 basic. I am in the process of wiring a new AEM X-Series WBO2 (30-0300) which is fairly straightforward. However, I now know that I can no longer use the Megasquirt's usual CAN protocol along with AEMNet. I began delving into which other AEMNet devices may be compatible and useful and came up with this short list:
1. AEM Vehicle Dynamics Module (30-2206): Really impressive set of GPS/Time/Accelerometer/Gyroscope features. Really an AIO for all of that stuff.
2. AEM CD7 Digital Dash (30-5700): Nice digital dash. I would never personally install, but curious as to whether MS3x can broadcast data in the AEMNet format?
3. AEM X-Series Boost Gauge (30-0306) and other AEMNet enabled gauges in general: Firstly, is 1kpa of scaling sufficient to act as a MAP input? Secondly, can the MS3 receive AEMNet broadcasts from devices other than the 30-0300?
4. AEM Sensor Expansion Boards: As above, can the MS3x read, say, oil pressure, oil temp, ethanol content, etc from CAN?
Now, I understand that 11-bit CAN broadcasting can still be used with AEMNet devices attached, just not the 29-bit extended message headers. I also understand that the MegaSquirt CAN protocol is unique in that it does not support broadcasting, only the poll/response style of messages. I have yet to peer into the 1.5.x firmware code (I assume this is not even available? No idea with the license/development scheme for it is...) for the AEMNet features, but given that there are little to no configurations for AEMNet stuff, I presume that it is hard-coded such that if EGO is set to use CAN EGO and Fetch EGO Data is set to the AEM X UEGO setting, a custom implementation of the AEMNet protocol receives data via CAN and handles it. If this is indeed the case, then would it be possible to update the code to include receiving capabilities for various AEMNet devices?
1. AEM Vehicle Dynamics Module (30-2206): Really impressive set of GPS/Time/Accelerometer/Gyroscope features. Really an AIO for all of that stuff.
2. AEM CD7 Digital Dash (30-5700): Nice digital dash. I would never personally install, but curious as to whether MS3x can broadcast data in the AEMNet format?
3. AEM X-Series Boost Gauge (30-0306) and other AEMNet enabled gauges in general: Firstly, is 1kpa of scaling sufficient to act as a MAP input? Secondly, can the MS3 receive AEMNet broadcasts from devices other than the 30-0300?
4. AEM Sensor Expansion Boards: As above, can the MS3x read, say, oil pressure, oil temp, ethanol content, etc from CAN?
Now, I understand that 11-bit CAN broadcasting can still be used with AEMNet devices attached, just not the 29-bit extended message headers. I also understand that the MegaSquirt CAN protocol is unique in that it does not support broadcasting, only the poll/response style of messages. I have yet to peer into the 1.5.x firmware code (I assume this is not even available? No idea with the license/development scheme for it is...) for the AEMNet features, but given that there are little to no configurations for AEMNet stuff, I presume that it is hard-coded such that if EGO is set to use CAN EGO and Fetch EGO Data is set to the AEM X UEGO setting, a custom implementation of the AEMNet protocol receives data via CAN and handles it. If this is indeed the case, then would it be possible to update the code to include receiving capabilities for various AEMNet devices?
#2
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,979
Total Cats: 356
2) The CD7 can be configured to receive normal 11bit CAN data, ie it is compatible with everything if you program it.
3) No, 1kPa is not enough, you need at least 0.5kPa steps. On top of that, the frequency of the messages is even more important. At 100Hz max, it is slow for a MAP input
4) Yes since you can set the CAN receiving mode to receive 29bit CAN messages. Familiarity with CAN messages required.
3) No, 1kPa is not enough, you need at least 0.5kPa steps. On top of that, the frequency of the messages is even more important. At 100Hz max, it is slow for a MAP input
4) Yes since you can set the CAN receiving mode to receive 29bit CAN messages. Familiarity with CAN messages required.
#3
2) The CD7 can be configured to receive normal 11bit CAN data, ie it is compatible with everything if you program it.
3) No, 1kPa is not enough, you need at least 0.5kPa steps. On top of that, the frequency of the messages is even more important. At 100Hz max, it is slow for a MAP input
4) Yes since you can set the CAN receiving mode to receive 29bit CAN messages. Familiarity with CAN messages required.
3) No, 1kPa is not enough, you need at least 0.5kPa steps. On top of that, the frequency of the messages is even more important. At 100Hz max, it is slow for a MAP input
4) Yes since you can set the CAN receiving mode to receive 29bit CAN messages. Familiarity with CAN messages required.
#4
@Reverant another question that has popped up: is it possible to remove the 120u resistor built into the MS3? I’d like to have the ECU act as a stub in the middle of the bus so that I can have one end of the bus in the engine bay and the other in the dash, but that only works if I can remove the resistor and stub out the ECUs CANH/CANL.
#6
Thanks Rev, makes sense. For 4, I have already attempted to configure custom 29bit CAN receiving of a few AEMNet CAN devices, hopefully differences in the protocols does not cause issues. I’ll be reading through the protocols in detail soon. Also, I should be able to run 500hz CAN with AEMNet.
Thread
Thread Starter
Forum
Replies
Last Post