Hello Guest it is May 26, 2019, 09:53:23 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

They are on the development version part of the FTP site.  As with any development/beta builds, you need to be extremely careful and test things for your own safety!  Because the development builds haven't gone through the same amount of internal testing as the release builds do. 


But I will say this...  4088 looks good.  It is definitely a release candidate.   


Mach4 General Discussion / Re: mach4 and Galil plugin
« on: February 14, 2019, 02:44:03 PM »

The problem is that if there is something that doesn't work with it, I'm not going to be capable of fixing it for the 21x3 series.  And I'm about 99% sure that the plugin will not work with a 21x3 at this time.  Because I did a lot of structural changes to better support the 4000 series controllers that are just not compatible with the 2000 series controllers.  :(  The reason I'm not 100% sure is because I don't have a 21x3 for which to test.  But just from working on the Galil plugin for many years, my experience tells me 21x3 is a no go now. 

The 4000 series is just a much better fit to Mach than the 2000 series ever was.  And as good as the Mach/Galil combination was with the 2000 series controls way back when, there really is no comparison to the Mach/Galil combination with the 4000 series.  So much so, I dumped all of my 2000 series controllers and bought 4000 series controllers to replace them.  Yeah, it was a bit painful.  But WELL worth it. 


3804 was the last "official" release.  We are up to 4088 on the development builds at the moment.  So you can see 3804 is nowhere near the bleeding edge builds.  We are working on trying to get another official release out now. 


You get the message in the status history the next time you press Cycle Start.  On some older builds, it crashed completely when the timeout happened.  This was due to the timeout not being graceful at all, to put it mildly.  This was fix in later versions.  I'm not remembering which at the moment though... 


Mach4 General Discussion / Re: mach4 and Galil plugin
« on: February 14, 2019, 12:39:42 AM »
2143s will probably never get tested.  :(  Kenny has moved to the Caribbean and I don't have any 21x3s anymore.  The best thing is to move to a supported controller.  41x3 or 40x0 and RIOs for extra I/O, if needed.  And if the 21x3 did ever work, we would not support it.  The plugin is now written to take advantage of motion modes that the 21x3 simply doesn't have, namely Contour mode. 


Mach4 General Discussion / Re: Sending Info to a Database from a Script
« on: February 14, 2019, 12:33:15 AM »
Well...  I guess I put all of those modules in after 3804!  :(  You could try one of the development versions from the FTP site.  4088 is the most recent.  And by all accounts it is looking pretty good. 


Mach4 General Discussion / Re: delay
« on: February 14, 2019, 12:23:42 AM »
Ok, try looking at the state of the machine, as Craig alluded to.

In the cycle start button, you can put some more scripting in the up event script. 

local mstate = mc.mcCntlGetState()
if (mstate == mc.MC_STATE_HOLD) then
    wx.wxMilliSleep(2000) -- two seconds.


Mach4 General Discussion / Re: Connect to Mach4 using VS 2012 C++
« on: February 14, 2019, 12:18:39 AM »
One would need to link to MachAPI.dll via the MachAPI.lib to write a GUI to replace the Mach4GUI.exe.  Otherwise, an app to monitor or control the core along side the Mach4GUI would link to MachIPC.dll via MachIPC.lib.  MachAPI.h is the header to use with both of the link libraries.  All of these are in the SDK and require a developer key. 


Mach4 General Discussion / Re: Sending Info to a Database from a Script
« on: February 12, 2019, 12:38:19 AM »
What version (build) of Mach are you running?  The luasql module have never been in the addons directory to my knowledge. 

Should be:


Mach4 General Discussion / Re: Screen Set Property Descriptions
« on: February 09, 2019, 09:55:22 PM »
There is no documentation of our internal screen format.  You are own your own in there...  I will say that the font property is specific to the OS and I have NO idea what it comprises. 

No Bg color is transparent in some places and opaque in others.  Again, this is an OS thing.  You pretty much can't have a transparent tab in MS Windows.  So the controls that are laid upon a tab WILL take on the tab Bg Color.

It is not possible for a user to create new label codes.  They have to be programmed into the GUI.  If you have ideas for some, put them in the feature request thread. 

SysVars are G code variables.  #100, #1100, #1200, etc...  SysVars can be used to create custom parametric G code programs. 

SysParams are system parameters.  SysParams define the control behavior.  They are changed with G10L50 and read with PRM[ x ] (where x is the desired parameter).  There are not many things a user would ever need to change in the SysParams.  Most of these only pertain to the Industrial license with Macro B.  Tool life management, Custom G codes, etc... 

The DRO font size is intetionally programmed to fill the height of the element.  If that doesn't fit the desired look, then make the DRO flat with no border and put a faux background bitmap behind it.  The sky is the limit.