SRADStar2Settings Structure

Structure defining the parameters in SRADStar2Settings

C/C++ Declare

typedef struct __declspec (align(2))
{
   uint16_t perf_en;
   OP_ETH_GENERAL_SETTINGS opEthGen;
   OP_ETH_SETTINGS opEth1;
   OP_ETH_SETTINGS opEth2;
   CAN_SETTINGS can1;
   CANFD_SETTINGS canfd1;
   CAN_SETTINGS can2;
   CANFD_SETTINGS canfd2;
   uint16_t network_enables;
   uint16_t network_enables_2;
   LIN_SETTINGS lin1;
   uint16_t misc_io_initial_ddr;
   uint16_t misc_io_initial_latch;
   uint16_t misc_io_report_period;
   uint16_t misc_io_on_report_events;
   uint16_t misc_io_analog_enable;
   uint16_t ain_sample_period;
   uint16_t ain_threshold;
   uint32_t pwr_man_timeout;
   uint16_t pwr_man_enable;
   uint16_t network_enabled_on_boot;
   uint16_t iso15765_separation_time_offset;
   uint16_t iso_9141_kwp_enable_reserved;
   ISO9141_KEYWORD2000_SETTINGS iso9141_kwp_settings_1;
   uint16_t iso_parity_1;
   uint16_t iso_msg_termination_1;
   uint16_t idle_wakeup_network_enables_1;
   uint16_t idle_wakeup_network_enables_2;
   uint16_t network_enables_3;
   uint16_t idle_wakeup_network_enables_3;
   uint16_t can_switch_mode;
   STextAPISettings text_api;
   uint16_t pc_com_mode;
   TIMESYNC_ICSHARDWARE_SETTINGS timeSyncSettings;
   unsigned short hwComLatencyTestEn;
   RAD_REPORTING_SETTINGS reporting;
   ETHERNET_SETTINGS2 ethernet;
   RAD_GPTP_SETTINGS gPTP;
}SRADStar2Settings;

Visual Basic .NET Declare

C# .NET Declare

Remarks

Item	Description
perf_en	Performance test. Default value = 0
opEthGen	See OP_ETH_GENERAL_SETTINGS structure
opEth1	See OP_ETH_SETTINGS structure
opEth2	See OP_ETH_SETTINGS structure
can1	See CAN_SETTINGS structure
canfd1	See CANFD_SETTINGS structure
can2	See CAN_SETTINGS structure
canfd2	See CANFD_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.
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.
lin1	See LIN_SETTINGS structure
misc_io_initial_ddr	Not Used
misc_io_initial_latch	Not Used
misc_io_report_period	Not Used
misc_io_on_report_events	Not Used
misc_io_analog_enable	Not Used
ain_sample_period	Not Used
ain_threshold	Not Used
pwr_man_timeout	Not Used
pwr_man_enable	Not Used
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
iso_9141_kwp_enable_reserved	Not Available
iso9141_kwp_settings_1	See ISO9141_KEYWORD2000_SETTINGS structure
iso_parity_1	ISO9141 Parity setting: 0 - no parity, 1 - even, 2 - odd
iso_msg_termination_1	Not Available
idle_wakeup_network_enables_1	Bitfield containing list of hardware networks to look at for sleep enable. 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.
idle_wakeup_network_enables_2	Bitfield containing list of hardware networks to look at for sleep enable. 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.
network_enables_3	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.
idle_wakeup_network_enables_3	Not Available
can_switch_mode	Not Available
text_api	See STextAPISettings structure
pc_com_mode	Not Available
timeSyncSettings	See TIMESYNC_ICSHARDWARE_SETTINGS structure
hwComLatencyTestEn	Not Available
reporting	See RAD_REPORTING_SETTINGS structure
ethernet	See ETHERNET_SETTINGS2 structure
gPTP	See RAD_GPTP_SETTINGS structure