Advanced Search

The next thing to do was get to know the bearings and screws. There was plenty of grime to clean.


Turns out there is some slop and rust in the x thrust bearing so I got some of those in the mail for x and y.


Next I needed to make a fixture plate for vises since the tslot table top was missing. 



Then I did some test cuts in aluminum to see how the mechanicals are doing. 

Then some cuts in tool steel. Some minor chatter with a ten thou stepover but Im pretty satisfied.

Hi guys. Im very excited to get a decent control in this new to me cnc mill from 1990.   The first thing I wanted to do is pick the machine up a little bit. It wasnt very ergonomic so low to the ground.  ...nothing that a couple 200 lb metal chucks cant fix.  I machined a couple of dowels at the right spots to fit inside the tube leveling feet so I never have to think about it moving around on me.  Now my machine has a 6" lift! I knew the 4x4 days would come in handy. Much better!

Rather than an error at the modbus level, is it possible that
the back to back G96/G97 commands are causing a step in
the commanded RPM that generates a drive fault  of some kind
say from lack  of a braking resistor during decell?

The method I mentioned includes instructions on how to install the RT kernel too linuxcnc.org/docs/stable/html/getting-st...nate_install_methods

You might be able to use an ethercat step/dir module. Beckhoff have one. There are plenty of others

Not sure about the other parts, but:

6.7.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux.

Is not a real time kernel.

( It needs to say "PREEMPT_RT" )
 

yes, follow the steps on the 2.9 docs getting linuxxnx at about heading 7, download  and run the script
The version in Bookworm was about 18 months old so getting linuxcnc from our web site is a much better idea!

I am starting my linuxcnc experience on Debian Trixie - I just did the todays upgrade  - and I have a kernel 6.7.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux. My current issue - is that I have lost apt access to the linuxcnc-uspace, linuxcnc-uspace-dev and mesaflash  packages.   These packages may have been held back from release but I am not in a position to know.  I have a different system - running on Trixie 6.5.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.131  2023-11-29  x86_64 Gnu Linux - with these packages loaded.
So there is a 5 month difference in time -  What I would like to know - Should I continue to persist in attempting to use Trixie as the base level of my systems - or is it wiser to go back to Debian 12.      I have two months calendar time before I have the CNC system together.   Thanks for looking into this.

Hi,

I've switched my lathe to use the Mitsub_vfd rs485 driver. All working great, except when fusion puts two m3 commands almost back to back... one G97 one G96, the second command causes the VFD to error out and stop on the second command.

The issue goes away of I pop an M1 in between the two. So I guess it is a timing issue and the interface needs to be told to wait for the previous command to complete?

Has anyone else experienced anything similar?

Thanks!

Hey,

I'm trying to use the 2.9 Version from the repo with linux-cnc 2.9.2, but when I press a button I always get the message "Failed to find sub "opsng_functioname' before EOF", for example when I press the x- button "Failed to find sub 'Opsng_xminus' before EOF".
I placed the folders /python & /psng into my configuration folder as stated in the instructions, but it seems I made a mistake somewhere?

//Edit: nevermind - I had the [RS274NGC] part twice in my ini, so it simply didn't see the PSNG stuff - my bad.

Besides this I have two different probes: one probe touch probe which issues a high signal when pressed, and the tool-setter issues a low when pressed. Does anyone know how I could malke usage of both of them? Normaly linux cnc seems to only support one probe-input and I would need to inverse the logic when changing the probes.

Kind regards

 would need help with the hal of my caroussel, because I think I did anything and by miracle it works just about.

when i set these parameters
net sensor-locking hm2_7i97.0.inmux.00.input-15
net sensor-pre_indexing hm2_7i97.0.inmux.00.input-14-not



 pin 14 is blinking so it corresponds to the locking sensor. the carousel behavior is correct but on the video you can see that when input-14-not the motor turn in rev so the motor has the instruction to turn fwd and rev. i have a mechanical safety to prevent the two contactors from tuning the motor at the same time.

so I modified
net sensor-locking hm2_7i97.0.inmux.00.input-14-not
net sensor-pre_indexing hm2_7i97.0.inmux.00.input-15

and pin 14 doesn't blink and the carousel can't lock.

You could use motion.current-vel and the scale component
to scale and adjust the PWM setting based on the current velocity.

 

I am interested in your approach to drive Laser power from the QtPlasmac “Cut Amps”.

Although I’d like to link S from 1-1000 with this to the boards analog or pwm generator, for my particular setup it would be very important to insert reductions in power when the machine’s speed is less than the commanded speed.

The trajectory planner will naturally reduce the feed rate when approaching a corner, as it needs to reduce the speed to be physically possible to change direction.
As the laser is maintained at whatever power is defined, the material will be burned in these corners, because no reduction was imposed proportional to the reduction of velocity.

Do you have any suggestions to reduce the spindle power in these corners, aligned to the reduction of velocity?

Thank you.

verser wrote:

Probe Screen v2.9 update has been released:
- Designed for LinuxCNC v 2.9
- Supports Axis and Gmoccapy interfaces and screens from 1280x1024
- Supports metric and imperial

Sources

I have tried to make it work in LCN2.9 but it has not been possible, I don't know if it is because this instruction is wrong:
EMBED_TAB_COMMAND= gladevcp -c probe -x {XID} -u psng/python/probe_screen.py -H psng/psng.hal psng/probe_screen.glade

The TAB is created to appear blank and from what I see it does not load anything.
 
 

This patch fixes #177, "Forgetting G64 mode after E-stop,"

That's a huge problem, wonder how long it existed?

JT