PaulG. Posted October 27, 2009 Report Share Posted October 27, 2009 Our company has been getting an increasing number of orders for devices that use CAN bus. I have zero CAN bus experience so I'm shopping for a good (and preferably cheap) CAN interface/adapter that comes with handy-dandy LabVIEW drivers and/or examples to use for testing. Thanks in advance. Quote Link to comment
ShaunR Posted October 27, 2009 Report Share Posted October 27, 2009 Our company has been getting an increasing number of orders for devices that use CAN bus. I have zero CAN bus experience so I'm shopping for a good (and preferably cheap) CAN interface/adapter that comes with handy-dandy LabVIEW drivers and/or examples to use for testing. Thanks in advance. As its your first time, go with what you know! http://www.ni.com/can/ Quote Link to comment
PaulG. Posted October 27, 2009 Author Report Share Posted October 27, 2009 I went to NI first. Too many choices. Quote Link to comment
ShaunR Posted October 27, 2009 Report Share Posted October 27, 2009 I went to NI first. Too many choices. The main difference between them is the speed. What devices are you intending to talk to? Quote Link to comment
crelf Posted October 27, 2009 Report Share Posted October 27, 2009 I have zero CAN bus experience so I'm shopping for a good (and preferably cheap) CAN interface/adapter that comes with handy-dandy LabVIEW drivers and/or examples to use for testing. NI also sells a really good CAN device simulator that's great for dipping your toes in the water. 1 Quote Link to comment
jcarmody Posted October 27, 2009 Report Share Posted October 27, 2009 Our company has been getting an increasing number of orders for devices that use CAN bus. I have zero CAN bus experience so I'm shopping for a good (and preferably cheap) CAN interface/adapter that comes with handy-dandy LabVIEW drivers and/or examples to use for testing. Thanks in advance. We've had good luck with Kvaser CAN devices; our CLA prefers them to NI and ValueCAN. They're cheaper, too. http://www.kvaser.com/can/ Quote Link to comment
PaulG. Posted October 27, 2009 Author Report Share Posted October 27, 2009 The main difference between them is the speed. What devices are you intending to talk to? We mostly deal with ISO 11898-2 type CAN's, 1 Mbits/sec, but I don't think we really need that level of speed. We don't do design validation. Just functional testing of printed circuit assemblies. Quote Link to comment
hooovahh Posted October 27, 2009 Report Share Posted October 27, 2009 I've done some work with VectorCAN stuff but I wasn't impressed. The NI CAN devices would of worked better for what we needed, but since Vector is more specialized maybe if we were trying to do more crazy things than just read they would have been the product to have. Quote Link to comment
Jarimatti Valkonen Posted October 28, 2009 Report Share Posted October 28, 2009 We've had good luck with Kvaser CAN devices; our CLA prefers them to NI and ValueCAN. They're cheaper, too. http://www.kvaser.com/can/ We've also used Kvaser CAN devices with LabVIEW. They work OK. The programming may take a bit more time with them compared to the NI hardware. The CAN Frame Channel Conversion Library was quite useful in that specific instance. I don't remember why we didn't use the CAN Channel API. Was it that it's only for NI devices? Quote Link to comment
ned Posted October 28, 2009 Report Share Posted October 28, 2009 We've also used Kvaser CAN devices with LabVIEW. They work OK. The programming may take a bit more time with them compared to the NI hardware. The CAN Frame Channel Conversion Library was quite useful in that specific instance. I don't remember why we didn't use the CAN Channel API. Was it that it's only for NI devices? Yup, the CAN Channel API is only for NI hardware. I recall doing something similar once: reading raw CAN frames from a KVASER card, writing them to one of the NI-CAN simulated interfaces configured for frames, and reading them back from the other simulated interface configured for channels. This was actually easy to set up, and I had good experiences with the KVASER hardware and software tools. Quote Link to comment
hooovahh Posted October 28, 2009 Report Share Posted October 28, 2009 The CAN Frame Channel Conversion Library was quite useful in that specific instance. I don't remember why we didn't use the CAN Channel API. Was it that it's only for NI devices? I believe that Channel API also does not work on any NI USB device, so it would also need the Frame to Channel conversion library. We've also used that library on a FPGA CAN device, where all you receive is a raw stream of bytes. We passed that to the host main, which had an engine running that simply took it, converted it to channel API, and then put it on the virtual CAN bus (CAN256 I believe) and then any where in the code any engine could read CAN 257 as Channel and read what was on the CAN bus that the FPGA was connected to. I think NI has examples on how to do this. Quote Link to comment
Mellroth Posted October 29, 2009 Report Share Posted October 29, 2009 I went to NI first. Too many choices. If you first decide to go with the new XNET boards, you get down to a more reasonable amount of boards. We have been using both the Series2 and XNET boards, and the biggest problem with the Series2 boards is the amount of on-board memory that limits the number of frames you can handle autonomously. With XNET this is solved, each port have separate buffers for output and input (the older boards shared one buffer for all ports and directions). XNET also support bus-termination, that can be set from SW. In our cases we do a lot of fault insertion (skipping X frames, inserting erroneous parameters in the frames etc.) and handle J1939 TP.BAM-TP.DT transfers. Due to this, we have to create our own engine above the NI-CAN or XNET layers. In this scenario XNET really outperforms the NI-CAN, both in terms of actual time it takes to get information to/from the driver, but also in jittering (which is much lower for XNET). One thing that is missing in XNET compared to NI-CAN, is the ability to run simulated interfaces. /J Quote Link to comment
Bjarne Joergensen Posted October 30, 2009 Report Share Posted October 30, 2009 Hi At my company we use ESD-CAN from: http://www.esd-electronics.com/ They work very well and there is a good debugging tool too. regards Bjarne Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.