Hello Guest it is March 28, 2024, 11:38:45 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 - rrc1962

611
General Mach Discussion / Re: Is this possible?
« on: October 18, 2010, 06:53:14 PM »
There are some initial positioning and offset differences depending on which probe is used.  A macro that runs at the beginning of the program sets all that up.  

basically what I did was use a DPDT switch on the machine.  One pole switches the two probe inputs and the other switches to ground when probe 1 is selected.  That runs back to the controller where mach sees it as an input (Input 1).  When my macro runs, it checks the state of input 1 and sets things up accordingly.  It works very well.

My only concern is that I have an LED on screen for the two probes.  Probe 1 is active when input 1 is active, so I have OEMLED 821 lit (true) when probe 1 is active.  Basically, probe 2 is active when OEMLED 821 is false so no LED is really needed for probe 2, but for cool factor I wanted to add one.  I added a userLED, then wrote a macropump that just sets it's state opposite that of OEMLED 821.

This works great, but I'm concerned about this piece of code running all the time and using valuable resources.  It's just a simple if then else like this....

If getOEMLED(821) = False Then
   setUserLED(1102, 1)
else
   setUserLED(1102, 0)
end if

612
General Mach Discussion / Re: Is this possible?
« on: October 18, 2010, 01:46:52 PM »

2 ways to do what you need.

1. wire ALL probes in series on one set of pins. Then which ever one trips the input THAT is the active probe. Very simple logic.

2. Use a mach output signal to drive a flip flop relay to reverse the probe input between 2 probes. Call it from VB monitor the flip flop to see which is     active.  More complicated logic.



I thought of #1 but the problem was that is if probe 2 is needed and probe 1 contacts first, there is no way to deal with that.

#2 has promise.  I'm using a gecko G540 drive which has two outputs and I'm using them both.  Right now I have a three position switch on the machine that selects the probe.  In Mach I also have a switch (so to speak) that selects the probe because each probe has different logic associated with it.  So first you have to select the probe on the machine, then you have to select the same probe in Mach.  

The probe won't change during the program run cycle.  Ideally I want to have buttons on the mach screen to select probe 1 or 2, then have a macro at the beginning of the program set things up to read from the correct probe.  A Mach controlled relay in place of the switch on the machine would work.

One other idea would be to use a double pole switch on the machine and use one input to mach.  If that input were low, call it probe 1.  If the input were high, call it probe 2.  This method would eliminate the on-screen switches in Mach and instead just check the "probe state" input and set things up based on that.  I'd rather have a button on the mach screen over a mechanical switch on the machine, but ultimately, I just want one switch.  Sounds like it may be easier to put it on the machine and read it's state from Mach.  Could have an LED on screen to indicate switch position.  This way I can still use G31 to probe, which has never let me down.  I think I've talked my self into giving this a shot.  

613
General Mach Discussion / Re: Is this possible?
« on: October 18, 2010, 09:34:47 AM »
I have 2 inputs for 2 probes that do different things based on some conditional logic.  My initial thought was to just switch the pin assignment for the probe function.  I could write a probe macro and instead of using G31, just use "G01 Z-1" and in the While isMoving loop, look for a low input.  In other words, if condition 1 is met, check input 1 for low.  If condition 2 is met, check input 2.  When the input goes low, stop motion and exit while loop.

How would I check an input from a VB script?

Thanks

614
General Mach Discussion / Is this possible?
« on: October 17, 2010, 08:02:18 PM »
Is it possible to change a pin assignment via VB?  for instance, change the probe input for pin 11 to pin 12 using a VB script.

Thanks

615
General Mach Discussion / Re: Relationship between acceleration and CV.
« on: October 12, 2010, 09:59:54 AM »
I changed look ahead distance from 20 to 300 and it helped. 

616
General Mach Discussion / Relationship between acceleration and CV.
« on: October 11, 2010, 08:58:52 AM »
Hi All...

I was wondering if someone could set me straight on this.  I'm having some trouble getting arcs to cut smooth.  For conversation sake, lets say we have two kinds of arcs.  (1) consistent radius arcs where you have one arc with a consistent radius from start to finish and (2) variable radius arcs where the arc is made up of small line or arc segments.  Variable radius arcs are causing the problem.

This is on a plasma machine and speed is set to 500IPM with an acceleration of 40.  Steps per inch are 1712. on X and Y.  Yesterday I was cutting a file with lots of variable radius arcs from 1/8" steel at 230IPM and noticed that I had a lot of jerky motion in the arcs.  The longer consistent radius arcs were smooth and cut at full speed, but the variable radius arcs were jerky and cut much slower.  CV is on and none of the CV helpers are checked in general config.  It seems that this is amplified the higher the acceleration is, almost as if the higher acceleration begins to override CV where it begins to act as if it's in exact stop mode, especially at higher speeds.   I can reduce acceleration where arcs are smoother, but then at higher speeds corner rounding is excessive.  To reduce corner rounding I have to lower the speeds.  It also appears that I can reduce speed and arcs get better.  The issue seems to be high speeds AND high acceleration.

Here is little chunk of code from one of these variable radius arcs.  This is just a sweeping curve and uses a bunch of small arc commands to complete the curve.

