Advanced Search

That works! thanks for that little bit of advise. I could have saved myself the headache by asking right away.

wels wrote:

Is the DRO box the buttons added in settings, then yes. I just found that I need hal pin

qtplasmac.ext_laser_touchoff
I have to figure out where to put it and if it will work...

That is not quite right. You just need to finish the following hal connection in either the <machine_name>.hal file or the <machine_name>_connections.hal file, I cant remember where it is off the top of my head.

Then do the peripheral offsets part and the LASER button will show.

I would verify that the index works by manually setting the index enable signal
for the tested joint (via the halcmd sets command) and then manually moving
the axis past the index mark to see if the index enable signal gets cleared
at the index mark.

I am going to assume you made a custom button for your laser.  The LASER button in the DRO box is not shown until a offset is set, I reckon the user manual does not explicitly say that.  I'll mark it down to add it to the docs later.

Assuming you made the correct HAL connections

You need to use the peripheral offsets section to set the offset between the torch and the laser, and then the LASER button will appear. 

Is the DRO box the buttons added in settings, then yes. I just found that I need hal pin

qtplasmac.ext_laser_touchoff
I have to figure out where to put it and if it will work...

Did you make a custom user button for your Laser, or are you using the LASER button in the DRO box?

I forgot to mention that this is in QTPlasmaC

Another note on this, I don't have home limits, just the index it looks for. This could be the stem of my issue but the reference machine I am "copying" is the same setup with no limits just search for the index

I already wired in another small 12v PSU, it powers something on the heidenhain impulseformer so I'm not sure if that would introduce noise into the encoder input but I do have buck converters as well now that you mention it.

I am Trying to set up a laser to align the work to the sheet in QTPlasmaC, however, it does not appear to be working properly. In the owners manual it says it should change to mark edge and then mark origin. it just changes to show it is turned on. What am I missing?

Hi all,recently my pc running version 2.8.2 broke down and i had to replace it and installed 2.9.
Thankfully I kept a copy of all my files, so that helped me out a lot.After a couple of hours i got my setup to work again.
The only thing that doesn't work is tool measurement.The option in the advanced settings tab keeps getting greyed out.The line in preference file gets changed to when loading LinuxCNC: use_toolmeasurement = False

Usually when I did a manual tool change, the spindle moved to a certain location and than a popup shows up to change the tool. After clicking ok, the actual tool measurement is performed.
Now the machine doesn't move, it just shows the popup.

(Homing, moving, starting the spindle all works. )

 

Cooped-Up wrote:

Waiting on another power supply for 12v as one of my cards needs that rather than 24v the machine provides.

You can probably use a small buck-converter to source 12V from the 24V line, rather than use a whole PSU. 
 

sconisbee wrote:

Unfortunately, I’m still not getting a stable speed above 1900 rpm. I suspect this is due to the sampling of the 100 PPR disk — when I decrease the base period, the speed stabilises, and by reducing it further I’ve managed to get stable(ish) readings up to around 1900 rpm. Above that, HAL Scope just sees phase A as high rather than a pulse train.

1900 rpm and a 100 hole disc is 3.2kHz. What base thread rate are you running? a typical base thread of 25,000nS can count at 40kHz. 
(well, 10kHz allowing for oversamplng. I don't know if the Pi can do 25,000ns though) It's possible that something in the sensor path is electrically slow. 
 
Does Remora have faster encoder counters? 
 

I'm in the chat now with the same username as here.

Yeah the EC300 is the rt1052. Its become a slightly null point for the moment as I've managed to fix the issue temporarily. the pull up on the schmitt trigger for the opto interrupter sensor was too high off the shelf (cheapo Chinese modules) so the pulse width was way too wide, so above around 1800rpm it was just giving a logic high instead of pulses. now got a nice pulse train up until around 4500rpm so for now, i think this will work.