Messages

3541

General Mach Discussion / Re: Mach 3 Driver??

« on: October 27, 2018, 03:37:30 PM »

Hi,
it may be that its loaded but corrupted, that is what happens if you don't reboot through the installation procedure.

It has been many years since I first installed a Mach3 parallel port I do recall it took numerous attempts for me to get the
sequence correct including the reboot before I got it to work.

These days I use Mach4 and a SmoothStepper and the sometimes cranky/quirky/buggy parallel port are but a memory.

Craig

3542

PoKeys / Re: Pokeys, mach4 no go?!

« on: October 27, 2018, 02:54:43 PM »

Hi,
the PoKeys has so many inputs why are you trying to combine home and limit functions into one?

In Machs early days when everyone had a parallel port there was only five inputs and you had to combine things. Now with
so many inputs you don't have to do it anymore.

It reduces confusion....one switch, one input pin, one function.

Craig

3543

General Mach Discussion / Re: Mach 3 Driver??

« on: October 27, 2018, 02:49:24 PM »

Hi,
there are two parts to Mach, the GUI and Gcode interpreter and the Mach3 parallel port motion controller.

From your description the GUI/Interpretor is installed and working but not the parallel port.

May I suggest open the PC's Device Manager and see if Mach's parallel port driver is listed. If it is remove it.
When you run DriverTest.exe it should re-install the driver.

This is from the Mach3 Installation Guide, if you have not rebooted during the installation of the parallel port driver then it describes
your problem:

2.1.3 The Vital Reboot
You must reboot Windows before running Mach3. This reboot is vital. If you do not do it, you will get
into great difficulties which can only be overcome by using the Windows Control Panel to uninstall the
driver manually. So please reboot now.
If you are interested in knowing why the reboot is required, then read on. If not, you can skip to Section
2.2.
Although Mach3 will appear to be a single program when you are using it, it actually consists of two
parts: a driver, which is installed as part of Windows like a printer or network driver, and a graphical
user interface (GUI).
The driver is the most important and ingenious part. Mach3 must be able to send very accurately timed
signals to control the axes of the machine tool. Windows likes to be in charge. It runs normal user programs
when it has nothing better to do itself. Because Mach3’s operation is so time-critical, it cannot
be a “normal user program.” It must be at the lowest level inside Windows (that is, it handles interrupts).
Furthermore, to do this at the high speeds possibly required (each axis may be given attention
up to 100,000 times per second), the driver needs to tune its own code. Windows does not approve of
this (it's a trick that viruses play), so it has to be asked to give special permission. This process requires
the reboot. So if you have not done the re-boot, then Windows will give the Blue Screen of Death and
the driver will be corrupt. The only way out of this is to manually remove the driver.
Having given these dire warnings, it is only fair to say that the reboot is required only when the driver
is first installed. If you update your system with a newer version, then the reboot is not vital. The
install sequence does, however, still ask you to do it. Windows XP boots reasonably quickly, so it is
not much hardship to do it every time.

Craig

3544

Mach4 General Discussion / Re: If output/input is off or onn

« on: October 22, 2018, 05:05:54 PM »

Hi,
just looking at what I've posted and it wont work either...try this:

local inst= mc.mcGetInstance()
local Output0Handle = mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT0)
local Output0=mc.mcSignalGetState(Output0Handle)
if ( Output0~=0) then
   wx.wxMessageBox("Output on")
end

Craig

3545

Mach4 General Discussion / Re: If output/input is off or onn

« on: October 22, 2018, 02:14:31 PM »

Hi,

local inst= mc.mcGetInstance()
local Output0Handle = mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT0)
local Output0=mc.mcSignalGetState(Output0Handle)
if (sig == Output0) then
   wx.wxMessageBox("Output on")
end


Craig

3546

Mach4 General Discussion / Re: Mach 4 Goto Work Zero

« on: October 21, 2018, 05:10:28 PM »

Hi,
Mach4's greatest strength is its ability to customized.....its greatest weakness, or rather source of complaints, is that it NEEDS to be
customized to work.

