Topics

1

General Mach Discussion / MENU Problem

« on: February 23, 2017, 11:09:21 PM »

Hello,

I have two computers to do milling using Mach3.
Let me give them temporary names as PA and PB.
Both PA and PB are also running on Windows 7.

The problem is that the following menus are not working on PA.
Completely no response. No window appears.
 Config -> Motor Tuning
  Function Cfg's -> Calibrate Spindle...
  Function Cfg's -> ScrewMapping
A common point is that these menus are drawing graphs.
That must be the key.

But it's OK on PB.
Of course I checked both registry settings.
No difference.
Of course I copied Mach3 including .xml and other files from PB to PA.
Still problem.

PA hardware must have no problem,
So what is the cause?
If someone noticed possible solution, please let me know.

Best Regards.

2

VB and the development of wizards / Mach3 doesn’t read some VB Script.

« on: August 05, 2016, 03:02:40 AM »

Hello,

As you know, Mach3 loads a G-Code file (e.g. test.tap) and starts its Cycle.
In the G-Code file, you can use Macros (e.g. M333) after making M333.m1s file written by VB Script.
The problem is that Mach3 doesn’t read some files including Macros, displaying
 “Please wait…Generating Path….”, and never retrieve.
Or it sometimes reads, but stops at the Macro (e.g. M333), and never retrieve.

As you know, Mach3 has the VB Script Editor and Debugger..
From the debugger, the program runs perfect.
The program is shown as follows: (just a sample)

''Using G01 instead of G31
Code( "G01 X100 F200" )
While GetOEMLED( 825 )=0
Wend   'until Probe LED on
SetVar( 1000, GetABSPosition(0) )
DoOEMButton( 1003 )  'press stop
While IsMoving()
Wend
Code( "G01 X0 F2000" )

Any basic suggestions on how to run VB Script in Mach3 would be greatly appreciated. 

/E

3

G-Code, CAD, and CAM discussions / Mach3 unexpectedly dwells after G31 stop. Help me!

« on: July 20, 2016, 09:05:50 PM »

Hi all,
I'm using Mach3 of Version R3.043.066. OS is Windows 7 or XP..
There is a problem.
After G31 probing action, Mach3 dwells for nearly 2 seconds unexpectedly.

To say concretely,
    G31 Y150 F1000 (Metric)
Then, if a probe signal came at Y coordinate 110 mm, the motor stops immediately.
That's of course OK.
But the problem is the next action.
For example, the next command is to back..
    G01 Y10 F10000
The motor doesn’t start immediately and starts nearly after 2 seconds.
Too slow!!
Do I need some configuration setting?

I will appreciate your help with this situation.