Just tried a Rpi2 plugged into the TinyG over my network but it’s not quite working. I connected to the Rpi IP address from my laptop and it saw the thing, connected (picture came up and one without a picture?) but sorta stalled never getting to ready. Oddly, some things would work like reset but no jog, jogging worked fine on the Rpi running chilipeppr (no webgl support :-().
Just wondered if anybody else had this flaky connection before I dig in more. Almost… next is the video widget. A client runs his 3d printer over the web so I wanted to show him Chilipeppr could do the same thing.
I’ve had issues with commands just going flaky where sometimes it would work flawless, other times it would get every few commands but completely ignore others or not do anything at all. I hardwired the network on my Pi instead of using WiFi and all of those problems seemed to have vanished…for now anyway.
Sebastian, Thank you! That worked for me too. I went back and forth between the two; http://chilipeppr.com/tinyg?v9=true worked, but http://chilipeppr.com/tinyg is just not working for me. I have wireless for both the rPi and the laptop. The only glitch I saw using ?v9=true was odd delays when holding down the jogging keys. Homing works and the default logo ran and so did any move I typed in. I’ll be running more but I need to hook up the rPi camera and get that part going. Any pointers would be welcome since this one would have driven me nuts thinking I was doing something wrong.
If anyone wants to go into the TinyG widget and add an if statement to the “version” event to check that it’s a G2 and then test if the user loaded the url with ?v9=true and if they didn’t it pops up an alert that would be a nice addition. This has caught many folks recently given the rise in popularity of the G2. The reason ?v9=true is so important is that it determines whether or not to send the long SR request. v8 supports up to 255 characters in the SR request and the current firmware of G2 only supports 160 characters so it is a problem.
