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

301
Mach4 General Discussion / Re: UC100 Mach4 Lathe G83 fail
« on: February 28, 2017, 06:47:20 PM »
What build are you running?  Also, I tested your G code and it ran flawlessly under Sim and Galil.  I wish I had a uc100 to test with, but I don't.  :(

Steve

302
Mach4 General Discussion / Re: Hobby/Industrial and Profiles
« on: February 28, 2017, 03:03:36 PM »
In your case, you can use either one, hobby or industrial.  If your PC on a machine with the industrial license that goes bonkers, we will work with you.  The main intent on the industrial licensing is that we would like to have 1 license per machine.  If your PC on that machine went bonkers and is no longer operational and you had to throw another PC on it, that would not be a conflict.

You say you don't need macro B, but you may like it.  Never know unless you try it.  :)  

You can move a Hobby profile to Industrial.  And then you can add in the industrial features to that profile.  However, once you do that, you really can't move that profile back to Hobby because the industrial features that you used simply won't be there anymore.  But about the only thing that happens is the industrial features disappear from the profile, so no biggie.  

If you have several machines, then I would think about putting industrial on you most capable machine and hobby on all of the rest.  You got it, might as well use it.  :)

As to copying the profile, if you package it up, then everything needed to run that profile is included (screen set, macros, tool table, parameters, etc...) with the exception of custom files that may be in the Modules directory.  

Steve

303
Mach4 General Discussion / Re: UC100 Mach4 Lathe G83 fail
« on: February 28, 2017, 02:41:08 PM »
Well, it is a bit different from M3 to M4.  In fact, I really want for people to get the idea that comparing Mach 3 to Mach 4 is really like comparing apples to oranges.  They are both machine controllers (fruit), but that is about the extent of it.  Plugins differ tremendously on how they operate between Mach 3 and Mach 4.  And the differences between Mach 3 Turn and Mach 4 Lathe are even more stark.

I'm not saying you should not ask for help here at all.  And I'm not dismissing the problem either.  I wanted to know if it runs with Sim on your machine.  It works fine on my machine, but I may have a different setup.  If Sim produces the same error on your machine as the uc100 does, then I would know there is something different between our two setups and the we can start digging further.  My goal was to help you.  I know that Sim doesn't even cut air very well.  :)  But trying Sim is a very important step in the diagnostics process.  That was the point that I was trying to convey.  Maybe I should do better with my communications too!

Steve

304
Mach4 General Discussion / Re: Hobby/Industrial and Profiles
« on: February 27, 2017, 07:12:59 PM »
The best thing yo do would be to package the profile up in your hobby installation and import it to your Industrial installation. 

Brains were replaced by LUA sripting in the screen's PLC script or by using the PMC (Programmable Machine Controller), which is a ladder logic front end.

Steve

305
Mach4 General Discussion / Re: UC100 Mach4 Lathe G83 fail
« on: February 27, 2017, 07:08:32 PM »
My point being is if Sim works and it doesn't on the uc100, then I suspect the uc100 plugin.  That is what we use Sim for mostly.  To verify proper operation of a hardware motion plugin.  If it doesn't work in Sim, then suspect a bug in Mach.  So the FIRST thing one should do if they have a problem is to test with Sim.  Because you will know who to talk to rather quickly. 

Steve


306
Mach4 General Discussion / Re: UC100 Mach4 Lathe G83 fail
« on: February 27, 2017, 05:49:16 PM »
Have you run it with Sim?  Works fine in Sim for me.  

Steve

307
Mach4 General Discussion / Re: Offset image in tool path window
« on: February 27, 2017, 02:07:12 PM »
Typically, one sets the offset BEFORE loading the G code file.  In other words, pick up your part zero first.  Then load the G code.  It isn't a bug but rather just how it works.  If you change your work offset, just hit regen tool path.  You can automate that with scripting, if you wish, but why?  Just press a button!  :)

Steve

308
Mach4 General Discussion / Re: Lua Macro Parameters
« on: February 25, 2017, 07:53:52 PM »
The first thing to understand is if you do ANYTHING from a GUI event that is long running, it will lock the GUI for that duration.  Why?  Because you have directed the thread that runs the GUI to run your code.  While it is doing that, it can't sit there and update DROs and work the buttons.  So the thing to do is hand off the task to another thread.  That is what mc.mcCntlMdiExecute() does.  It executes your code in a thread in the core. 

If you are running the stock screen set, take a look at the Modules directory.  mcMasterModule.lua.  That is a module file that is "required" by the screen load script.  This is the lua method of "including" common code.  Open up the screen load script in the screen editor and see how it is implemented. 

Otherwise, there is a bunch of really dry reading in the LUA programming manuals.  :(  The manuals are good, but damn...  painful to read.  LOL

Steve

309
Mach4 General Discussion / Re: Lua Macro Parameters
« on: February 25, 2017, 04:16:03 PM »
Use mc.mcCntlMdiExecute() from the button script.  It will be the same as running it in the mdi window.

Otherwise, the more proper way to run code from both the screen and a macro is to put the common code in a module.  Then require the module in both the screen script and the macro script.  Then all you need to do is call the lua module function.

Steve

310
Mach4 General Discussion / Re: Offset image in tool path window
« on: February 25, 2017, 04:10:04 PM »
After you set a work offset, you will have to regenerate the tool path. 

Steve