Advanced Search

besriworld wrote:

I don't know if it's correct but I directly turn off the main power switch and everything goes off.

hehe! That is one way to do it! But I don't think Linux likes getting the power cut like that? Or is that assumption wrong?

/Thomas

Hi,

I use a "Odroid H4" as master and it has two network interfaces. Perfect for LinuxCNC with EtherCAT and cabled networking. However, I'm having the issue that both network interfaces shows up as if they both can connect to the internet: 


Two things annoy me:
1. Is there a way to rename these devices? The naming is kinda useless as it is and it bothers my OCD, preferably i'd call one Internet and the other EtherCAT or something like that, but i've seem to have tried everything google suggests me to rename them, without any luck...apparently not the correct one yet, ideas?
2. The top network card is the one connected to the internet...but every time the machine starts, it attempts to connect to "Internet connection" via the bottom one. These attempts causes the EtherCAT bus to reset every minute or so...to solve this i have to press "Disconnect" at the lower card and press "Internet connection" at the upper card...at every start of the system Can i somehow mark the EtherCAT card as "hands off!" for internet-stuff? And the internet is automagically connected via the upper one? First i thought "easy fix", i'll just swap cables and use it the other way around....BUT lo and behold, the problem was the exact same, but now the interfaces was just switched around...ideas?

I know this isn't "LinuxCNC and ethercat specifics", but i assume others here have had the same issues, so i hope it is ok...

/Thomas

I don't know if it's correct but I directly turn off the main power switch and everything goes off.

I've been wanting this to, so thanks for the input!....but.... how do you guys handle the shutting down process? Currently i'm quiting LinuxCNC with ctrl+q, going to Application-->Logoff in Debian and clicks Shutdown....waits untill the screen turns off and then flicking the main-switch on the machine.... is there a better way?

Hi,

I'm trying to setup the  Vers WLR v9 probe  and i got it working fine together with the Vers toolsetter. However, there is a pin out for errors. This triggers if there is issues with the communication for the probe(e.g. if it runs out of battery, is not turned on, communication fails and so), but how to configure this in HAL to halt the probe-cycle? First i thought about making some logic to check if motion-type is "probing" and combine that with the error pin. But the issue is the famous "one pin for all probing", so i don't think i "know" if i'm using the 3D probe and should monitor the error pin or i'm using the toolsetter and the 3D probe is intentional not active(causing the error-pin to trigger!). I've seen several posts about using M-codes to determine which probing cycle to run, but i've also seen people warn about this approach since it requires you to remember to use them each time....

Am i missing something obvious here or have others found a clever solution to this?

/Thomas