From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

Timestamping and Latency for CAN USB 8473

I will be having my Labview application running on a Windows based system.  

 

This application shall be sending and receiving data over CAN USB 8473. 

 

 

The specs say:  Hardware timestamping – 1 μs resolution

 

 

Does it mean that I will be able to get the data at a resolution of 1 us even if windows cannot go faster that 1 ms.?

Does it mean that this device will have an internal clock to do the same?

Does this device have an internal buffer? If yes, how long will it hold the data (1s, 2 s, 10s, etc.) ?

 

0 Kudos
Message 1 of 2
(6,110 Views)

the 1µs refers to the timestamping which is provided by the internal clock of the USB hardware

The internal buffer of the USB 8473 is pretty small and can buffer only a few frames, if this buffer is getting filled the frames will be transmitted to the host queue which can be configured in size.

 

refer to the NI-CAN manual for details on using queues

 

Here an overview:

 

Using Queues
To maintain an ordered history of data transfers, NI-CAN supports the use
of queues, also known as FIFO (first-in-first-out) buffers. The basic
behavior of such queues is common to all NI-CAN objects.
There are two basic types of NI-CAN queues: the read queue and the write
queue. NI-CAN uses the read queue to store incoming network data items
in the order they arrive. You access the read queue using ncRead to obtain
the data. NI-CAN uses the write queue to transmit network frames one at a
time using the network interface hardware. You access the write queue
using ncWrite to store network data items for transmission.

 

Read Queue Length is the maximum number of unread frames for the read queue of the CAN Network Interface Object.
A typical value is 100. For more information, refer to ncReadNetMult.vi. The internal read queue exists between the CAN hardware and the NI-CAN device driver. This internal read queue holds frames temporarily prior to transfer a larger queue in the NI-CAN device
driver. The larger NI-CAN device driver queue grows as needed in order to accommodate high bus loads. For more information on reading from the CAN Network
Interface Object, refer to ncReadNetMult.vi.

 

 

Message 2 of 2
(6,064 Views)