N0710 G03 X6.6918 Y7.5278 I0.1871 J-0.0141 F170.0
N0720 X6.6919 Y7.5145 I0.2151 J-0.0051
N0730 X6.6928 Y7.5007 I0.2417 J0.0092
N0740 X6.6945 Y7.4866 I0.2618 J0.0250
N0750 X6.7043 Y7.4444 I0.2762 J0.0415
N0760 X6.7089 Y7.4310 I0.2518 J0.0791
N0770 X6.7141 Y7.4182 I0.2274 J0.0851
N0780 X6.7198 Y7.4062 I0.1975 J0.0869
N0790 X6.7247 Y7.3974 I0.1673 J0.0863
N0800 X6.7304 Y7.3882 I0.1516 J0.0888
N0810 X6.7386 Y7.3771 I0.1374 J0.0923
N0820 X6.7695 Y7.3476 I0.1239 J0.0993
N0830 X6.7776 Y7.3421 I0.0989 J0.1368
N0840 X6.7861 Y7.3371 I0.0958 J0.1502
N0850 X6.7950 Y7.3324 I0.0929 J0.1651
N0860 X6.8074 Y7.3268 I0.0923 J0.1866
N0870 X6.8204 Y7.3218 I0.0899 J0.2162
N0880 X6.8341 Y7.3174 I0.0874 J0.2517
N0890 X6.8485 Y7.3137 I0.0847 J0.2943
N0900 X6.8634 Y7.3105 I0.0816 J0.3453
N0910 X6.8785 Y7.3079 I0.0777 J0.4066

This is another sweeping curve that uses a bunch of line segments to complete the arc.

N1630 G01 X7.7780 Y6.6682 F170
N1640 X7.7775 Y6.6666
N1650 X7.7691 Y6.6421
N1660 X7.7683 Y6.6400
N1670 X7.7529 Y6.6040
N1680 X7.7517 Y6.6016
N1690 X7.7394 Y6.5788
N1700 X7.7381 Y6.5766
N1710 X7.7242 Y6.5554
N1720 X7.7224 Y6.5529
N1730 X7.7069 Y6.5338
N1740 X7.7047 Y6.5314
N1750 X7.6920 Y6.5188
N1760 X7.6900 Y6.5170
N1770 X7.6810 Y6.5096
N1780 X7.6801 Y6.5088

There is some logic in Sheetcam to determine when to use arcs and when to convert those to linear moves.

Basically I'm wondering if there is something in this code that could be changed to smooth things out at higher speeds or if I'm just up against the physics of the machine and/or software.  Anything you guys can suggest would be greatly appreciated.

Thanks in advance.


617
General Mach Discussion / Going into exact stop in small arcs
« on: October 07, 2010, 05:11:02 PM »
Has anyone seen this before?  It seems that when ever the machine reaches a small radius, it goes into exact stop mode and completes the radius as short, abrupt segments.  I have constant velocity mode selected.  I haven't changed the Mach setting in months.  The only thing I did was upgrade Sheetcam.  Larger arcs are fine.  Seems like any arc smaller than about 1/2" radius goes into exact stop mode.  Below is code segment.  This code goes into exact stop mode.   The repeating pattern I see is a short G01 move followed by a short G02 arc move.  I'm not sure why that's happening or if it should be happening.

N0390 G01 X4.9800 Y2.9950 F75
N0400 G02 X4.9821 Y2.9923 I-0.0223 J-0.0201 F75.0
N0410 G01 X4.9940 Y2.9757 F75
N0420 G02 X4.9954 Y2.9736 I-0.0244 J-0.0175 F75.0
N0430 G01 X5.0062 Y2.9555 F75
N0440 G02 X5.0073 Y2.9534 I-0.0258 J-0.0154 F75.0
N0450 G01 X5.0170 Y2.9338 F75
N0460 G02 X5.0181 Y2.9313 I-0.0269 J-0.0133 F75.0
N0470 G01 X5.0306 Y2.8990 F75
N0480 G02 X5.0314 Y2.8967 I-0.0280 J-0.0108 F75.0
N0490 G01 X5.0384 Y2.8733 F75
N0500 G02 X5.0390 Y2.8709 I-0.0288 J-0.0085 F75.0
N0510 G01 X5.0448 Y2.8432 F75
N0520 G02 X5.0451 Y2.8412 I-0.0294 J-0.0061 F75.0
N0530 G01 X5.0483 Y2.8181 F75
N0540 G02 X5.0485 Y2.8167 I-0.0297 J-0.0041 F75.0
N0550 G01 X5.0523 Y2.7751 F75
N0560 G02 X5.0523 Y2.7738 I-0.0299 J-0.0027 F75.0

Any thoughts would be greatly appreciated....

Thanks

618
General Mach Discussion / Re: Jogging on toolpath screen
« on: May 31, 2010, 11:04:24 AM »
Thanks Hood....I had added a jog on/off button but I used system function "Jog Toggle" instead of OEM function code 103.  It's working now.

619
General Mach Discussion / Jogging on toolpath screen
« on: May 30, 2010, 09:11:02 PM »
Hi all...

Is it possible to jog on the toolpath screen.  It seems to work on every screen but toolpath and settings.  I'd like jogging to be enabled on the toolpath screen as well.

Thanks.

620
General Mach Discussion / Emulated Inputs
« on: May 15, 2010, 06:24:19 PM »
Hi guys... I know I've done this before, but can't seem to get it working now.  The only emulated input that appears to work is the eStop.  I have keys set for limits and home on all three axes.  I see the LED's light in diagnostics, but when I hit the X home during a X reference nothing happens.  What am I doing wrong?   Thanks.