Advanced Search

You might need to increase the number of pins (default is 15 input- and 15 output-pins):
linuxcnc.org/docs/html/ladder/classic-ladder.html#_variables

hello,

I've spent hours playing with the PID values ​​and still have the same problem...
In the meantime, I've made progress on other points on the machine to take my mind off things.

If I move the spindle to 45 degrees, then 145, 245, and 345, no problem; it positions itself correctly at the value. However, if I move it from 45 to 245, the spindle goes to maximum speed without stopping...

But since yesterday, I've had an interesting lead. When this doesn't work, I realized that the spindle command becomes negative (LCNC, probably choosing the shortest path, by wanting to rotate the spindle in the opposite direction).
And that's the problem: the spindle doesn't change direction, so the PID drifts...

To confirm my idea, I made the same movements, but imposed the rotation direction with an M19 Rx P1.
And then, if I move the spindle from 45 to 145 degrees or from 45 to 345, there's no longer a problem; it positions itself every time.

I've probably found the cause, but how to resolve it, I don't know.

Do I have an error in my HAL or am I missing a line?
Do you have any leads?

The LEDs are working properly.
The label translation is perfectly sufficient.

Thanks for the good work.

Switched to the generic driver, ok.
You probably need to add the configPDOS="true" to the linelike

Hello everyone,I have a proximity sensor that detects whether the machine door is open or closed. I’d like to integrate this signal into my system so that:

1. If the door is open, the program automatically pauses.
2. If the door is closed, the program continues.
3. The program should not start if the door is open — it should only start once the door is fully closed.

What’s the best way to implement this behavior in my setup?

Haha, ok..

Taking this as the cia402 reference example github.com/dbraun1981/hal-cia402/blob/main/example/cia402.hal
you normally connect opmode to the cia402 module. I would say connect lcec.0.5 to cia402.2 in the same way as in the example.

Grüß dich michael,
das ist dann mein Plan B,
ich hoffe natürlich das noch irgendjemand vielleicht ein Datenblatt hat.
Der diesen Eintrag hier liest.

Viele Grüße,

I get this error:
./sodick.hal:253: Pin 'classicladder.0.in-15' does not exist
It sees all the pins, all the inputs and outputs work, but it doesn't see the 16th pin.
HAL:
loadrt classicladder_rt
# Подключение входов Classic Ladder к физическим входам
net cl-in-01 lcec.0.5.in-01 => classicladder.0.in-00
net cl-in-02 lcec.0.5.in-02 => classicladder.0.in-01
net cl-in-03 lcec.0.5.in-03 => classicladder.0.in-02
net cl-in-04 lcec.0.5.in-04 => classicladder.0.in-03
net cl-in-05 lcec.0.5.in-05 => classicladder.0.in-04
net cl-in-06 lcec.0.5.in-06 => classicladder.0.in-05
net cl-in-07 lcec.0.5.in-07 => classicladder.0.in-06
net cl-in-08 lcec.0.5.in-08 => classicladder.0.in-07
net cl-in-09 lcec.0.5.in-09 => classicladder.0.in-08
net cl-in-10 lcec.0.5.in-10 => classicladder.0.in-09
net cl-in-11 lcec.0.5.in-11 => classicladder.0.in-10
net cl-in-12 lcec.0.5.in-12 => classicladder.0.in-11
net cl-in-13 lcec.0.5.in-13 => classicladder.0.in-12
net cl-in-14 lcec.0.5.in-14 => classicladder.0.in-13
net cl-in-15 lcec.0.5.in-15 => classicladder.0.in-14
net cl-in-16 lcec.0.5.in-16 => classicladder.0.in-15

# Подключение выходов Classic Ladder к физическим выходам
net cl-out-01 classicladder.0.out-00 => lcec.0.5.out-01
net cl-out-02 classicladder.0.out-01 => lcec.0.5.out-02
net cl-out-03 classicladder.0.out-02 => lcec.0.5.out-03
net cl-out-04 classicladder.0.out-03 => lcec.0.5.out-04
net cl-out-05 classicladder.0.out-04 => lcec.0.5.out-05
net cl-out-06 classicladder.0.out-05 => lcec.0.5.out-06
net cl-out-07 classicladder.0.out-06 => lcec.0.5.out-07
net cl-out-08 classicladder.0.out-07 => lcec.0.5.out-08
net cl-out-09 classicladder.0.out-08 => lcec.0.5.out-09
net cl-out-10 classicladder.0.out-09 => lcec.0.5.out-10
net cl-out-11 classicladder.0.out-10 => lcec.0.5.out-11
net cl-out-12 classicladder.0.out-11 => lcec.0.5.out-12
net cl-out-13 classicladder.0.out-12 => lcec.0.5.out-13
net cl-out-14 classicladder.0.out-13 => lcec.0.5.out-14
net cl-out-15 classicladder.0.out-14 => lcec.0.5.out-15
net cl-out-16 classicladder.0.out-15 => lcec.0.5.out-16

