Advanced Search

Must be the third time i am looking at this and can not figure out what is going on, and the picture is not helping.
Can you do some more details, like where the mill is cutting and what direction it is traveling, and just to be sure, that there is no undercut as it looks in the picture.
Or am i looking at it from the wrong perspective?

What do Debian 12, Ubuntu 24 and Linux Mint Debian Edition 6 have in common? ... besides being all Debian, they can all have LinuxCNC installed with a single line after an update:
sudo apt install linuxcnc-uspace
So, not a single distro, but a single distro!
There is also Gento Linux that NTULINUX maintains and supports, and has also RTAI kernels for it and Debian.
Now, has anyone tried to compile LinuxCNC on CL? Maybe that already works.
I compile on every new version of normal Mint and use the created debs to quickly install on many PC's and laptops i use and test, so that also works.
-
No idea where i was headed with this, had a pizza and 2 coffees and had one of the laptops with me so i was browsing the forum and doing maintenance ... been doing a lot of installs lately as i got 5 laptops (4 used and 1 new), not counting the existing ones... send help !

Got another Lenovo X240 and X1 Carbon Yoga laptop/tablet, will update when i get to testing them on a machine as they are installed and ready.

Another possibility is to use the siggen to set the rate (0.1 Hz for example)
and drive the oneshot component with the siggen clock pin, then set the on time
with the onseshot width pin.

The oneshot component has a reset input that could be used for enabling
the output with the coolant-on signal

Nothing to do.

After:
> cmake -DPICO_SDK_FETCH_FROM_GIT=on -DCMAKE_BUILD_TYPE=Release ./Remora-RP2040-W5500-main
> make
OR
> cmake -DPICO_SDK_FETCH_FROM_GIT=on -DCMAKE_BUILD_TYPE=Debug ./Remora-RP2040-W5500-main
> make

It always exits with "fatal error".

Found it:
forum.linuxcnc.org/49-basic-configuratio...timed-output-flasher

I would like to try something like 2 seconds on and 10 seconds off

Looks like only the 3.3V regulator is damaged.

I have now parenthesized print. in stdglue.py and that error has disappeared from the log.

The python error now showing looks like a similar error regarding exception. I have added parentheses to the except lines but must still have the syntax wrong as the same error persists.

I have attached the error log and the stdglue.py file and would be most grateful for some more help!

   
 

Using SigGen would probably work fine, but i have yet to use it, but do have a look here:
linuxcnc.org/docs/2.9/html/man/man9/siggen.9.html
it will do the same time on and off, so might not be exactly what you want, ex. at 0.5Hz it will do 1sec on and 1sec off.
There are other ways also, so we need to know if you do need separate times for on and off.

I just started the mist coolant system today and it works great.
I've been looking around the forum for the possibility of having the coolant turn on and off every X seconds.
The information I've found is pretty confusing for me.... I'd really appreciate your help once again.
I hope I'm not too annoying asking about every thing I come across. 

Did you set the step times to 5000?
 

The drives are there and should be working.

I had this whole mill making chips well for a few years with a parallel port and 2.7 i think. A power surge took out the VFD for the spindle. There was some glitch with linux that the screensaver wouldn't wake up so you'd have to reboot. I had that one bypassed, but it resurfaced and I couldn't remember how to fix it. I made a bad vfd buy on ebay and later a couple of stepper drives went bad at some point. Then it sat for a while. I'm trying to get it running again now.

It has some new to me used gecko 201's on all 3 axes. Its got an offbrand new vfd that works in manual mode at least on the spindle. and a new (used) PC with 2.9 on it.

I checked for movement on all three connected axes. Seems to have different holding torque on different axes but no movement whatsoever.

The 7I95 isolated inputs are "inmux" pins

When LinuxCNC is running:

halcmd show pin *inmux*




 

Actually its easier to test this on a 7I97/7I97T

Do you have a 7I97 or 7I97T?