RealDash version 2.3.3

  • 2.3.3 released 23.11.2023


  • RealDash CAN is able to send configuration message for CAN speed and mode.
  • Forza Motorsport 8 is now supported.
  • New calculated input: 100 to 200 kph seconds.
  • New inputs for TPMS: Air Leaking, Battery Low, Sensor Connected.
  • New option for Graph Gauge: Flatline.
  • CAN and OBD2 XML files can now be stored in My RealDash and downloaded in RealDash connection settings.
  • Deelife TPMS system is now supported.


  • Fixed gauge update problems on non-active pages.
  • Debug Data View uses bigger font.
  • Is Daytime input is set from the clock.
  • Fixed WiFi Enabled and Bluetooth Enabled inputs.
  • Fixed multiple unit conversion errors in datalog playback.
  • OBD2: Fixed error code reading on some vehicles.
  • Android: Fixed external navigation app not launching.
  • Android: Fixed SocketCAN connection.
  • MRD: Fixed 400 Bad Request when credentials have special characters.


This release also includes large technical update for My RealDash.

You can now upload CAN and OBD2 XML files in MRD and import them in RealDash connection settings (My RealDash subscription is required). XML files are located in My RealDash ‘Garage’ section.

Deelife TPMS system is now supported. It is an affordable TPMS system available here:

It seems to work out of the box, but in some cases you may need to configure the TPMS system with Deelife’s own Android software.


What does the configuration frame look like?

Would it be possible to implement the bluetooth model as well?

If CAN configuration setting is enabled, RealDash sends two CAN frames immediately after connection is established:

can bitrate 20000: canSpeedByte = 0x01
can bitrate 50000: canSpeedByte = 0x02
can bitrate 100000: canSpeedByte = 0x03
can bitrate 125000: canSpeedByte = 0x04
can bitrate 250000: canSpeedByte = 0x05
can bitrate 500000: canSpeedByte = 0x06
can bitrate 800000: canSpeedByte = 0x07
can bitrate 1000000: canSpeedByte = 0x08
{ 0x67, 0x33, 0x22, 0x02, 0x15, canSpeedByte, crcByte1, crcByte2, crcByte3, crcByte4 }
Mode Normal: mode = 0x11
Mode Loopback: mode = 0x12
Mode Silent: mode = 0x13
Mode Loopback Silent: mode = 0x14
{ 0x67, 0x33, 0x22, 0x01, mode,  crcByte1, crcByte2, crcByte3, crcByte4 }
1 Like

If we are in luck it works already just by selecting Bluetooth as connection type. If not, we would need to find the protocol specs.

1 Like

I’m implementing it here but it sends both frames in the same buffer, is that right?

I don’t understand what you mean by this.