LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

More
2 years 2 months ago #306847 by meister
do you run halcompile on the linuxcnc host ?
or at least you have to copy the rio.so (from halcompile) file to /usr/lib/linuxcnc/modules/ on the lcnc host

Please Log in or Create an account to join the conversation.

More
2 years 2 months ago - 2 years 2 months ago #306848 by Mecanix
meister post=306847 userid=19472
do you run halcompile on the linuxcnc host ?
or at least you have to copy the rio.so (from halcompile) file to /usr/lib/linuxcnc/modules/ on the lcnc host

yes of course, or else it wouln'd have connected to the fpga. From the host computer: $ sudo halcompile --install rio.c 

Can I bother you more and ask to see how you configure your network interface on your lcnc linux? Below is what mine look like. 
Code:
$ sudo nmcli con mod "Wired connection 2" ipv4.method manual ipv4.addr "192.168.10.194/8" ipv4.never-default "yes" $ sudo nmcli con up "Wired connection 2"  [img]https://i.postimg.cc/cLk1jnst/RIO3.png[/img]
Last edit: 2 years 2 months ago by Mecanix.

Please Log in or Create an account to join the conversation.

More
2 years 2 months ago #306849 by meister
your log say's: wrong header: 116, 105, 114, 119, 0,...

this is the tx header, it looks like you get the data back you have send (UDP-loop test or so).

the right rx header is: 97, 116, 97, 100,

Please Log in or Create an account to join the conversation.

More
2 years 2 months ago #306850 by meister
ahhh, ok, your lcnc host have the ip of the rio-interface, that explain also the udp-loop :)
set it to 192.168.10.1 or so

for subnet you can use 255.255.255.0 (bcast is than 192.168.10.255), but that should also work
The following user(s) said Thank You: Mecanix

Please Log in or Create an account to join the conversation.

More
2 years 2 months ago #306851 by Mecanix

ahhh, ok, your lcnc host have the ip of the rio-interface, that explain also the udp-loop :)
set it to 192.168.10.1 or so

for subnet you can use 255.255.255.0 (bcast is than 192.168.10.255), but that should also work
Ok that's great, at least we know why it doesn't work on this pc. If I set the interface IP to 192.168.10.1 then I can't ping the fpga anymore. I'm confused. For the record the FPGA/w5500 is connected directly into the Wired connection 2. 

Just to double confirm, you mean like this? (that doesn't work btw):
Code:
$ sudo nmcli con mod "Wired connection 2" ipv4.method manual ipv4.addr "192.168.10.1/8" ipv4.never-default "yes" $ sudo nmcli con up "Wired connection 2"
 

Please Log in or Create an account to join the conversation.

More
2 years 2 months ago #306852 by meister
i never used nmcli, so don' know, but i would use '192.168.10.1/24'

Please Log in or Create an account to join the conversation.

Time to create page: 0.267 seconds
Powered by Kunena Forum