Advanced Search

Hey guys,
back to the same problem as before.
We successfully cut a few files and then we got the same error with the height would exceed z axis max limit.
Tried to disable the torch and start program: Same error.
Loaded the last successful file that we cut and tried cycle start: Same error.
Closed qtplasmac, restarted, homed etc. Loaded same successful file that we cut: Same error.
Any suggestions?
I am wondering if the g code filter is a problem. Creating g code from hypertherm nestmaster and running it through a filter.
However it doesn't explain it working a few times in a row and then failing. I have also tried changing to different material setting that I have saved and running the program again to see if it helps.

You would typically do this by launching the editor with sudo:

sudo mousepad /etc/network/interfaces

My interfaces file looks like this:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
       auto eno1
       iface eno1 inet static
           address 10.10.10.100
           hardware-irq-coalesce-rx-usecs 0


Notes:
1. Your Ethernet device name may not be "eno1" (try "ip a" to discover your Ethernet device name)
2. If you configure the port in the interfaces file, you should disable any configuration done in the network manager GUI



 

I'm converting a PM-833TV mill to cnc and am using an Intel NUC for the computer and following Dr. D-flow's directions.

They state:

Open the network interfaces file by navigating to /etc/network/ and open the interfaces file via your file explorer or terminal. Add/change the text in this file to conform to the code below.
Other's on the forums say to do the same. The problem is that I can not edit the system files. They are read only and after extensive searching, I have not found directions on editing the files, almost as if no one has to unlock them.

The IP for the network card is set through the network GUI and the mesa 7I96S has jumpers set to 10.10.10.10 and I am able to ping the card, but with slow times.

I did not set a root password and only have a password on my user name, as instructed by: kcjengr.github.io/probe_basic/stable_quick_start_apt.html#

How to update ethercat, I have version 1.5 installed and it shows me an error I can't update it to IgH EtherCAT master 1.6.1 1.6.1

when i try to open probe basic it crashes before fully loading and gives an error.

can gmoccapy use the probe or does it have to be in probe basic?
i have it wired to a input and selected as probe in the config but it the only pid i found in hal show never triggers. the probe light isnt green either, so i may have two issues.

For about 2-3 months there has been a problem

with compiling linuxcnc on debian 10

there is such an error:
cp ../scripts/rtapi.conf ../tests/uspace/spawnv-root/rtapi.conf
Compiling libnml/inifile/inifile.cc
Compiling libnml/inifile/inivar.cc
Compiling libnml/posemath/_posemath.c
Compiling libnml/posemath/posemath.cc
c++: error: unrecognized command line option ‘-std=gnu++20’; did you mean ‘-std=gnu++2a’?
c++: error: unrecognized command line option ‘-std=gnu++20’; did you mean ‘-std=gnu++2a’?
c++: error: unrecognized command line option ‘-std=gnu++20’; did you mean ‘-std=gnu++2a’?

I suspect that I need a newer compiler, because on debian 12 the compilation works normally.

Can this problem be solved in some simple way?

Hello Cmorley

There is a small problem with the spindle lift function during pause.

If you pause the program with the "spindle lift" function and then press stop, the spindle locks and you can't start it, even in manual mode.

1. start the program
2. pause the program (with the "spindle lift" function enabled)
3. stop the program
4. after these actions you can't start the spindle normally.

The only way to start the spindle is either to restart qtdragon or this combination:
1. start the program
2. press "spindle lift"
3. pause the program
4. resume the program

The drive will attempt correct for lost steps up to the tolerance - this is a separate setting from the alarm.  If it can't correct to within the tolerance window, the drive will fault and the alarm signal will be triggered.

I think the tolerance is reasonably tight from the factory - it's just the alarm that's silly.

Regarding the power supply - increasing voltage won't provide more 'power'.  It will only permit the motor to turn higher RPM before losing steps.

