02-15-2007 04:35 AM
02-15-2007 04:52 AM - edited 02-15-2007 04:52 AM
Just to add some useful facts:
I use NICAN 2.4.
I found out that the error code on some pages is referred to not as due to an unsupported feature but trying to configure an object that is already open and in use. This is not the case in my code (then it would probably not work with the PCI card either), the error comes at the very first use of the object - the initial configuration. The only thing that has been done prior to running that configuration is configuration of the channel (CAN0 object), there is no code running in parallell with this, it's all very straight forward (configure and open CAN0 - no errors, configure STD0...error).
Message Edited by Mads on 02-15-2007 04:53 AM
02-15-2007 08:07 AM
02-15-2007 08:25 AM
Ouch, that's a bummer...(is it just me or is that limitation rather invisible on the product page?)
Thanks for the answer
02-16-2007 08:24 AM
Hi,
Yes you are right, there is no word online. Only the readme and the manual do mention the fact, that only the Network Interface Object is supported.
I agree, we need this information online as well. I have triggered the right people already to change the online documentation.
Right now, hopefully you get around this limitation. The biggest problem perhaps is the periodic transmission, which has to be done with USB in Software.
If you dont get around, please contact your Sales Representative.
DirkW
03-07-2007 09:17 AM
03-08-2007 08:20 AM - last edited on 01-26-2024 04:53 PM by migration-bot
Hi,
Yes thats correct the CANopen Library uses objects for some periodic tasks and the 847x USB CAN does not support object communication. Thus no CANopen Library support for the USB CAN dvices. Sorry.
See the KB for these and other USB CAN limits: ni-can function call support for 847x devices
DirkW