Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I went through the technical manual, and found the variables to tweek to enable the resistor braking. On the Yasawa they seem to be: L30-04 = 3 L8-01 = 1 then I set: C1-02 for .2 (sec) deceleration Oh boy, what a difference the correct settings make! Thank you for getting back Scott! --J. Ray

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

See page 72 of manual for breaking resistor config. Scott On Tuesday, August 18, 2020, 12:17:35 PM CDT, jrmitchellj wrote: Hi Scott. I have a Yaskawa V1000 on my spindle, and have installed a encoder on the spindle. Would you share what settings in the V1000 to get rigid tapping workin

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 18 August 2020 15:16:07 Jon Elson wrote: > On 08/18/2020 12:13 PM, jrmitchellj wrote: > > Hi Scott. > > I have a Yaskawa V1000 on my spindle, and have installed a encoder > > on the spindle. > > Would you share what settings in the V1000 to get rigid tapping > > working well? I have br

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 08/18/2020 12:13 PM, jrmitchellj wrote: Hi Scott. I have a Yaskawa V1000 on my spindle, and have installed a encoder on the spindle. Would you share what settings in the V1000 to get rigid tapping working well? I have braking resistors installed, but don't know what variable to change to brin

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 18 August 2020 13:13:47 jrmitchellj wrote: > Hi Scott. > I have a Yaskawa V1000 on my spindle, and have installed a encoder on > the spindle. > Would you share what settings in the V1000 to get rigid tapping > working well? I have braking resistors installed, but don't know what > vari

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Hi Scott. I have a Yaskawa V1000 on my spindle, and have installed a encoder on the spindle. Would you share what settings in the V1000 to get rigid tapping working well? I have braking resistors installed, but don't know what variable to change to bring them into play. Any help & tips always wel

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 08/04/2020 02:05 PM, Thaddeus Waldner wrote: Do any servos or VFD systems actually run their base frequency higher than 20khz? If not, where do those harmonics come from? Many servo systems run above 20 KHz to increase bandwidth. And, the sharp switching transitions cause there to be man

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 04 August 2020 15:05:10 Thaddeus Waldner wrote: > Can you or someone else please expand on that? > > Most VFD that I am familiar with operate between 10khz and 20khz. I > personally like to configure them upwards of 16khz because I find the > squealing noise annoying. I suppose that the

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Can you or someone else please expand on that? Most VFD that I am familiar with operate between 10khz and 20khz. I personally like to configure them upwards of 16khz because I find the squealing noise annoying. I suppose that the main reason to not do that is that it increases switching losses.

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 08/04/2020 08:00 AM, Matthew Herd wrote: I am guessing that the source of the trouble is probably the VFD, as 80kHz seems like a plausible base frequency for driving an AC motor. Only the USC should be operating at a frequency higher than 60Hz other than the VFD. The machine uses three g

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Thanks Gene, I just ordered a Rasmi unit that should be able to mount behind the VFD inside the panel (assuming enough depth in the box). Apparently they make them for Yaskawa drives, but my Hitachi has the same bolt pattern. I’ll get it installed and see how it looks. If that checks out, I’l

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 04 August 2020 09:09:38 andy pugh wrote: > On Tue, 4 Aug 2020 at 14:03, Matthew Herd wrote: > > I am guessing that the source of the trouble is probably the VFD, as > > 80kHz seems like a plausible base frequency for driving an AC motor. > > Add an input filter to the VFD. They are not

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 04 August 2020 09:00:30 Matthew Herd wrote: > Yes, I figured as much, but I figure it’s a problem that should be > solved and the noise looks like a contributing factor. > > I am guessing that the source of the trouble is probably the VFD, as > 80kHz seems like a plausible base frequenc

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 04 August 2020 08:48:28 andy pugh wrote: > On Tue, 4 Aug 2020 at 13:39, Matthew Herd wrote: > > I’m wondering if there’s any value in isolating power and logic > > grounds or isolating either one from the machine. > > That isn't always possible, even if you want to. The drives themsel

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 04 August 2020 08:37:06 Matthew Herd wrote: > Sorry for the delayed reply. I did some work on the scope on Sunday > morning and have attached some pictures of the results. Let me know > if they don’t come through. > > In sort, the results appear to show a roughly 80kHz noise when the

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 4 Aug 2020 at 14:03, Matthew Herd wrote: > I am guessing that the source of the trouble is probably the VFD, as 80kHz > seems like a plausible base frequency for driving an AC motor. Add an input filter to the VFD. They are not expensive. Look on eBay for "Rasmi" (one manufacturer, but

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Yes, I figured as much, but I figure it’s a problem that should be solved and the noise looks like a contributing factor. I am guessing that the source of the trouble is probably the VFD, as 80kHz seems like a plausible base frequency for driving an AC motor. Only the USC should be operating

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 4 Aug 2020 at 13:39, Matthew Herd wrote: > I’m wondering if there’s any value in isolating power and logic grounds or > isolating either one from the machine. That isn't always possible, even if you want to. The drives themselves tend to tie them together. But, random indexes shouldn'

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Sorry for the delayed reply. I did some work on the scope on Sunday morning and have attached some pictures of the results. Let me know if they don’t come through. In sort, the results appear to show a roughly 80kHz noise when the machine is turned on, with spikes pretty frequently exceeding

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 08/01/2020 01:37 PM, Matthew Herd wrote: Thanks Gene, I hope you’re well also. I disconnected that grounding wire, no difference observed in the ppmc.0.encoder.03.index behavior. The noise seems the same both when spindle is running and stopped, with a tendency strongly toward "true" than

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 08/01/2020 11:10 AM, Matthew Herd wrote: I'm still having issues with the rigid tapping. It works sometimes and fails other times. After scoping the motion.spindle-revs, it appears to be consistent with what we would expect aside from one possible issue. The spindle revs reset to zero upon

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Saturday 01 August 2020 18:39:47 Matthew Herd wrote: > Thanks Chris, that was my thinking as well. I’ll try that tomorrow > and see what we find. I’m not sure there’s much more I could > disconnect in the ground department, but we’ll start looking at that > after we isolate the problem to enc

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Thanks Chris, that was my thinking as well. I’ll try that tomorrow and see what we find. I’m not sure there’s much more I could disconnect in the ground department, but we’ll start looking at that after we isolate the problem to encoder vs. USC board. > On Aug 1, 2020, at 5:35 PM, Chris Alber

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Sat, Aug 1, 2020 at 11:40 AM Matthew Herd wrote: > Thanks Gene, I hope you’re well also. I disconnected that grounding wire, > no difference observed in the ppmc.0.encoder.03.index behavior. The noise > seems the same both when spindle is running and stopped, with a tendency > strongly towar

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Saturday 01 August 2020 14:37:49 Matthew Herd wrote: > Thanks Gene, I hope you’re well also. I disconnected that grounding > wire, no difference observed in the ppmc.0.encoder.03.index behavior. > The noise seems the same both when spindle is running and stopped, > with a tendency strongly to

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Thanks Gene, I hope you’re well also. I disconnected that grounding wire, no difference observed in the ppmc.0.encoder.03.index behavior. The noise seems the same both when spindle is running and stopped, with a tendency strongly toward "true" than "false." Pulses seem to be both long and sho

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Saturday 01 August 2020 12:10:55 Matthew Herd wrote: > I'm still having issues with the rigid tapping. It works sometimes > and fails other times. After scoping the motion.spindle-revs, it > appears to be consistent with what we would expect aside from one > possible issue. The spindle revs

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I'm still having issues with the rigid tapping. It works sometimes and fails other times. After scoping the motion.spindle-revs, it appears to be consistent with what we would expect aside from one possible issue. The spindle revs reset to zero upon G33.1 being called, then count up until they s

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Thanks Andy, I’ll give the documentation a thorough read through and see how it might be best incorporated. > On Jul 23, 2020, at 3:07 PM, andy pugh wrote: > > On Thu, 23 Jul 2020 at 17:06, Jon Elson wrote: > >>> Who is in charge of the integrator’s manual? I’d like to investigate >>> writi

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Thu, 23 Jul 2020 at 17:06, Jon Elson wrote: > > Who is in charge of the integrator’s manual? I’d like to investigate > > writing some additional sections. > > > You can submit suggested changes to John Thornton, or get > commit access yourself. Fir docs you can edit the asccidoc file live o

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/23/2020 05:21 AM, Matthew Herd wrote: I should also note I made an error in my revolutions calculation. It should be RPM / 2 / 60 sec * deceleration time = revolutions to stop, assuming linear deceleration. That’s probably the default for most drives. For 560 RPM, that comes out to 2.

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Thu, 23 Jul 2020 at 11:24, Matthew Herd wrote: > Who is in charge of the integrator’s manual? I’d like to investigate writing > some additional sections.= We all are. :-) The "Integrator manual" may not be the manual you need to change, but is made of these files. https://github.com/LinuxC

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I should also note I made an error in my revolutions calculation. It should be RPM / 2 / 60 sec * deceleration time = revolutions to stop, assuming linear deceleration. That’s probably the default for most drives. For 560 RPM, that comes out to 2.8 revolutions. So my observations at 2.9 revo

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/22/2020 08:51 PM, Matthew Herd wrote: Upon testing, I found that rigid tapping worked as intended, Excellent. Glad Robert Ellenberg is watching here, as most of us had no idea the trajectory planner had this behavior. I love rigid tapping, and have made two fixture plates with a 1" g

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I got the braking resistor installed, fiddled with all the DC injection braking and dynamic braking parameters on the machine, then started turning down the deceleration time. It looks like I only tuned the acceleration time when I originally installed the VFD because it was set to the default

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 21 July 2020 18:40:35 Scott Harwell via Emc-users wrote: > Just got my new Control Engineering in the mail and saw this."Top 5 > VFD parameter changes explained" > > > > > > > > > > > > Top 5 VFD parameter changes explained > > Chris Vavra > > Learning Objectives Setting five parameter

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Just got my new Control Engineering in the mail and saw this."Top 5 VFD parameter changes explained" | | | | | | | | | | | Top 5 VFD parameter changes explained Chris Vavra Learning Objectives Setting five parameters can take care of most VFD programming. Consider VFD control met.

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Matt, Are you seeing overvoltage faults on the VFD? If you are not decrease the decel time until you see a fault and then bump it back up until you are fault free. I don't know what the breaking resistors will do if you are not seeing a fault now, they are used to drop the B+ from the regen dur

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 21 July 2020 14:44:12 Robert Ellenberg wrote: > I totally agree that a silent failure mode (especially one that can > break taps) is bad news. Perhaps thankfully, we've gotten away with it > for a long time: based on the git history, the 10-rev overshoot limit > and this silent failure

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I totally agree that a silent failure mode (especially one that can break taps) is bad news. Perhaps thankfully, we've gotten away with it for a long time: based on the git history, the 10-rev overshoot limit and this silent failure mode has been around at least since the 2.6 days, maybe earlier.

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 12:43 PM, Matthew Herd wrote: When I installed the spindle encoder, I used a shaft at the top of the head. Due to my failure to investigate more fully, it turns out that it’s geared 1:1 with the spindle (but is not a part of the spindle). So when I go into backgear, the encoder

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tuesday 21 July 2020 13:09:16 andy pugh wrote: > On Tue, 21 Jul 2020 at 18:03, Robert Ellenberg wrote: > >1. The rigid tapping cycle allows a hard-coded 10 revolutions > > > > >56> of overtravel beyond the nominal b

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 12:27 PM, andy pugh wrote: On Tue, 21 Jul 2020 at 18:16, Matthew Herd wrote: Thanks for the insights. I suspected something along these lines, even if I might have other problems with noise. I can confirm, the spindle stops way too slowly and definitely more than 10 revolutio

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 12:14 PM, Matthew Herd wrote: Hi Rob, Thanks for the insights. I suspected something along these lines, even if I might have other problems with noise. I can confirm, the spindle stops way too slowly and definitely more than 10 revolutions pass before stopping. Long story sho

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On a related note, I’ve noticed that the G-Code reference for G33 and G33.1 refers you to the integrators manual, but there’s little documentation on spindle synchronized motion. I’d be willing to add a section based on what I learn from this experience. It might be helpful to make sure there’

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 12:09 PM, andy pugh wrote: On Tue, 21 Jul 2020 at 18:03, Robert Ellenberg wrote: 1. The rigid tapping cycle allows a hard-coded 10 revolutions of overtravel beyond the nominal bottom of the hole w

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 12:00 PM, Robert Ellenberg wrote: Based on the videos and your descriptions of the behavior, you may be running into a TP issue I've seen (in simulation) with very sluggish spindles or very high spindle speeds. Here's what I think is going on: 1. The rigid tapping cycle allows

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 18:46, Matthew Herd wrote: > When I installed the spindle encoder, I used a shaft at the top of the head. > Due to my failure to investigate more fully, it turns out that it’s geared > 1:1 with the spindle (but is not a part of the spindle). So when I go into > backgea

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 10:15 AM, Matthew Herd wrote: Ahh, so I do use limit switches and a homing routine. So it’s homing to the same position (plus or minus a few thousandths or so). So, use the # key to show machine coordinates, and then move the Z to the safe limits of travel, and note the Z value

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 10:14 AM, Matthew Herd wrote: The ppmc.0.encoder.03.index pin is something I can halscope easily enough. I was having a little trouble getting used to the halscope interface, and without a signal that I know will repeat every revolution, it’s hard to be sure you’re not just miss

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