On steppers, the 'power' - torque, in other words - is determined by the amps available to the motor/drive.  If your 36v supply can't manage enough amps to the drive that would result in lower torque.  Or if the drive is programmed to only use half the amps the motors are capable of handling.

You mentioned before that you adjusted the microsteps without using the software.  It's possible you accidentally set the drive max amps lower than desired via one of the dip switches.

I suggest you set the dip switches to whatever position means 'software program only' and set the max amps based on the motor, input steps/rev, and everything else via the programming software.  Note that inside the software, you won't directly set 2/4/8/10/N 'micro-steps'; rather, you'll be determining how many input pulses are required per revolution and may need to adjust LCNC's steps/unit output.

I've used similar Nema23 closed-loop steppers from Stepperonline on a medium sized plasma, and they had a remarkable amount of torque.

For NPN sensors you wire the 7I96 input common (TB3 pin 12) to +24V

Also for NC home/limit sensors you must invert the inputs

 

Wenn es bei geringen Geschwindigkeiten über größere Verfahrwege funktioniert, dann passen ja die scales.

Hast du mal die Absolutwefte gescheckt, wenn du höhere Geschwindigkeiten nutzt?

Ich vermute jetzt erstmal ein EMV Thema.

Woran sind die GMS angeschlossen? Mesa vielleicht? Und sind das differentielle und mit geschirmten Leitungen?

Julian

Hallo Gemeinde,
ich versuche seit Tagen meine GMS (Ditron DC11) mit meinen Servos (JMC iHSV57 180 Watt) laufen zu lassen.
Wenn ich langsam fahre (bis 2000mm/min) dann geht das noch, aber wenns schneller wird, dann fährt die Achse ca. 30 - 40mm und geht dann mit nem Positionsfehler aus. Den Servo habe ich bereits in sämtliche Richtungen parametriert, weich, mittel, härter und ganz hart, dass sogar noch mit zig Abwandlungen. Im JMC-Oszilloskop bekomme ich den so hin, dass der eine max. Abweichung von 8-10 Schritten im Eilgang hat, wobei 1 Schritt 0,001mm sind. Mit dem PID und dem HAL-Scope habe ich auch versucht bis zum Erbrechen, es wird einfach nicht besser.
Ich weiß einfach nicht mehr weiter, wo ich noch dran drehen könnte, bin einfach ratlos und drauf und dran die GMS rauszuschmeißen.

Vielleicht hat ja einer von euch einen passen Rat was ich machen könnte und wo der Fehler liegt.


Danke und Gruß
Olli

i found a few videos but they don't cover much. But i think the alarm part should be easy enough. i think i got enough info to set that and save the new settings to the drive. seems like after the settings are saved you need to cycle the power once after that if the info i found is correct? i don't see how it would hurt anything after you exit out of the software.
i think once you change the factory setting from 4,000 to something small i will see conditions for lost steps, With the current settings if you have a condition that causes lost steps it just corrects until it gets back to where the encoder says it should be i could see that causing surface finish issues if that is in fact what is going on?

i think the first step is to get that changed and saved to the drives and do some testing to see if i get alarms or not. if i do get alarms then i need to figure out if it can be corrected in the internal drive settings or something else needs done? if all else fails i can try a 48V power supply or just get a bigger nema 23 motor if it leads back to the X axis. if that does not help then i will have to live with it as is or go back to the drawing board and make reductions.

anyways it's a way to collect more information to narrow things down so thanks for the help everyone.

Hello, thank you very much for the feedback.

I did not change the original wiring of the servo motors to the Indramat 3TRM2. A tachometer signal is connected for each axis. I connected my 7i77according to the attached circuit diagram.

 

Told you it was horrible

Not sure about the "T" model, but the "Y" model drive software calls following error "Position Deviation Alarm Threshold".

 

I kept looking at what is displayed in the terminal when linuxcnc starts.
I just did read readhmid and there’s the pwm, pin 1/14, plain as day.
Thank you for helping me despite my ignorance. You rock