Riley from TinyG confirms that the gcode sender can corrupt the TinyG board

[dgtlmoon]

Hi

After spending a lot of time on https://www.synthetos.com/topics/yet-another-spindle-flashing-light-problem-why-is-it-so-easy-to-crash-the-tinyg/#post-9646 eventually I got a reply via email from Riley who said

"This is a newer issue where chilipepper is sending files that we cannot control. Long story short this issue is not the same as the initial blinking issues. However it does do the same thing. We will fix this for you if you would like.
"

Essentially I accidentally sent some binary data in the gcode chillipeppr box and now my unit is requiring a reflash of the bootloader

What's frustrating is that this sounds like Riley Porter/TinyG already knew of the issue

[chilipeppr]

I'm a bit confused how you were able to send binary data via ChiliPeppr? If
you only pasted in binary data, did you then also hit the play button to
send it? I read your forum post and it's not clear to me what binary data
you would have sent? When Gcode is read in from a file drag drop or a paste
operation it tries to 3D render it and place it in the Gcode widget where
it parses line by line. If everything looked completely wrong it would seem
to me you never would have hit play. If you never hit play, you never sent
your Gcode and thus there's no way that effected your device.

So, can you help shed light on this?

On Mon, May 2, 2016 at 11:10 PM, Leigh notifications@github.com wrote:

Hi

After spending a lot of time on
https://www.synthetos.com/topics/yet-another-spindle-flashing-light-problem-why-is-it-so-easy-to-crash-the-tinyg/#post-9646
eventually I got a reply via email from Riley who said

"This is a newer issue where chilipepper is sending files that we cannot
control. Long story short this issue is not the same as the initial
blinking issues. However it does do the same thing. We will fix this for
you if you would like.
"

Essentially I accidentally sent some binary data in the gcode chillipeppr
box and now my unit is requiring a reflash of the bootloader

What's frustrating is that this sounds like Riley Porter/TinyG already
knew of the issue

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#38

[dgtlmoon]

It was a late night and I pressed play :) I accidentally dragged a zipped SVG file into the area and pressed play

[dgtlmoon]

Ok so I got mt mkII programmer and reflashed the board and everything seems OK.

But, check this out, the gcode box contains SVG data half way through rendering...

[chilipeppr]

Hmm. You might have found a bug. The SVG widget should stop the SVG file
from propagating to the Gcode widget itself.

On Sat, May 7, 2016 at 3:22 AM, Leigh notifications@github.com wrote:

Ok so I got mt mkII programmer and reflashed the board and everything
seems OK.

But, check this out, the gcode box contains SVG data half way through
rendering...

[image: screenshot_2016-05-07_12-21-41]
https://cloud.githubusercontent.com/assets/275001/15091623/6534e31a-144e-11e6-957a-4f00e3f05e86.png

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)

[dgtlmoon]

Yes something is not quite right with the SVG Import and the GCode component

I'm getting a few JS errors now also, will try to figure out how to reproduce it

[dgtlmoon]

Hm, so Ive cleared all the stored SVG imports (drag and dropped to the workspace) in Chrome > Resources under 'local storage', reloaded the page, dragged a new SVG to the workspace, sent gcode to workspace and...

[chilipeppr]

Can you post a screenshot?

On Sun, May 8, 2016 at 10:50 AM, Leigh notifications@github.com wrote:

Hm, so Ive cleared all the stored SVG imports (drag and dropped to the
workspace) in Chrome > Resources under 'local storage', reloaded the page,
dragged a new SVG to the workspace, sent gcode to workspace and...

[image: screenshot_2016-05-08_19-49-13]
https://cloud.githubusercontent.com/assets/275001/15099466/0ff7ecb8-1556-11e6-8780-8376a443d840.png

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#38 (comment)