Advanced Search

Yes, I added some notes to my previous post, you are absolutely right, it is not changing state - see previous if you would!

And yes you are right BCC is putting out a feed per min based on pitch, which is not cool. They say they will modify the processor as I request, we'll see....

Nick

NICKKINSMAN wrote:

I opened up Machine -config and picked the spindle-revs and it counts up at like 20 decimal places on the 'watch'. I also checked the motion-spindle-enable and it shows;

FALSE motion.spindle-index-enable <=> spindle.index.enable

When selected in 'watch' it shows a red dot.

I believe that means it's connected?

Yes.

The next question is whether index-enable changes state when you run the code. (you probably need Halscope to see that).
Though I am not at all sure that G94 uses index.

Wait, hang on, I have my modes confused (as, possibly, does BobCAM)

G95 is feed-per-rev mode, and is what you might use for a thread if G76 was too confusing.
G94 is feed per minute. I think that G0code just gives you a very, very, slow feed of .063 in/minute. That would look like a stopped machine.

I opened up Machine -config and picked the spindle-revs and it counts up at like 20 decimal places on the 'watch', and hits 1 count per revolution (at least as best I can tell, I did not try to match up exactly but it is pretty close by eyeball). I also checked the motion-spindle-enable and it shows;

FALSE motion.spindle-index-enable <=> spindle.index.enable

When selected in 'watch' it shows a red dot.

I believe that means it's connected?

OK, on further testing I may have an index enable problem! I ran a G76 threading cycle to see how it would work, after some initial confusion, I found that it would index and start, but only after stopping the spindle. So, it would not start a pass with spindle moving, but once I stopped and restarted it would do a pass, then return Z and move in X for next pass, but would not start cutting. Once I stopped and re-started the spindle, it would then sync (you could see the hesitation while it waited for the spot to come around, running spindle slow) complete the next pass, return, etc and stop. Stop spindle, restart, Etc, etc....until completed passes.

So, where would my problem lie then? It appears EMC is hooked up, but something is not kicking off the enable to start moving. Sounds like a hardware problem maybe? But on what point? I'll recheck my terminations to the right pins, but since I am getting the right spindle rev counts based on encoder counts, would it be the index signal which is causing the problem??

Thanks for the feedback! Sooooo close....
Nick

beta1 is good.
Hope it helps you out.
Let me know of any other problems.

finally it works
I had the beta1 version.
thank you for your help

I'll check it out when I get home
in a few hours

Then you compiled it your self? Does the splash page in pncconf say alpha or beta1? (this is on the page it's self not in the terminal.

I have 2.5, but would perhaps not
download from buildbot.linuxcnc.org/ lucid master-rt

NICKKINSMAN wrote:

I'm still trying to get my hands around the coding in HAL, but I have the spindle encoder connected and working via PncConf. I have the RPM meter setup in Axis with good readout. When I go into the axis config, I can pull up the rev count pin and I get counts all the way around the revolution to 3 decimals, with continuous counts up. I am hoping that means it is working!

It means it is working, but is it linked back into EMC2?

Put a halmeter on the motion.spindle-revs pin specifically, and see if that follows the encoder position. It needs to increment by 1 for every complete revolution.
You also need motion.spindle-index-enable linked if you want to do threading (but possibly not for that BobCAD way of approximating a thread.)

Machine->show hal config will also indicate if those pins are linked.

I'm still trying to get my hands around the coding in HAL, but I have the spindle encoder connected and working via PncConf. I have the RPM meter setup in Axis with good readout. When I go into the axis config, I can pull up the rev count pin and I get counts all the way around the revolution to 3 decimals, with continuous counts up. I am hoping that means it is working!

Othewise is there something else to check?

And yes, I am confused on why BCC does not output the threading command, I have canned cycles selected. I will have to give them a call. I hear your compliant on BCC. I thought it was pretty good software to begin with, but this posting leaves a lot to be desired. I do like the milling side of it, but haven't had a chance to run the code yet.

Thanks!

OK, yes I need to touch of the G54 then, I was not doing that, just touching off the tool table. I will do that.

Thanks!
Nick

when you extracted it was it still in the folder named custom_firmware ? It should be.

The text should go in the file named .pncconf-preferences

Then open pncconf from a terminal when the splash screen shows it should say
something like "Pncconf founf extra firmware"
it should also say something like:

/home/chris/Desktop/custom_firmware/firmware.py

You are sure your using 2.5 ( hmm when did you get 2.5?)

NICKKINSMAN wrote:

G01 X.962 Z0. S500 M3 G94 F.063

Do you have motion.spindle-revs wired in HAL? Without that, G94 won't work.
www.linuxcnc.org/docview/html/config_emc2hal.html

Also, that is unlikely to cut a decent thread (and there is no chance of multi-pass threading that way.)

thanks for the reply.
but it does not work.
I added the bit file
and downloaded firmware.py
and extract it on the desktop.
I put the text in the file also,
if it was the right file?

I forgot to mention, in case you didnt know to add the PIN file Peter sent you in the folder
/lib/firmware/hm2/7i43-4

probably need root access to do that