Advanced Search

Oh thank you so very much! I thought I was going crazy. Your explanation makes a lot of sense.

Might be nice to add a note to that document to clarify this as it's not incredibly obvious. I'm a LinuxCNC newby and I'm not sure of the protocol for making changes like this but if it's something I can or should do I'm happy to try adding a note. Thanks again!

and everything is right!
The fact is that the pin outs of the Raspberry are inputs for the LinuxCNC and vice versa...

You will see that if you configure input pins with hal_pi_gpio, in the halcmd show pin command they will be shown as OUT

 

I think if tool measuring button is pressed it should be set same as for tool height
but again, Im not the real CNC guy,
I can live with manual process, its good enough for me

I am using LinuxCNC to drive a PUMA type robot with brushed DC motors, encoders, and harmonics on each joint.  I have a 7i77 and 5i25 controlling 5 AMD motor drives for control.    Unfortunately, the joints do not have brakes, so every time get an FERROR fault, all drives are disabled and the arm drifts down until I can run over to the computer and re-enable the drives.
Can I alter my HAL file to pause after a fault and then re-enable the drives automatically?  I have found some messages that are on the right track like:
"I would use a combination of a timedelay hal component connected to the amp enable output, then the output of that to an and2 comp combined with the fault input from the drive, then the output of the and2 to motion.axis.N.amp-fault-in. This would essentially disable the amp's fault signal until the timdelay expires after turning on. "  from Todd Z

But, I've got to say - the HAL file is like my grasp of Spanish.  I can read it and get the gist of what is happening, but ask me to actually write something correct and I am illiterate.  I'm going to need some hand holding I'm afraid.

 

That is exactly the document I have been using. As a test I tried to configure just one GPIO pin as an output - but when I run Halcmd Show Pins in a terminal that pin is showing up with direction set to "in"

Is there any chance that I don't understand what "Show Pins" is reporting. What does "direction" mean in this context - is there any chance that I do want direction to be "in" for an output? That seems unlikely.

I will read and try it

Thanks

Hi,
lcnc 2.10-dev (builded from master)

I saw that,
I want to avoid multiple steps,
What I need is run a command from the dialog (by button from a dialog, or by external signal like pendant)
my imaginary flow be like
programm triger TxM6
it goes to change location
shows toolchange dialog
I change the tool by pressing additional button on a dialog / phisical button on a pendant
press OK
and it continue its procedure with qc_autotool_change macro

Im looking for a solution to overcome blocking during dialog or
replace that dialog with my own, without the need of changing dialog_widget.py file (and keep the changes all the time I update the lcnc)

all the rest would be handled by the program itself, including spindle speed, locations, ...

in short I want to have another action during manual change, since I dont need to work with wrenches rather button click

priv I had air release button closeby, but after rewiring all the air contorls goes to the back side of my cnc (
I would consider adding phisical button for tool replace later, but it would be through lcnc logic, not directly, means - I need lcnc be not blocked (

Thanks Todd for looking over my setup.

Your laying out of the not-so-clear configuration led me to move things where they belong. The Z-Axis Configuration is driven by Joint 3. But since I only added the second Y later, it came after the Z's definition.
When I changed the ordering I realised that my homeing Order wasn't correct either. Which led to the situation that LinuxCNC would try to home an axis that i hadn't attached yet (Z's Joint). Which then in turn would lead to a situation where Y and X would never home and me waiting forever. Having now fixed the priorities, axis do home as they should. Thanks for pushing me to it!

That said for the Gantry: does it make sense to use keep the trivial trajectory setup or would I rather use one of the available gantry components to manage Y? I havent really found pros and cons online. Both side of the gantry should are fixed by leadscrews so theres little to no tilting possible.

Thanks again,
Alessandro

danke es läuft schon es werden sicher andere config sachen auch kommen es musste einfach der pci-x adapter gegen einen anderen hersteller getauscht werden 

wir sind es gewohnt viele frösche zu küssen bis die prinzessin erscheint

danke für die inspiration

Yes, that looks correct.

Maybe try a 'toggle' component:
linuxcnc.org/docs/devel/html/man/man9/toggle.9.html

If you want an M5 gcode to shut your spindle off you would probably want to use an internal motion pin like 'spindle.0.on' and invert that.

linuxcnc.org/docs/html/man/man9/motion.9.html

Actually, looking at this more closely, it's probably specific to dmitrys Mechatrolink hardware as 'nyx' refers to his hardware driver:

Looks like you have an EtherCAT setup so my input is not really relevant after all.

[edit]
I would expect that you need set the gear ratio in the motor drives.

My present HAL spindle start, stop logic is working as desired except M05 commands in my gcode files are ignored.

I can change the OR gate to a 4 input (personality 0x204), however I'm not sure what signal I would use to drive that 4th input, or if there is an overall more elegant solution for spindle control. Note: I always manually start the spindle before hitting the run button for gcode execution, so I don't really need G03, G04 capability.

Suggestions please.
   

Hello Aciera,
Can you share your note here ?.
I searched in DH-parameters for Genserkins and Vismach/Melfa-sim, could not find your note or anything mentioned about absolute encoder
Thank you.