Speeduino Serial 03, no VSS

cel_turbo · June 30, 2023, 3:10am

Hello.
I was looking for why Realdash did not receive VSS information in Realdash by Serial 03 by Speeduino.
Monitoring by the Hterm serial monitor I saw that speeduino was sending 75 bytes by command A.
The VSS information is in byte 100 and 101.
I corrected the code to send all 123 bytes of information.
But despite the information appearing in Hterm, Realdash did not show the VSS, I believe it was mapped in Realdash by an old version of the code.
The data sent are these up to line 346:

github.com

noisymime/speeduino/blob/f331271d5a4a12c624b5abded54bf48e34fede29/speeduino/cancomms.ino#L208


      
                  else if (cmd == 0x32)
                    {
                     CANSerial.write("n");                       // confirm command type
                     CANSerial.write(cmd);                       // send command type  , 0x32 (dec50) is ascii '0'
                     CANSerial.write(NEW_CAN_PACKET_SIZE);       // send the packet size the receiving device should expect.
                    }
              #endif
          
          
  currentStatus.spark ^= (-currentStatus.hasSync ^ currentStatus.spark) & (1U << BIT_SPARK_SYNC); //Set the sync bit of the Spark variable to match the hasSync variable
          
          
#if defined(CANSerial_AVAILABLE)
            byte fullStatus[NEW_CAN_PACKET_SIZE];    // this must be set to the maximum number of data fullstatus must read in
            fullStatus[0] = currentStatus.secl; //secl is simply a counter that increments each second. Used to track unexpected resets (Which will reset this count to 0)
            fullStatus[1] = currentStatus.status1; //status1 Bitfield, inj1Status(0), inj2Status(1), inj3Status(2), inj4Status(3), DFCOOn(4), boostCutFuel(5), toothLog1Ready(6), toothLog2Ready(7)
            fullStatus[2] = currentStatus.engine; //Engine Status Bitfield, running(0), crank(1), ase(2), warmup(3), tpsaccaen(4), tpsacden(5), mapaccaen(6), mapaccden(7)
            fullStatus[3] = (byte)div100(currentStatus.dwell); //Dwell in ms * 10
            fullStatus[4] = lowByte(currentStatus.MAP); //2 bytes for MAP
            fullStatus[5] = highByte(currentStatus.MAP);
            fullStatus[6] = (byte)(currentStatus.IAT + CALIBRATION_TEMPERATURE_OFFSET); //mat
            fullStatus[7] = (byte)(currentStatus.coolant + CALIBRATION_TEMPERATURE_OFFSET); //Coolant ADC
            fullStatus[8] = currentStatus.batCorrection; //Battery voltage correction (%)

Tks.

realdashdev · August 8, 2023, 8:13am

I think the Serial 03 is hardcoded into RealDash. Where could I find info on what is current Serial 03 datastream?

cel_turbo · October 3, 2023, 12:11am

The data sequence follows the order of line 210 to 346, it has not yet been updated in the documentation.