error counts when using transmitest
Posted: Fri 26. Feb 2016, 11:23
hi,
I'm using Ubuntu 15.04 32bit with kernel 3.19.0.51-generic
Im running on Ubuntu on a Virtual Box VM version 5.0.14
I've installed the latest drivers... peak-linux-driver-7.15.2
built to use Chardev version of drivers.
I have a loop back terminated cable connecting CAN1 and CAN2
this is my current cat /proc/pcan in screenshot.. I can use the transmitest and receivetest to send and receive the transmit.txt i see the output of receive test so i know i have installed the drivers and can run the test. However I get big error counts when I CTRL C on the transmit test I get in the attached screenshot..
This is a screenshot of what I get when just running transmit test.. when i run transmitest and receive test i get this after i press ctrl C on transmitest term.. more error counts.
Sometimes the Ubuntu VM locks up and I need to restart..
I've noticed also that CAN1 is running on pcan32 and CAN2 is pcan33 but sometimes .. it would swap to CAN1 on 34 and CAN2 on 35.. like it is still being used so has to allocate a new set..
any help would be appreciated .. i am very new to using PEAK and linux..
thank you,
Nick
I'm using Ubuntu 15.04 32bit with kernel 3.19.0.51-generic
Im running on Ubuntu on a Virtual Box VM version 5.0.14
I've installed the latest drivers... peak-linux-driver-7.15.2
built to use Chardev version of drivers.
I have a loop back terminated cable connecting CAN1 and CAN2
this is my current cat /proc/pcan in screenshot.. I can use the transmitest and receivetest to send and receive the transmit.txt i see the output of receive test so i know i have installed the drivers and can run the test. However I get big error counts when I CTRL C on the transmit test I get in the attached screenshot..
This is a screenshot of what I get when just running transmit test.. when i run transmitest and receive test i get this after i press ctrl C on transmitest term.. more error counts.
Sometimes the Ubuntu VM locks up and I need to restart..
I've noticed also that CAN1 is running on pcan32 and CAN2 is pcan33 but sometimes .. it would swap to CAN1 on 34 and CAN2 on 35.. like it is still being used so has to allocate a new set..
any help would be appreciated .. i am very new to using PEAK and linux..
thank you,
Nick