I connected CANopen bus. connection is correct, as shown in Figure
after rebooting the controller connection is lost, as shown in the figure. Diagnosis of an error. "NetID 0: No CAN driver"
after the operation "Tool -> Update Beaglebone Black" the connection is restored, as shown in the figure
What is the reason and what can be done?
I tried different versions of packages (18.104.22.168 and 22.214.171.124)
CoDeSys version 3.5 SP9+
I'm use bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img
at moment no idea why this happens.
Have no hw here to check. But never seen it before.
Somehow the can driver is not ready at the point when the runtime is starting up.
Could you test if a restart lead to a working bootproject
/etc/init.d/codesyscontrol stop/etc/init.d/codesyscontrol start
cat /tmp/codesyscontrol.log and give us this output.
Happy New Year!
Thank you for responding quickly.
I am able to check only on 9 January.
Just write the result.
1) After reboot saved log file -
Socket_CanMiniDriver_Setup: using /opt/codesys/scripts/rts_set_baud.sh
Socket_CanMiniDriver_Setup: registering can interface 0
openRxSocket: Opened socket for reading (can0)
openRxSocket: ioctl(SIOCGIFINDEX): No such device
canopen bus NOT worked
2) After restart working bootproject
/etc/init.d/codesyscontrol start) saved log file -
not exist error ioctl for can0
canopen bus worked
Somehow the can driver is not ready at the point when the runtime is starting up?
Help me, please!
codesyscontrol_after_reboot.zip [3.18 KiB]
codesyscontrol_after_stop_start_service.zip [3.69 KiB]
I found a temporary solution.
I edited file /etc/rc.local
and add next strings:
systemctl stop codesyscontrol
systemctl start codesyscontrol
CAN bus work after a reboot, but now the boot is taking longer than 16 seconds.
Something wrong in codesyscontrol!
Need help developers!
bbb_canopen_slave.zip [942.14 KiB]
bbb_canopen_master.zip [703.71 KiB]
our problem at the moment is on our board this does not happen.
Then can0 interface starts relieable.
So I would give this a try:
add in /etc/network/Interfaces then can0 interface
iface can0 inet static
Could you please try this an give a feedback if this solves it reliable for every startup?
Thanks for the advice!
I'll try tomorrow and I will write immediately.
Network settings work through the file /etc/network/interfaces in Debian 8.6?
I thought all the network settings in Debian 8.6 (Jessie) made through the service ConnMan, and file /etc/network/interfaces is not used.
The original post I got this from can be found here: https://groups.google.com/forum/#!topic ... fNwIk_dWlg.
Thanks to Brian Anderson for the original comment.
I'm try add in /etc/network/Interfaces then can0 interface
iface can0 inet static
(After restart BBB, command ifconfig not show can0)
What else can I try?
Same problem with my app. Thank you alt your previous post, it was very helpful for me (rc-local solution).
One more thing... Have you any experience, whats happening when BBB starting on the CANbus, because I have an other CAN capable device and if BBB starting then the other device going to wrong?! It means the ARM processor will stop when my BBB booting.
Log in to post a comment.