Before I try debugging the code that works for everybody else without issue (big clue right there) I think it might be smart to replace some of the other devices on the USB (channel?) that might be dying and causing issues. I'm familiar with visual studio, but I think that you're probably right and this is a windows issue. now that I think about it, I'm a bit suspicious that it only happens on the Z axis, are page up/down special in some way? I might try re-mapping those keys in Mach 3 to see if the problem follows. Replacing the dongle fixed the connectivity but not the Z axis issue. I also thought that windows was freezing so I replaced the USB wifi dongle which I suspected was dying due to connectivity problems. I was very, very, behind on my windows updates so I allowed the system to update and shut it down.įlash forward to a few days ago when I power it up to make some parts and run into this Z axis problem. Last month I powered it up to rework some parts and it worked great. The machine was sitting around for about a year. I have a high degree of confidence that the only thing that changed on the machine were changed by windows update. Sometimes the Z axis travels only while the key is pressed (works properly), sometimes it travels 2 or three inches then stops before hitting anything, and sometimes it goes for broke and continues until something else stops it and the axis disables. Usually when it happens I'll hit the up down keys a bunch of times, but I'm not certain that actually does anything useful. Another part of me suspects that windows update really is out to get me. Where should I start debugging this problem? Part of me suspects that after years for faithful service the board is failing. It only happened once, but it coincides with the Z axis issue and I have never seen happen before. One other issue to note is that I recently had my spindle warmup gcode program freeze and lock up. I don't think it's the keyboard because both the page up and page down keys are affected and I haven't been able to reproduce this in other applications. It's interesting to note that I haven't seen this issue with X/Y jogging.
It seems very random, but If I had to estimate I'd say it occurs once every 20 or so key presses. The new issue that I'm running across is that the Z axis Jogging will randomly fail to stop when the keys are released, causing the Z axis to either fully retract or crash into whatever unlucky thing is beneath it at the time. I'm currently running v4.35f, and it seemed very stable up until recently.
I have been using mach3 through the plugin for a few years now.
0 kommentar(er)
