Hello Guest it is November 27, 2022, 09:06:35 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 - Nitromuse

Pages: 1 2 3 4 5 6 »
VB and the development of wizards / Re: Active and Passive Probing
« on: May 03, 2014, 07:14:33 AM »
Sorry, that link did not work, try http://www.tormach.com/documents.html, document TD 10088

VB and the development of wizards / Re: Active and Passive Probing
« on: May 03, 2014, 07:09:35 AM »
By Tormach's definition, Active probing involves a circuit that is 'made' when the probe makes contact, that uses a N.O. switch, that is used on one axis only, such as a tool setter.  Their Passive probe is wired differently since it is sensing any one of three axes, using a N.C. switch, and 'breaks' the circuit on contact.  A probe of this type is typically used for digitizing an existing part, or edge finding.
Some users use both types of probes and Tormach does makes a software utility for switching from one mode to the other, but the user must exit Mach to make the change, obviously an unwanted extra step.  See their document TD10088 on the subject. TD10088: Passive Probe Installation Instructions
I was hoping to find a way to change modes on the fly, as to not have to shut down Mach, and reboot it in order to make this change.  But it is my belief that Mach only reads the profile XML file once at startup which governs which mode is used, so basically I'm looking for a way to 'force' Mach to acknowledge this change without closing and re-opening it.
Any ideas?

VB and the development of wizards / DoOEMButton
« on: April 29, 2014, 04:39:18 PM »
Hello World,
I'm having a problem with a simple macro that calls the DoOEMButton(1003) Stop, works like a charm from the script editor, but not when called from the MDI Input.  I'm sure I've saved it in the right directory by putting a message in the macro that shows when I run it from either place.  I've tried it both with While IsMoving and without, same outcome, works in the editor but not in MDI.  Have you experienced this, what's the work-around?
Many thanks!

VB and the development of wizards / Active and Passive Probing
« on: April 26, 2014, 08:00:12 AM »
Hello World,
I'm interested in being able to change modes of probing on a Tormach machine, active to passive, or passive to active, on the fly, that is to say without exiting Mach and using the Config 4.4 utility, and then re-start Mach, obviously a pita if we could find a way around it.
I assume Mach only reads the profile XML file at startup, so in essence we would have to find a way to force this change on Mach's exe, as opposed to it 'finding' the change at startup.
Thank you for your help.

General Mach Discussion / Re: Not getting how to use tool length offsets
« on: August 23, 2013, 01:30:18 PM »
Looks like you have received some good helpful responses but I will add if you had a crash while using TLO's the two most common culprits are not calling G43 Hx, or being in a different work offset than where you set your Z zero.  Personally I don't use a tool change location either, on my Tormach it happens wherever you are, very convenient.  For measuring and setting tool length offsets I reserve a work offset such as G58, when it's time to set TLO's I just call G58 G0 X0 Y0, making sure you have adequate Z height.  Most measuring routines will call G49 since you are measuring an absolute length, so you will loose your G43 call.  As a safety if you call the work offset such as G54, and call G43 Hx in your G code part program you'll go along way in avoiding any more nasty noises.

Are you hand entering the tool lengths in the tool table?  This is another potential for fat-fingered errors.  If you are, you may want to check out CNCneeds automatic tool setter, very accurate, very affordable, it's compatible with Tormach's Automatic Tool Changer touch-off routine, and best of all it enters the data directly in the tool table as it measures each tool.

VB and the development of wizards / Error Message on Older Version
« on: June 07, 2013, 03:36:17 PM »
Hello World,
A simple function, MachMsg has always run well on several different machines but receives an error message when run on a machine with version R 2.42

If IsActive(Digitize) Then
       MachMsg("The Probe Input Is Already Active", "PROGRAM HALTED",0)
      Exit Sub
End If

Can you tell me what needs to be updated or how to get around this?
Your help is appreciated, John

Screen designer tips and tutorials / Re: Screen Colors
« on: May 10, 2013, 01:06:42 PM »
That's what it was, I was missing the Mill bitmaps, the directory just had the Tormach bitmaps, all's good now.
Thanks for the straightforward help!

Screen designer tips and tutorials / Screen Colors
« on: May 10, 2013, 09:20:34 AM »
Hello World,
I've replaced the standard Tormach screens with the 1024.set.  Functionally everything is fine but the colors are all off.  I've directly copied a good copy of the 1024.set file to the proper directory and have checked the xml to verify that Layout is 1024.set.  What am I missing?
Your help is appreciated, John

VB and the development of wizards / XML Documentation
« on: November 19, 2012, 09:14:15 AM »
Hello World,
A real simple question but an important one, is there documentation on the XML entries to better understand their sometime cryptic meanings, and therefore have a better control of Mach via their use?  For example, ProbeTLO.
Thanks again,

VB and the development of wizards / Re: Persistent Parameters
« on: November 11, 2012, 03:52:29 PM »
Well a long day but I finally got it and learned a bit in the offing.  No matter what I did the use of SetVar and GetVar, the best easiest way to do what I've been trying to do, upon closing Mach would write the value to the XML that was in the Mach3\macros\profile directory. I even deleted this file a couple of times but it would re-write itself on closing.  When I re-started Mach it would read the value of the Var from the XML in the Mach3 directory, that was with version 3.042.033.  Finally I decided to try version 3.043.066 and it worked like a charm, no XML in the Mach3\macros\profile directory!  So Gerry when you asked if I was using an old version of Mach I guess we should have taken it more to heart.  Maybe I can get back to making chips tomorrow.  Thanks for your help gentlemen.

Pages: 1 2 3 4 5 6 »