Dash 2 versus Dash 2 Pro - limitations to GEMS Ecu?

[markk]

no longer req.

[Support]

Correct with regards to the DASH2pro not needing an interface.

The GEMS is fully configurable on what it transmits and the DASH2 is fully configurable on what it decodes so you just need to setup both sides.

This is how i recommend it is done...



* Open GEMS ECU software
* Open CAN configuration
*Choose the messages you want to transmit using the red boxes above
*Export DBC file using button highlighted in green



* Open DASH2pro configuration software
* Click on CAN inputs - Green
* Load GEMS DBC file - Purple
* Drag and drop the messages from the red box and drop them on the blue. This will auto fill the configuration

Once complete send configuration to the DASH and then connect lite monitor to check the messages are being decoded.

Kind regards,
Support (K)

[markk]

no longer req.

[Support]

The communication from this particular GEMS ECU is all done on CAN, so you will need to use the CAN-serial adapter or use the CAN interface option on the data loggers which support it.

Martin

[markk]

no longer req.

[Support]

The EM36 doesn't transmit in our RS232 protocol, which you wouldn't expect it to. Since CAN is pretty much standardised in how the data is formatted it is much easier for us to do an interface for CAN than for serial. Yes our DASH units read data in via RS232, but the DASH and the ECU are not talking the same language.

Martin