When I installed the spindle encoder, I used a shaft at the top of the head. Due to my failure to investigate more fully, it turns out that it’s geared 1:1 with the spindle (but is not a part of the spindle). So when I go into backgear, the encoder reads opposite direction and at a different r

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 18:16, Matthew Herd wrote: > Thanks for the insights. I suspected something along these lines, even if I > might have other problems with noise. I can confirm, the spindle stops way > too slowly and definitely more than 10 revolutions pass before stopping. > Long stor

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Hi Rob, Thanks for the insights. I suspected something along these lines, even if I might have other problems with noise. I can confirm, the spindle stops way too slowly and definitely more than 10 revolutions pass before stopping. Long story short, I can’t readily run the machine in back ge

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 18:03, Robert Ellenberg wrote: >1. The rigid tapping cycle allows a hard-coded 10 revolutions > >of overtravel beyond the nominal bottom of the hole when reversing >direction. That feels

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Based on the videos and your descriptions of the behavior, you may be running into a TP issue I've seen (in simulation) with very sluggish spindles or very high spindle speeds. Here's what I think is going on: 1. The rigid tapping cycle allows a hard-coded 10 revolutions

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Ahh, so I do use limit switches and a homing routine. So it’s homing to the same position (plus or minus a few thousandths or so). > On Jul 21, 2020, at 11:07 AM, Jon Elson wrote: > > On 07/21/2020 04:20 AM, andy pugh wrote: >> On Tue, 21 Jul 2020 at 10:18, andy pugh wrote: >> >>> We are not

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

