SVCAN3Settings Structure
his structure defines various settings for the ValueCAN3 device.
Remarks
Structure Element
CAN_SETTINGS can1
CAN_SETTINGS can2
icscm_uint16 network_enables
Bitfield containing the software license enables. Depending on the hardware license purchased the customer may have to conditionally select which hardware channels to enable. For example the neoVI Red license allows the user to enable any 2 Dual Wire CAN channels and any 2 LIN channels. To enable a specific network its corresponding bit must be set (1). In order to transmit or receive on a network it must be enabled.
Bit field values:
HSCAN1 : 0 MSCAN : 1
icscm_uint16 network_enabled_on_boot
Normally neoVI only initiates its comm channels when CoreMini is running or if neoVI is online with DLL/Vehicle Spy 3. Practically this means the the CAN controllers stay in Listen Only mode until the device goes online. Once online the neoVI loads the user settings. Setting this parameter to 1 will change this behavior so that the neoVI enables its controllers immediately on boot.
Default value = 0.
icscm_int16 iso15765_separation_time_offset
In an ISO15765-2 Transmission, the receiver transmits a flow control message that informs that transmitter how much time there should be between individual CAN messages. This parameter allows the user to shift that spacing to make it smaller or larger. Valid range is -1563 to 1563 units where each unit represents 6.4us. Defaults to 0. If IFS plus the offset is negative than the Tx Messages will be back to back.
Default value = 0.
Examples:
ISO15765-2 Tx Message Inner frame spacing is exactly what is specified in flow control message: iso15765_separation_time_offset = 0
ISO15765-2 Tx Message Inner frame spacing is what’s specified in flow control message.+ 998.4 us: iso15765_separation_time_offset = 156
ISO15765-2 Tx Message Inner frame spacing is what’s specified in flow control message.- 998.4 us: iso15765_separation_time_offset = -156
icscm_uint16 perf_en
icscm_uint16 misc_io_initial_ddr
MISC IO Initial Data Direction Register. Controls the initial data direction of the tristates on all misc digital pins. Each bit corresponds to an individual misc pin. Bit value of 0 signifies an input and bit value 1 signifies and output. Bit values corresponding to non existent pins (EX MISC7-MISC15 on FIRE) have no effect.
Default value = 0.
Examples:
Set MISC1 to be output, all else input: misc_io_initial_ddr = 1
Set MISC1and MISC2 to be output, all else input: misc_io_initial_ddr = 3 (11 binary)
Set all MISC pins to output: misc_io_initial_ddr = 65535 (1111111111111111 binary)
icscm_uint16 misc_io_initial_latch
MISC IO Initial Latch Register. Controls the initial output latch value on all misc digital pins. Each bit corresponds to an individual misc pin. Bit value of 0 signifies an low voltage (ground) and bit value 1 signifies high voltage (3.3 V). Bit values corresponding to non existent pins (EX MISC7-MISC15 on FIRE) have no effect.
Default value = 0.
Examples:
Set MISC1 to be high, all else low: misc_io_initial_latch = 1
Set MISC1and MISC2 to be high, all else low: misc_io_initial_latch = 3 (11 binary)
Set all MISC pins to high: misc_io_initial_latch = 65535 (1111111111111111 binary)
Note: In order for digital outputs to work correctly the corresponding bit in misc_io_initial_ddr must be set to output and corresponding bit in misc_io_analog_enable must be cleared.
icscm_uint16 misc_io_report_period
Period in milliseconds of device report message holding digital and analog data.
Note: Periodic reporting requires misc_io_on_report_events[0] to be set.
icscm_uint16 misc_io_on_report_events
Bitfield holding enables for various report triggers for the General IO report.
Default value = 0.
Bit field values:
Last updated