Messages

901

Galil / Re: DMC-2143 time out

« on: November 18, 2015, 01:09:50 PM »

The difference between 4.5 and 4.6 is the Galil communication libraries.  I don't know what may be causing the CPU load.  I simply don't see it on my machine at all.  But...  25% is not 100%, so it should run fine.

902

Galil / Re: Trouble with RESET

« on: November 18, 2015, 11:56:45 AM »

There is your problem.  There is nothing that is doing a SH for your B axis.  When you issue a global SH (SH by itself) command, it basically does a SH ABCD thus covering the B axis.  Typically, slaving is done through Mach and not on the Galil controller.  You would map your Galil B axis to a Mach A, B, or C axis and then slave X to the chosen axis.  In short, nothing in the Galil plugin is going to issue a SH for your B axis unless it is mapped to a Mach axis.

Steve

903

Mach4 General Discussion / Re: Re: Mach 4 and Galil

« on: November 17, 2015, 06:20:08 PM »

We are working on it with Galil.  Maybe a beta by the end of the year.  But nothing set in stone as yet. 

Steve

904

Galil / Re: Trouble with RESET

« on: November 17, 2015, 12:15:39 PM »

Check your MO jumper settings.  In the file, there is a clear SH ACD that should have enabled all of the servos.  Also, check that there is no code on the controller that is disabling the axes.  Like a #AUTO script.

Steve

905

Galil / Re: DMC-2143 time out

« on: November 17, 2015, 12:10:53 AM »

D2700-MUD Atom board.  2.1 GHz, I believe.  4GB of RAM on Windows 7 32 bit.

Steve

906

Galil / Re: Trouble with RESET

« on: November 17, 2015, 12:08:34 AM »

Are you running steppers? 

907

Mach4 General Discussion / Re: Machine Position 0,0,0 reset???

« on: November 06, 2015, 08:37:08 PM »

In fact, the fixture offsets are saved across Mach sessions.  If I set a G54 offset, all I have to do is restart Mach, home the machine, and hit "Goto Zero".  I'm right back at part zero.

So I'm not sure why your G54 offsets are cleared at all unless they are manually cleared (zeroing the DROs at the home position).

Steve

908

Mach4 General Discussion / Re: Machine Position 0,0,0 reset???

« on: November 06, 2015, 08:31:26 PM »

When you home the machine, move the the axes to the part zero.  Zero out the DROs.  Now the G54 fixture offset is in place.  Click on the "machine coordinates".  This is how far you are from the home position.  Write down the X and Y values.  Say X machine pos is -12 and Y machine pos is -8.  (Just generalizing)

Then, modify your G code program.  Add

G10 L2 P1 X-12 X-8

after your program initialization lines and before any movement. 

Done.  Now all you have to do is home the machine and run the program.  This assumes that the vise or fixture is always in the same place on the table and the part zero never changes. 

That is how you set a fixture offset in a program.

Now...  one question I have is why is your G54 fixture offset getting cleared when you home your machine?  Mine doesn't.  I can home my machine, move to and set part zero, home my machine, and then press "goto zero" and I'm right back at part zero.  Try it with Sim.  Works every time with the default profile.  Nothing in Mach is clearing the G54 offset.  Maybe the motion plugin is not setting the home position to machine 0?

Steve

909

Mach4 General Discussion / Re: Machine Position 0,0,0 reset???

« on: November 06, 2015, 03:58:34 PM »

Have a look at G10.  But as Gerry says, it depends on accurate homing.

G10 L2 P1 X_ Y_ Z_

The L word/address specifies the type of offset.  L2 for fixture offsets.
The P word/address specifies the fixture offset to set.  P1 for G54, P2 for G55, etc..

Steve

910

Galil / Re: DMC-2143 time out

« on: November 05, 2015, 06:29:39 PM »

I don't have any of the older plugins.    I can tel you that 4.5 fixed a lot of things, so running anything older than that is just not going to be a good idea.  But I do not understand why 4.6 loads the processor!  I'm running 4.6 against a 4080 controller (external amps) with Mach 3 on an ATOM processor and I never see about 20% CPU utilization.  So something on your hardware must be causing it.  Check your Ethernet device settings and see if there are some performance features that you can turn on. 

4.6 has been around a long time now.  So I had thought it was pretty reliable. 

Steve