Advanced Search

mmh, i dont understand. how would you do this? I thought you had to do it through a subroutine or m code. 

Btw, this is how the m120 looks like.

This is not a LinuxCNC version issue.

This is a hal setup or hardware issue.

1. Do you have +10V on 7I76E SPINDLE+ relative to 7I76E SPINDLE- ?
2. Can you set the spindle speed to 1/2 way up and then run:

halcmd show all  > all.txt
 and post the all.txt file here

(you run halcmd from a terminal window when LinuxCNC is running)
 

Would something like this work? net pendant-encoder-a pendant.encoder-a [HMOT](CARD0).0.gpio.034.in
net pendant-encoder-b pendant.encoder-b [HMOT](CARD0).0.gpio.035.in
net pendant-encoder-btn pendant.encoder-btn [HMOT](CARD0).0.gpio.036.in
net pendant-jog-a pendant.jog-a [HMOT](CARD0).0.gpio.037.in
net pendant-jog-b pendant.jog-b [HMOT](CARD0).0.gpio.038.in
net pendant-jog-btn pendant.jog-btn [HMOT](CARD0).0.gpio.039.in
net pendant-momentary pendant.momentary-btn [HMOT](CARD0).0.gpio.040.in
net pendant-mode-sw pendant.mode-sw [HMOT](CARD0).0.gpio.041.in
net pendant-axis-x pendant.axis-x-sel [HMOT](CARD0).0.gpio.042.in
net pendant-axis-y pendant.axis-y-sel [HMOT](CARD0).0.gpio.043.in
net pendant-axis-z pendant.axis-z-sel [HMOT](CARD0).0.gpio.044.in
net pendant-z-y-sel pendant.z-y-sel [HMOT](CARD0).0.gpio.045.in
net pendant-dpad-up pendant.dpad-up [HMOT](CARD0).0.gpio.046.in
net pendant-dpad-down pendant.dpad-down [HMOT](CARD0).0.gpio.047.in
net pendant-dpad-left pendant.dpad-left [HMOT](CARD0).0.gpio.048.in
net pendant-dpad-right pendant.dpad-right [HMOT](CARD0).0.gpio.049.in
net pendant-coolant-hw pendant.coolant-hw [HMOT](CARD0).0.gpio.050.in
I know im missing something.

It won't have anything to with the Linuxcnc installation. If there was an issue, something missing, Linuxcnc would produce an error.
M
Maybe if you could take a picture of the power wiring to the board, that may show something. I've looked at things in the past for hours on end and missed a simple error.
I can understand how things can get very frustrating.
I take it you have measured the output voltage when not connected to the spindle input ?
The spindle does take a variable voltage and not a pwm signal, just asking as you were concerned about not being able to select pwm. Sorry for these simple questions, please dont take them as an insult .

I don't have an MPG. It's all done with switches. 1. empty 26. PE
2. empty 25. empty
3. momentary switch 24. empty
4. mode switch 23. empty
5. DT (encoder) 22. encoder power 5vdc
6. SW (encoder) 21. X,Y,Z; Z-Y: unused GND
7. CLK (encoder) 20. momentary GND
8. Z (X,Y,Z switch) 19. encoder GND
9. X (X,Y,Z switch) 18. D-pad GND
10. Y-Z switch 17. down
11. unused 16. up
12. empty 15. right
13. empty 14.left
Its all connected to a parallel port breakout board, connected to the P1 of the Mesa 7i96s. I don't NEED a python script. If i can handle the logic through hal, that would be the best way for me. I don't even need the logic. I just want to get them functioning and then i can add features later. I have a spindle encoder so i would need to load at least one more. The diagram doesn't reflect and additional encoder connected to 1,2,12. At the end of the day, Ai does complicate otherwise basic tasks. Thank you for the responses. If you need anymore information, just let me know.

Videos 7i76e spindle failure  
thankkkkkkkssssss !!!!!!
I have performed all the tests before starting the forum. It does not output 10 VCC, it does not regulate voltage, that's why I started the thread.
I am confused with this situation, the board was working perfectly on a lathe with version 2.7.15. Now I need to install it on another machine. I tried 2.8 - 2.9.4 - 2.9.5 the result is always the same, it does not regulate voltage. But there is something that is not connecting, linuxcnc shows good operation in Halshow, but it does not go out through the 7i76e.

I am going to reinstall linuxcnc from scratch again and see what happens.
thank you all for trying to help me!!! I'll post updates soon!!!
 

Some interesting suggestions on latency improvement here:
dantalion.nl/2024/09/29/linuxcnc-latency...arameter-tuning.html

But don't get too obsessed with it.
50k jitter is fine with a Mesa card. Though I would be a bit unhappy with 250k.
Try running the latency test without a base thread, you won't need one with a Mesa card.

The download links will all work if you take out the "s" in "https://..."
There is a problem with the wiki certificate. We keep trying to fix it, but without much luck.

When we had a similar problem with stringy chips, drilling holes with carbide drill with trough coolant in CrMo4, a modified G83 cycle solved that. Only retracting by 0.2mm after 2mm. Continue this 2.2mm / retract 0.2mm  steps until 
final depth, we made all the 120 holes without interruption and big loss of time. I think feed was about 0.12/rev

Can you describe what you want to happen? I have a feeling that the AI might be over-complicatiing things. But without knowing your requirements it is hard to tell.

Does the MPG connect to a Mesa counter, or only to GPIO?

Darium wrote:

Remapping is way way over my head and messing around with it can crash my machine
 

The simplest case of remapping is fairly straightforward. It starts off looking a lot like a subroutine in its own file (which is also a possibility) 

See section 2.6 here: linuxcnc.org/docs/stable/html/remap/rema...xample_remapped_code

Your ngc file would probably just contain the usual G83 but wrapped with a spindle reversal, and passing-through the XYZRQ etc parameters. 
 

What happens if you just wire selected-pocket directly in HAL?

Unfortunately a problem has been found with the 2.9.5 release with the touch-off dialog in Axis. 
It will not accept values other than zero. 
If you don't use Axis or always touch-off to zero then you can use 2.9.5 without problems. 
If you do need to use Axis and non-zero touch-off then you can either revert temporarily to 2.9.4 or MDI G10 to achieve the same effect as the touch-off dialog (which actually does use G10) 

I hope to release a 2.9.6 with this problem fixed rather more quickly than the usual "measured" cadence. 

Now believed to be fixed: forum.linuxcnc.org/29-forum-announcement...xcnc-v2-9-6-released
 

Basically what the original m10 from probe basic does. It tells the carousel comp the pocket number

What does M120 do?