OK, I got more info. I started my laundry sign again, it got further and failed with our old friend… I videoed from the time it started to cut again in the job until it failed and even what I did after that but I won’t post that part
log from failure:
Maslow-serial (fail-l3).log (29.5 KB)
log from retract all:
Maslow-serial (fail-l3-retract).log (2.2 KB)
sorry, wrong vid… one moment:
Here is the fail:
gazinux wrote:
I am referring to the belt slipping not the magnet. reconsider the assumption
that the belt movement is perfectly tracking the rotational advance of the
magnetic shaft for every belt tooth and assume it slips for some people at
times --how would the software handle that and can we test that assumption?
There would be no way to detect that situation, so the software would not be
able to handle it (until the next time that you retract/extend when belt length
is reset)
but this is extremely unlikly to happen, the belt teeth are engaged with the
gear the magnet is attached to, it’s pinched pretty tightly with the other gear,
and both gears are in bearings with no forces on them to limit their movement.
David Lang
Ron Lawrence wrote:
My problem is that my dry runs (i.e. no cost) all work fine
if it works with the router off, but not with it on, it’s almost certinly EM
interference.
David Lang
not only router on, but cutting. In other words, it has not happened (at least for me) when doing dry runs with router and vacuum running, but the bit not engaged.
If this issue is caused by EM interference is there a way to ground the router or shield the sensors?
Running the servo to loosen the belt sometimes results in either
(a) the belt is engaged and spins the encoder gear assembly or
(b) the belt gets slacked on the spindle and so the encoder gear assembly is blind and no rotation.
Does the fact that we have to deal with (a) and (b) mean we can’t rely on closed loop operation for sled movement? (a) can run closed loop. (b) cannot.
I’ve come up with this design, which decouples the PCB from the router, v2 of the PCB mount has a large flat area under the PCB that you could cover with some foil and add an earth wire to it
Could you try v2 of my M4 router mounter be gone?
To fit it you do have to completely undo the top router clamp from all four sets of supports (and the clamp itself) and then you can slide that clamp up in order to mount the support uprights.
Then silver foil and an earth strap under the PCB mount to see how it impacts EMF
Have you ruled out the Zm over 90 issues from the other thread?
gazinux wrote:
Running the servo to loosen the belt sometimes results in either
(a) the belt is engaged and spins the encoder gear assembly or
(b) the belt gets slacked on the spindle and so the encoder gear assembly is blind and no rotation.Does the fact that we have to deal with (a) and (b) mean we can’t rely on closed loop operation for sled movement? (a) can run closed loop. (b) cannot.
all that matters for your position is the length of the belt that is past the
encoder, it doesn’t matter how tight or not the belt on the spindle is.
David Lang
Sean Keehn wrote:
If this issue is caused by EM interference is there a way to ground the router or shield the sensors?
we don’t know how the interference is getting in to the system, it could be to
the main board, it coudl be to the power, it could be to the encoder. We are in
the early stages of figuring this out
in addition to shielding, it may help to:
add extra filtering on the 24v going in to the maslow from it’s power supply
don’t run the power for the maslow and the power for the router right next to
each other
ground the direction pin on the sensors (design mistake, it should default to
being right, but sometimes it doesn’t)
This file starts out with a boot up, is that because after the issue you can’t press “Retract All” without restarting because the machine won’t let you?
It disconnected from the browser right after i captured the log so i didnt get the chance to
I guess i should have left it on the anchors…
I’ll print it out and give it a shot. It may be a while until I can get this on the maslow and try it.
Yes, I zeroed Z (bottomed out) after that insight and I look at that setting now every time to make sure its “reasonable” based on the home z + the bit length…
I did run another extension cord over from another outlet in the garage for router/vacuum, I moved the ferrrite collar for the router up closer to the router, and took off my zip-ties holding the maslow power and router power to each other. I wrapped the router’s cord around the vacuum hose, which I tried to ground (not sure how effective that is given its just a copper wire attached to ground and wrapped around with copper tape to the inlet of the hose).
I did do the grounding of the direction pin on these encoders so they are not floating
I’ve spent about 2 hours cutting with no issues and now i can’t even start a cut without getting the 15mm warning. At first i thought it was because i was cutting too high on the board, but after seeing others success i somewhat ruled that out. Ran a full calibration with no bit and got fitment of 0.89 then added my bit back and tried running the code and couldn’t even get it to start the cut. I did notice both errors were on the top left and top right motors. Not on the bottom due to slack in the system after raising the z axis.
Ron Lawrence wrote:
I did run another extension cord over from another outlet in the garage for
router/vacuum, I moved the ferrrite collar for the router up closer to the
router, and took off my zip-ties holding the maslow power and router power to
each other. I wrapped the router’s cord around the vacuum hose, which I tried
to ground (not sure how effective that is given its just a copper wire
attached to ground and wrapped around with copper tape to the inlet of the
hose).
I think you want to run a bare wire inside the hose to prevent the static
buildup.
David Lang
douglas fields wrote:
I’ve spent about 2 hours cutting with no issues and now i can’t even start a cut without getting the 15mm warning. At first i thought it was because i was cutting too high on the board, but after seeing others success i somewhat ruled that out. Ran a full calibration with no bit and got fitment of 0.89 then added my bit back and tried running the code and couldn’t even get it to start the cut. I did notice both errors were on the top left and top right motors. Not on the bottom due to slack in the system after raising the z axis.
what size frame and workpiece?