Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Content

The recording of the ninth episode of a monthly live broadcast for Patrons, which aired live on March 19th. 

Read more... 

(Cross-posted for your convenience :))

Files

Previews only

OctoPrint On Air #9

A recording of the ninth video chat and Q&A about all things OctoPrint for my Patrons on Patreon that aired live on March 19th 2017. My Patrons can submit questions to answer during the Q&A session via a Google Form before and also live during the broadcast via the chat.

Comments

Jonathan Charnas

For RC usage tracking... I'd be willing to have an automated "phone home" module that sends automated reports somewhere in case of a fault, or maybe even a "submit report" popup bringing the users to a google form to report on the usage. I know, more infrastructure to build in for the RCs that you wouldn't use for release versions, it'd be a PITA to get it right, but that's my perspective as an end user. Not sure how others feel about it. For the polling tool, there's SurveyMonkey, not sure about their free vs paid options though...

Jonathan Charnas

BTW thanks for answering both of my questions about packaging OctoPrint and the serial communication. I submitted the questions a while back, and after you mentioned the modular approach to the comm layer we started rethinking how to do this for the Replicape. Since Kamikaze runs Octoprint on the same machine as where the printer is controlled from we're considering writing a plugin then and modifying redeem to use a file handle directly and having only the controls going through the Octoprint API (i.e. start print/pause/resume/cancel/progress in the print). We'll see how it works, though it may end up messing the gcode viewer synchronization, it's probably a decent idea for a Replicape powered board. I will test and let you know how things work with packaging Octoprint for Kamikaze 2.1.1 :)

foosel

PITA pretty much sums it up ;) I'm on and off looking into something like an issue helper based on gists. But for something like RCs I'd prefer something less automated - I might be wrong with that assumption but my hope would be that people running the RCs would hopefully also be open to give a quick thumbs up in a github issue. Still not too settled on things though. Regarding SurveyMonkey, there pricing model is insane... I'll probably solve the situation by using Google Forms & their "linear scale" question type ("How important is feature X? Very < o o o o o > Irrelevant").

foosel

I'd also love to hear how you do the packaging since you also mentioned those version number issues. Feel free to get in touch about this (usually online during the week at #octoprint on freenode IRC). Regarding your plugin idea, that's definitely something I'd love to see working in the future. Still a long way to go though for this to be _easily_ possible (you could probably already do it by implementing your own serial port or even replacing the printer interface and hence the comm layer with your own, and then taking care of the printer communication through a more direct channel).