Can't get my spindle to turn on

More
06 Aug 2020 07:19 #177470 by tommylight
Sorry, i meant the spindle PWM scaling is to high in the hal file, but it might be ok.
As for missing stuff, it should work without it as the important PWM and spindle on are there.
The spindle on is set at pin 17 in hal, so make sure you have the spindle relay attached to output 1 on the G540, open Axis GUI and after enabling the machine press F9, that should trigger the relay then with F11 and F12 try the speed.

Please Log in or Create an account to join the conversation.

More
06 Aug 2020 15:41 #177526 by devinw
Yeah, did that. Nada though. I am 1000% sure my relay is on pin 17/Output 1 on the Gecko, because I can boot back into Mach4 and it's working and triple checked that's how it's configured.

Please Log in or Create an account to join the conversation.

More
06 Aug 2020 15:55 #177529 by tommylight
Can you try making another config but this time in the second screen choose "import from mach" ?
That would need access to an xml file that mach creates, so you would need to copy that from windows to Linux.

Please Log in or Create an account to join the conversation.

More
07 Aug 2020 05:34 #177578 by devinw
Welllll, I don't think I can because I believe they have done away with XMLs with Mach4. I think mach3 was the end of XML profiles . I copied my whole profile folder to a thumb drive but stepconfig didn't want to read anything in there.

I also opened linuxcnc and pulled up the HAL monitor and could see the output on parallel port pin 17 flip true/false as I turned the spindle on, so the program definitely THINKS it's flipping the bit, but it's not getting to the Gecko! So strange!

I quadruple checked again in my Mach4 config and indeed Spindle On Is pin 17, and the spindle definitely works, complete with relay click. This is a real head scratcher

Please Log in or Create an account to join the conversation.

More
07 Aug 2020 06:19 #177581 by anfänger
I would check if the signals and pins get high as they should. I usually try to debug with haushoch here:
linuxcnc.org/docs/html/hal/halshow.html
Also I would try to manually set pin 17 to high with
Halcmd
linuxcnc.org/docs/html/man/man1/halcmd.1.html

I would be something like:
halcmd setp NAMEOFPIN high

If it is linked these should come an error and you can try toggle the signal:
halcmd setp NAMEOFSIGNAL high

This would also error if everything is connected correctly

Sorry that i don‘t put in the signal and pin names from your hal, but I can‘t open hal files on the device I am working right now

Please Log in or Create an account to join the conversation.

More
07 Aug 2020 11:29 #177595 by tommylight
Can you try changeing this line in hal
loadrt hal_parport cfg="d000 out"
to
loadrt hal_parport cfg="0xd000 out"
What does
sudo lspci -v
in a terminal say ?

Please Log in or Create an account to join the conversation.

More
07 Aug 2020 11:30 #177596 by tommylight

Can you try changeing this line in hal
loadrt hal_parport cfg="d000 out"
to
loadrt hal_parport cfg="0xd000 out"
and
setp parport.0.reset-time 1000
to
setp parport.0.reset-time 5000
What does
sudo lspci -v
in a terminal say ?

Please Log in or Create an account to join the conversation.

More
11 Aug 2020 23:53 #177960 by devinw

Can you try changeing this line in hal
loadrt hal_parport cfg="d000 out"
to
loadrt hal_parport cfg="0xd000 out"
and
setp parport.0.reset-time 1000
to
setp parport.0.reset-time 5000
What does
sudo lspci -v
in a terminal say ?



Same thing.

Sudo lspci -v dumps a ton of stuff out. Regarding the PP it says oxford semicondrocut LTD device c110. Io ports at d000 size 8 and d008 size 4. Kernel drive parport_pc

Please Log in or Create an account to join the conversation.

Time to create page: 0.272 seconds
Powered by Kunena Forum