Welcome, Guest. Please login or register.
Did you miss your activation email?
April 26, 2017, 04:54:57 AM

Login with username, password and session length
Search:     Advanced search
* Home Help Search Calendar Links Login Register
+  Machsupport Forum
|-+  Recent Posts
Pages: 1 2 3 4 5 6 7 8 9 10

 on: April 26, 2017, 03:44:01 AM 
Started by Ian K - Last post by Ian K
Was directed to the drop down menu of the NcUSBpod in the Plug Ins menu. A bit counter-intuitive for me I was stuck in the homing and limits box. Which is where it would logically be. But it looks as though the detection and backing off from the limit switch is looked after by the USB to parallel software. You can dial up the amount and direction of back off once the switch is detected.

I was about to give up on the hardware/software the came with the 6040 kit from a Noname brand in China and go for a UC100 and  Gecko 540. I presume the plug in software for the UC100 will be similar and that's where you'd go to set up the homing switch direction and back off?  The UC100 and Gecko 540 is the standard with the best product support is it?

 on: April 26, 2017, 12:08:17 AM 
Started by tdesut - Last post by tdesut
Owkey thanks for the help Smiley

 on: April 25, 2017, 11:47:59 PM 
Started by Ian K - Last post by Ian K
A bit of progress, ref all home is now going through X,Y and Z axis. I don't know what has changed, but I might have had two setups, ( fixtures do you call them?) Only trouble is that once the home switch is detected, the motors pause , but the  Z and X axis don't reverse to back off, they just go through the switch another 5 mm or so, set zero and then move on to the next axis. If I reverse the homing direction of X and Z everything is OK. i.e.. they back off in the reverse direction,  But that's not really a fix. I'm just altering where I home to suit. I'd rather zero Z at the bottom of the stroke.

Is there any setting to reverse the back off from switch direction? I'd think it should automatically be the reverse of the zeroing direction?

 on: April 25, 2017, 11:37:11 PM 
Started by sparky3 - Last post by sparky3
I will pose the question down there. it works while jogging but wont compensate for .0001 moves. only .001 and .01 moves.
Now that I think about it I have not tried .0001 moves with the MDI. I will try that tomorrow then pose the question.

 on: April 25, 2017, 10:57:56 PM 
Started by KennyPowers - Last post by KennyPowers
I'm having trouble getting any of the screen tabs to work in Mach 3.  Everything was working and I come in today and the A axis is reversed and non of the tabs will work(mdi, diagnostics etc). I click and they do nothing.  They were all working a day ago but have no clue what I did or what happened.   Wondering if anyone out there would know what caused it or if this has ever happened to anyone else. Thanks

 on: April 25, 2017, 06:26:07 PM 
Started by cncnc - Last post by thespindoctor
I hope you get it figured out.   Someday soon you will look back and feel good about the accomplishment, once it works!

 on: April 25, 2017, 06:05:46 PM 
Started by kharrisonkevin - Last post by kharrisonkevin
I think that I just found must of the trouble. The y axis rail when the guy put it on was out by 1/8" and wanting to make the machine make very small jumps not visible to the eye. But when watching the vac hose you could see it make small shakes in the middle of the ways.. I ground the high spots out to straighten . I got the machine to Mill a 1" holein aluminum accurate to.004.  Close enough for doing wood. Just thought I would share my findings it might help someone else.

 on: April 25, 2017, 04:20:44 PM 
Started by cncnc - Last post by cncnc
Thanks for your help, Keith.
Yes, I have the newest plugin and configured everything properly. First I connected the Pokeys via USB, but ultimately swapped it for Ethernet because I had some other connection problems.
I used my MacBook via Bootcamp but maybe that didn't work out quite well. I'm gonna switch to a native Windows PC and will report afterwards if the issues are still existent or vanished.
Thanks again, at least I have a starting point now!

 on: April 25, 2017, 12:20:24 PM 
Started by rrc1962 - Last post by rrc1962
Has reverse run been impemented in M4?  I don't see a function in the documentation or button action for it.


 on: April 25, 2017, 12:15:03 PM 
Started by rrc1962 - Last post by rrc1962
I think the issue was in one particular macro.  I wrote some test macros with some motion commands and they all executed fine with no timing issues.  I couldn't pinpoint the issue with the macro because it worked in the editor but failed when run.  When it failed it just went to the next line which made me think it was just blowing past the mcCntlGcodeExecuteWait().  I re-wrote the macro and it worked.

I did figure out that using a combination of mcCntlMdiExecute() and mcCntlGcodeExecuteWait() can cause strange behaviour. I've seen a total crash and I've seen where the code seems to function, but it doesn't update the screen (DRO's and toolpath display) while it's doing it.  For instance using mcCntlGcodeExecuteWait() in the macro, then calling the macro from a button using mcCntlGcodeExecuteWait(inst, 'M3000') caused a crash.  Calling the same macro using mcCntlMdiExecute(inst, 'M3000') works if there is no other code or if this is the last line of code, otherwise it blows past the mcCntlMdiExecute() and on to the next line.  

If I take the code out of the macro, using mcCntlGcodeExecuteWait(), and drop it in a button script, it seems to work, but the screen doesn't update while the code is running.  It updates after the button script is done.  It's just a matter of figuring out what works with what.  

Pages: 1 2 3 4 5 6 7 8 9 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!