Advanced Search

If you use -5V and +5V supply you have -5 to 5V control, not 0-10V. With that you have 10V range yes, but the lower end is at -5V, not 0.
Remember that with only 3 wires (supply, ground, speed) the 0-10V speed is measured against ground.
You have to use separate 10V supply for the control.

Test with SPIN+ = 5V, SPIN- = gnd. The spindle should turn with half speed if it survived the negative voltage.

It's also good to tell the maker/model/etc of the spindle, it helps to undestand how it should be controlled.

The title is also highly misleading, if the spindle controller died it's caused by the negative voltage applied and is actually a connection problem. Not caused by mesa card.

OP, why such a bad tittle ?
Not good.

If I rerun rt_setup.sh, it is not updating the two files in /etc/linuxcnc and manually editing the lcnc_setirqaffinities.sh to have the correct IP does not result in the IRQ being pinned to the correct CPU (2 instead of 8, still). So looks like I still have some investigations to do, but at least I now know what needs to be accomplished.

Thanks for reply and help. I may need some more help. I will try it. Report it back.

Now, I am more confused. I need a 10v range; the only power I have available at the 7i96s is ±5v and ±12v. The spindle has a 3-wire connection, Power Supply (10-26 VDC), Ground (0 VDC), and Speed Control (0-10 VDC). The Power Supply connection is connected to +12 VDC, the Ground connection goes to the control box Gnd (signal and chassis), and the Speed Control is connected to SPIN_OUT. Since I do not have a 10v supply, I am providing ±5v; my understanding was I needed offset mode to move the -5 to +5v range to 0 to 10v range.

Is that not correct?

I'll take a look Monday or Tuesday, I don't have a PCI test system here.

Actually I see the issue, I accidentally made a fallback configuration
I can fix it later today

For 0 to 10V, you would not use offset mode

If you wanted -5V to +5V (and you had +5V and -5V supplies)
you would connect SPIN- to -5V, SPIN+ to +5V and use offset mode.

Also note in offset mode with +5V and -5V supplied, the output voltage
will be at -5V when PWM is disabled so a separate spindle enable is a necessity.


The output voltage cannot go below the SPIN- voltage
or above SPIN+ voltage regardless of any settings.
 

As I mentioned, I have SPIN+ fed +5v and SPIN- fed -5V; that was the only way I could get the 10v range. I understood that setting hm2_7i96s.0.pwmgen.00.offset-mode to true would give me the 0-10v the spindle expects.

I guess there is the risk that the supplied ±5v could vary somewhat; I'm unsure how to protect against that. But at s18000, the voltage should have been well within the 0-10v range.

Yes, I think  some kernel change made Ethernet latency more sensitive to IRQ pinning

Bonjour,Je sais que je ne dépose pas ma demande au bon endroit, mais le forum français me laisse en plan depuis des mois!Si je poste ici c'est que le forum linuxcnc partie française semble ne plus vraiment vivre. forum.linuxcnc.org/46-francais/48516-mes...a-configuration,donc je tente ma chance ici.Ma configuration matérielle est composée de 3 cartes MESA 6i25 7i75 7i78Je n'ai pas de port parallèle sur l'ordi.Mes axes fonctionnent ainsi que les prises d'origines.Il m'est arriver de fabriquer une pièce ou deux avec le gcode produit avec freecad atelier path, devenu cam dans la version la plus avancée.Ce que je souhaite faire avec le jog/mpg c'est de manœuvrer mes axes, sans forcement créer une pièce dans freecad/cam/gcode.Je dispose d'un pavé numérique/touches de direction usb qui agit, mais il faut ajuster le vitesse de déplacement de chaque axe (le réglage choisi à un moment, vaut pour tout les axes) ce qui est risqué si l'on oublie de minimiser celle-ci lors de la descente du Z, pénétration de la fraise dans la pièce.J'ai trouvé cette doc à l'adresse suivante: wapl.es/cnc/2020/02/23/linuxcnc-jog-wheel-setup.html/Je ne parviens pas à rendre utilisable ce jog mpg.Mon câblage correspond, sauf erreurs à ce qui est indiqué sur cette doc, reste que dans pncconf l'adéquation des termes employés dans icelle ne correspond pas aux choix possibles liés aux entrées sorties sélectionnable pour chacune des IO de IO17 à IO22 (j'ai cablé les fils mais leurs fonctions ne peuvent être définies selon les termes employés dans la docSeule IO23 (estop=AU) est sélectionnable telle que dans pncconf en tant que AU.Pour les pins de la db25 non dédiées à une IO de la carte mesa les (-) je ne vois pas comment les cabler.J'ai essayé de rassembler les infos de la doc dans un fichier calc afin de rendre plus lisible, pour moi, les données.Les IO de la doc ne sont pas sériée, les IO sérigraphiées sur la carte sont nommées de IO0 à IO16, ce qui correspond dans pncconf à IO17/IO33 mes méninges disjonctent parfois.  Merci d'avance pour votre aide vivement souhaitée.Cordialement

 

I think I see my mistake, I only changed the second instance (line 145) to 10.10.10.11 and overlooked line 117. Sorry for the trouble and thanks for the help!

I knew it was something I had missed. Odd that the old debian 10 vanilla install just worked, but the debian 12 was so finicky about having the cpu isolated and irq pinned.

I have now tried to improve the bios according to the Linuxcnc documentation as suggested by rodw.

I also followed the instructions in the link from tommylight and tried to reduce the latency in this way.

Since the result is not really good yet, it would be great if I could get hints on a possible solution based on the files in the attachment

The output voltage is limited to the SPIN+ voltage supplied to the 7I96S
(at 100% PWM meaning the commanded RPM= OUTPUT_SCALE the
output voltage will be the SPIN+ voltage, at a commanded RPM of 0
the output voltage will be 0V relative to SPIN-)

I am pretty sure I never typed 25263 into pnfconf. Since the spindle's maximum RPM is 25000, I will reset OUTPUT_SCALE. I think I may have set it to that value at one point, but I have made so many changes that I am losing track.

I am not sure why the spindle went crazy, all I can think is the voltage went too high.

Yeah, A bit of error/status reporting would improve that script