CAN Data Reception – SmartyCam 3
FAQ
Question: How can I allow SmartyCam 3 to receive GPS data provided via a CAN protocol, such as lap time or GPS coordinates, to display in their overlays?
Answer: The SmartyCam 3 (Corsa, GP and Dual) can integrate essential parameters generated by third-party devices, such as GPS coordinates, lap times, clock synchronization, and GPS speed, to provide overlay indications without requiring an AiM GPS module. This requires following specific configuration criteria.
GPS Coordinates
To display GPS coordinates received via CAN on the SmartyCam 3, submit the information according to these criteria:
- Information must be transmitted as DWORD (32bit).
- Data must be expressed in degrees 10e-7 (e.g., 120.5984799° becomes 1205984799).
- West and South coordinates (negative values) must be expressed as a 2's complement.
- The function to choose is "ECU Latitude" or "ECU Longitude".
- Endianness, arbitration ID, and byte placement are free.
Example: A coordinate expressed in sexagesimal degrees (e.g.: 120° 35' 91') must be converted to decimal degrees (120.5984779) and then multiplied by 10,000,000 (1205984779) to be sent via CAN as 0x47E1D1E1F.
For negative coordinates, such as -120.5984799 deg, the value is sent as a 2's complement: 0xB81E21E1.
Configuration Screenshot Description: The CAN channel setup screen requires the "Data Format" field to be set to "Signed integer" (indicated by an orange box in the original document). The configuration for GPS Latitude is displayed, with "Number of Bits" set to 32 and "Data Format" as "Signed integer". The byte mapping illustrates the distribution of these bits across bytes.
Lap Times
To correctly display lap time information received via CAN from an ECU or third-party system, follow these criteria:
- Time shall be expressed in thousandths of a second (ms).
- Data should ideally be arranged on at least one WORD (16bit).
- The function must be selected as "ECU Lap Time", "ECU Best Lap Time", or "ECU Rolling time", depending on the transmitted information.
- Endianness, arbitration ID, and byte placement are free.
Example: A time of 6'11"13 (371.13 seconds) needs to be converted to thousandths of a second (371130 ms) for transmission via CAN as 0x7BE1. If the control unit transmits the channel in hundredths of a second, the conversion can be used by multiplying x10.
Configuration Screenshot Description: The CAN Measure Settings screen for "LapTime" is shown, with "Number of Bits" set to 16 and "Data Format" as "Unsigned integer". The byte mapping indicates how the 16 bits are arranged.
Master Clock
Typically, the internal date and time of SmartyCams are synchronized via an AiM GPS module. If no GPS module is present, synchronization can be managed through a specific CAN channel.
The Master Clock information received via CAN bus must follow these criteria:
- Expressed in GPS UTC Time (seconds elapsed since 1/1/1980).
- Sent as DWORD (32bit).
- The function to be selected is "ECU GPS UTC Time".
- Endianness, arbitration ID, and byte placement are free.
Configuration Screenshot Description: The CAN Measure Settings screen for "GPS UtcTime" displays "Number of Bits" set to 32 and "Data Format" as "Unsigned integer". The byte mapping details the bit distribution for this 32-bit value.
Vehicle Speed
Vehicle speed is usually calculated by the AiM GPS module. If no module is available, this channel can be received via CAN with the following criteria:
- The function to be selected is "ECU GPS Speed".
- Endianness, arbitration ID, byte placement, and unit of measurement are free.
Configuration Screenshot Description: The CAN Measure Settings screen for "GPS Speed" is configured with "Number of Bits" set to 16 and "Data Format" as "Unsigned integer". The byte mapping illustrates the bit arrangement for speed data.
Compatible GPS and Lap Time Channels
For automatic track recognition and circuit position, the following GPS channels must be received via CAN, configured with the indicated functions:
- GPS Latitude (Function: GPS ECU Latitude)
- GPS Longitude (Function: GPS ECU Longitude)
- GPS Vehicle Speed (Function: GPS ECU Speed)
GPS Channel Functions Compatible with SmartyCam 3:
| GPS Channels | Function | Unit |
|---|---|---|
| GPS UTC Time | Time - ECU GPS UTC Time | s |
| GPS UNIX Time | Time - ECU GPS UNIX Time | s |
| Vehicle Speed | SPEED - ECU GPS SPEED | km/h |
| GPS Latitude | Coordinate – ECU Latitude | Deg⁷ |
| GPS Longitude | Coordinate – ECU Longitude | Deg⁷ |
| GPS Altitude | Coordinate – ECU Altitude | m |
Function Table for Lap Time Channels:
| Lap Time Channels | Function | Unit |
|---|---|---|
| Lap Time | Time - ECU LAP Time | ms |
| Lap Number | Number - ECU Lap Number | ms |
| Best Lap Time | Time - ECU Best Time | ms |
| Rolling Time | Time - ECU Lap Time | ms |
RaceStudio3 Integration
If using a protocol released on RaceStudio3 (owned by AiM), you can integrate additional CAN information or a third-party external GPS module using the "Merge" feature. This allows adding channels, provided their IDs do not already exist in the existing RaceStudio3 protocol.