Page 1 of 3

M84

PostPosted: Tue Nov 09, 2010 1:47 pm
by Merlin
Great job guys ...this is a great addition to your systems

However I cannot see any CAN or RS232 set up page ....I have a few circut cars I would be fit them to that would need one or the other ??


John P

Re: M84

PostPosted: Tue Nov 09, 2010 4:19 pm
by MarkMc
Hi Merlin,
The basics are the M84 will send out a specific CAN data set which is suitable for the MDD. When you install the software a Dash Manager recieve template is also installed so you have your dash can recieve the M84 data too.

There is also the ability to use the SLM in a similar way to the M400/M600/M800 and VCS (Video Cature System).

The RS232 is for recieving GPS.

Re: M84

PostPosted: Tue Nov 09, 2010 8:22 pm
by Merlin
thanks Mark

ok sounds good ....but what about a BR2 ??

John P

M84 with LTC in the Manual

PostPosted: Wed Nov 10, 2010 10:17 am
by TunedByShaneT
In the Manual it says an LTC can be connected to the M84 but Im not sure I understand how this is done as the sensor setup only allows the choice for Lambda 1 or Lambda 2 Input in the setup.

Does the M84 just know when an LTC in connected on the CAN bus and the sensor calibration is set to PLM over CAN that it should ignore Lambda 1 Input and pay attention to the LTC?

Re: M84

PostPosted: Wed Nov 10, 2010 12:15 pm
by RossB
John,
There is no BR2 support on M84.

Shane,
When you set the Lambda1 or Lambda2 calibration to "PLM on CAN" the ECU will recieve the PLM or UTC CAN data on CAN ID 460 and 461. We will put togaether some more detailed information about the comms setup and make that available shortly.

M84 Reading LTC

PostPosted: Wed Nov 10, 2010 6:11 pm
by TunedByShaneT
Fair enough - when the calibration is set to PLM over CAN it automatically knows to look for the LTC.

Thanks for the Updates.

Re: M84

PostPosted: Wed Nov 10, 2010 9:06 pm
by Merlin
RossB wrote:John,
There is no BR2 support on M84..



ok this will serverly limit what i fit this ecu to ....
As a group of cars Im involved with run in the same class (IPRA) we use one beacon for our logging and lap times
and to compare our data

should I then be hunting down all the second hand beacon receivers that connect to a digi input ??
or

do you Plan to add this at a later date


John P

Re: M84

PostPosted: Thu Nov 11, 2010 8:05 am
by RossB
You can connect a GPS to the M84, i2 will then generate lap times in your data using the GPS data. This is a far more cost effective way of doing what you want. You also have the benefit of being able to do GPS track mapping and compare racing lines as well as lap times. A 5 Hz GPS will cost you about half what a BR2 costs.

The BR2 can be connected using a digital input as well as CAN, so there is no gain in finding an old receiver, but this is not supported on the M84 either. There are no plans to change at this stage.

Re: M84

PostPosted: Thu Nov 11, 2010 8:34 am
by JamieA
John,
When we looked at the ECU specifications, our general thoughts went like this..

A BR2 by itself is about $559 retail, if you plug that into your M800, you get your data split up into laps.
If you add a G sensor $370+ for a single axis, you could then log lat G force, and then add a Speed sensor, you could get a track map.

Instead of this, if you buy the Garmin 5hz GPS at $295, you get Lap times in M800 data (using the new i2 insert GPS beacons feature), track mapping, race lines, and speed. It will give you all of the same information that you were getting above, at about 1/3 of the cost.

Our thougts on this were that for the level that this ECU is aimed at, there was few reasons that a customer buying one would want a Br2 instead, even if you already owned the transmitter, which is another $500 on top of the above costs.

The GPS is a cheaper, better method for your purposes.

-Jamie

Re: M84

PostPosted: Fri Nov 12, 2010 10:36 am
by Dragon
You mentioned connection to MDD only. What about the SDL and ADL? What kind of messages are sent to these?
How do I set up each of those to receive data from the M84?