Advanced Search

It might not be a trivial solution, but you could write a custom home component that takes the two pins as input. eg rough, then fine.
Ref: linuxcnc.org/docs/stable/html/man/man9/homecomp.9.html
Linuxcnc does this using home_latch_velocity eg fast sensing, then slow for accuraccy on the one pin.

Hi
Thanks for answer.
Its openloop. I think the second sensor that wait for the metal pin on the pulley makes the homing more accurate.

Sensor 1 rough homing to a reference marked area.
Sensor 2 then fine homing.
Call it 2 state homing?

Original is the secomd sensor used for 2 things..
Thing 1 homing accurate..
Thing 2 counts the pin everytime the pulley is turned full.
The full rotation means as example 400 steps done.. is the pin triggering the sensor befor or later then its out of position.
But i only want to use the secomd sensor for more precise homing.

This is not possible right? To make it possible it needs a special component or?

i found this:

github.com/mydani/linuxcnc_misc/blob/mai...e_index_stepdir.comp

looks like inside linuxcnc there is no other option.

thanks

I think you need to add a timer to call a function to read linuxcnc's stat.
Here is most of the odea - not tested:

You cannot connect an output pin to joint.N.index-enable
because joint.N.index-enable pins are bidirectional ("Tri-State")

When index is used for homing, LinuxCNC expects to use encoder
hardware to detect the actual index pin and signal that detection
to LinuxCNC via the joint.N.index-enable pin. joint.N.index-enable
is used as a bidirectional signal, that is, when LinuxCNC detects the
coarse home position, it then sets joint.N.index-enable true. This signals
the hardware to enable index detection. When the index is detected,
the hardware normally does two things: it clears (sets to false)
joint.N.index-enable (signaling LinuxCNC that the index has been detected)
and normally also zeros the position.

Does this joint have encoder feedback or it this an open-loop step/dir system?

If no encoder (and you have an up-to-date LinuxCNC installation) , there is firmware
that supports homing to index in open loop step/dir systems, so instead of connecting
a GPIO pin to joint.N.index-enable you would connect to hm2_7i92.0.stepgen.NN.index-enable
to joint.N.index-enable.




 

Hi!

i have here a axis which has 2 home sensors.
The first sensor is the reference.
the second is a sensor on the pulley.

how it works? Home to first sensor.. then go back until sensor 2 is active.

i the first sensor works on linuxcnc..then i add the second..
net index-sensor gpio001.... 
inet index-sensor joint...index-enable

but then i get error.. 

cant add i/o pin to index... its already output pin hm2_7192.0.gpio.005.in

in the ini i change the parameter for use index as true.. but this doesnt solve anything.

do i need to add a encoder in the bitfile or what is my failure??

thanks

Understanding this is not a quick answer I drop here an AI analysis of your sample atc_sim config. Maybe it can be a good starting point?

After several attempt to use the _ini() variables in my macro to move the table to the x/y offset location, I've finally just hard coded the values into the macro.  While this is not the ideal implementation, it does keep the values in a single location should I need to modify them in the future.

At this point I now have all of my gvcp buttons working except the combo box to select the current coordinate system to use for a given job.  I'll work on that option at a later date.  The key frustration is the inability to jog once the laser is toggled.

This is particularly interesting in that both the spindle enable and the spindle coolant are enabled via relays as well and neither of them inhibit jogging after they are activated. 

Does anyone have any suggestions regarding why the laser might inhibit jogging? 

These are the HAL commands associated with the laser:

# *** Crosshair laser Toggle and LED ***
net machine-is-on => gladevcp.crosshair-ctl-active
net crosshair-toggle-out <= gladevcp.crosshair-toggle
net crosshair-toggle-out => hm2_5i25.0.7i76.0.0.output-02
net crosshair-toggle-out => gladevcp.crosshair-led

I don't see anything that might be interfering with jogging.

Spindle-enable and coolant-flood, (I'm using M8 to cool my spindle), are configured as follows:
# --- SPINDLE-ENABLE ---
net spindle-enable  =>     hm2_5i25.0.7i76.0.0.output-00

# --- COOLANT-FLOOD ---
net coolant-flood  =>     hm2_5i25.0.7i76.0.0.output-01

The main difference that I notice is that these function are activated by LCNC signals. Maybe there is something associate with these two signals that needs to be added to the laser activation process.

I'm open to any suggestions that might point me in the right direction to resolve this issue.

Kind regard,
 

Hi, I also got my rpi5 and the 7c81 to run. First I had problems in the pncconf due to language settings. After this pncconf worked fine. Afterwards I had to change the hm2_spix in the created .hal

I'm trying to modify a GladeVCP to have a label that displays the current active work coordinate system.  And to put it bluntly Python is kicking my butt.  So how exactly would one set up the python handler file to read the linuxcnc stat.g5x_index then use that to change the string that is displayed in the gtk label? 
In my  GladeVCP the label I want to use is named "work_coord_label" and I would like the label to read "G54(front)" when the G54 coordinate system is active, and "G55(Rear)" when G55 is active.  (The other coordinate systems can meerly read G56,G57... as there is no plan to use them at this point.)

PS.  This is on a machine running Linuxcnc ver 2.7.25 (And I don't think I can ugrade because this system requires a very low latency RTAI config that I don't think I can easily replicate with newer versions.)

Thanks for your discussion. A few minutes ago I got my simple concept breadboard running with adaptive feed so that I can throw a physical switch that is attached to a GPIO pin on the Rpi5 and the trajectory backs up. As is typical, once I got some of the basic ideas of the HAL programming (thanks A METRIC TON to swolebro and his excellent tutorials!), I has able to hack a HAL file together. I now need to think more about the system architecture which relates to your discussion. Am I missing something or does the linuxCNC documentation lack one key element that is critical for the newbie: there are precious few if any examples of HAL command syntax in the documentation...not the case for most languages. I think including a few examples per command would greatly lower the learning curve.

This is normally what motion.spindle-at-speed is used for.
LinuxCNC checks motion.spindle-at-speed  after the
spindle speed has changed in the Gcode and pauses
the first cutting move after the spindle speed change until
motion.spindle-at-speed is true. 

If you have a way to read the spindle speed, usually the
"near" hal component is used to generate the spindle-at-speed
signal. This can also be done if the spindle drive has a signal to report
that is is at speed.

Note that this will not work if you want to stop or alter the feed rate
if the spindle slows during operation, as motion.spindle-at-speed is ignored
after the first cutting move that follows a spindle speed change.

If you need to alter or stop the feed if the spindle speed drops during operation,
you would need to use adaptive feed (motion.adaptive-speed) and some hal math
or logic.
 

Hi,
I looking for something can stop feed when spindle rpm is lower what is setup in G code S300 for example -15% and start feed when rpm back to S300.
 

Fixed setting up a new install on a desktop pc, the same configuration shows the ATC tab as it should.. now I need to figure out how to configure the ATC according to my setup :

1) I have a servo motor with 17 bit abs encoder with an unknown gear reduction due to this retrofitted ATC. Setup with an INPUT SCALE: 157.48 it takes from 0 to 255 units to make a full turn

2) How to implement it in Probe basic is there a documentation?

thanks for your time

Somehow now that I decided to ask fot it I guess I finally succesfully installed it. using the autoinstall option, during the installation it asks if you want to force UEFI, at that point if you answer NO the auto-partitioner create just two partitions instead of three.

Then it finally asks you where you want to install the GRUB bootloader. where /dev/sda is the location to set