There is a PIN in the terminal:
37  bit   OUT         FALSE  lcec.0.5.in-01 ==> cl-in-01
    37  bit   OUT         FALSE  lcec.0.5.in-02 ==> cl-in-02
    37  bit   OUT         FALSE  lcec.0.5.in-03 ==> cl-in-03
    37  bit   OUT         FALSE  lcec.0.5.in-04 ==> cl-in-04
    37  bit   OUT         FALSE  lcec.0.5.in-05 ==> cl-in-05
    37  bit   OUT         FALSE  lcec.0.5.in-06 ==> cl-in-06
    37  bit   OUT         FALSE  lcec.0.5.in-07 ==> cl-in-07
    37  bit   OUT         FALSE  lcec.0.5.in-08 ==> cl-in-08
    37  bit   OUT         FALSE  lcec.0.5.in-09 ==> cl-in-09
    37  bit   OUT         FALSE  lcec.0.5.in-10 ==> cl-in-10
    37  bit   OUT         FALSE  lcec.0.5.in-11 ==> cl-in-11
    37  bit   OUT         FALSE  lcec.0.5.in-12 ==> cl-in-12
    37  bit   OUT         FALSE  lcec.0.5.in-13 ==> cl-in-13
    37  bit   OUT          TRUE  lcec.0.5.in-14 ==> cl-in-14
    37  bit   OUT         FALSE  lcec.0.5.in-15 ==> cl-in-15
    37  bit   OUT          TRUE  lcec.0.5.in-16
    37  bit   IN          FALSE  lcec.0.5.out-01 <== cl-out-01
    37  bit   IN          FALSE  lcec.0.5.out-02 <== cl-out-02
    37  bit   IN          FALSE  lcec.0.5.out-03 <== cl-out-03
    37  bit   IN          FALSE  lcec.0.5.out-04 <== cl-out-04
    37  bit   IN          FALSE  lcec.0.5.out-05 <== cl-out-05
    37  bit   IN          FALSE  lcec.0.5.out-06 <== cl-out-06
    37  bit   IN          FALSE  lcec.0.5.out-07 <== cl-out-07
    37  bit   IN          FALSE  lcec.0.5.out-08 <== cl-out-08
    37  bit   IN          FALSE  lcec.0.5.out-09 <== cl-out-09
    37  bit   IN          FALSE  lcec.0.5.out-10 <== cl-out-10
    37  bit   IN          FALSE  lcec.0.5.out-11 <== cl-out-11
    37  bit   IN          FALSE  lcec.0.5.out-12 <== cl-out-12
    37  bit   IN          FALSE  lcec.0.5.out-13 <== cl-out-13
    37  bit   IN          FALSE  lcec.0.5.out-14 <== cl-out-14
    37  bit   IN          FALSE  lcec.0.5.out-15 <== cl-out-15
    37  bit   IN          FALSE  lcec.0.5.out-16
    37  bit   OUT          TRUE  lcec.0.5.slave-online
    37  bit   OUT          TRUE  lcec.0.5.slave-oper
    37  bit   OUT         FALSE  lcec.0.5.slave-state-init
    37  bit   OUT          TRUE  lcec.0.5.slave-state-op
    37  bit   OUT         FALSE  lcec.0.5.slave-state-preop
    37  bit   OUT         FALSE  lcec.0.5.slave-state-safeop

Hallo Jochen,

ohne Datenblatt kommst du nicht weiter.
Meistens ist es leider so, dass nur eine Schnittstelle an solchen Antrieben vorhanden ist.
D.h. entweder CanOpen ODER Puls-/Richtung-Schnittstelle. 

Ich würde den Motor gegen eine Schrittmotor ersetzen, vieleicht findest du einen passenden zu dem PLE60-Getriebe und kannst wenigstens dies behalten.

Viele Grüße

Hier jetzt noch mal die Platine von der Rückseite.

Ja das mache ich natürlich sehr gerne, ein wenig habe ich ja schon raus gefunden.Nur nicht welcher Logikpegel von dem Regler erwartet wird.Die Stromversorgung habe ich schon lokalisiert plus/minus, habe ich mit dem Multimeter schon ermittelt.Die Firma wird mir auch wahrscheinlich nicht mehr antworten, bei genauerem hinsehen auf der Webseite habe ich gemerkt, dass die Home Seite gelöscht wurde und die Firma Zeit 2014 aus dem Amtsregister gelöscht wurde. Es sind nur noch wenige Daten verfügbar, ausgerechnet mein Regler nicht.Anbei aber die Bilder die ich gemacht habe.Ich bin für jede Hilfe dankbar.

sorry im a idiot. this was the wrong file.

 

I think I pushed a fix for the leds staying on problem - at least in the tests I did it worked.
The label is a bit harder to fix satisfactorily. It's now at least translatable.

if I add these commands, on my machine the camera fails.
we need to find away to detect possible resolutions.

How do you know what resolution is displaying in qtdragon?

I have a small CNC job shop in my garage. I currently have a Sharp SV-2412SX VMC with a Fanuc control. I need to start taking some turning jobs. I have an Emco Maximat Super 11 manual lathe that I was thinking about doing a LinuxCNC conversion on. But the more I think about it, I want a heftier, more capable CNC lathe with an ATC. But I am not ready to drop another $25k+ on used machine.

Someone local is selling a Mazak QT8 with a CAM T-2 control for $2500. It needs work and it looks like a good candidate for a LinuxCNC retrofit.

I'm a software engineer by profession. I don't know much about LinuxCNC yet, but I am learning. I'm currently going through some classicladder tutorials, and HAL tutorials as well to get my head around what it takes to do a retrofit and better understand the LinuxCNC ecosystem.

Do you guys have any recommendations on where I should begin to better understand what existing components on the Mazak QT8 I can use and what existing components will need to be replaced because they won't work with LinuxCNC. I have a lot to learn, but I am not intimidated by projects like this. I just need some advice regarding the best place to start and how a map out a project like this. 

Thanks!
Chris