The ppmc.0.encoder.03.index pin is something I can halscope easily enough. I was having a little trouble getting used to the halscope interface, and without a signal that I know will repeat every revolution, it’s hard to be sure you’re not just missing it with your scope parameters. I’m sure t

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 04:20 AM, andy pugh wrote: On Tue, 21 Jul 2020 at 10:18, andy pugh wrote: We are not looking for noise, we are looking for spurious encoder count resets. But, thinking further, even if there _is_ noise on the index line, the encoder counter should ignore it. It ignores all the _

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/21/2020 04:18 AM, andy pugh wrote: On Tue, 21 Jul 2020 at 01:59, Gene Heskett wrote: Try halscoping motion.spindle-revs through a G33,1 cycle in air. halscope hasn't, Andy, by decades, enough bandwidth to register the noise I'd be looking for. We are not looking for noise, we are looki

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 10:18, andy pugh wrote: > We are not looking for noise, we are looking for spurious encoder count > resets. But, thinking further, even if there _is_ noise on the index line, the encoder counter should ignore it. It ignores all the _real_ indexes unless index-enable is se

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 01:59, Gene Heskett wrote: > > Try halscoping motion.spindle-revs through a G33,1 cycle in air. > > halscope hasn't, Andy, by decades, enough bandwidth to register the noise > I'd be looking for. We are not looking for noise, we are looking for spurious encoder count reset

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 22:14:10 Jon Elson wrote: > On 07/20/2020 07:43 PM, Gene Heskett wrote: > > Interesting. I wonder if he accidently fixed an unwanted ground, or > > made a bad one good doing it? Murphy is alive and well despite our > > reward funds. > > Yes, he had unwanted grounds (loops)

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/20/2020 07:43 PM, Gene Heskett wrote: Interesting. I wonder if he accidently fixed an unwanted ground, or made a bad one good doing it? Murphy is alive and well despite our reward funds. Yes, he had unwanted grounds (loops) all over the place. Actually, he has NO ground, only a neutra

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 20:39:38 andy pugh wrote: > On Tue, 21 Jul 2020 at 01:33, Matthew Herd wrote: > > Good thoughts Jon and Gene, I was thinking the same thing. The > > count when running the encoder diagnostics keeps resetting to 0. So > > I will drag out my scope and see what I find. > > I

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 20:30:59 Matthew Herd wrote: > Good thoughts Jon and Gene, I was thinking the same thing. The count > when running the encoder diagnostics keeps resetting to 0. So I will > drag out my scope and see what I find. Hopefully a little checking of > the grounds plus a braking

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 20:30:30 Jon Elson wrote: > On 07/20/2020 07:04 PM, Gene Heskett wrote: > > I think I'd drag out one of my 100+ MHZ scopes and look for noise of > > the type one might get from lack of a single point ground. > > Right. if the indexres test of the diagnostics shows the > pos

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Tue, 21 Jul 2020 at 01:33, Matthew Herd wrote: > > Good thoughts Jon and Gene, I was thinking the same thing. The count when > running the encoder diagnostics keeps resetting to 0. So I will drag out my > scope and see what I find. I think you will have a lot more luck with halscope than r

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I had a suspicion that the very long deceleration times might have exposed a bug in the software. I doubt I’m exceeding soft limits, but I’ll run some more tests when I play with it next. > On Jul 20, 2020, at 8:30 PM, Jon Elson wrote: > > On 07/20/2020 07:04 PM, Gene Heskett wrote: >> >> I

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Good thoughts Jon and Gene, I was thinking the same thing. The count when running the encoder diagnostics keeps resetting to 0. So I will drag out my scope and see what I find. Hopefully a little checking of the grounds plus a braking resistor and I’ll be able to rigid tap. I’ve got a projec

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/20/2020 07:04 PM, Gene Heskett wrote: I think I'd drag out one of my 100+ MHZ scopes and look for noise of the type one might get from lack of a single point ground. Right. if the indexres test of the diagnostics shows the position resetting multiple times/rev (may only happen when spind

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 18:57:03 Jon Elson wrote: > On 07/20/2020 05:27 PM, Matthew Herd wrote: > > Working through Jon’s suggestions, the answers to his questions are > > as follows. Also, I’m running version 2.7.11 if that helps. No > > internet in my shop means it gets infrequent updates. > >

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/20/2020 05:27 PM, Matthew Herd wrote: Working through Jon’s suggestions, the answers to his questions are as follows. Also, I’m running version 2.7.11 if that helps. No internet in my shop means it gets infrequent updates. Running the universal stepper diagnostics program with the comm

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Working through Jon’s suggestions, the answers to his questions are as follows. Also, I’m running version 2.7.11 if that helps. No internet in my shop means it gets infrequent updates. Running the universal stepper diagnostics program with the command sudo .univstepdiags 378 bus indicates b

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 15:28:22 Jon Elson wrote: > On 07/20/2020 01:59 PM, Gene Heskett wrote: > > Jon's (Pico Systems) pwm-servo is a full 4 quadrant controller, > > without a brakiing R, it will charge the caps in the supply from 125 > > to about 160 but turns my 1 hp PMDC motor on my GO704 arou

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/20/2020 01:59 PM, Gene Heskett wrote: Jon's (Pico Systems) pwm-servo is a full 4 quadrant controller, without a brakiing R, it will charge the caps in the supply from 125 to about 160 but turns my 1 hp PMDC motor on my GO704 around in about 400 milliseconds. If your supply is higher than m

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Monday 20 July 2020 10:57:30 Matthew Herd wrote: > Thanks for the input Jon, Andy, and Scott. Unfortunately, it already > counts positive in the clockwise direction, so that’s not it. I’ll go > through Jon’s list of suggestions step by step when I get back to the > machine in a few days and l

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I am using the vari-speed head, so I’m already in the high range and running at minimum speed. Unfortunately I can’t tune the VFD ramp down to be optimum for low speed because at high speed it overloads (due to the increased inertia). And so far as I know my Hitachi VFD can only ramp down in a

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Do you have a 2 speed gear box? If so try tapping in high range with lower spindle (motor) speed. This will give you a much better ramp. Scott On Monday, July 20, 2020, 10:00:14 AM CDT, Matthew Herd wrote: Thanks for the input Jon, Andy, and Scott.  Unfortunately, it already counts

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/20/2020 10:51 AM, Matthew Herd wrote: Hi Andy, "But does it also count negative in reverse?" Yes, counts go up and down, depending on the direction I turn the spindle, either manually or under power. Hmmm, the mystery deepens! Well, it may be that the encoder index-enable connection i

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Mon, 20 Jul 2020 at 17:07, Matthew Herd wrote: > > It appears to increment/decrement by exactly 1 for each revolution, but I > didn’t put a degree wheel on the spindle to be sure of my rotation > measurement. If it is close to 1, then it probably is 1. I think we need to see your HAL file.

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

