PCI-8513

[LeeDT]

Hi, 

I had a Labview application using "On RTSI Input - Transmit CAN frame" feature on CAN series 1 hardware. Now we are plan to migrating the series 1 CAN hardware to NI-XNET (PCI-8513); While the application run, Error message as below shown.

Error - 1074388559 occurred at NI-CAN Configure CAN Object - RTSI   

Is this causing by hardware not compatible among NI-XNET card & series 1 NI-CAN application? If yes, any workaround on this so that the existing code is still reusable since we are thinking to upgrade the hardware only, not software. 

I'm already installed NI-XNET Compatibility Library for NI-CAN and also NI-CAN 2.7

Thanks for your advice in advance. 

[Muthuraman]

Hi,

This is not an answer to the previous post. I have similar issue.

I am planning to replace NI - CAN - S1 with NI XNET 8513 (Any form factor). The software i used earlier with NI-CAN-Series 1 is NI CAN 2.1.

https://www.ni.com/en-us/shop/model/pxi-8513.html

The above ni link says that API support for XNET is provided by NI CAN (Frame & Channel).

does that mean i need not change (or minimal change is needed)  the software used for NI-CAN-S1 even though i am replacing it with XNET 8513.

Simply put in as a single sentence "Only hardware needs to be replaced and software retained", the solution will still work for CAN protocol.

Thanks,

Muthuraman S

[Gibson]

thats right. please check the NICAN Manual Chapter F for more information

The NI-XNET Compatibility Library for NI-CAN is a software layer added
as part of NI-XNET. This software layer enables code that uses Frame or
Channel APIs to work with NI-XNET CAN (not FlexRay) hardware, where
compatibility between the older APIs and the new driver and hardware is
possible. As a result, you can use the new NI-XNET hardware under the
more limited capabilities of the previous APIs, while you can develop
NI-XNET native versions to take advantage of greater native performance.
Even without native NI-XNET code, the side-by-side performance of the
same NI-CAN code using NI-XNET hardware under compatibility can
provide an upgrade over older hardware.

esp on Page F-4 you ll find an overvierw of all functions and properties which may have broken compatibility

the feature ncConfigCANObjRTSI.vi

RTSI mode:
on RTSI input—transmit CAN frame,
on RTSI input—timestamp RTSI event,
RTSI output on receiving CAN frame,
RTSI output on transmitting CAN frame,
RTSI output on ncAction call

is listed as not supported through the XNET Compatibility Library

[Muthuraman]

Gibson,

Thanks for your suggestions. It was really helpful.

Appreciate it.

Regards,

Muthuraman S