Advanced Search

Ok, I didnt realize this, because the Probe Basic GUI and the VFD switched the ENA/FWD Output if I give some MDI S command. I can see that in the GUi, my relai clicks, the VFD switches to Run. But the Pin says the truth...

I don't fully understand why this Enable command should come only from the XHC-WHB-04 pendant (set pdnt....) and not from the PB Gui - I would like to enable the spindle over the pendant but more in an OR funktion not only with the pendant.
I have to say that all these spindle commands weren't made by myself but from someone else who wanted to help me out in the past. And I couldn't test it in real life, because my VFD wasn't connected until now.

How should I change the settings so that it works with GUI and pendant? can you give me some hints, please?
Thanks for your support!
Hanno

The spindle is off:

bit FALSE pdnt.spindle.is-on ==> hm2_7i76e.0.7i76.0.0.spinena
 

PCW, thanks for your eyes on it. Here the lines:

hanno@cnc2:~$ halcmd show all | grep spin
10 bit OUT FALSE halui.spindle.0.brake-is-on
10 bit IN FALSE halui.spindle.0.brake-off
10 bit IN FALSE halui.spindle.0.brake-on
10 bit IN FALSE halui.spindle.0.decrease
10 bit IN FALSE halui.spindle.0.forward
10 bit IN FALSE halui.spindle.0.increase
10 bit OUT FALSE halui.spindle.0.is-on
10 bit IN TRUE halui.spindle.0.override.count-enable
10 s32 IN 0 halui.spindle.0.override.counts
10 bit IN FALSE halui.spindle.0.override.decrease <== pdnt.spindle.override.decrease
10 bit IN FALSE halui.spindle.0.override.direct-value
10 bit IN FALSE halui.spindle.0.override.increase <== pdnt.spindle.override.increase
10 bit IN FALSE halui.spindle.0.override.reset
10 float IN 0 halui.spindle.0.override.scale <== pdnt.spindle-override.scale
10 float OUT 1 halui.spindle.0.override.value ==> pdnt.spindle.override.value
10 bit IN FALSE halui.spindle.0.reverse
10 bit OUT FALSE halui.spindle.0.runs-backward
10 bit OUT TRUE halui.spindle.0.runs-forward
10 bit IN FALSE halui.spindle.0.start
10 bit IN FALSE halui.spindle.0.stop
40 bit IN FALSE hm2_7i76e.0.7i76.0.0.spindir <== spindle-cw
40 bit IN FALSE hm2_7i76e.0.7i76.0.0.spinena <== pdnt.spindle.is-on
40 float IN 0 hm2_7i76e.0.7i76.0.0.spinout <== spindle-vel-cmd-rpm-abs
60 bit IN TRUE qtpyvcp.spindle-encoder-rpm.enable
60 float IN 0 qtpyvcp.spindle-encoder-rpm.in
60 float IN 0 qtpyvcp.spindle-load-indicator.in-f
60 u32 IN 0x00000000 qtpyvcp.spindle-load-indicator.in-i
60 float IN 150 qtpyvcp.spindle-load-indicator.max-val
60 float IN 0 qtpyvcp.spindle-load-indicator.min-val
60 bit IN FALSE qtpyvcp.spindle-override.reset
33 bit IN FALSE spindle.0.amp-fault-in
33 bit IN TRUE spindle.0.at-speed <== spindle-at-speed
33 bit OUT FALSE spindle.0.brake
33 bit OUT FALSE spindle.0.forward ==> spindle-cw
33 bit I/O FALSE spindle.0.index-enable
33 bit IN FALSE spindle.0.inhibit
33 bit IN FALSE spindle.0.is-oriented
33 bit OUT FALSE spindle.0.locked
33 bit OUT FALSE spindle.0.on ==> spindle-enable
33 bit OUT FALSE spindle.0.orient
33 float OUT 0 spindle.0.orient-angle
33 s32 IN 0 spindle.0.orient-fault
33 s32 OUT 0 spindle.0.orient-mode
33 bit OUT FALSE spindle.0.reverse ==> spindle-ccw
33 float IN 0 spindle.0.revs
33 float OUT 0 spindle.0.speed-cmd-rps
33 float IN 0 spindle.0.speed-in
33 float OUT 0 spindle.0.speed-out
33 float OUT 0 spindle.0.speed-out-abs ==> spindle-vel-cmd-rpm-abs
33 float OUT 0 spindle.0.speed-out-rps ==> spindle-vel-cmd-rps
33 float OUT 0 spindle.0.speed-out-rps-abs
27 bit OUT FALSE whb.button.macro-3 ==> pdnt.reserved.for.spindle+
27 bit OUT FALSE whb.button.macro-4 ==> pdnt.reserved.for.spindle-
27 bit OUT FALSE whb.button.macro-8 ==> pdnt.reserved.for.spindle.dir
27 bit OUT FALSE whb.button.spindle-minus
27 bit OUT FALSE whb.button.spindle-plus
27 bit OUT FALSE whb.halui.spindle-override.decrease ==> pdnt.spindle.override.decrease
27 bit OUT FALSE whb.halui.spindle-override.increase ==> pdnt.spindle.override.increase
27 float OUT 0 whb.halui.spindle-override.scale ==> pdnt.spindle-override.scale
27 float IN 1 whb.halui.spindle-override.value <== pdnt.spindle.override.value
27 float IN 0 whb.halui.spindle-speed-cmd
27 bit OUT FALSE whb.halui.spindle.decrease
27 bit OUT FALSE whb.halui.spindle.forward
27 bit OUT FALSE whb.halui.spindle.increase
27 bit IN FALSE whb.halui.spindle.is-on
27 bit OUT FALSE whb.halui.spindle.reverse
27 bit OUT FALSE whb.halui.spindle.start
27 bit OUT FALSE whb.halui.spindle.stop
bit FALSE pdnt.reserved.for.spindle+
bit FALSE pdnt.reserved.for.spindle-
bit FALSE pdnt.reserved.for.spindle.dir
float 0 pdnt.spindle-override.scale
==> halui.spindle.0.override.scale
<== whb.halui.spindle-override.scale
bit FALSE pdnt.spindle.is-on
==> hm2_7i76e.0.7i76.0.0.spinena
bit FALSE pdnt.spindle.override.decrease
==> halui.spindle.0.override.decrease
<== whb.halui.spindle-override.decrease
bit FALSE pdnt.spindle.override.increase
==> halui.spindle.0.override.increase
<== whb.halui.spindle-override.increase
float 1 pdnt.spindle.override.value
<== halui.spindle.0.override.value
==> whb.halui.spindle-override.value
bit TRUE spindle-at-speed
==> spindle.0.at-speed
bit FALSE spindle-ccw
<== spindle.0.reverse
bit FALSE spindle-cw
==> hm2_7i76e.0.7i76.0.0.spindir
<== spindle.0.forward
bit FALSE spindle-enable
<== spindle.0.on
float 0 spindle-vel-cmd-rpm-abs
==> hm2_7i76e.0.7i76.0.0.spinout
<== spindle.0.speed-out-abs
float 0 spindle-vel-cmd-rps
<== spindle.0.speed-out-rps
40 bit RW TRUE hm2_7i76e.0.7i76.0.0.spindir-invert
40 bit RW FALSE hm2_7i76e.0.7i76.0.0.spinena-invert
40 float RW 24000 hm2_7i76e.0.7i76.0.0.spinout-maxlim
40 float RW 1000 hm2_7i76e.0.7i76.0.0.spinout-minlim
40 float RW 24000 hm2_7i76e.0.7i76.0.0.spinout-scalemax
hanno@cnc2:~$

 

