Hello Guest it is April 26, 2024, 03:37:06 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

221
Mach4 General Discussion / Re: Toolpath recognize C axis moves than A
« on: March 17, 2021, 12:59:49 AM »
A Axis Rotation is what it is called in the tool path because that is the most common axis.  Consider it a misnomer.  A rotates around X, B rotates around Y, and the C axis rotates around Z.  So what axis does your rotary axis rotate around? 

You can try setting it to rotate around Z, as that would be the C axis.  But I'm not entirely sure what you want.

Steve

222
Mach4 General Discussion / Re: Trouble using scr Library
« on: March 17, 2021, 12:46:12 AM »
You have to require and INIT the scr library.  -99 means IPC not initialized.  :)

Once required:

scr.scIpcInit("127.0.0.1")

The better way of doing this is to create a register (in mcRegFile) for which the toggle button's state will reside.  Use the button's event scripts to write the button button state to this register.  Then read that register from the M code. 

The scr library is meant more for remote control applications.  Using it in a M code macro script is highly discouraged.  The Mach registers are the primary means of sharing data from the screen to the core and plugins.  They registers are fast and efficient vs. the scr library is pushed through the TCP/IP subsystem. 

Steve

223
Mach4 General Discussion / Re: Map surface wizard does not function
« on: March 17, 2021, 12:35:39 AM »
Use 4682 and update your video driver possibly?  Nobody else has complained about screen 4680 issues. 

Steve

224
Launch your profile.  Help->Support->Package Current Profile.  Then he imports it with the Mach 4 Launcher. 

Steve

225
Mach4 General Discussion / Re: Working complex Lua Modules into Mach4
« on: March 12, 2021, 04:31:35 PM »
We launched Mach 4 at IMTS running on Linux.  Meaning Mach 4 ran on Linux before it ran on Windows.  :)  We don't ship a Linux version because we don't have a good software protection options on Linux. 

I was trying to find time to compile up a websockets module for you.  But if you can use regular TCP sockets, that would probably be a better options for you in the long run. 

Steve

226
Mach4 General Discussion / Re: Working complex Lua Modules into Mach4
« on: March 12, 2021, 01:26:39 PM »
To build compiled modules, you will need to get a full dev environment setup.  It is a can of worms!  The version of LUA that we use is 5.3.4.  So you will need to start with finding that source.  Then find the source for all of the websocket dependencies.  Then you compile them all into modules.  But only install the websockets, as the rest are already present in the modules directory. 

It isn't easy.  :(  But it is not impossible.

Steve


227
Mach4 General Discussion / Re: New Version Of Mach4 DRO problems
« on: March 12, 2021, 01:17:05 PM »
What is the build of the "new version" of which you speak?  Because I put a lot of new versions up all of the time.  I did do some work in DROs too.  But I have no idea if what I worked on has any relevance since you didn't specify a build number.  :)

Steve

228
Mach4 General Discussion / Re: Enhanced stupidity between 2 machines
« on: March 11, 2021, 03:23:40 AM »
Nobody using the metric system ever landed on the moon.  :)  Sorry...  I just had to.  LOL

But here is something actually usefull.  You can export your profile from one machine and import it to another machine.  Use the menu path Help->Support->Package Current Profile.  Save that file to a USB stick and sneaker net it over to the new machine.  Then launch the Mach loader.  Not a Mach4Mill or any other "named" profile icon.  Just the Mach4 Loader icon.  When the "Select Profile" dialog pops up, Hit the "Import Profile" button and point towards your profile package you created.  It moves custom screens, macro scripts, settings...  everything. 

Steve

229
Mach4 General Discussion / Re: 4612 Build
« on: March 11, 2021, 03:11:37 AM »
Well, all I can say on the multi-line MDI is that was on the wish list from Mach3.  We took all of the Mach 3 "wishes" and put them into Mach 4.  Well, as many as we could.  So what does that say?  Not everyone likes the same thing!  LOL  What a shocker.  Anyway, to most VERY cool thing about Mach 4 is you can make it work any way you wan it to.

Steve

230
20 lines of lookahead mostly.  Yes, even for 3D work. But I mill steel and aluminum on a box way mill mostly.  So now your question has me wanting to ask questions.  :)  What are you wanting out of the lookahead?  A smoothed profile that doesn't hold tight to the path?  Or do you want something that holds as tightly to the path as it can?

Either way, the lookahead will not have anything to do with your jogging issue.  That sounds like a buffer depth issue to me.  And when I say buffer depth, I mean the amount of time that is buffered in the motion controller.  If you have a large motion buffer, changes in the feed rate will be delayed.  And the start of the profile may be delayed as well, depending on how the motion controller implements the buffer. 

ESS ships with very conservative settings.  I can't remember what exactly off hand, but I think it is something like 122 or the like?  The cycle time for the ESS is 1 millisecond.  So that is over a tenth of a second in the motion buffer!

But for Mach 4 on a decent computer, you can get by with extremely small motion buffers.  Say like 30 milliseconds worth.  Say the motion loop is fired ever 10 milliseconds.  I like to stay "three mistakes high" (an old RC model airplane saying) so 3 x10 = 30 milliseconds.  With a small buffer like that, feed hold appears instantaneous.  Jogs start appear to start instantly.  The whole system seem to respond to human input "instantly", even though it really isn't.  Any buffer depth less than 100ms is hard for use humans to detect.  Personally, I like to stay below 60ms.  So 122ms of motion delay is going to be noticeable.  However, it will run on even the crappiest of PCs.  :) 

So if you left the default setting for the motion buffer, I bet that is you jog issue.  Maybe it will solve you other issues as well. 

I have milling machines and lasers.  No routers.  I just like milling metals and catching things on fire.  :)  So unfortunately, I can't run a part for you.  But I know there are plenty of people that do run 3D reliefs with Mach 4/ESS. 

I saw your Rosetta machine video.  ESS and Mach 4 can certainly do that on that hardware.  No problem at all.  I need to find a video of us running trochoidal tool paths on a machine at IMTS one year.  We kept up with the Hurcos!  It was amazing to watch.  But I have seen ESS do that plenty of times.   Now, will your pantograph machine move like that Rosetta?  I would like to see a video of that G code running on the pantograph machine.  It may shed a lot of light on the issues at hand. 

But check you buffer setting first!  it may be the answer. 

Steve