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.
Probably because it will accept negative value for a tool lenght unless you include in your VB that lenght will always be Positive.
If you get negative value, Try using the command ABS(variable)
This will return the absolute value of the variable.
Jeff
Here's a more detailed description. I have a zero touch plate routine that many have been using. This code should never drive the bit into the workpiece. I am also using a SmoothStepper (SS) which may actually be the problem. However, I am aslo doing something that I am suspecting may be casuing an error and cofusing Mach or the SS. Rather than use a touchplate, I have simply shorted two wires togther to simulate the plate being touched while testing this feature. I have read that the G31 code will actualy retract the bit a very short distance after the probe fires. My hand shorting of two wires wouldn't simyulate the probel breaking contact at just the irght time for this small retraction so today I started wondering if I was causing a problem with my test method and then wondered if I could error trap. I am not at the machine today, so I can't simply try a real touchplate, although that scrares me a bit since this sometimes drives toward the table when the button routine performs the final retract. Another person also sent me a message that they were using the same routine I am using and it normally works OK. However, one time they had the touch plate so far away that the bit failed to contact the plate by the end of the G31 move. They hit zero again and after the bit hit the plate, the machine then drove the bit very hard into the touchplate/workpiece. They are not using a SS, so I thought that perhaps he too had an error condition that our button routine needs to trap.
Sorry for the lengthy explanation. Just thought it better to give the full picture.
I use G31s for touching off many, many times a day, with a SmoothStepper, running my own macros. Never had a problem, *except* one time on a previous version of Mach which *did* have a bug that resulted in breaking my probe. That bug was fixed within hours or my reporting it, and a new version of Mach posted. What version of Mach are you using, and what SS plug-in?
Regards,
Ray L.
I am using R3.043.000. This is the development release, but Gerg of Warp9 told me to use it as it is the best version to run with a SS. I am also using the latest SS plugin. What versiosn are you using? Also, could you post your button code so I can review it to see any difference mine may have. Finally, the Mach manual says in many places 'It is an error if:" Surely there is a way to trap those errors in the routine and handle them. I'm not saying that is my problem in this case, but if errors can occur it is good practice to handle them. Perhaps the manual is ismply saying that the operation is not valid rather than anacutual an error raised.
Here's a more detailed description. I have a zero touch plate routine that many have been using. This code should never drive the bit into the workpiece. I am also using a SmoothStepper (SS) which may actually be the problem. However, I am aslo doing something that I am suspecting may be casuing an error and cofusing Mach or the SS. Rather than use a touchplate, I have simply shorted two wires togther to simulate the plate being touched while testing this feature. I have read that the G31 code will actualy retract the bit a very short distance after the probe fires. My hand shorting of two wires wouldn't simyulate the probel breaking contact at just the irght time for this small retraction so today I started wondering if I was causing a problem with my test method and then wondered if I could error trap. I am not at the machine today, so I can't simply try a real touchplate, although that scrares me a bit since this sometimes drives toward the table when the button routine performs the final retract. Another person also sent me a message that they were using the same routine I am using and it normally works OK. However, one time they had the touch plate so far away that the bit failed to contact the plate by the end of the G31 move. They hit zero again and after the bit hit the plate, the machine then drove the bit very hard into the touchplate/workpiece. They are not using a SS, so I thought that perhaps he too had an error condition that our button routine needs to trap.
Sorry for the lengthy explanation. Just thought it better to give the full picture.
The G31 code (linear probe) refers to errors that may occur if the program point is less than .01" from the start point. Is there a way to add error checking in the VBscript button code to trap errors?
Do xylotex have microstepping?
Hood
Dave, thanks for pointing this out to me. I'd say you are great help.
Attached is the source code for the shuttle pro plug-in.
Thanks Art
Brett
We are finding VB difficult with Mach 3 Is there a tutorial on this anywhere?
specifically right now:
Is it possible to add an OCX object or an active X control to the screen? We would like to put a Mschart object to record torch tip voltage, and be able to watch the chart as it runs
In general, does Mach3 allow all visual basic objects like the Mscomm, mscharts,etc... to be used?
Thanks in advance.
Guest