Advanced Search

cmorley wrote:

If you use a graphic display , the file is checked each time it is loaded.
Look here how that is actually done:
github.com/LinuxCNC/linuxcnc/blob/master...qt5_graphics.py#L350
 

Thanks for your reply, I dont wanna use graphic display. I simply just want to know if I select a file from a file browser for example, or even a list of gcode files, it returns me an error with some details about the gcode syntax error in that file
I studied the link you've provided but it was so complicated. I didnt get it well

Can you share your ini file and tool change macro ? 

 

What 'driver' config should be used for the Rtelligent ECT86?

I just set it to one of the Gekko's until I could figure out something better, but obviously you likely already have.

Thanks

I am trying to get a tool length sensor setup and as I have not worked with LinuxCNC in a long time, getting this figured out is going to a be a bit slow.  I would much rather spend my time making stuff than fighting with software. 

This may sound strange but are any of you interested in being paid for a few hours of consulting to help me get things running?

I am in France at the moment (I am am American mechanical engineer who lives in Norway but has a workshop in France just to make things interesting  

I have this setter  www.sorotec.de/shop/Z-Finder-inductiv-PN...865.html?language=en 
and am running a Mesa 7I76-5I25 cards on a small CNC router ( cncwerk.de/forum/viewtopic.php?f=2&t=21) with a ER spindle motor.

Thanks 
Luke 

I have never used EtherCat with Raspberry so I can't answer you.
However, I read on the forum that others have had a similar problem
(forum.linuxcnc.org/9-installing-linuxcnc...ectory-lib-modules-6 -1-0-25-rt-amd64#310761).
Maybe you can find some useful information there.

I tried in qt_vismach.py ​​in the same way as in the screenshot, but then the color of the entire generated path changes depending on the type of movement. 
Maybe draw separate paths for each color, then it will be easier to turn off the selected path?

It os working now, thanks for the tip !

More info, please.
About the hardware....

So I've found something interesting, I have configured a machine, done bench testing, everything seems good.
Only issue is the estop, it seems to only trigger on the transition from input high to input low. My estop is wired how I would say is standard, normally closed contact, if the wire is cut then estop will trigger.  I also tried the reverse situation, so high input is estop condition, but it will allow me to start the machine in an estop condition, until I clear the estop then activate it again. I probably haven't explained this well but the machine shouldn't startup with a hardware estop active. Actually now I think about it setting up a hardware estop when I was using a MESA card disabled the software estop button and relied on hardware estop, only the software enable button worked. Has anyone else encountered this ?

 
This is the laws of physics at work.
Velocity and acceleration is king for plasma
Acceleration determines the maximum arc radius that can be negotiated without slowing down

Design you parts to not have sharp corners or loop the corners.

connect spindle.0.speed-out-rps to spindle.0.speed-in

something like this assuming neither of these pins are already connected to a signal:

net fake-spindle-feedback spindle.0.speed-out-rps spindle.0.speed-in

A little more difficult, as vismach doesn't know anything about the type of move, only that it has moved. I'll experiment a bit.

It sure seems useful if vismach and the normal plotter could be combined.

Your spindle encoder is directly driven by the spindle, just checking.

Hi everybody,
I will try to explain the situation the best I can.
I build myself a CNC Mill and it ran great for many projects, no issues at all. One day, I started a job and I found the Y axis completely crashed in the ballscrew bearing block with the drive in error. 

I get no problem while jogging only, when executing a program and it only happens after a couple of hours of the job. I tried lowering the max speeds, accelaration, highering the step time (like i said the machine worked great before so I don't see why it could have helped but I tried anyway) but nothing works. The weirdest thing is that it seems that everything works great and out of nowhere the y axis decides to go ram itself directly in the hard limits (it seems, am not quite sure if it's gradual or just like what I just described). Also, something worth mentioning the problem cannot be mechanical slippage I triple checked and everything is tight.

I tried many times to execute the program above the stock without any load on the steppers but I get the same result. My theory is that I have a problem with either my pcie to lpt or my breakout board but the weird thing is that it's only a few hours in the job that the problem occurs so I don't know why these components would work at the beggining of the job but not in the middle of the job.

I am really lost here I hope someone experienced the same issue and can help me. If you have any questions let me know.