A Complete PDM32 Configuration Example

This example follows a PDM32 configuration from its source channels to its outputs, display and transmitted data. It uses a cooling fan to show how the features work together. The same configuration workflow applies to the features offered by another selected device; its inputs, outputs and electrical ratings remain specific to that model.

The temperatures and RPM below illustrate the logic. Choose the actual sensor, load-protection settings and operating thresholds for the vehicle. This software example does not replace the PDM32 installation and wiring instructions.

1. Create the PDM32 Configuration

Open Configurations, click New Configuration, select PDM32 and give the configuration a useful name and comment. You can prepare it before connecting the PDM32. Configure only the hardware present in the installation.

For this example, identify these sources and destinations:

Example installation
Item	Purpose
Water-temperature channel	An ECU channel or an appropriately wired analog sensor supplies `WaterTemp`.
Engine-RPM channel	The selected ECU protocol supplies RPM, or the supported physical input is used.
GPS module	Supplies speed, position and GPS lap timing if required by the installation.
Fan power output	A suitably rated PDM output and protected circuit supply the fan.
PDM display	Shows temperature, RPM and the fan’s diagnostic values.
Optional camera	A rear-view camera uses the PDM’s camera-input page; a SmartyCam receives a separate data stream for its recorded video.

2. Establish the Input Channels

In Channels, open the wired analog input when using a direct temperature sensor. Select the sensor, set its function and units, and name it WaterTemp. Set its sampling and logging options. Configure the pull-up according to that sensor’s circuit.

If water temperature and RPM come from the ECU instead, select the vehicle’s protocol in ECU Stream and enable the required channels there. Review CAN termination and silent mode for the actual bus. Use CAN2 Stream for an additional compatible CAN module, when present.

Calibrate any input that needs a physical reference after transmitting the configuration. First establish that the actual readings are credible, then use them as the inputs to the logic. See Channels, ECU Streams and Recording Settings.

3. Add Expansions and the Display

Add the installed expansion models under CAN Expansions and associate the correct serial numbers. Configure a channel expansion’s sensors or a lambda controller’s fuel/AFR settings in that expansion’s panel. Use Keypad for the keypads offered by the selected configuration.

For the PDM display, select the model actually connected: the PDM32 manual describes 5-, 6- and 10-inch displays. The chosen display determines the layouts and controls available in the later steps.

An Open device used as an AiM expansion may first need its own connection mode configured. See CAN Expansions, Keypads and Open Devices before adding it to the master.

4. Define Math and Fan-Request Logic

Create a status variable named FanRequest with distinct activation and deactivation conditions:

set it ON when WaterTemp > 100 deg C;
set it OFF when WaterTemp < 80 deg C.

Between the thresholds, it retains the state established by the previous event. Set the labels and any qualification times required by the application. Enable logging of FanRequest so that its state can be compared with the output current and status after a run.

If a derived measurement is also needed, create it in Math Channels before using it elsewhere. For example, two appropriately configured brake-pressure inputs can feed a bias calculation. This is a device calculation, available to the configuration while the PDM is operating.

See Math Channels, Status Variables and Commands for the available calculation types, Boolean conditions, toggle behaviour and multiple-state variables.

5. Configure and Protect the Fan Output

Select the physical fan output in Power Outputs, name it CoolingFan and start with Continuous mode. Use FanRequest as its activation condition.

Set the current threshold, starting allowance, overcurrent time, retry policy and open-load detection for the actual circuit. Enable the fan’s current and status channels for recording where those options are offered. These diagnostic values show what the output is doing; FanRequest records what the logic requested.

For a fan designed for PWM control, the same workflow can use PWM instead. Select a permitted output frequency, configure the duty-cycle conditions and transition times, and check the behaviour at every range boundary. Do this only for a load and output type that support the selected mode.

The fields and protection sequence are explained in Configuring Power Outputs.

6. Set Parameters for the Session

In Parameters, choose the lap-detection source and reference-speed channel. For GPS timing, ensure that the GPS and intended track are available to the PDM. Send the track through Tracks for Analysis and Devices.

Review the start-recording condition. If using custom conditions, select the channels, comparisons and AND/OR relationship deliberately. Check the actual configuration’s defaults instead of copying an RPM or speed threshold from another product’s manual.

7. Build the Display, LEDs and Alarm

Choose a layout and assign fields for WaterTemp, RPM, fan current and fan status. Add FanRequest to a suitable field or icon if an indication of the requested state is useful. An icon requires a layout that supports it and a visibility/image condition based on the intended channel.

Configure shift lights from the selected RPM source, with per-gear thresholds if needed. If the selected LED mode is predictive time instead, configure its time increment and the required GPS/reference-lap setup.

Create a temperature alarm. The PDM32 manual’s logic example combines high water temperature with RPM above 2000; choose the actual conditions for the vehicle. Add a message or measurement and an LED action. Decide how it ends. If the alarm must remain visible until acknowledged, choose the corresponding button/reset ending condition and provide that reset action.

See Displays, Icons, Shift Lights and Alarms for layout assignment, icons, LED sequences and multi-action alarms.

8. Add Commands and Outgoing Streams

For a connected rear-view camera, add the PDM’s camera-page command and use the vehicle’s reverse-gear signal as its condition. The protocol determines the reverse-gear value. Also configure any required page-change or alarm-reset commands.

For a SmartyCam, map RPM, speed and water temperature in SmartyCam Stream. Select the matching incoming stream in the camera configuration and assign those values to its overlay. To include a non-standard value such as fan current, use an advanced stream where the selected master/camera combination offers it.

If another CAN unit needs fan current or status, create the required payload in CAN Output. Match that unit’s bus, identifier, field layout and conversions, then check the decoded values at the receiver. See SmartyCam Streams and CAN Output.

9. Save, Transmit and Verify

Save the configuration, power and connect the PDM32, then click Transmit. Check the target device and any requested expansion-serial associations. Wait for the transfer result before opening Live Measures.

Warning

A forced temperature, RPM or button value can switch on real loads. Isolate actuators or use a suitable bench setup before testing the fan logic.

First check the real input readings and the detected expansion network. Then verify the example logic in this order:

Illustrative fan-request checks
Test condition	Expected observation
Begin below the OFF threshold, then increase to 90 deg C.	The request remains OFF; no ON event has occurred.
Increase above 100 deg C, for example to 101 deg C.	The request becomes ON after any configured qualification time.
Reduce to 90 deg C after activation.	The request remains ON because the OFF condition is not yet true.
Reduce below 80 deg C, for example to 79 deg C.	The request becomes OFF after any configured qualification time.
Compare request, current and status.	The output’s diagnostics distinguish a normal request from a protection event.
Trigger and acknowledge the temperature alarm.	The intended actions occur and the configured ending/reset action clears them.

For a PWM setup, also check every duty-cycle range and transition. Check the camera-page command, SmartyCam overlay and any external CAN receiver separately. Remove all forced values, confirm normal readings and verify that a short test recording contains the channels selected for logging.

PDM Example References

The sequence above combines the features in the PDM32 User Guide, sections 11-18, 21 and 22. For PDM08, use its own input/output ratings and the corresponding PDM08 configuration chapters. The following feature chapters name other products whose manuals document each operation and explain the differences that affect the workflow.