Hello Guest it is October 21, 2019, 09:17:49 AM

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

91
Mach4 General Discussion / Re: Sending Info to a Database from a Script
« on: February 14, 2019, 11:48:55 PM »
I did a video that maybe explains things. 

In the video section of this forum:  https://www.machsupport.com/forum/index.php?topic=39466.0

or direct to youtube:  https://www.youtube.com/watch?v=BtzPPv1WNZQ

Steve


93
Mach4 General Discussion / Re: Sending Info to a Database from a Script
« on: February 14, 2019, 05:12:58 PM »
That means that the luasql/mysql.dll can't find the libmysql.dll client file.  This goes back to putting the mySql dll files into the PATH environment variables.  Or, you can drop the libmysql.dll into the Mach directory. (Attached is my libmysql.dll file).

Then Start Mach.  Next, open the Zerobrane editor with the menu path "Operator -> Open Script Editor" and load the file I a previously attached.  You should be able to step through the code.

Steve




94
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. 

ftp://ftp.machsupport.com/Mach4/DevlopmentVersions/

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

Steve

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

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. 

Steve

96
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. 

Steve

97
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... 

Steve

98
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. 

Steve

99
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. 

Steve

100
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.
end

Steve