It appears to increment/decrement by exactly 1 for each revolution, but I didn’t put a degree wheel on the spindle to be sure of my rotation measurement. > On Jul 20, 2020, at 11:58 AM, andy pugh wrote: > > On Mon, 20 Jul 2020 at 16:53, Matthew Herd wrote: > >> "But does it also count negativ

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Mon, 20 Jul 2020 at 16:53, Matthew Herd wrote: > "But does it also count negative in reverse?" > Yes, counts go up and down, depending on the direction I turn the spindle, > either manually or under power. And motion.spindle-revs goes up or down by exactly 1.0 for each revolution? -- atp "

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Hi Andy, "But does it also count negative in reverse?" Yes, counts go up and down, depending on the direction I turn the spindle, either manually or under power. Matt ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Mon, 20 Jul 2020 at 16:00, Matthew Herd wrote: > > Thanks for the input Jon, Andy, and Scott. Unfortunately, it already counts > positive in the clockwise direction, so that’s not it. But does it also count negative in reverse? -- atp "A motorcycle is a bicycle with a pandemonium attachmen

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Thanks for the input Jon, Andy, and Scott. Unfortunately, it already counts positive in the clockwise direction, so that’s not it. I’ll go through Jon’s list of suggestions step by step when I get back to the machine in a few days and let you know how it goes. I also realized that a spindle b

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

I would swap A phase with B phase this should correct count direction. Scott H On Sunday, July 19, 2020, 6:16:57 PM CDT, Jon Elson wrote: On 07/19/2020 03:59 PM, Matthew Herd wrote: > Hi all, > > I made my first attempt at using spindle synchronized motion for a rigid > tapping operat

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On 07/19/2020 03:59 PM, Matthew Herd wrote: Hi all, I made my first attempt at using spindle synchronized motion for a rigid tapping operation on my Bridgeport BOSS mill today and it didn’t go as planned. It has a spindle encoder and a Pico USC board. I can use the spindle to read encoder c

Re: [Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

On Sun, 19 Jul 2020 at 22:02, Matthew Herd wrote: > It appears that the down feed works properly, but the spindle either never > reverses or reverses very slowly and the synchronized motion on retract > doesn’t appear to reliably track the spindle motion. Does the encoder count up in the cloc

[Emc-users] Problem with Rigid Tapping on USC Equipped Bridgeport

Hi all, I made my first attempt at using spindle synchronized motion for a rigid tapping operation on my Bridgeport BOSS mill today and it didn’t go as planned. It has a spindle encoder and a Pico USC board. I can use the spindle to read encoder counts and spindle position (I already use PYVC