Hello Guest it is April 28, 2024, 06:34:21 PM

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 - HimyKabibble

1521
General Mach Discussion / Re: USB "Pendants"
« on: October 12, 2008, 05:27:43 PM »
Look at the Fang Game Pad. I absolutely love mine!

http://www.ideazon.com/us/products/fanggamepad.asp


http://www.sureneeds.com/fang.html $26.99

Were you able to interface it the way you wanted using only the utilities than came with it, or Mach macros, or both?

Regards,
Ray L.

1522
General Mach Discussion / Re: USB "Pendants"
« on: October 12, 2008, 03:07:12 PM »
Dave,

    Thanks!

Regards,
Ray L.

1523
General Mach Discussion / Re: Rapid not working during jogging
« on: October 12, 2008, 02:41:11 PM »
I don't know if there's anything in the XML that coudl affect that, but it seems likely.  You might want to create a new profile (just configuire that one axis), and see if that gets it working.  If it does, then you either need to figure out what's wrong with your old XML, or just create a complete new one.

Regards,
Ray L.

1524
General Mach Discussion / Re: USB "Pendants"
« on: October 12, 2008, 02:36:48 PM »
Dave,

    Cool!  How long is the cord?

Regards,
Ray L.

1525
General Mach Discussion / Re: Rapid not working during jogging
« on: October 12, 2008, 01:40:49 PM »
What happens if you slow down the fast jog to perhaps 90%?  Or if you reduce the max speed for that axis a bit?  The idea being to find out if there is a threshold above with it doesn't work, or if it's the fast-jog functionality itself that's broken.

Regards,
Ray L.

1526
General Mach Discussion / USB "Pendants"
« on: October 12, 2008, 01:38:59 PM »
Has anyone used one of these: 

http://www.contourdesign.com/shuttlepro/
http://www.contourdesign.com/shuttlepro/shuttlexpress.htm

as a pendant for Mach?  Seems to me it would work nicely, and the configuration software appears to be very flexible, especially in allowing a single button to cycle through a list of operations so, for example, one button could be used to cycle through a list of jog step sizes or rates.  Seems to me the jog/shuttle wheels would also make a pretty nice way of jogging, albeit on only one axis at a time.

Regards,
Ray L.

1527
General Mach Discussion / Re: Rapid not working during jogging
« on: October 12, 2008, 01:31:05 PM »
Is it *only* jogging that doesn't work?  i.e. - does the axis move normally under program control?  Even rapids?

Regards,
Ray L.

1528
General Mach Discussion / Re: VFD Forward/Reverse Relay Control in Mach3
« on: October 12, 2008, 11:36:16 AM »
Chris,

    Since you have a SmoothStepper, I'll give you the (perhaps limited) benefit of my experiences getting the spindle speed control working over the last week.  It was anything but an intuitive process, but I finally got it working as I wanted.  My machine has a two-speed motor, and four step pulleys.  My goal was to have the "spidnle speed" command that Mach sees be the VFD frequency times 10.  So, for example, doing an S750 in the G-code would set the VFD to 75Hz.  I modified my SheetCAM post-processor so I could input RPM into SheetCAM, and the post-processor would then figure out which motor speed and step pulley to use, insert an M00 into the G-code prompting me to make those settings, then output the S commands as VFD frequency times 10.
    When I first brought up the spindle speed control through my CNC4PC C10 board and SmoothStepper, after much futzing around, I ended up with settings that worked, but not very well.  Speed was uneven, wandering around quite a bit, especially at lower frequencies.  After a few days, it stopped working even that well - really went to hell.  Seems the LM2907 on the C10 went Tango-Uniform.  So, I replaced the LM2907, and this time set about trying to understand how the circuit really worked, and how to optimize the Mach and SmoothStepper settings.  This turned out to be quite an exercise, and required putting an oscilloscope on the LM2907 to see what was being commanded (step pulses coming into), and what was being output (analog voltage to VFD).
    Here's what I determined:  First, the "step pulse width" settings in the Motor Tuning dialog do nothing with SmoothStepper.  Instead, there is a corresponding setting in the SmoothStepper config dialog.  The key to getting reliable operation is getting this step pulsewidth setting, and the stes/unit setting in the Motor Tuning dialog properly balanced.  In addition, I had to fudge the max frequency setting in the VFD to get the desired range of motion.  The VFD outputs a 10V supply to be used with the control voltage input.  With 10V coming in, the C10 can only output about 8.5V.  So, I increased the VFD max frequency to about 120Hz, so the 8.5V from the C10 would correspond to about 90HZ, which was my desired max frequency.  Next, using the oscilloscope, I looked at the duty cycle of the step pulses coming into the LM2907, and determined that the 5uS default setting was far too narrow, and would require an extremely high pulse frequency to generate any usable output.  So, I played with pulsewidth settings to get one that seemed to give close to the range I wanted.  Finally, I played with steps/unit to scale the response as I wanted.  I ended up with, I believe, 40uS pulsewidth for the step pulses, and 4600 steps/unit.  This gives the response and scaling I wanted, and the speed is now stable, even at very low frequencies.  Response is also reasonably linear, being off a perhaps 10% (high) at the very low end, but well within 1% at the high end.
    I can't guarantee your settings will be the same, or even close, but this is what worked for me, and there was no way I could have ended up there just fumbling around in the dark, and chaning settings at random.  As I said, the key is getting the pulsewidth and steps/unit properly balanced to each other.  If you don't have that, it just won't work in a rational manner at all.

Regards,
Ray L.

1529
General Mach Discussion / Re: Continuing a job after an event stops it
« on: October 12, 2008, 11:20:29 AM »
One other thing to be aware of - I can't explain what's happening here, but it's bitten me several times....  I've had a problem come up that forced me to stop the program.  I then re-zeroed, backed up to the beginning of the last cut, and re-started the program.  On a few random occasions, Mach seemed to still be confused about where it was, and where it was going, as the first move after the re-start went to the wrong place.  Oddly, this has never been a result of Mach and the machine being out-of-sync, as I did a GoToZero, and it returned *exactly* to zero, and I was able to re-re-start the program from there, and it was fine.  It seems at times Mach gets whacked to where it is internally confused, and it makes a bogus move following a fault.  Sometimes, this move is off just a little, sometime, a LOT.  Once that one bogus move is out of its system, all is OK again.  That's why I suggested making the first cut after a fault an "air cut", both to verify you've re-started at an appropriate place in the program, and that Mach is not suffering from some minor transient brain damage.

Regards,
Ray L.

1530
General Mach Discussion / Re: Macros For Dummies
« on: October 11, 2008, 10:02:49 PM »
Hate to say this, but I run a smooth stepper also, and my "Brians" work with it............
Perhaps you need to upgrade to the latest Dev version of Mach, and the latest Plugin for the SS??

Scott


Scott,

   Brains work with SS, but don't like the (stupid) way I implemented my pendant.  Macros give me a better way to do what I wanted to do anyway, and couidn't do with brains alone.

Regards,
Ray L.