VERY early days of a new project.
I am entirely new to TuroboLamik.
Currently I have a Mopar BB 440 RB fitted with Edelbrock ProFlo 4 EFI. The transmission is a standard Chrysler TF727.
I want to fit an 8hp70 and use a TurboLamik TCU to control it.
The ProFlo 4 does have a rudimentary Can Bus, the details of which are attached to this post in PDF format.
The Edelbrock ProFlo 4 is not listed in the TurboLamik manual, but I have been told that it could be possible to use it’s data stream.
My question is how to go about making the Standalone Edelbrock ECU comunicate with the TurboLamik TCU and to clarify which data would be useful to the TCU operation. There is no Torque table in the ECU.
Anyone?
Edelbrock Pro Flo 4
Edelbrock Pro Flo 4
- Attachments
-
- Edelbrock ProFlo 4 CAN Data Stream Protocol v2.pdf
- (103.21 KiB) Downloaded 138 times
Re: Edelbrock Pro Flo 4
In your other post the information about RPM, TPS and MAP is all that is needed from the ECU. The TQ values are from the CAL:Press/Torque table in the TCU and are used for shifting (RPM & MAP for its axis). You should be good to go once you get CAN setup. If you have an issue post in the help forum as I don't check here often. If you live near Florida come by the shop or vist VIR, AMP or the TheFirm when we all meet up - stop by.
Re: Edelbrock Pro Flo 4
Thanks for the invite … unfortunately I am in New Zealand.
Any idea what the guys at TurboLamik were referring to when they asked I if the Pro Flo 4 ECU is an “Open Can” device?
Do you think they were asking if the ECU was locked like some OEM ECU’s are or is there some type of “Open Can” protocol?
Any idea what the guys at TurboLamik were referring to when they asked I if the Pro Flo 4 ECU is an “Open Can” device?
Do you think they were asking if the ECU was locked like some OEM ECU’s are or is there some type of “Open Can” protocol?
Last edited by JACB on 04 Jan 2025, 22:44, edited 1 time in total.
Re: Edelbrock Pro Flo 4
He is referring to a device that adheres to a CAN standard and supports higher-layer protocols for data integrity etc.. This ensures that integrating the Proflo with the TCU firmware will remain consistent, even if the Proflo software is updated in future versions.
Re: Edelbrock Pro Flo 4
Thanks M4comp
This is a subject I know nothing about, but I want and need to learn.
Regarding your comments above, what would make a suitable Google search term for me to learn more about higher-layer protocols for data integrity? Previously I searched Google for “Open Can” and you can imagine what I got!
Searching YouTube I came up with this Link: https://youtu.be/k35wlcQs0Qw?si=tNgvwXYyoWZZSe2R but that didn’t help much either.
Do you know if the Pro Flo 4 supports the “Open Can” (or is it “CANopen”) higher-layer protocol?
This is a subject I know nothing about, but I want and need to learn.
Regarding your comments above, what would make a suitable Google search term for me to learn more about higher-layer protocols for data integrity? Previously I searched Google for “Open Can” and you can imagine what I got!
Searching YouTube I came up with this Link: https://youtu.be/k35wlcQs0Qw?si=tNgvwXYyoWZZSe2R but that didn’t help much either.
Do you know if the Pro Flo 4 supports the “Open Can” (or is it “CANopen”) higher-layer protocol?
Re: Edelbrock Pro Flo 4
In my opinion, there's no need to go too deeply into the specifics. There are numerous automotive and on/off-highway CAN standards, with CANopen being more tailored toward automation. The end user only needs to know baud rate, the ID and byte locations and the firmware handles it for you.
Instead, I suggest focusing your time on exploring the parameter tree in TunerPro, particularly Torque Calculation. Once you're familiar with that, move on to RPM Limit -> Automatic Settings & Lockup Settings to understand shift and lockup points. ZeroTo60 has a few youtube videos that cover torque you should watch.
Within the CAN parameter tree:
CAN 1: This is used for the shifter, provided it operates on CAN. If analog it will be setup under Analog further up in the parameter tree.
CAN 2: This handles engine data, specifically Custom CAN RX, which is where the CAN information from your other post will come into play.
Instead, I suggest focusing your time on exploring the parameter tree in TunerPro, particularly Torque Calculation. Once you're familiar with that, move on to RPM Limit -> Automatic Settings & Lockup Settings to understand shift and lockup points. ZeroTo60 has a few youtube videos that cover torque you should watch.
Within the CAN parameter tree:
CAN 1: This is used for the shifter, provided it operates on CAN. If analog it will be setup under Analog further up in the parameter tree.
CAN 2: This handles engine data, specifically Custom CAN RX, which is where the CAN information from your other post will come into play.
Re: Edelbrock Pro Flo 4
Thanks again .. But you are slightly missing my point. At the moment I own an Edelbrock ProFlo 4 ECU which is fitted to my car. I do not yet own a TurboLamik TCU. As previously stated, this is the research stage of a new project. So before purchase, I want to be certain that the two devices are compatible and will pair.
I looked in the Turbolamik manual and could see that only selectable, preconfigured Stand-Alone controllers are:
Ecumaster EMU & EMU BLACK & EMU PRO
Megasquirt
AEM
Motec M1
Haltech
Link G4X
Holley EFI
Vems
Delta ECU
Syvecs S7-1 and S7Plus
MaxxECU
No - Edelbrock ProFlo 4
I wrote to TurboLamik EU. I sent the Edelbrock Protocol information (see the first post above) and asked can the TurboLamik TCU work with the Edelbrock Data Stream? If so how do I add the Edelbrock ProFlo 4, to the above list or go about setting up the communications manually? I got a reply saying, “it should work”, is the Edelbrock device OPENcan? I havnt been able to answer their question.
So I have the information about the Edelbrock device (where it talked about a “validated DBC file”, if that helps?) and I can see in the TurboLamik receiving protocol requirements in the TCU manual under CAN Communication/Read.
But I am still no closer to understanding how, I would setup TunerPro software to receive the Edelbrock data stream, than when I started.
Can I have some specific instructions how to do this and how would I go about adding the Edelbrock ProFlo 4 to the list of Stand Alone ECU’s, for those that follow in my footsteps? I believe we are talking about the CAN 2 setup process.
I looked in the Turbolamik manual and could see that only selectable, preconfigured Stand-Alone controllers are:
Ecumaster EMU & EMU BLACK & EMU PRO
Megasquirt
AEM
Motec M1
Haltech
Link G4X
Holley EFI
Vems
Delta ECU
Syvecs S7-1 and S7Plus
MaxxECU
No - Edelbrock ProFlo 4
I wrote to TurboLamik EU. I sent the Edelbrock Protocol information (see the first post above) and asked can the TurboLamik TCU work with the Edelbrock Data Stream? If so how do I add the Edelbrock ProFlo 4, to the above list or go about setting up the communications manually? I got a reply saying, “it should work”, is the Edelbrock device OPENcan? I havnt been able to answer their question.
So I have the information about the Edelbrock device (where it talked about a “validated DBC file”, if that helps?) and I can see in the TurboLamik receiving protocol requirements in the TCU manual under CAN Communication/Read.
But I am still no closer to understanding how, I would setup TunerPro software to receive the Edelbrock data stream, than when I started.
Can I have some specific instructions how to do this and how would I go about adding the Edelbrock ProFlo 4 to the list of Stand Alone ECU’s, for those that follow in my footsteps? I believe we are talking about the CAN 2 setup process.
Re: Edelbrock Pro Flo 4
The information you provided in the PDF about Proflo's CAN structure is all that is required. Of course the TCU wired up as well. The preconfigured ECU's you listed just skips the part where the user sets up the CAN themselves. OR if the needed channels are spread apart and need 2 or more CAN id's to get the needed data to the TCU. In your case everything we need is on one single can ID (300) so a custom CAN setup will work.
Address 300 (Which is the CAN ID) provides you with 8 bytes of data, you will use 5 of those bytes.
RPM which uses 2 bytes
Throttle Position 1 byte
Manifold pressure 2 bytes
You would enter your CAN id in the turbolamik TCU software and for each of those named channels enter their byte location + multiplier and offset. Multipliers and offsets just scale the data to fit in the byte(s) and not 'spill out of' their maximum value each byte is capable of.
For example
1st. The ECU ID you would enter would be 864 (I'm assuming that 300 is in hex from the PDF). If it's in decimal you would just put 300.
2nd. RPM byte position put 0, this one is confusing due to the PDF showing 1-8 but the TCU uses 0-7 for the same 8 positions just decreased by 1.
3rd. Set TPS byte position 4, same thing here TCU uses 0-7 for byte position. Also put 0.392157 for TPS multiplier and 0 for your TPS offset.
4th. Set MAP byte position 5, same thing here TCU uses 0-7 for byte position. Also put 1.0 for MAP multiplier and 0 for your MAP offset.
5th. Then in the TCU, connect and enable live data and confirm your RPM, TPS and MAP = what the ECU shows.
Address 300 (Which is the CAN ID) provides you with 8 bytes of data, you will use 5 of those bytes.
RPM which uses 2 bytes
Throttle Position 1 byte
Manifold pressure 2 bytes
You would enter your CAN id in the turbolamik TCU software and for each of those named channels enter their byte location + multiplier and offset. Multipliers and offsets just scale the data to fit in the byte(s) and not 'spill out of' their maximum value each byte is capable of.
For example
1st. The ECU ID you would enter would be 864 (I'm assuming that 300 is in hex from the PDF). If it's in decimal you would just put 300.
2nd. RPM byte position put 0, this one is confusing due to the PDF showing 1-8 but the TCU uses 0-7 for the same 8 positions just decreased by 1.
3rd. Set TPS byte position 4, same thing here TCU uses 0-7 for byte position. Also put 0.392157 for TPS multiplier and 0 for your TPS offset.
4th. Set MAP byte position 5, same thing here TCU uses 0-7 for byte position. Also put 1.0 for MAP multiplier and 0 for your MAP offset.
5th. Then in the TCU, connect and enable live data and confirm your RPM, TPS and MAP = what the ECU shows.
Re: Edelbrock Pro Flo 4
THANK YOU M4comp
That is exactly what I was hoping to find.
Would it now be possible for you/TurboLamik to add that “Edelbrock ProFlo 4” configuration to the list of Stand Alone ECU’s?
Those that follow in our footsteps would greatly appreciate it.
I will have to work out where the Edelbrock wiring enters the TurboLamik TCU & consider if there will be any termination issues, I dare say that it’s all in the manual. I need to do a little more reading.
That is exactly what I was hoping to find.
Would it now be possible for you/TurboLamik to add that “Edelbrock ProFlo 4” configuration to the list of Stand Alone ECU’s?
Those that follow in our footsteps would greatly appreciate it.
I will have to work out where the Edelbrock wiring enters the TurboLamik TCU & consider if there will be any termination issues, I dare say that it’s all in the manual. I need to do a little more reading.