- Posts: 66
- Thank you received: 0
Pin 'spindle-enable' does not exist
- EragonPower
- Topic Author
- Offline
- Senior Member
-
In a previous topic i was looking for a solution to my spindle VFD problem, to recap, my VFD has FWD and REV pins for controlling it, not ENA and DIR, as my mesa 7i76e, so i tried to reconfigure the pin outputs to work with FWD/REV in hal, the modification worked at first, AXIS started, but i couldn't try the VFD because i hadn't homed the machine(i haven't a CNC yet, it's coming in the next month, but i've started to build the electical panel any way), i've made this mod some days ago.
Fast forward to today, i've started AXIS from the Desktop and this error appared:
./CNC.hal:379: Pin 'spindle-enable' does not exist
i've looked through the .hal file for an hour searching for the problem, but i found none.
Here are the .hal and .ini files with also the crash report.
Is there anyone that knows what causes the problem?
Thanks in advance
Attachment not found
Attachment not found
Attachment not found
Please Log in to join the conversation.
./CNC.hal:379: Pin 'spindle-enable' does not exist
Just say that the error is on line 379 in the hal file. I am not sure but the pin spindle-enable might have changed so use halshow to find the correct name.
Try just hashing # that line out to move on.
Please Log in to join the conversation.
- EragonPower
- Topic Author
- Offline
- Senior Member
-
- Posts: 66
- Thank you received: 0
./CNC.hal:381: Pin 'spindleEnableMesa' does not exist
Edit: I've rewatched a video from swolebro on youtube( www.youtube.com/channel/UCRMLI3S0AFukV1tzX6Cl2Cw ) and noticed that he wrote "motion." in front of "spindle-on", so i tried that and AXIS started. I'm not shore why that worked, maybe it's because spindle-enable is a motion pin, so it needed "motion." before it (motion.spindle-enable)
Please Log in to join the conversation.
net <net-name> <pins>
you have
net <pins> <net-name>
Please Log in to join the conversation.
EragonPower wrote: "motion." in front of "spindle-on", so i tried that and AXIS started.
Which version of LinuxCNC are you using?
if motion.spindle-on is a valid pin name then you must be using an old version of LinuxCNC.
But from other things that you have said I suspect that what you have done is create a signal name in HAL called "motion.spindle-on"
The HAL "net" command creates a signal, to which you can then connect as many pins as you want.
But the signal name can be anything (including the name of an existing pin, but that's a really bad idea)
The pin names, however, must be pins that already exist at the time that the net command is executed.
And, on LinuxCNC v2.8+ the spindle on is "spindle.0.on" (or, spindle.1.on for the second spindle, and so on)
Please Log in to join the conversation.
- EragonPower
- Topic Author
- Offline
- Senior Member
-
- Posts: 66
- Thank you received: 0
The problem is that AXIS gives a "Pin does not exist"
Update: I've remade HAL file through PnCConf, added and2 components, loaded them into the servo-thread, and connected the signals to the pins of the ands.
I was doing a big mistake, i was connecting the signals to the and2 using this structure:
net spindle-enable => and2.0.in1
the arrow wasn't needed an i wasn't specifing the pin, i've instead have used:
net spindle-enable and2.0.in1
When i've started using this structure AXIS started without errors and everything looks right
Please Log in to join the conversation.
If I have such problems, I do comment out the entry in my Hal file. I do this with all stuff, that is not ok, until my GUI does start. Then I do open Hal show from the GUI and open the same time the Hal file in an editor. So I can compare the pin names from the Hal file and halshow. After correcting the names, I save the Hal file and restart linuxcnc.
Norbert
Please Log in to join the conversation.
EragonPower wrote: I'm using Linuxcnc 2.8, at first adding "motion." made AXIS start, but now, it's now working again, am i missing something? I'm fearly new at linuxcnc, i don't have many hours working with HAL.
The problem is that AXIS gives a "Pin does not exist"
Update: I've remade HAL file through PnCConf, added and2 components, loaded them into the servo-thread, and connected the signals to the pins of the ands.
I was doing a big mistake, i was connecting the signals to the and2 using this structure:
net spindle-enable => and2.0.in1
the arrow wasn't needed an i wasn't specifing the pin, i've instead have used:
net spindle-enable and2.0.in1
When i've started using this structure AXIS started without errors and everything looks right
Those two statements do the exact same thing. The => does nothing and is for visual enjoyment only.
Please Log in to join the conversation.
andypugh wrote: And, on LinuxCNC v2.8+ the spindle on is "spindle.0.on" (or, spindle.1.on for the second spindle, and so on)
I really don't understand how this spindle.0.on signal is generated and by what. Is it logically the same as spindle.0.enable in the spindle RT component man? I get the feeling that "on", "enable", "true" and "1" may all have the same effect.
linuxcnc.org/docs/2.8/html/man/man9/spindle.9.html
PncConf has set up 3 PID instances for my lathe (x, y and s) but I can't see spindle being called. However, in the main hal file I have 3 connections to my spindle-enable net:
net spindle-enable <= spindle.0.on (where does this come from?)
net spindle-enable => pid.s.enable
net spindle-enable => hm2_5i25.0.7i76.0.0.spinena
Can you tell me where spindle.0.on connects? Many thanks. You will note that there is no "loadrt spindle" anywhere.
There are still various things not working here. The pendant connects up but doesn't control the Probe Basic GUI. I have some work to do here to understand what is happening.
Attachment not found
Attachment not found
Attachment not found
Please Log in to join the conversation.
Please Log in to join the conversation.
