New startup script capability in the SPJS widget.

New startup script capability in the SPJS widget. Automatically send any Gcode or other text on open of the port. This is handy on the TinyG v9 where there’s no EEPROM and you have to send your config each time you connect.

Anyone know’s when the TinyG v9 is available?

This is a nice feature, i will try with my Arduino due, thanks @jlauer

@Michael_Jacobsen NOt for a bit still we still have testing to do. We actually might even go 1 more generation in hardware before we start selling it.

@Riley_Porter_ril3y Darn - my OX could really use it (and am hesitant with going for the V8 now that we know a new version is lurking in the horizon).

@Michael_Jacobsen ​ well us could load a due with g2 and use your gshield to drive it for now.

John - I wasn’t uber-obvious that the three commands that appeared were “templates” and not executed. After they didn’t happen, it was obvious. I entered a one line script ($xvm=1) and saved it. I had a hard time getting reconnected to spjs (the black reconnect popup was ineffective). After refreshing the whole CP fiddle, I was able to reconnect and it ran.
Does the entered script run on all connections via the identified SPJS? Is there a way to save a script and disable it? I bounce among tinyG, tinyGv9 and G2onDue, so will need unique (and LONG) scripts for each, or none in the case of tinyG.

Forgot to add - looks useful!

And perhaps should add, I am running SPJS 1.76 and SP widget 1.75.
I sort of assumed this was a SP widget based implementation? It did run with SPJS 1.76, but with some reconnect difficulty

A bit more, I tried it again - just disconnect from SPJS, then wait a bit, try reconnect. It does not reconnect, but I do see in top-middle screen a pop-up with “Serial Port Ajax Error”