SVCAN4IndSettings Structure
Remarks
Item | Description |
---|---|
can1 | See CAN_SETTINGS structure |
canfd1 | See CANFD_SETTINGS structure |
can2 | See CAN_SETTINGS structure |
canfd2 | See CANFD_SETTINGS structure |
ethernet | See ETHERNET_SETTINGS structure |
lin1 | See LIN_SETTINGS structure |
iso9141_kwp_settings | See ISO9141_KEYWORD2000_SETTINGS structure |
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 |
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 |
perf_en | Performance test.?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 |
network_enabled_on_boot | Not Defined |
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. |
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. |
Reserved | Reserved |
termination_enables | Bitfield containing the termination enables. For the neoVI Fire 2, the termination is grouped into banks. Only 2 form a single bank can be neabled. |
flags | Not used |
ethernet2 | See ETHERNET_SETTINGS structure |
Last updated