If you run LinuxCNC, enable the spindle and set the spindle speed say 1/2 way up, then:

halcmd show all | grep spin

and post the results here, that would help debugging this.
 

Hello together,
another question and problem with my LCNC config.
After solving installation, homing, network, latency problems with your help, I could make the next step and check my spindle output function.
I'm using a chinese 2,2kW standard spindle with a Hitachi WJ200 VFD, parameters set with Hitachi proDrive, the FWD/Stop control is working correctly, but I cannot measure any volts at the Spindle Output of my 7i76e TB4. The electronic pot gets 10V from an external voltage source, these 10V are measureable at TB4, Pin 3.
Im using Probe Basiv V.5 under Debian 12 and LCNC 2.9.3. on a Lenovo Think Centre M92p Tiny, 8 GB i5 2900 GHz.
I set the output with MDI S6000 and can see, that spindle-out goes to 100 (rps), Spindle-enable goes on, but I can not see any voltage at Pin 3.
Do you have any idea what is going wrong here?

Wiring:
8 Dir + STP (Hitachi WJ200 D2)
7 Dir - GND
6 En + STA  (Hitachi WJ200 D1)
5 En - GND
4 nc
3 SPI + +10V external voltage
2 SPI OUTPUT  -> Analog In O
1 SPI -       -> GND, L


INI:
MAX_OUTPUT = 24000.0
OUTPUT_SCALE = 24000
OUTPUT_MIN_LIMIT =  1000
OUTPUT_MAX_LIMIT = 24000

