SmartyCam Streams and CAN Output

An input protocol describes how the device receives another unit’s messages. An output stream describes the messages the device sends. Configure both ends of a connection with matching identifiers, field positions, units and conversions.

Assign the Standard SmartyCam Functions

Products documenting SmartyCam Stream: PDM32/PDM08; MXS/MXG 1.2 and 1.3, MXP/MXP 1.3, MXT 1.3 and their Strada versions; MXm, MXq, MXPS, MX2E, MXK10 Gen4/Gen5, SW4, ECULog, XLog and Solo 2 DL. Earlier MXS Strada, MXL2, EVO4S and EVO5 manuals also list this feature.

The master sends data to a SmartyCam so that its camera configuration can use the values in the video. Select the appropriate camera generation and the default stream, where the page offers that choice.

  1. Open the master’s SmartyCam Stream.

  2. Select each required function, such as engine RPM, speed or temperature.

  3. Choose the channel that supplies that value. The normal list filters channels by function.

  4. If the required source is not offered, check its function first. Where available, Enable all channels for functions expands the selection; verify that the chosen value and units are appropriate.

  5. Save and transmit the master configuration.

  6. In the camera configuration, choose the matching incoming protocol and assign its channels to the overlay controls.

The master stream and camera overlay are separate configurations. A channel can be sent correctly while a camera control is assigned to a different channel. See Camera, Lap Timer and Kart Settings for the camera-side procedure.

Build an Advanced SmartyCam Stream

Products documenting advanced/custom streams: the MX 1.2/1.3 logger and Strada manuals, MXm/MXq, MXPS, ECULog, XLog and Solo 2 DL; the SmartyCam 3 and SmartyCam 4 Corsa manuals describe the receiving camera setup. The choices available depend on the selected master and camera generation.

Use an advanced stream when the standard function mapping does not contain the required data or layout. In SmartyCam Stream, select SmartyCam 3 onward and Advanced where offered. Define payload headers and channel fields as described below, then give the stream a recognisable protocol name and save it.

Open the camera configuration’s CAN Protocol page and select that named stream for its connection to an AiM master. Reassign the overlay fields where needed, then transmit both configurations.

On ECULog and XLog, SmartyCam Stream is available only when the EXP connector is assigned to AiM CAN. It is unavailable when EXP is assigned to external CAN2.

On MXPS, the advanced stream uses the same payload-building procedure as CAN Output2. This describes how to edit the messages; it does not assign the SmartyCam stream to the vehicle’s CAN2 port. Configure the two streams separately.

Define General CAN Output Messages

Products documenting CAN Output: PDM32/PDM08; MX 1.2/1.3 logger and Strada families; MXm, MXq, MXPS, SW4, ECULog, XLog, Solo 2 DL, and the earlier MXS Strada, MXL2, EVO4S and EVO5. ACC2/ACC3 Open, K6/K8/K15 Open, LCU1S/LCU2 Open and GPS09c Open also document output-message configuration for their own channels. See CAN Expansions, Keypads and Open Devices for their operating modes.

CAN Output sends selected device values to an external receiver. It is useful, for example, for sending a PDM’s measured output current or a SW4’s button states to another unit. Available buses and channels differ by model.

  1. Select the output bus provided for this connection. PDM32 documents CAN1 and CAN2; other devices can expose a different set of output pages.

  2. Click Add new Payload and enter the header details.

  3. Select an unused CAN identifier with the required address format: 11-bit standard or 29-bit extended, where offered.

  4. Set the data length, byte order and transmission frequency for the receiver. The PDM32 manual describes classic CAN payloads of 1-8 bytes and frequencies of 1, 2, 5, 10 or 20 Hz. Use the choices offered by the selected device.

  5. Open a field in the payload and select the channel to transmit. Configure the field position, length and conversion according to the receiving protocol.

  6. Repeat for the remaining fields and payloads. Review the complete byte/bit layout before saving.

  7. Transmit the configuration and check the decoded values at the receiver.

Match the sender to the receiver

Item

Check at both ends

CAN identifier and format

The same numeric identifier and standard/extended address format. Avoid an identifier already used by another transmitter.

Payload length

Every configured field fits within the transmitted data bytes.

Byte and bit positions

Fields have the same boundaries and do not overlap other fields.

Byte order

The receiver interprets multi-byte values in the sender’s little-endian or big-endian order.

Representation and scaling

Signedness, multiplier, offset, units and decimal scaling describe the same physical value.

Rate or event

The receiver accepts the chosen update rate. Keypad Open also documents transmission on a change of value; this is a model-specific choice.

If the CAN Output page offers Create CAN Input Protocol, it can produce an input definition for a receiving AiM configuration. Select that protocol on the receiver, transmit both configurations and compare physical values at both ends. For a protocol edited independently, use Custom Protocols.

Verify a Stream Before Using It

Check more than whether messages are present on the bus. Compare at least one known value at the source and receiver, then vary it. Include a value with decimal places when the field uses scaling, and a change of state when the field carries flags or buttons.

For an advanced SmartyCam stream, check the selected protocol and the overlay assignment as well as the master channel. For an external CAN receiver, use that receiver’s decoded values. Resolve an unexpected factor, offset or sign before using the channel in control or alarm logic.

Sources for Outgoing Streams