Hello Guest it is March 28, 2024, 09:02:34 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - flenser

Pages: « 1 2
11
General Mach Discussion / Re: lathe threading problem - ghost trigger
« on: February 27, 2010, 12:17:50 PM »
I had them enabled originally. Spindle RPM won't read unless they are enabled. I disabled them to try to eliminate all possible sources of the trigger the threading code is getting.

If I understand correctly, it should hang forever on g76 without a trigger.

It doesn't hang with or without the spindle relays enabled. It makes cutting passes as if it's getting a trigger, but it isn't getting one. Not from me, anyway.

Jeff

12
General Mach Discussion / Re: lathe threading problem - ghost trigger
« on: February 27, 2010, 11:43:32 AM »
I attached my xml file. It should be very close to the default machturn file.

Setting spin up and down delay didn't have an effect.

Thanks - Jeff

13
General Mach Discussion / lathe threading problem - ghost trigger
« on: February 27, 2010, 10:15:02 AM »
Sorry if this has been covered before. I spent a while looking for related issues without success. You can probably skip over all but the last two paragraphs. I don't think the problem has anything to do with my wiring.

I started with the CNC4PC index pulse card, and setup the index with a slotted disc pretty much as described. I mapped it to an input port, enabled the spindle output (not sure why this is required), and entered an m3 command. The spindle RPM reads correctly.

The code produced by the threading wizard, however, appears to start each pass without waiting for a pulse. I thought I might have a noise problem, checked the signal with a scope, but it looks fine. I then switched to using a hall effect sensor I had laying around, and while the RPMs still read correctly, the gcode from the thread wizard still starts seemingly without waiting for a pulse.

OK, I mapped the index input to the estop input to make sure it stayed off, disabled the spindle output, turned off the spindle: true RPM reads zero. I run the code output by the wizard in diag mode, and the index led remains off the entire time. I see the wait for trigger led come on, then go off and a thread pass is started. Where is it getting the trigger?

I started with the latest version, but removed it and installed version 033 based on recommendations in numerous threads.

Thanks - Jeff


Pages: « 1 2