CAN Expansions, Keypads and Open Devices
An expansion adds channels, controls or a display to an AiM master device. Configure the master when the expansion is part of its AiM CAN network. An Open device can also have its own configuration for a network that uses a freely defined protocol. Choose the intended connection before creating the configuration: it determines which device receives it.
The examples below cover ACC2/ACC3, K6/K8/K15 keypads, LCU controllers, Channel Expansion, TC Hub, GPS09c Open, GS-Dash and Memory Module. Available models, channels and settings depend on the selected master, expansion and firmware. Use the choices offered for that exact configuration; a CAN connector alone does not establish compatibility.
For the complete master workflow, see A Complete PDM32 Configuration Example. For conditions and state variables used by buttons and LEDs, see Math Channels, Status Variables and Commands.
Choose the configuration that owns the expansion
AiM expansion through a master. Open the master’s configuration, add the expansion and identify its serial number. Save and transmit the completed configuration to the master. Check the expansion through the connected master’s live measures and firmware information.
Open device on an external CAN network. Connect the Open device to the PC through its specified USB cable, create a configuration for that Open model and configure its channels or buttons and communication protocol. Save and transmit to the Open device. The CAN messages must match the receiving system.
Open device on an AiM CAN network. Select the AiM connection mode where the Open model provides it, transmit that mode to the Open device, then configure it through the master as described for that model below. A custom CAN Output protocol and the proprietary AiM CAN connection are different operating modes.
These paths are documented in the ACC2 Open configuration guide, the ACC3 Open configuration guide and the LCU Open configuration guide.
For ACC2 Open and ACC3 Open, selecting CAN AiM removes the need to define a custom outgoing protocol: the device operates as its corresponding AiM expansion. For LCU1S/LCU2 Open used as a slave of an AiM master, follow the master’s expansion procedure and the channel settings of the non-Open controller.
Add and identify an expansion in the master configuration
Products documented: ACC2, ACC3, LCU-One CAN, LCU1S/LCU2, Channel Expansion and TC Hub.
Open an existing configuration for the master, or create one for its exact model.
Open CAN Expansions and click New Expansion. Select the expansion model and confirm. For an ACC3 Open, select its Open variant rather than ACC3.
Give the expansion a name. Enter the serial number printed on the physical unit, or read it from the connected system using the serial-number command.
To read a serial number, power the expansion and connect its master to the PC through a connection supported by that master. If a selection window lists several expansions, choose the intended physical unit and confirm.
Open the expansion’s channel settings and configure the sensors, functions and recording parameters it provides.
Save the configuration and transmit it to the master. When prompted to associate expansions with serial numbers, check each association against the installed units.
Select the connected master and check that the expansion appears in its firmware information. Inspect the relevant live measures to verify the channel values.
Reading a serial number identifies the unit; the channel settings still need to be completed and transmitted.
See ACC3 identification and channel setup, LCU serial-number selection and LCU-One connection checks.
Note
AiM keypads are configured in the Keypad tab in current RaceStudio 3. Older product manuals show them under CAN Expansions. Existing configurations retain their keypads when opened in the current interface.
Configure additional sensor inputs
Products documented: ACC2/ACC3 and their Open versions, Channel Expansion and TC Hub.
For an ACC, first choose the cable or thermocouple arrangement that matches the installed harness. Open each channel and set its name, function, specific sensor, sampling frequency, unit and precision where offered. Repeat for the remaining channels, then save and transmit to the device that owns the configuration.
Keep these hardware differences when selecting the sensor:
Product |
Input selection |
|---|---|
ACC2 / ACC2 Open |
Four configurable analog inputs, including thermocouples with the appropriate harness. The cited manuals specify a maximum of 200 Hz. |
ACC3 |
Ch01/Ch02 are analog; Ch03/Ch04 can be analog or digital speed inputs. Select Digital for a compatible square-wave speed sensor. |
ACC3 Open |
Select the analog/digital function and thermocouple arrangement offered for the connected model and harness. |
Channel Expansion |
Ch1/Ch2 can be analog or speed inputs. Selecting either as digital also makes the other digital. Ch3/Ch4 are analog. Thermocouples are unsupported. |
TC Hub |
Four temperature inputs for K-type thermocouples. |
For a speed input, enter wheel circumference and pulses per revolution where requested. A wheel-speed channel also requires its wheel position where offered. Do not substitute the input pulse frequency for the frequency at which the calculated speed is sent or recorded.
The ACC3 sensor selector separates Custom, AiM and Supported sensors. Choose the exact entry: the AiM PT-100 2K includes its pull-up resistor, whereas the Supported PT-100 entry requires the external resistor specified by its wiring instructions.
See ACC2 channels, ACC3 sensors and speed inputs, Channel Expansion input settings and TC Hub temperature channels.
The ACC3 manual explicitly lists PDM models, MX 1.2/1.3 and MX v2 models, SW4, EVO4S/EVO5, MXPS, MXsl, MXm/MXm v2/MXq, MX2E and MXK10 among its masters. It also lists Solo 2 DL/Solo 2 DL v2, ECULog and XLog with external power. Refer to the ACC3 compatibility and power requirements for the exact product list.
Check and calibrate expansion sensors
Products documented: ACC2 Open, ACC3 Open and Channel Expansion.
Configure the sensor before calibrating it. Select the connected device or master, inspect its live measures and use the calibration procedure offered for that sensor. For a potentiometer zero adjustment, place it at the required zero position before applying the calibration command.
For ACC2 Open and ACC3 Open, the product guides distinguish a USB cable for configuration from a cable that also powers the sensors. Use the powered arrangement specified by the product when checking live channel values or calibrating; a cable that permits configuration alone may not support either operation.
The Channel Expansion guide distinguishes calibration for gear sensors and potentiometers from auto-calibration for the sensors that provide it. Follow the procedure for the selected sensor; changing a channel’s displayed unit is not a calibration.
See ACC2 Open connection and calibration requirements, ACC3 Open zero calibration and Channel Expansion calibration choices.
Configure a keypad as an independent Open device
Products documented: K6 Open, K8 Open and K15 Open.
Connect the keypad to the PC through its specified USB cable.
Create a configuration for the exact Keypad Open model.
Configure its buttons and LED colours.
In CAN Input, select the protocol that supplies feedback from the other equipment. If needed, create a custom protocol using the CAN Driver Builder.
In CAN Output, define the messages carrying button states. The Open keypad guide supports periodic transmission and transmission when the transmitted fields change; select the behaviour required by the receiver.
Save and transmit to the keypad.
An Open keypad can use received CAN information for LED feedback. This allows a colour to indicate that equipment has responded, in addition to indicating that a button was pressed. Its documented internal Device Brightness increase and decrease commands use Momentary buttons.
To use this hardware on an AiM CAN network instead, set connected to AiM device in its own configuration and transmit that setting. Then open the master’s Keypad tab, add the correct Open keypad variant and configure it for that master.
See Open keypad configuration and CAN feedback, Open keypad CAN transmission and Open keypad use with an AiM master.
Set lambda channels and the fuel multiplier
Products documented: LCU-One CAN, LCU1S/LCU2 and LCU1S/LCU2 Open.
Add the exact controller to the master configuration, or create its own configuration when using an Open controller independently. Identify the controller, then choose the fuel’s stoichiometric AFR multiplier from the available values or enter the required custom value.
Set the channels’ recording frequency, units and precision where offered. For LCU2, configure both sets of controller channels. Save and transmit to the master or Open controller as appropriate, then check the live measurements and the controller’s diagnostic channel.
For LCU-One CAN, the guide also documents enabling or disabling its four channels and selecting its channels as display-field sources. The Bosch LSU 4.9 probe described in that guide does not require a separate user calibration. Setting the fuel multiplier changes the AFR conversion; it does not calibrate the probe.
Controller families have different compatibility and diagnostic codes. The cited LCU1S/LCU2 guides exclude MXL, MXL2 and MyChron, while LCU-One CAN has a separate MyChron5 procedure. Do not replace one family with another without checking the exact master’s product documentation and available models. The LCU-One CAN+Analog variant is also distinct from LCU-One CAN.
See LCU1S/LCU2 master configuration, LCU Open channel configuration and LCU-One fuel and channel settings.
On the MyChron5 path documented for LCU-One CAN, the instrument detects the controller at startup. Its display fields are selected on MyChron5 through System Settings > Display Setup. Check recognition through System Information > Net Info. This product guide describes an instrument menu workflow, rather than the master configuration procedure above: LCU-One CAN with MyChron5.
Build an Open device’s outgoing CAN messages
Products documented: ACC2 Open, ACC3 Open, LCU1S/LCU2 Open and Open keypads.
Open the device’s CAN Output settings and select Open where required.
Set the bus bit rate and add or select a payload.
Configure its CAN identifier, length, byte order and transmission timing using the options available for this model.
Assign the source channels to the payload fields and set their encoding to match the receiving protocol.
Add other payloads where required. Use identifiers that do not conflict with other messages in the intended network.
Save and transmit to the Open device, then verify reception in the receiving system.
The ACC3 Open guide specifically requires a different identifier when another payload already uses the proposed default. The LCU2 Open guide shows two sets of controller payloads. Open keypads also support sending on field changes. Select transmission timing from the values offered for that exact model.
For the payload fields and encoding workflow, see SmartyCam Streams and CAN Output and the ACC2 Open CAN Output procedure, ACC3 Open payload procedure and LCU Open CAN Output procedure.
Select GPS09c Open CAN, RS232 or AiM output
Product documented: GPS09c Open.
Connect GPS09c Open to the PC with its specified USB cable and open its configuration. Choose the output needed by the receiving system:
CAN Open: set the bus bit rate and each message’s identifier, DLC, byte order and frequency. The cited guide lists 1, 5, 10 and 25 Hz. Assign the required GPS and date/time information.
RS232: configure the serial parameters, select the required NMEA sentences and set each sentence’s transmission frequency.
AiM CAN Connection: select this mode for an AiM CAN network. The AiM dash or logger then manages the module automatically as described by the guide.
This procedure comes from the GPS09c Open guide. For GPS09c Pro Open, also consult that model’s documentation for its additional IMU channels.
Configure a GS-Dash through its logger
Products documented: GS-Dash with EVO4S/EVO5. The PDM32 guide also lists GS-Dash among its available expansions; use the display options offered in that master’s configuration.
GS-Dash receives its configuration from its logger. Select it as the display in the master configuration, choose a page layout and assign a channel to each field. Set channel labels and units where offered. In layouts containing the RPM bar, the GS-Dash guide restricts lap-time fields to the right-hand side.
Configure its shift lights using the desired RPM source, LED colours and thresholds, including per-gear thresholds where used. Configure alarm conditions, LED behaviour, messages and displayed measures, then choose how each alarm ends. Trigger commands can change pages, act as display-button presses or reset alarms.
See GS-Dash configuration through EVO4S/EVO5 and the PDM32 expansion list.
Use Memory Module and Strada Logger
Products documented: Memory Module and Strada Logger.
Memory Module does not require a separate channel configuration. Connect it to a compatible logger before recording; the logger and module store data in parallel. After the session, insert its SD card into the PC, select Memory Module in RaceStudio 3 and use Download to import the data.
Check compatibility for the exact logger and module type. The Memory Module guide and the Strada Logger application note describe different compatibility for recording and Strada dash variants. Do not treat the two modules as interchangeable or infer compatibility from the presence of an SD card.
See the Memory Module compatibility table, Memory Module download workflow and Strada Logger application note.