sven
/
icsscand
mirror of https://github.com/intrepidcs/icsscand.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
24 Commits
3 Branches
3 Tags
188 KiB
C++ 95.5%
CMake 4.5%
 
 
Go to file
Paul Hollinsky b5d56bc740 v2.1.0 
Update copyright date
Update to libicsneo v0.3.0
Report transmits down to the kernel for echo
Allow filtering devices by serial number
 		2022-03-31 18:18:33 -04:00
src Update copyright date to 2022 2022-03-31 18:13:23 -04:00
third-party Refactor for libicsneo v0.3.0 API changes 2022-03-31 15:41:19 -04:00
.gitignore Initial commit of Version 2.0.0, with CAN FD support 2019-05-02 19:23:12 -04:00
.gitmodules Initial commit of Version 2.0.0, with CAN FD support 2019-05-02 19:23:12 -04:00
CHANGELOG v2.1.0 2022-03-31 18:18:33 -04:00
CMakeLists.txt Refactor for libicsneo v0.3.0 API changes 2022-03-31 15:41:19 -04:00
LICENSE Update copyright date to 2022 2022-03-31 18:13:23 -04:00
README.md v2.1.0 2022-03-31 18:18:33 -04:00

README.md

Version 2.1.0

This is the usermode daemon for the Intrepid Control Systems SocketCAN support. This daemon requires that intrepid.ko is loaded on your system.

  1. Build and load the kernel module follwowing the instructions in intrepid-socketcan-kernel-module.

  2. Install the dependencies needed. These are CMake 3.2+, GCC 4.8+, git, libusb-1.0-0-dev, and libpcap.

On Ubuntu or other Debian-based systems, run sudo apt install git cmake gcc libusb-1.0-0-dev libpcap-dev build-essential.

  1. Clone this repository recursively by running git clone --recursive https://github.com/intrepidcs/icsscand.git

  2. Switch into the cloned directory, cd icsscand

  3. Make a build directory and switch into it, mkdir build && cd build

  4. Invoke CMake, cmake .. -DCMAKE_BUILD_TYPE=Release

  5. Build the daemon, make

  6. The daemon is now available as libicsneo-socketcan-daemon

  7. Start the daemon up to begin connecting to devices. Use sudo ./libicsneo-socketcan-daemon. If you're happy with the results and would like to run in the background, run sudo ./libicsneo-socketcan-daemon -d to run in daemon mode.

  8. CAN interfaces will have been created, but are "down" or, in other words, not enabled for transmit and receive yet. You can see them with ip link. They will be labelled can0, can1, and etc. They will have an alias listed which corresponds to the serial number of the device and network on that device.

  9. Enable the CAN interface with sudo ip link set can0 up, replacing can0 with whichever interface you'd like to enable

  10. You can now use any SocketCAN application with this interface. A good package for testing is the can-utils package. You can get this package with sudo apt install can-utils. A good testing tool which comes with this package is candump. Running candump can0 will print a line for every incoming frame.