Hello Guest it is September 20, 2020, 08:01: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 - smurph

891
Mach4 General Discussion / Re: DRO Code differences
« on: April 28, 2014, 09:30:24 PM »
Your right if I do a
MDI: G1X1F10
it does move correctly
so it has to be in the jog routine.

I like the red DRO's  ;)

All things are possible in the screen designer.  You can make that happen in the PLC script!  Just look at the modes and see if G68 is in effect and turn the DROs any color you like.

Steve

892
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 28, 2014, 09:14:54 PM »
Why do we need a PP option? That is what M3 was for. It is an outdated platform. It is time to move on. M4 will be fine.

Thanks for your support!  We hope Mach4 will be worth the wait.  And some of these guys are having a blast with it!  Which is really nice to see.

Steve

893
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 28, 2014, 09:09:18 PM »
Now to the constructive stuff...

I think you will be fine with what you have below.  I run it on an atom D2700 board with a Galil 4080.  If you have problems, you can turn the refresh rates down a bit.  We have them pretty stoked as compared to Mach3.  You should be able to run @ 25ms refresh rate though. 

Are there systems requirements? I'm looking at using an Asus Vivo PC VM40B computer to Mach 4 on my Bridgeport.
Specs:
Processor: 1.5GHz Intel Celeron 1007U
Cache:    L3: 2MB
Memory: 4GB    Type: DDR3 SDRAM
Graphics Card    Type: Integrated
Installed: Intel HD Graphics
Hard Drive: 500GB 7200rpm
Operating System: Windows 8 (64-bit)
Want to use Galil DMC 4080 motion control.
and PoKeys 57E connected to PoNET kbd48CNC
Still using AMC drives to Baldor servo motors.
Hoping Galil plugin for Mach4 will not take too long.

894
Mach4 General Discussion / Re: DRO Code differences
« on: April 28, 2014, 08:51:51 PM »
Thanks!  I'll try it out.

It may be that the jog planners are not picking it up.  Seems to work fine in files.

Steve

895
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 28, 2014, 08:48:55 PM »
Where do you get your stats from? 

896
Mach4 General Discussion / Re: DRO Code differences
« on: April 28, 2014, 08:13:22 PM »
Is G68 not working?  Can you give an example?

Steve

897
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 28, 2014, 04:35:14 PM »
If writing a plugin or a third party app, yes.  Contact Todd Monto.  You might want to get things rolling.  However, we won't release the API until all of the documentation is done.

Steve

898
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 28, 2014, 12:44:47 PM »
Is it going to be possible to remotely access and control Mach4 as I could with Mach3 using third party software such as:
Mach = (Mach4.IMach4)Marshal.GetActiveObject("Mach4.Document");
Script = (Mach4.IMyScriptObject)Mach.GetScriptDispatch();

Then using script.Code(Gcode);  to send the command to Mach4 to move the steppers etc.
I have tried this with the Mach4 demo but it wont connect or respond.

There is no DCOM interface.  Mach4 is cross platform and we had to choose a way of doing the remote stuff that is also cross platform.  There is a library that you will link to in order to accomplish this.  The full API is exposed.  Running scripts, etc...

Steve

899
Mach4 General Discussion / Re: DRO Code differences
« on: April 27, 2014, 10:36:27 PM »
A function is not a loop.  And not all loops are bad.  You just have to make sure that the loop will not loop for a long time (or forever).  But functions are a great idea.  Take a look at the Screen Load script.  That is where I put functions that are used by the PLC script.  So put your getAngle() function there and call it from the PLC script.

Steve

900
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: April 27, 2014, 09:03:40 PM »
I forgot to mention that the DROs highlight with a double click. 

Steve