HAL:
#    SPINDLE
#  ************
# ---digital potentionmeter output signals/setup---

setp   hm2_7i76e.0.7i76.0.0.spinout-minlim    [SPINDLE_0]OUTPUT_MIN_LIMIT
setp   hm2_7i76e.0.7i76.0.0.spinout-maxlim    [SPINDLE_0]OUTPUT_MAX_LIMIT
setp   hm2_7i76e.0.7i76.0.0.spinout-scalemax  [SPINDLE_0]OUTPUT_SCALE
setp   hm2_7i76e.0.7i76.0.0.spindir-invert true

net pdnt.spindle-speed-abs   => hm2_7i76e.0.7i76.0.0.spinout
net pdnt.spindle.is-on       => hm2_7i76e.0.7i76.0.0.spinena
net spindle-cw               => hm2_7i76e.0.7i76.0.0.spindir
net spindle-vel-cmd-rpm-abs  <= spindle.0.speed-out-abs => hm2_7i76e.0.7i76.0.0.spinout

# ---setup spindle control signals---

net spindle-vel-cmd-rps        <=  spindle.0.speed-out-rps
    #net spindle-vel-cmd-rpm        <=  spindle.0.speed-out
    #net spindle-enable             <=  spindle.0.on
net spindle-cw                 <=  spindle.0.forward
net spindle-ccw                <=  spindle.0.reverse
    #net spindle-brake              <=  spindle.0.brake
    #net spindle-revs               =>  spindle.0.revs
net spindle-at-speed           =>  spindle.0.at-speed
    #net spindle-vel-fb-rps         =>  spindle.0.speed-in
    #net spindle-index-enable      <=>  spindle.0.index-enable

# ---Setup spindle at speed signals---
sets spindle-at-speed true

Thank you for any help!
Hanno




   

The first problem is real time issues with the network interface.

To get a rough idea where things are, can you run these two commands and reply with the results:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10

