Emtron SL4 to PDM30 CAN Messaging

Discussion and support for MoTeC Power Distribution Modules

Emtron SL4 to PDM30 CAN Messaging

Postby impLODE on Tue Feb 28, 2023 2:07 am

I am struggling to figure out the setup required to receive Emtron SL4 ECU data in a PDM30.
I am trying to capture Engine Speed, Engine Temp and Ground Speed for starters.
Would anyone be able to give me some guidance as I cannot figure out if the Bit Masking or Addressing is correct.
I am receiving values in the PDM30 but nothing that looks like the current ecu Engine Temp.
Thanks very much in advance.
Attachments
PDM30-2.jpg
PDM30-2.jpg (495.1 KiB) Viewed 4755 times
PDM30-1.jpg
PDM30-1.jpg (584.37 KiB) Viewed 4755 times
SL4.JPG
SL4.JPG (112.54 KiB) Viewed 4755 times
impLODE
 
Posts: 8
Joined: Sat Jul 06, 2019 3:56 pm

Re: Emtron SL4 to PDM30 CAN Messaging

Postby impLODE on Tue Feb 28, 2023 4:39 pm

*Update*
With these settings on the PDM I am able to see what appears to be Engine Temp values however they are not the same but they move in the same direction.

Increase in temp on the ecu increases the temp value in the Monitor PDM screen.

Strangely, 80 C on the ecu is exactly 80 C in the PDM however the values do not scale in a linear manner lower or higher than this temperature.

This is enough for me just to turn on and off the radiator fans based on conditions I have set on the PDM side but am I supposed to see the same exact temperature values in both the ecu and pdm if I have set this up correctly or is this a normal / acceptable setup to trigger the fan output?
Attachments
PDM30.1.JPG
PDM30.1.JPG (58.75 KiB) Viewed 4735 times
PDM30.JPG
PDM30.JPG (43.38 KiB) Viewed 4735 times
impLODE
 
Posts: 8
Joined: Sat Jul 06, 2019 3:56 pm

Re: Emtron SL4 to PDM30 CAN Messaging

Postby MikeD on Wed Mar 01, 2023 3:31 am

Hi,
your settings are wrong, and you just had some luck that at a specific temperature the actual values correlate with what you get presented in the PDM software.
Talking about engine temperature as an example (read Emtron documentation to find out what I write here):

Emtron values are transmitted as 16bit (unsigned) and little endian byte order (="byte swap" setting), so change those settings on all your signals.

Temperature is transmitted with a resolution of 0.1 deg and an offset of -50 degC.
So the ECU transmits 80 degC on the CAN as 80*10= 800 + offset 500 = 1300 (= the raw digit value that the PDM will read).
Your scaling is "divisor 16" which means 1300 / 16 = 81.25 (so you are calculating wrong but at that moment the luck is on your end... it's obviously not correct but you could leave it like this if thats all you need.)

I would now probably use a divisor of 10 (to get correct degC values but offset by 50 degC) and rename the CAN input like "SL4.Engine.Temp+50°C" if that makes sense for you... it would mean that when you receive said 80°C engine temp then thats a raw value of 1300 and divided by 10 it results in a value of 130 (which is 80°C + 50).
In this way if you ever need another temperature threshold like 85°C then it's still very easy for you to figure out as a PDM value of 135 equals 85°C.

For the following two signals RPM and VEHICLE SPEED first you have to be aware that the PDM can only handle values from 0 - 255.

For engine RPM the divisor of 100 could be reasonable as the PDM can handle values up to 255 resulting in up to 25500 rpm.
Using this divisor 100 brings you "RPM/100" (which I would use as the name for this input) and then 100 rpm = PDM value 1, 200 rpm = 2, 300 rpm = 3... you get the idea...

SPEED is transmitted with a resolution of 0.1 similar to the temperature above, but without an offset, which makes it a bit easier than the temperature from above.
if you use divisor 10 then you will receive your speed in full kph units, but be aware that in case you go faster than 255 kph then the PDM will interprete this wrong, it may start from zero once the overflow happens.
So depending on which systems you want to switch ON/OFF by speed this could lead to terrible misbehaviour in the worst case.
If your car will go faster than 255 then you need to choose a higher divisor, so to not run into trouble.
For example if you choose divisor 20 then it will result in "kph/2", meaning your PDM value of 1 = 2 kph, 2 = 4 kph, 3 = 6 kph and so on... this way you could go up to a PDM value of 255 = 510 kph before the overflow would happen.
If you still go faster than this, ... well... take care then.

Good luck!
Last edited by MikeD on Wed Mar 01, 2023 2:47 pm, edited 1 time in total.
MikeD
 
Posts: 20
Joined: Fri Nov 29, 2019 5:45 am

Re: Emtron SL4 to PDM30 CAN Messaging

Postby Stephen Dean on Wed Mar 01, 2023 8:52 am

Hi Mike,

Thanks for that response.
Stephen Dean
MoTeC Research Centre Melbourne, Australia
User avatar
Stephen Dean
Site Admin
 
Posts: 1614
Joined: Tue Dec 02, 2014 10:29 am
Location: Melbourne

Re: Emtron SL4 to PDM30 CAN Messaging

Postby impLODE on Sat Mar 04, 2023 3:56 pm

Hi MikeD,

Thank you!

I will try with these settings once the car comes back from getting the engine fitted. I really appreciate the insights and your clear examples!

It is an AE86 so we should be able to keep the speed below 255!

Legend!
impLODE
 
Posts: 8
Joined: Sat Jul 06, 2019 3:56 pm


Return to PDM15 PDM16 PDM30 and PDM32

Who is online

Users browsing this forum: No registered users and 3 guests