Page MenuHomeAleph Objects Inc

Printer powers off then back on when homing axis
Closed, ResolvedPublic


Quiver beta 0017
Whenever starting a print (via USB or to calibrate nozzle) the printer will turn off by itself then turn back on. I have also seen it do it on home X, home Y, and Home All in the Move Axis menu, but not the Auto Home button. I have tried it on .100 and .101 firmware. Unsure if electrical issue or software issue. Printer has been put on the rack with a red tag.

Event Timeline

DaniAO assigned this task to kent.Mar 14 2019, 11:42 AM

QB0016 is exhibiting similar behavior. It did it when homing all axes, and when trying to calibrate nozzles. It did let me start burn-in, but when i cancelled the print, it restarted.

It may be worth noting that it will turn off without any contact between the machine and myself, so it's not like I'm shocking it. I also noticed the touch screen seems to hang up right before restarting, so for instance if I'm attempting to home the Z axis, the Z button appears to stay "depressed" until it restarts.

paulette added a comment.EditedMar 14 2019, 3:14 PM

@MikeR was unable to replicate at his station. We brought it back to mine (Cahow) and was able to replicate the problem. It only happens when the USB Cable is connected to Cahow. We tried it on Robert's station (Cardinal) and were not able to replicate. While in the middle of running the nozzle auto calibration, we unplugged the USB cable and plugged it into Cahow and it died. I did not have this issue until today, after the Wednesday updates. Could this be related?

oliver added a subscriber: oliver.Mar 14 2019, 3:25 PM

T4947 these may be similar issues.

karrad added a subscriber: kaleb.Mar 15 2019, 8:17 AM

@paulette Try switching USB cables and see if you can replicate the issue. If it is consistent with that swapped out, it could be an issue with your USB port on Cahow.

@kaleb ^^

also are you plugging directly into the USB port on the CPU or is it into a USB hub?

Could be a bad hub

kaleb added a comment.Mar 15 2019, 8:37 AM

@paulette And as I mentioned in the work package you submitted, please test whether this affects other printers (especially other quivers) or just this specific machine. I can see from cahow's logs that you and Robert were testing the same printer based on the serial number and that it failed on cahow but not on cardinal. Unfortunately the error isn't very descriptive of a possible cause.

This feels similar to an issue I had in beta and I wonder if its possibly it might have something to do with 2 different grounds.

MikeR added a comment.Mar 15 2019, 1:23 PM

Since @paulette is not here today I went ahead and tried all the above options. I tried two different brand new usb cables and the restart still occurred. I tried the cables in all the different usb ports that were built into the cpu so I don't think its the hub. I also grabbed a different printer, quiver 13, and still the restart happened. I also took the printer to a few other work stations, Bustard, Sapsucker, and Thrush. I was not able to re-create the restart on any of those workstations. I was however able to re-create the restart on Mallard when I went to use that work station. I do not feel there is anything wrong with the printer but I do think there is an issue with the Mallard and Cahow computers. I'm not sure what it could be but in my opinion after checking different cables, computers and printers, those two work stations have some kind of bug or short or just worn out.

kaleb added a comment.Mar 15 2019, 2:15 PM

@MikeR @paulette Would you mind testing a mini2 or taz6 on cahow too? I noticed @MikeR tested another quiver but that may be an issue endemic to quiver for whatever reason. If it is an issue with the workstations, that will help narrow it down.

I have tried 3 different Taz 6 this morning and have not had a problem yet.

kaleb added a comment.Mar 18 2019, 3:07 PM

@paulette Is this happening with other quivers on cahow?

I have not had the time to get much further testing. I tried QB0015 this morning with no issues, and have had no issues with any Taz6 at all.
I will update again as soon as I can get more information.

kent removed kent as the assignee of this task.Apr 1 2019, 1:06 PM
Steven assigned this task to paulette.Apr 2 2019, 9:45 AM
Steven added a subscriber: Steven.

@paulette have you had a chance to test any more Quiver for this issue?

logan added a comment.Apr 2 2019, 10:08 AM

Checked in with @paulette:
Since the last update, she has only had one Quiver unit to test with due to a delay in tool head production. That unit, QB21, has not presented this issue as of yet.
Tool heads have made it through testing today and should be available on the production floor shortly. We will be watching closely for this issue

i have tried 3 different quivers today total and have not had an issue at all. I'm thinking that it was just a weird bug that fixed itself when the computer had its weekly reboot.

logan added a comment.Apr 2 2019, 3:24 PM

Lets leave this open throughout the week, if it doesn't come up again by then we'll mark resolved for now. There were also FW changes between then and now I'm pretty sure.

I tried the original firmware versions from when I first encountered this issue (.100 and .101) and could not get it to repeat, so it seems to not have been a firmware issue.

logan closed this task as Resolved.Apr 4 2019, 2:43 PM

No additional occurrences, closing this out for now. Please re-open this ticket if it becomes an issue again.