The value of Lawicel 2.0 is more in standardization of a serial interface. This would lead to very high performance and better socketcan support than you get from SLCAN. Then as soon as you plug it in you’d get can0, can1, can 2. It’d be possible with a custom native driver (no serial in between, a socketcan driver hardware to CAN in one shot) to get three socketcan interfaces out of the M2: two CAN and one SWCAN. The hardware would have to expose multiple serial ports (theoretically possible) or SLCAN would have to be modified and those modifications up-streamed so that people can download the new version on whatever version of linux they’re using. SLCAN just supports one CAN device per serial port. There are LOTS of them out there - Caring Caribou, can-utils, etc. So, if you are using linux and don’t want to use Savv圜AN (it’s available for linux too) then you can use most any other socketcan compatible program. Look up lawicel and socketcan and M2RET will present itself as a valid lawicel device on linux and support socketcan. It is still serial on linux but there is serial socketcan and you can use it.
As luck would have it, M2RET supports that too. On linux there is a standard that all drivers can use and then any program that is socketcan compatible can use any adapter that is socketcan compatible. Every adapter has a different driver that talks a different way and programs have to include code to talk to all of the adapters they want to talk to. Really, as Rod kind of alluded to, there is no such thing in Windows. But, there is no Windows driver to make it some sort of generic CAN device that you can use with other programs. Or Savv圜AN if you’re more partial to GUIs. Then any serial port program like RealTerm or PuTTY can be used to communicate. Yeah, you will need to load M2RET onto the M2 to make it able to send and receive CAN traffic.
0 kommentar(er)
