- This topic has 5 replies, 3 voices, and was last updated 10 years, 9 months ago by
.
-
Just after I spent 30 minutes documenting the crashing problem here, the following baffling sequence occurred. It is mindblowing that TinyG would repeatedly think Z0 was an arc command, over and over. Then it had a complete meltdown. Note at the bottom, when I manually enter a “G0Z0”, and TinyG responded by sending my cutter to x5y11 at high speed, breaking the bit! WTF?
I was wrong about the problem being related to cancelling CoolTerm. What follows is all manually typed. I am not sending a file, and I didn’t cancel anything.
tinyg [mm] ok>
z5
tinyg [mm] err: Arc specification error: z5
tinyg [mm] ok>
z5
tinyg [mm] err: Arc specification error: z5
tinyg [mm] ok>
Z5
tinyg [mm] err: Arc specification error: Z5
tinyg [mm] ok>
g0z0
tinyg [mm] ok>
tinyg [mm] ok>
posx:-8.905,posy:-9.592,vel:0.277,stat:5
posx:-8.760,posy:-9.374,vel:179.823
posx:-7.829,posy:-7.972,vel:691.362
posx:-5.575,posy:-4.580,vel:1242.308
posx:-2.458,posy:0.111,vel:1462.507
posx:0.773,posy:4.974,vel:1350.714
posx:3.370,posy:8.883,vel:906.929
posx:4.688,posy:10.867,vel:310.353
posx:4.994,posy:11.328,vel:22.401
posx:5.000,posy:11.336,vel:0.000,stat:3`>Not saying that you shouldn’t spend time attempting to find bugs
Thanks for responding Mcgyvr. You have the wrong idea. I’m certainly not looking for bugs. I’m just trying to get an important project done. Ought to be pretty simple.
>My mom said.. “Then don’t touch your eye..
Yes, I’d like to stop poking myself in the eye. But I have a project I started in November, the reason I bought the TinyG, is DUE next week. Due as in I’m royally screwed if this isn’t done. I’m talking “thousands down the toilet” screwed.
>Maybe you should just use the e-stop button or find another way
Certainly a fine idea, except, this is the best I have found. If Riley or Alden have suggested a solution, I didn’t see it.
> I’m sure they would be happy to do that for you since you have repeatedly complained about not being able to do so..
If that was an option, why didn’t someone say so two months ago? Have I not made it clear there is something very wrong here?
Anyway, I appreciate that you wrote back. Sometimes I feel like I’m all alone here.
>Gcode is modal – the gcode interpreter must have been in a G2 or G3 arc command before entering the z5′s.
Yes, I said this gcode draws 24mm circles. That’s all there are are G3s.
>The arc specification error is Gcode telling you that the command is not a full specified arc.
That was my assumption.
>When you entered the G0 Z0 command you changed to traverse mode.
Yes, it should have. So then why didn’t it go to X5? That has been the behavior until today. IF I enter a malformed G3, I get an error. After that, it should respond normally to commands, but didn’t.
>Was X5 Y11.336 a target of the previous arc?
I posted the gcode in the previous message on this topic. It is:
G0 X13.015 Y0.0 G1 F333.0 Z-0.9 G3 F200.0 X-6.5075 Y11.2713 I-13.015 J0.0 G3 Y-11.2713 I6.5075 J-11.2713 G3 X13.015 Y0.0 I6.5075 J11.2713 G1 F333.0 Z-1.8 G3 F200.0 X-6.5075 Y11.2713 I-13.015 J0.0 G3 Y-11.2713 I6.5075 J-11.2713 G3 X13.015 Y0.0 I6.5075 J11.2713 G1 F333.0 Z-2.7And forgive me for pointing out that you did not address the substance of my message. Quote: “Note at the bottom, when I manually enter a “G0Z0″, and TinyG responded by sending my cutter to x5y11 at high speed, breaking the bit!”
- You must be logged in to reply to this topic.
