SVCAN412Settings Structure
This structure defines various settings for the ValueCAN4-1 and ValueCAN4-2 devices.
C/C++ Declare
typedef struct __declspec (align(2))Visual Basic .NET Declare
<StructLayout(LayoutKind.Sequential, Pack:=2)> Public Structure SVCAN412SettingsC# .NET Declare
[StructLayout(LayoutKind.Sequential,Pack=2)]Item | Description | ||
---|---|---|---|
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 | ||
network_enables | Bitfield
containing the software license enables. 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.
| ||
termination_enables | Bitfield
containing the enables for CAN Termination. To
enable a specific channel its corresponding bit must be set (1). .
| ||
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 | ||
text_api | See STextAPISettings structure | ||
flags | Bitfield with misc settings for the device. List below gives the parameter
with the bit number to have set to enable. Disable USB Check On Boot : 0 |
IntrepidCS API Documentation - (C) Copyright 2000-2022 Intrepid Control Systems, Inc. |
Last Updated : Thursday, August 16, 2018