Inputs provide data to outputs for processing. They can be realtime sources or files that playback pre-recorded sequences.
Toggle: Simply a checkbox, disabled is 0, enabled is 1.
Constant: Input a value that is convertable to float32 and it will be output continually.
Sim: This input uses the simulation component which can be configured via the Car Setup tab. Note this input is not completed and does not quite perform as expected but can still be used to generate interesting signals to test with, they just don’t behave physically accurately.
- RPM – Current RPM of the engine
- Torque – Current Torque output of the engine (not transmission)
- Throttle – Current throttle input of the engine.
- Speed – Current speed of the vehicle
- Gear – Current gear – output continually not on change
- Gear Up – fires once when gear is changed up
- Gear Down – fires once when gear is changed down
- Engine Start – fires once when engine starts
- Engine Stop fires once when engien stops
CAN: Uses the PEAK PCAN device. Realtime CAN connection using PEAK sdk. Configure using the PEAK Panel button – configuration not covered here. You also need to load a DBC file for the network you are connected to. After this you can get all instances of the selected parameter, when they come in.
Traces: Grouped together for easier explanation. These all load recorded or generated files and play through them according to an internal timer. All these files have timestamps associated with parameters and those are used to determine when a parameter is output. The user will select which (of potentially many) parameters in the file is used for a given signal. The file can be loaded into multiple signals at once (its only loaded by the application once) so the user can select multiple parameters from a single file.
Trace (vector asc): Vector CAN export. This signal also needs a DBC file loaded in order to be parsed. Note that its possible to have a mismatching DBC file that still matches ID’s in the trace. Be sure they REALLY match or your outputs will make no sense.
Trace (trc): Peak CAN export. This signal also needs a DBC file loaded in order to be parsed. Note that its possible to have a mismatching DBC file that still matches ID’s in the trace. Be sure they REALLY match or your outputs will make no sense.
Trace (HDF xls): Excel file created by Head Acoustics software. This can easily be generated by the user as well.
Trace (raw asc): Raw ascii file also exported by Head Acoustics. This file has no metadata, so it isn’t very fun to work with.
SinGen: Generates a sine wave with the magnitude specified and an offset of 0. Phase offset can be applied.
If you use the Dynamic mode, then the frequency setting becomes a ratio of the selected signal INPUT (not output). The indices start at zero.
Control Poller: Requests the value of a control from a connected xAF device. Uses the loaded list of controls (Tools->Controls) to display the available controls. Has a configurable polling period which defaults to 10ms.
MIDI Input: Uses detected MIDI devices. User needs to select a device, and a type of event (Note On, Note Off, Control Change, and None).
- Note On: Sends Fires while the note is active, else 0.
- NoteOff: Fires a when the note ends, else outputs 0.
- ControlChange: Fires on any change of a control.
- None: Nothing.
For each of these types you will get an associated list of sub-types. For notes you get piano keys, for controls you get a list of some named control types but many numbers. You will have to discover which match your device’s controls. You can use the Input section (‘Select Input’ -> ‘Midi’ then look at ‘Real-time data’) to see control messages as they come in from the device.
Since MIDI is only 0-127 – we have scaling (multiplying) and offset (adding) fields so you can move the value into a useful range. Scaling is applied first. E.g. input value of 10 from midi. Scale is 20 so the value becomes 200. Offset is -40 so the value becomes 160.