Advanced Search

AMD still has driver support on Linux for the 500 series gpus. I'll try using my integrated graphics but it hasn't worked before. Which is why I have a card in the first place.

Amd readeon RX560

Non-existant user wrote:

Should we delete the two duplicate replies above without the quoted text?

Yes please, i tried it myself but i guess that is not possible. Thanks!

OpenGL issues, what graphic card does the PC use?
Can it be removed? If yes, remove it and test with the onboard video.

PCW wrote:

if estop-latch.N.ok-out goes false, one of these must have changed:

estop-latch.N.ok-in  goes false
estop-latch.N.fault-in goes true

So I would watch these in halshow or halscope to see whats happening.

I also don't understand why you have two estop latches. It seems that one
should be sufficient (adding some logic if you need to add fault inputs or OK inputs)

 

Hi, thank you for your quick reply. I have been looking at these halshow/scope bits but could not get it to click.

I have tried with two latches, with the idea that one will be for external estop (input 00) and the other for software internal estop (user enable out).
I also tried with one, linking the ok-in for user-enable out and fault-in to input00 external estop. No succes.

I will keep trying, thanks.

If you have any more sugestions i would be happy to hear them.

Unlogic wrote:

I documented my e-stop setup using an external safety relay in the post linked below:

forum.linuxcnc.org/12-milling/50559-opti...rsion?start=0#284533

Maybe it will help you get your setup up and running.

 

Hi, thank you for your reply. I have read your documents on your build, very impressive, thanks for the detailed sharing and documenting.
I saw you used the oneshot function, i have tried implementing it like you did but no succes. I will try again once i got the time.

Thanks, cheers

This solution worked, but when i try to start my cnc file, it gives me an error. error report in the attached file.

Thanks for the tip. It was loading the wrong file.

HAL files specified in the HALFILES variable are found using a search. If the named file is found in the directory containing the INI file, it is used. If the named file is not found in this INI file directory, a search is made using a system library of HAL files.

tommylight wrote:

Yes it is as the change must also be reflected in HAL, so it would require having two of the same configs with and without the inverted input, very easy to do and use, but can not be used if both are to be used in the same run.
NO or NC does not matter much, but having both NC would make it possible to use the same input when wired in series.

Today the z probe arrived, I connected it to pin 11 which is where I have the 3d probe. In the hall file I have removed the "-not" so that it works like NC. I have configured it as a basic probe and it works correctly.

Now what I need is to connect it to the same input as the 3d probe (the 3d probe is NO) if possible. I have searched for information but the truth is that I have no idea how to do it.