Behind the <Go To Work Zero> button is a function  GoToWorkZero(). The function itself is defined in the screenload script.

Are you familiar with the Screen Edit functions? Can you navigate to the Screen Load script?

This is the code in my build of the screenload script around line 225:

Code: [Select]

---------------------------------------------------------------
-- Go To Work Zero() function.
---------------------------------------------------------------
function GoToWorkZero()
    --mc.mcCntlMdiExecute(inst, "G00 X0 Y0 A0")--Without Z moves
    mc.mcCntlMdiExecute(inst, "G00 G53 Z0\nG00 X0 Y0 A0\nG00 Z0")--With Z moves
end

---------------------------------------------------------------Note there are two lines of code, the one in use and the other is 'commented out' but is left intact that you may see its differences.
In particular note how the code explicitly calls a move to A0. If your machine does not have an A axis then the error you have described
results.

Simply Edit the line to remove the reference to the undefined axis:

---------------------------------------------------------------
-- Go To Work Zero() function.
---------------------------------------------------------------
function GoToWorkZero()
    --mc.mcCntlMdiExecute(inst, "G00 X0 Y0 A0")--Without Z moves
    mc.mcCntlMdiExecute(inst, "G00 G53 Z0\nG00 X0 Y0 \nG00 Z0")--With Z moves
end

---------------------------------------------------------------

Or you may chose to leave the original line but comment it out and add a new line to suit your needs. It will retain the option
to revert to the standard issue code should you wish by simply uncommenting it:

Code: [Select]

---------------------------------------------------------------
-- Go To Work Zero() function.
---------------------------------------------------------------
function GoToWorkZero()
    --mc.mcCntlMdiExecute(inst, "G00 X0 Y0 A0")--Without Z moves
   -- mc.mcCntlMdiExecute(inst, "G00 G53 Z0\nG00 X0 Y0 A0\nG00 Z0")--With Z moves
       mc.mcCntlMdiExecute(inst, "G00 G53 Z0\nG00 X0 Y0 \nG00 Z0")--With Z moves
end

---------------------------------------------------------------
Craig

3547

General Mach Discussion / Re: Difficulty Loading Mach3

« on: October 21, 2018, 04:57:29 AM »

Hi,
alright, but have you selected the parallel port driver or the USB plugin as active motion controller?

The latest Microsoft updates for Window 7 have interfered with the operation of then parallel port. There are one or two threads about it...
I recommend a search.

Craig

3548

General Mach Discussion / Re: Difficulty Loading Mach3

« on: October 21, 2018, 02:05:56 AM »

Hi,
I'm confused....you say:

had it run on CNC-USB software but

and then later say:

computer seem OK and the parallel port is confirmed as working OK

Do you have a USB connected external motion controller or do you have a parallel port breakout board?

You say also:

I am running Windows 7 32bit.

Have you read about the problems people have encountered with Microsoft updates to Windows 7 causing grief for Mach3 users?
It may be you have to 'unwind' several of the latest updates...I'm uncertain if there is a workaround or fix.
Alternately go to Mach4 but your Chinese controller will not do the business with Mach4....you will need a US or European made
controller like a SmoothStepper or a UC300.

Craig

3549

Mach4 General Discussion / Re: Mach 4 Goto Work Zero

« on: October 19, 2018, 09:32:56 PM »

Hi,
just below the DRO block there is a set of buttons, one in particular <Go To Work Zero>. Does it work?
If not tell us what the message is in the status bar.

The button has code attached which does exactly the same as your 'G1Y0X0Z0' command. Mach when it ships has code to
rewind the A axis to zero as well. If you don't have an A axis it will fail with a message something like:
'Axis 3 commanded while Disabled'.

<De-Ref All Axes> means break the homing, ie you have to <Ref ALL> before you can continue.

Craig

3550

Mach4 General Discussion / Re: Tool change how does it work

« on: October 19, 2018, 09:12:02 PM »

Hi,
you have to write your own M6 macro. There are some examples that ship with Mach that can often be used as is or with
a little modification. Take a look at Daz-the-Gaz's video:

http://www.machsupport.com/forum/index.php/topic,31032.0.html

Craig