There were '85 Escorts with ABS???

--Ian

 

oops 95 and yes ABS was optional they were also powerd by 1.8l Mazda BP motors.in the GT version 1991-1996.

 

Ok so I have it all installed and working. I'm trying to get the speeds to transmit over CAN to the Syvecs ECU. I spoke to Syvecs and as they have experience with the e46 m3 and said the ABS should be sending out the speeds on the 1f0 frame but im not getting anything. Im sure I read somewhere on here that the ABS needed to see communication with the clocks for it to transmit the CAN data. Anyone have any information on that or any other reason Im not getting anything.?

 

This is a neat find, I'm still on the hunt for a 1" master though.

Interested to see what kinda bracket you made to mount in that location.

 

Does the Syvecs have a native configuration for the hex output? I would imagine you still would need to configure the CAN protocol in the ECU first to establish a "handshake" if you will.

If the ABS pump has power, you can hook up to INPA to see if there are any errors that would be blocking the data transmission. I'm not sure if you can view CAN signals in INPA or not.

 

As mentioned on the Facebook group, without the rest of the E46 CAN bus, you're going to need to do more work to get the data out. I do not have personal experience with this, but I do recall some options:

1) you can reset the module over the K-line and it may start transmitting on the CAN bus. Exact steps unknown.
2) if something on your CAN bus can send messages at startup, there's a sequence you can use to start the data flow. I believe there's a .lua script in the RaceCapture source code that does this.
3) I think it's the E46 gauge cluster, but I might be wrong - if you put that on your CAN bus, probably with the matching VIN applied, you might get the data you need.

Short version, the reason Syvecs thinks you should be getting the data out is probably because they're assuming you have the rest of the E46 in place.

 

Anyone know the PN for either of these covers, the numbers on them do not correspond to a usable part number.

 

I am in the process of putting a mk60 in my 944T track car. I have a MS3PRO Ultimate ecu. I have it all plumbed up and just ran a second brake line for the rear. I am using a manual dual master 3/4"/13/16" masters with a bias bar.

Has anyone used the 4 outputs of the MK60 plug for the wheel speed inputs? Or only the CAN-BUS wires? If using the CAN-BUS, I read no resistor is needed? What are the settings needed for the MS and to use TC?


Also, I bought a few extra setups from the UK of the m12 banjo fittings with a 3AN top bolt for the tidy pressure sender hookup is anybody is interested in them.

Thanks,
Pete

 

I have it working, using the digital inputs to a micro squirt IO expander which communicates with the main MS3. I wanted flex so I didn't have enough high speed inputs left to do it directly to the MS3. You have to be careful most of the digital inputs top out at too low of a frequency to work with 41 pulses per revolutrevolution. Traction control is working great

I've not heard of anyone getting the mk60 can bus to work directly without the $1500 motorsports tune. Evidently they turn off the can bus stream when they can't talk to the bmw dash and ECM.

 

Well that is unfortunate. Now for a lightening round of questions.

What do you mean by "digital inputs top out at too low of a frequency to work with 41 pulses per revolution" How did you work around that? My 944 has 45 teeth- does that help?

I have at least 4 digital inputs not being used, on the ms3pro/ult black plug pins 5,6,13,14 are open. I am not sure the wiring needed for it. Each wheel speed sensor has 2 wires. I would assume I would attach each wheel sensor [mk60 pins 33,37,42,46] to these? Is a resistor needed? If so, how is it hooked up?

I plan on hooking up TC on/off with a potentiometer. Is that how yours is hooked up?

Thanks
Pete

 

Most digital inputs are only good for 1000hz or is it 100? At any rate at about 35mph they stop working. High speed inputs such as pt4 and flex can take the number of pulses to 160mph+........ Fast as I've been.

I just tune the % slip in TS and don't use a ****, 6-8% works well for me

 

Funny this should come up today.

I've had some time on my hands, so I used an Arduino I've had kicking around for years to tickle the MK60 into transmitting the wheel speed messages.

I'm not ready to call it done, or support n00bs in downloading, compiling, and uploading firmware, but if you've got some time, this might be helpful:

MK60 CAN tool

You'll need an Adafruit Feather, link in the README.

 

Can you confirm the data HZ it's transmitted at?

 

I have not yet, but it's easy enough, I can look into this.

MS4X Wiki says the message is sent either 1/10ms or 1/20ms.... so 50-100 times per second

 

E/ didn't realize this was already covered, mobile hadn't loaded the next page for me...

 

I'm seeing 142 wheel speed messages per second from the MK60. Each message contains all four wheel speeds.

That said, I'm starting to think we're not speaking of the same update rates.

What I'm doing is tricking the MK60 into publishing the wheel speed message onto its CAN bus. This is a pure "data" solution, nothing to do with the wheel speed outputs on the 47-pin connector.

Is this fast enough to do traction control? I dunno. From looking at the other messages, I think the intention is for the MK60 to request torque reduction from the ECU. I haven't seen those messages on the bus yet and I'm not sure what it takes to get them flowing.

 

I'm not sure how the wheel speeds over can bus has nothing to do with the wheel speeds. It is or isn't how fast each tire is turning.

~120hz should be enough, I'm technically using a micro squirt to convert the pulses to can bus

 

Which pin of the sensor is v+ and signal? There is a extra line of plastic on one side when looking at it.

Thanks

 

Ah, now I understand. Nomenclature issue. Or maybe just my pea-sized brain issue.

Hertz in my mind is cycles-per-second.

CAN bus messages, in my mind, are sent at intervals. They're not a "cycle" to me.

Triggers are read in pulses per second. To me, they're not a "cycle" either, but that's just my biased thinking. You could make an argument that they're just a frequency modulated signal that can be represented in hertz and I'd have to agree, but that's not my preference.

Basically, I'm not an EE, but I know enough to be dangerous. What little I know started from getting a Ham license back in the day, but now I work with embedded systems and digital logic, so most of my thinking is in milliseconds. I'm not actually even an embedded engineer, but again, enough to be dangerous.

 

I figure this may help someone else with their wiring.