fatal crash in driveboard

[j. eric townsend]

so, why I always run in debugging mode...

This is running my branch at 92e52c92ed426a9f0c4d6ba77db7ff10f6b905dc
which I believe is up-to-date with Stefan's master branch.

I had a job lock up yesterday half way through a cut. It's a DXF file
that I've cut several times with no problem so I'm guessing it's a
firmware bug. I've only browsed part of the code, but it might be
obvious to Stefan..

Here's the console log from debug mode where the fail happened

10.0.2.129 - - [25/Nov/2017 18:35:03] "GET /status HTTP/1.1" 200 317
126
~
ERROR: invalid marker
10.0.2.129 - - [25/Nov/2017 18:35:04] "GET /status HTTP/1.1" 200 318

Attached is *a* DBA file. This is the cut that failed, but I don't know
if the DBA got rewritten when I tried the cut a second time on fresh
media and the cut passed.

--
J. Eric Townsend, IDSA
design <http://www.allartburns.org>
hacking <http://www.flatline.net>
consulting <http://www.functionalprototype.com>

[j...@allartburns.org]

Watch me kick this dead horse down the street!

It's started happening again with engraving, several times in an hour.  I haven't

seen this in I don't know how many hours of cutting.  I rarely ever engrave and certainly

not for long jobs.  The ones I'm doing right now can take an hour or so.

Looking at the firmware "~" is being returned by serial_raster_resd() to report a variety

of non-error conditions and I wonder if this is somehow leaking out of the firmware.  I'm

going to modify driverboard.py to just ignore this character and *not* change any of

the self. variables and see what happens.

[jet townsend]

Of course it happens at the end of a 20-minute etch. I think it's
the firmware having the fault, lasersaur UI is waiting and I'm seeing
status messages on the debug console but the head isn't moving.

It also seems to only happen when I'm doing offet. Going to power-cycle
between etches and see if that helps.

--jet

> <http://www.functionalprototype.com>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "lasersaur" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to lasersaur+...@googlegroups.com
> <mailto:lasersaur+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/lasersaur/8b7f8c30-3c28-4acb-b8c0-a1314dd6c989%40googlegroups.com
> <https://groups.google.com/d/msgid/lasersaur/8b7f8c30-3c28-4acb-b8c0-a1314dd6c989%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Jet Townsend, IDSA