Advanced Search

In StepConf wizard, the "parallel port" page there is an entry for "parport base address" so set that to 0x2000 and test if the stepper moves.
If not, also try 0x2010 but it would be good to reboot the PC before testing it.

Habe ich das mit der Konfig der mesa Karten richtig verstanden, dass ich zuerst herausfinden muss wieviele Ein- und Ausgänge ich brauche um dann die passende Konfig auf die Karte zu spielen?

Installiere linuxcnc auf den Raspberry und starte einfach pncconf, dann kannst du dir die Mesakarte aussuchen und siehst selber was man braucht.
Du brauchst die Steigung deiner Spindeln (der Hersteller gibt 0.00375mm/schritt an, also vermutlich 1.5 oder 3 mm).
In pncconf werden Takt/Richtung für die Achsen fix vergeben sein, du musst den Pins nur korrekte Achsen zuordnen. Dann noch angeben an welchen Pins welche Endschalter hängen und das war eigentlich schon alles. Also praktisch nur von deiner HAL-Datei abschreiben.
Oder du schaust hier:  linuxcnc.org/docs/html/config/pncconf.html

If the "Emergency Stop" button (red X) does nothing, this is likely an issue in the hal or ini files.

Can you post your hal/ini files here?

Axis should look something like this initially (before estop is released):


 


After Estop is released and before power (Orange button) is on:


 


and after power is on:


 


 

On the stepper driver, the led is green and on the BOB there are 3 red led lights. I have a 36V 11A Stepperonline and a 24V 6A MeanWell power supply. I measured the output of the power supplies and they are working properly. For now, I just connected the X axis to test if the wiring is correctly and to learn to operate LinuxCNC.I also tried with another driver and stepper motor but is the same. Maybe because I didn't connected the Y and Z axis the stepper motor is not moving? Thank you for your time!

Hello. I have installed the latest version of LinuxCNC. Everything seems to be correct, but I cannot see the jogs to control the motors on the interface and the red ‘X’ does nothing. I do not know what to do. I cannot find a way to continue. Thank you.

   

You should be able to take the oritinal working ini file and copy it into it's original configuration directory, Saving it with a new name .ini.

Then you without making any changes to the original ini file other than it's name start the configuration. It of course will still be the same but have a new name. Then start making small changes to the ini file. You need to be aware of any variable references to the ini file that the hal file(s) use, and if any of them refer to sections of the ini that you are changing you will need to address them. These are very common in the sections of hal code referring to the joints and axis. There is a good chance you will have to make a copy of the main hal file, rename, and make changes there to go along with your ini changes.

I was talking about the index from the motorencoder - the inductive sensor is seen only once per rev.