Second firmware live stream happening this weekend: viewtopic.php?f=13&t=3992
For anything you'd like to see added to Speeduino
By GhjEng
#40426
Thanks @RealDashDev, this is great news :)
User avatar
By realdashdev
#40440
I'd like to get a confirmation that I'm doing this right.

1. Parse the ini file. Current ini file (November 2019 firmware) describes block of 99 bytes.
2. Send character 'A' to Speeduino (one byte).
3. Receive character 'A' from Speeduino (one byte).
4. Receive 99 bytes datablock.
5. Parse datablock per ini file.
6. goto 2.

Is this assumption of 'A' protocol correct?
By dazq
#40446
realdashdev wrote:
Mon Jan 20, 2020 3:05 pm
I'd like to get a confirmation that I'm doing this right.

1. Parse the ini file. Current ini file (November 2019 firmware) describes block of 99 bytes.
2. Send character 'A' to Speeduino (one byte).
3. Receive character 'A' from Speeduino (one byte).
4. Receive 99 bytes datablock.
5. Parse datablock per ini file.
6. goto 2.

Is this assumption of 'A' protocol correct?
Not quite.

If you skip step3 then the above will work for serial0 but not serial3 I'm afraid.

For serial 3 see this page for the current A data list.
https://speeduino.com/wiki/index.php/Se ... _interface
User avatar
By realdashdev
#40447
Ok, a recap:

With serial0:
1. Parse the ini file. Current ini file (November 2019 firmware) describes block of 99 bytes.
2. Send character 'A' to Speeduino (one byte).
4. Receive 99 bytes datablock.
5. Parse datablock per ini file.
6. goto 2.

With serial3:
1. Send character 'A' to Speeduino (one byte).
2. Receive character 'A' from Speeduino (one byte).
3. Receive 75 bytes datablock. (as per https://speeduino.com/wiki/index.php/Se ... _interface)
4. Parse datablock per spec.
5. goto 1.

This line of info got me confused:
https://speeduino.com/wiki/index.php/Se ... _interface
"If you send an "A" to the port it will reply with,
"A" confirming the received instruction (sent as 0x41 in hex),
The port will then transmit ALL the realtime data."

So above info is still true, but only with serial3?
Last edited by realdashdev on Tue Jan 21, 2020 12:58 pm, edited 1 time in total.
By dazq
#40448
Yes that is all true and correct.

The reason for the difference is when serial3 was first created the data list was the same between that and serial0.
At some stage the list on serial0 was reordered and later extended.

On a different note , am I correct in thinking realdash can support connection via an OBD2 socket using canbus?
User avatar
By realdashdev
#40449
dazq wrote:
Mon Jan 20, 2020 6:44 pm
On a different note , am I correct in thinking realdash can support connection via an OBD2 socket using canbus?
Sure, if no special headers need to be set, and incoming PIDs are on SAE standard list, it should work without any extra configuration just by selecting OBD2 as connection type.
By dazq
#40450
realdashdev wrote:
Mon Jan 20, 2020 6:54 pm
dazq wrote:
Mon Jan 20, 2020 6:44 pm
On a different note , am I correct in thinking realdash can support connection via an OBD2 socket using canbus?
Sure, if no special headers need to be set, and incoming PIDs are on SAE standard list, it should work without any extra configuration just by selecting OBD2 as connection type.
Excellent! No it talks OBD2 just like an OEM to full STDs
User avatar
By realdashdev
#40469
- 1.6.7-BETA1 released 21.1.2020, available from Play store if you are enrolled to the beta program.

New:
* Speeduino support for serial0 and serial3.

Fixes:
* Connectivity issues with PDSX-1 Bluetooth.
* Connection list is now saved properly when connection is removed.

The Speeduino support in this beta has following limitations/known problems:
- It is tested only with internal simulator, feedback from actual hardware users is welcomed.
- For serial0, there is no option to import speeduino.ini file. Instead RealDash uses ini file internally from November 2019 firmware.
- Bitmask values are not parsed or read from the stream.
- All multibyte data from Speeduino are assumed to be in big-endian format.
- Not all Speeduino specific inputs are listed on ECU Specific category.
- ECU Specific Speeduino inputs may still change and render existing inputs invalid.
By dazq
#40470
Cool!
Couple things.
First data is little endian.
Second Are the auxin/canin data available as many use these for fuel level or oil pressure etc?
User avatar
By realdashdev
#40489
Allright, could somebody verify that for example RPM is showing invalid value, but one-byte values like coolant temp is ok? I will then switch the endianess of incoming 2-byte values.

The 16 auxin/canin values are read from the stream. They are linked to ECU Specific->Speeduino: auxin_gauge0-15 inputs in RealDash.
  • 1
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9

Hi Rob! I'm afraid that speedy doesn't yet support[…]

Motronic 1.1/1.2/1.3 Compatible PCB

It also seems that even the 4.7nF cap for C25 i[…]

Dumb coil on plug (Motorcycle)

I'm switching over from a Megasquirt. Will a QuadS[…]

Time passes..... I've now got a 0.4.3c for this p[…]

Still can't find what you're looking for?