This will run for 1 minute and print statistics
(replace 10.10.10.10 with 192.168.1.121 if that's the 7I76Es address)

lspci | grep -i eth

(this should make it possible to determine the PCs Ethernet interface type)

Hello guys,
bad news for me.
Today i installed the VFD to the wall a bit far away from the control box. After i was done, i wanted to check if everything works and check if i still have some noise problems from the VFD. 
Due to the fact that i am again totally confused from 5-6hours of trying to fix it, i am not anymore sure if i got the unexpected real time delay on first start up (but later i got it all the time), but i have found out that when i jog by keyboard or mouseclick on the jog buttons quickly, lets say couple of short and quick jogs, then i get a joint following error 0 and the machine is then off. When i put it on and do the same quick and short jogs then i get following error 1. Then again the same and following error 2. (i would not take the sequence serious, i later also got following error 1 first, at least i believe, but i am not 100% sure)
I GET NO FOLLOWING ERROR WHEN:
- Jogging normalny, no quick clicks
- running a program

Is it possible that USB is the problem?
I havent changed anything since i posted the screenshot of the very-good latency in latency-histogram.

More info:
It happens also that when i want to start Linuxcnc i get a error (see picture), but its possible that it starts after trying second or third time.
Also sometimes Linuxcnc got stuck (freeze) or the whole PC, but of course i started to play around with the Bios settings and specific bios settings could create more problem.

I dont have PS/2 keyboard / mouse available to test. Changing two USB settings in BIOS did not help. (legacy usb something and one other option)

So, if you will have no idea, then my only option might be the 7i76eu, BUT i am also thinking to go back to Wheezy and Linuxcnc 2.8, IF its possible to do file sharing with e.g. Samba, but i believe that all tutorials are before windows did something to block the file sharing. Rodw wrote something about it, here in this thread.
PS: I need nothing but working Linuxcnc, mousepad/geany and file sharing or a browser that works so i can send files by mail or open Microsoft OneDrive.


 

Could StepGen be used to convert the absolute position data from the Fanuc encoder channels to quadrature pulses for outputting to encoder input on the drives? 

I have been using a very old Plasmac version from 2019 and although I alway planned to upgrade it, it just worked so got put off. A month or so ago I turned on my plasma only to find the hard drive had failed. I fitted a new ssd and did a build of QtPlasmac with Debian 12 bookworm. Although I got the machine working as such, I have a couple of issues that I am stuck on;

Using the same PC I used previously without issue, I now regularly get errors like 

“Mon24 13:59: Unexpected realtime delay on task 0 with period 1500000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.
Mon24 13:59: hm2/hm2_7i76e.0: Watchdog has bit! (set the .has-bit pin to False to resume)
Mon24 13:59: hm2/hm2_7i76e.0: Smart Serial port 0: DoIt not cleared from previous servo thread. Servo thread rate probably too fast. This message will not be repeated, but the hm2_7i76e.0.sserial.0.fault-count pin will indicate if this is happening frequently.”

I have tried the period setting at 1000000, 1500000, 2000000 etc latency test is around 35000. 



the other major issue is that I can’t cut anything that has an arc unless I use the QtPlasmac conversational. My sheetcam produced code just generates errors like

--- QtVCP Screen Started on: Mon, Feb 24 2025 13:12:29 ---
--- CNC_Plasma - QtPlasmaC v2.9-236.301, powered by QtVCP and LinuxCNC ---
Mon24 13:12: Tool 0: No Tool
Mon24 13:14: Loaded: /home/darren/linuxcnc/nc_files/examples/Darrens Gcode Files/Motor Moutn Blue Mill/10mm motor plate Arc Lead (SMM).ngc
Mon24 13:14: G-Code error in 10mm motor plate Arc Lead (SMM).ngc
Near line 42 of
/tmp/emcflt-m50pkakv.d/10mm motor plate Arc Lead (SMM).ngc
Radius to end of arc differs from radius to start: start=(X31.0695,Y19.2947) center=(X29.4735,Y20.3617) end=(X29.6980,Y20.4360) r1=1.9198 r2=0.2365 abs_err=1.683 rel_err=87.6824%

I have ensured G91.1 is active and all the holes entries are # out in the nc file. 

Can anyone point me in the right direction? I can provide any extra info needed


 

i am not sure whether this is a hal issue or an issue with qtdragon_hd.  
i have just installed 2.9 the newest build,
and rebuilt my machine.  on my old machine the esop on the screen and the physical estop worked independantly.  
now the estop on the screen only reflects the physical button.    may be this is the way it is ment to work and i just had somthing different. 
i liked it as i get the button on the oppiset side form the screen and i had an estop on both sides of the machine.
 

This is cool, I have Mesa CT making a working configuration for the 7i76EU now. Just need to add the spindle types.



Thanks PCW
JT

Update:
The machines works again, without unexpected real time delay and a very good latency, but i had to take the PC of my Lathe. (the lathe machine uses the Mesa 7i76e card)
That PC has a on-board graphic card, but i first tested it with the VGA that was already there and i got the same latency issues. As soon as i used the on-board vga, the latency was perfect and no "realtime errors" at start up.

I have started latency-histogram, with 4 x glxgears and a youtube video running for about 1 hour.
I first started the histogram, then opened one glxgears and waited to check if anything spikes happen. Then i opened 3 more glxgears. No latency spike. Then the youtube video and the pc was running like that for almost one hour without any change to the base thread.
On tomorrow i will run a milling program and check if anything bad happens.

Also i will connect that "latency issue PC" to the Lathe and hope there will be no problems, but i think with the Mesa card there shouldnt be any.

Perfect! Not sure what plasma cutter you have but if it was say hypertherm, a surface mount circular connector that just pushes into the socket on the machine and you would have a nice complete self mounting package. I used the 7i76e spindle relay for torch on so there is nothing wrong with your photo diode. You just need to add a pull down resistor on the arcOK as discussed in the qtplasmac docs. 

Of course if you had a XPR hi def its Ethercat anyway!

I want to set / reset a HAL pin by using G-codes (switching a pneumatic valve on/off).
In the documentation G-code Overview | 4. HAL pins and INI values is written: " ... the only way to set HAL pins from G-code remains M62-M65, M67, M68 and custom M100-M199 codes."
I wrote the below subroutine (macro):

   o<test> sub
   (MSG, Spannzange öffnen)
   M62 #<_hal[hm2_7i76e.0.7i76.0.0.output-00]
   o<test> endsub
   M2

When I run the macro, the response is: "Benannter Parameter nicht beendet"
(Using gmoccapy Ver 3.4.9 in German language)

Is there a better way to control HAL pins?
If not, what do I need to do?

Juergen
 

Fair enough. I thought I had gone through all the steps but I guess I missed it.

I just got a touch probe and want to set it up alongside my tool height setter.

Turns out the tool height setter I bought years ago is NC.
Without even thinking about checking I bought a NO probe which if I am thinking about it correctly if I wanted to wire them into the same pin it would have to be NO.

From what I can tell in reading though it seems like I should be able to wire them into separate pins on my 7i76e, distinguish one as NO, the other as NC, and get it to function properly correct?

And from reading it does sound like LinuxCNC still only has one probe function right? So in the configs I tie both sensors/pins to the single probe function correct?