SRADPlutoSettings Structure
This structure defines various settings for the RAD Pluto device.
Remarks
perf_en
Performance test. Default value = 0
can1
See CAN_SETTINGS structure
canfd1
See CANFD_SETTINGS structure
can2
See CAN_SETTINGS structure
canfd2
See CANFD_SETTINGS structure
lin1
See LIN_SETTINGS structure
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.
HSCAN : 0
LIN1 : 2
HSCAN2 : 5
network_enables_2
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.
Ethernet : 13
network_enables_3
Not used. Set to 0
termination_enables
Bitfield containing the termination enables.
HSCAN : 0
HSCAN2 : 5
misc_io_analog_enable
Not Used, set to 0.
pwr_man_timeout
Number of milliseconds of no bus activity required before neoVI enters low power mode. Note pwr_man_enable must be set for power management to be enabled.
Default value = 10000
pwr_man_enable
1 = enable Power Management, 0 = disable.
Default value = 0
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
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
iso9141_kwp_enable_reserved
Reserved
iso_tester_pullup_enable
Not used Set to 0
iso_parity
ISO9141 Parity setting: 0 - no parity, 1 - even, 2 - odd
iso_msg_termination
ISO9141 message termination setting: 0 - use inner frame time 1 - GME CIM-SCL
iso9141_kwp_settings_1
See ISO9141_KEYWORD2000_SETTINGS structure
ethernet
See ETHERNET_SETTINGS structure
text_api
See STextAPISettings structure
Flags
Set to 0
custom
See SPluto_CustomParams structure
Last updated