Hello Guest it is March 28, 2024, 03:28:39 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 - daffyduck

Pages: 1 2 3 4 5 »
1
Did you try double clicking inside the GCode tab window?  If I do that then I see line numbers.

2
Mach4 General Discussion / Re: mach3 motor not moving
« on: October 28, 2023, 04:37:16 PM »
I have had this issue in the past, but probably not the same root cause.  I have found that after time either the controller board gets scrambled, the driver, or the software.  A full hard shutdown of the controller, computer (software), power, etc.  Cleared it up.  Also maybe a directional signal broken wire?  You were running ok, shut down, then after startup nothing moves?

3
Mach4 General Discussion / Re: Lathe homing in the wrong direction
« on: October 28, 2023, 04:31:28 PM »
Not sure your entire system setup.  However I have had this issue in the past.  It happened when one of the wires for the directional input to the stepper driver broke.  If that happens no matter what you do your motion will only be in 1 direction.

4
General Mach Discussion / Re: Unidirectional creep - help
« on: October 28, 2023, 04:19:01 PM »
Hi Sooty1986,

I am curious to learn more about your issue.  Can you please elaborate?  I'm not necessarily saying that I can help however it sounds very similar to an issue I am having.  I have an issue where my z axis drops gradually during cutting operations. 

5
Mach4 General Discussion / Re: ZAXIS Decreasing (By Error) During Cut
« on: October 28, 2023, 03:53:20 PM »
I am reviving this thread as I am still having issues.  And wow time files, I see the original post was 2 years ago.  I have been doing a lot of laser work with the machine so the Z-Axis problem has not been an issue.  I am getting back into cutting and I am still struggling with the original problem as posted here.

Problem:  Z axis gradually drops (in error) over the entire cut job. It is so gradual that the job looks perfect until you measure the actual thickness at the end of the cut.  I just finished a piece that is ~ 550mm x 200mm, finishing pass along the 550mm length.  The job is 4mm too thin at the last path.  I have cut multiple jobs with the same error, always negative Z.

What I have tried/checked to root cause / fix:
  • Compared holding position of spindle (in holder) and cutter (in collet) to ensure they were not slipping.  No problems, all check out ok
  • Ran a 500 dry cycle test on the Z axis.  Each cycle moves the full range of movement. Compared cutter tip height by probing when dry cycle is done.  No issues.
  • Changed coupler type between Z axis stepper motor shaft and lead screw to a style that should have more holding power
  • Replaced anti backlash nut for Z axis lead screw
  • Verified the work piece is not moving
  • I checked the gcode cutter path to ensure that the correct z height value is being generated.  All ok.
  • I've put a pretty beefy stepper motor on the Z axis to limit the possibility of stepper motor slippage.  I installed a Nema 23 2.0 Nm/283.28oz.in

My thoughts on other possible issues / fixes:
  • I have a system with v slot rail and wheels.  I am thinking about changing the Z axis movement to ball screw with linear rails.  I am wondering if the v slot system is binding, albeit very slightly.  However seems very weird that the error is only in 1 direction (-z)
  • I do not have shielded cables.  Although it would be a huge job to tear apart the machine and replace and/or shield the existing cables of course I would do it if I thought it would fix the issue.  I ran the test with and without the spindle running.  I am making a strong assumption shielding is not the issue as it is irrelevant whether I am actually cutting a piece or not.  (There is no Z axis height issue with the 500 dry cycle test)
  • I am also questioning the holding power of any coupler between the stepper motor and lead screw.  The lead screw does not have a cylindrical, solid shaft on the end with a flat.  I am seriously questioning how much holding power the coupler can have with just 2 set screws and friction against the threads of the lead screw.  One thing I haven't done is measured how much lead screw is protruding from the holder bearing.  I will try another cut test and measure this value before and after.  If the lead screw is slipping inside the the coupler than it should show the difference.  However with 4mm of z delta per job it wouldn't take long for the lead screw to totally come dislodged.  Which is hasn't.  So the likelihood of this being the problem is low in my opinion.

I am baffled honestly.  I'm just grasping at straws now.  I am not one to quit or say I can't do it.  But honestly I don't know what else to try.  For sure something mechanically, electronically or with the software / firmware is an issue. 

Other than scrapping the whole machine and money that went into the machine build, I'm stumped.

Any thoughts / brainstorming is appreciated.

Thanks everyone.

6
Hello All,

For full transparency I also submitted ticket information to PoLabs Support.  However I thought I would also post here to see if anyone else has experienced the same issue or has any ideas. 

Whether I jog manually or send a GCode command the machine will only move in the negative X direction.  All other axes, YZA move properly.  I swapped computers and the stepper driver for the XAxis without success.  I also unplugged and disabled all homing switches.

I think that rules out software, switches and the stepper driver.  I am thinking the Pokeys board has gotten scrambled.  I also updated to the latest firmware.  And of course during diagnostics I have rebooted the computer and board multiple times.

In addition the board will not recognize the XAxis homing switch, which had been working fine.

Now a brief history which might give some clues.

Last week the machine went dead and would not move.  All axes were dead.  The problem was a dead power supply.  I replaced the power supply and cut a couple small jobs.  Now tonight after installing a new XAxis homing switch the machine will only move in the negative XAxis direction.  However as previously mentioned I have since disconnected and disabled all homing switches, with no luck.

I am scratching my head here.  Anyone have any ideas?

Thanks so much!

7
Mach4 Plugins / Re: XBox 360 Plugin - Can't get it to work or recognize
« on: December 30, 2022, 03:26:03 PM »
I also found that I have to first assign the trigger value to a variable before putting into a logical statement. Example:

LTR_Val = GetXin("LTR_Val")

8
Mach4 Plugins / Re: XBox 360 Plugin - Can't get it to work or recognize
« on: December 30, 2022, 03:11:18 PM »
Ok.  I am getting somewhere slowly.  I am using some debug output messages to trace the LUA script functionality.  For some reason, at least on my system, I need to explicitly define the number variable on both sides of an if statement operator.

For example, this does NOT work:
LTR_Val = GetXin("LTR_Val") --left trigger value 0-255
if LTR_Val > 0 then
   mc.mcCntlSetLastError(mInst,"LTR_Val not 0")
elseif LTR_Val == 0 then
   mc.mcCntlSetLastError(mInst,"LTR_Val 0")
end

However this DOES work:
LTR_Val = GetXin("LTR_Val") --left trigger value
if tonumber(LTR_Val) > tonumber(0) then
   mc.mcCntlSetLastError(mInst,"LTR_Val not 0")
elseif tonumber(LTR_Val) == tonumber(0) then
   mc.mcCntlSetLastError(mInst,"LTR_Val 0")
end

9
Mach4 Plugins / Re: XBox 360 Plugin - Can't get it to work or recognize
« on: December 30, 2022, 10:41:52 AM »
I found it on the Mach3 Plugins page :-). 

10
Mach4 Plugins / Re: XBox 360 Plugin - Can't get it to work or recognize
« on: December 30, 2022, 10:35:35 AM »
I am wondering if it is a native Windows dll or something DazTheGas made?

Pages: 1 2 3 4 5 »