Advanced Search

You can test the index-enable system by hand.

Open halshow (this is "show machine configuration" in Axis, in some other interfaces you may need to open a terminal and "halcmd loadusr halshow"

Add the x-index-enable signal to the Watch tab. I think you should see a button that allows you to set it.

Then rotate the motor by hand, and see if the index-enable signal ever goes false.

Hint, the colour scheme of halshow is eccentric. dark red = 0 / false and yellow = 1 / true

Are the stepper motors locked or free when they should move and don't?

There is a "quirk" in Stepconf that "Test axes" doesn't set the drive "enable" pins.
(Running the full system would, if the enables are configured)

Many stepper drivers have a "not-enable" input, which turns the drive off when high. (It's typically a waste of an IO pin with stepper motors)

If the motors are locked then the drives are enabled, and for some reason the step pulses are not being seen. If they are free then suspect the enable logic.

Hi,
I'm manually adjusting the max_output values ​​and the others now, but if I wanted to do everything in pncconfig, where can I find these values?
Thanks.
Milko

Changes pushed to 2.9 won't be accessible unless the devs issue a point release. eg 2.9.5
You would probably be better off upgading to master 2.10 branch so you get changes as they happen.
QT dragon is a pretty new GUI and Chris has been beavering away improving it all the time.....

Afaik you need to re-compile the ethercat sever with the --disable-eoe option.
 

Using rpi5. I have included my config files also.

Update: This I compiled bootloader version and Installed that. And added Blink in config.txt to test if firmware is working. Yes firmware is working and led is blinking. But Still no connection to RPI5, machine can't come out of estop.

Bonjour à tous,
J'ai une découpeuse plasma sous Mach3 et je souhaite l'utiliser avec LinuxCNC.
L'univers de LinuxCNC est nouveau pour moi donc j'avance à petit pas.
Après mes déboires avec l'axe X qui saccadait que j'ai pu régler en augmentant le "Base Period Maximum Jitter".

Je me retrouve dans l'impasse pour l'axe Y, j'ai 2 moteurs en symétrie (donc l'un des deux doit être inversé) mais quelle que soit la configuration des pins (ex: pin4= step Y/ pin 5= dir Y / pin 8 = tandem step Y / pin 9 = tandem dir Y inv), je n'arrive pas à faire bouger les 2 moteurs en même temps.
J'arrive à faire déplacer un moteur soit Y1, soit Y2 et seul celui config en step Y et dir Y fonctionne (juste Y1 s'ils sont configurés pareil).
Est-ce une mauvaise compréhension de ces paramètres ?
Dois-je éditer manuellement les fichiers .hal et .ini ?
Quel est la bonne méthode dans StepConf pour synchroniser 2 moteurs ?

Merci de m'avoir lu,
Raph

Ok but, when i'm done with the homing , the machine have a problem with the limits. It's convinced that it have the two meters going to the limit homing switch but after the homing it would have to do go to the others side for two meters. Maybe today i figure out how to do that.

If you are Chinese, add me on QQ: 304394405. If you are foreign, add me on Discord: onceloved.cn

I checked the index signal with a physical oscilloscope (Hameg 303 in this case) and I can see the index signal "fly by"... it is very fast

 

Thank you Andy, I will follow your advice to try to observe both, index-enable signal and hm2_7i80.0.encoder.00.input-index pin in the HAL scope and see if the index-enable pin behaves as you describe it.

Thank you
Sigi


 

Wiring is the same as the SKR2. RPi4 or 5?

I think I'm ready! Hopefully ordering the parts in the next 2 weeks. EEK!

 

 

Here is red box machine we are modifying into a control center. A keyboard and mouse pad will be secured to the shelf using velcro. Should make for a good cabinet plenty of space and resistant to impact. 

Yes. I have cloned latest remora-h7xx-pio repository from remora-cnc. And compiled that. And used config files attached in previous post.

Ok thank you that is a bit more more informative, if somewhat weird. As I suspected the whole MEM debacle is someone's labeling, maybe to make the machine more familiar.

Somewhere along the way some one is going to ask for the gcode file, and once again the config files and the rest relating to your machine so they may have a chance of the simulating the issue.

If there is any proprietary IP involved you may have to make an agreement with one of the devs to sort this issue out. I'm just putting this out there as your particular site situation is unknown.

Just a word of warning, if the issue relates to some sort of issue with any Mesa hardware you'll be dealing with the company run by the person you referred to as conceited. But what you need to consider is that over the years there has been dealings with people that have landed at this forum requesting cnc help not related to the Linuxcnc ecosystem, also those that will argue that Linuxcnc should support this hardware or that, usually related to some form of USB based controller that for various reason does not work within realtime, I know unrelated to your issue.

Now time to let bygones be bygones and other such cliches and sort this out. I can understand if this is causing some frustration but sometimes it can go both ways. Like multiple requests for a user to give information regarding their system, ask your sales or engineering team how this can be with some customers. But like I said if there is any proprietary IP involved some agreement with one of the devs maybe the way to go, so as any discussion can take place within a non-public way.