Duet Buddy - a proof of concept remote monitor

zapta

@richardmckenna, if type=2 has also the other relevant information we can just switch to it instead of type=3.

Does it require changes in the duet response json parser?

zapta

@dc42 said in Duet Buddy - a proof of concept remote monitor:

In the forthcoming RRF 3.01-RC2 it's also available via M409 K"network.name".

Thanks for the info. This require posting gcode to the duet, right? What is a reasonable and simple way of doing it?

Once we figure this out it will be useful for other functionality such as pressure-advance up/down buttons for interactive experimentation.

richardmckenna

@zapta type 1,2 and 3 all seem to share some information but unfortunately not all the bits we are are looking at.

status-type-1.json
status-type-2.json
status-type-3.json

So I think it would need a single call to 2, to get the name and repeated calls to 3 as it currently does.

the duet parser will need tweaking as it only looks for:

char state_char;
float progress_percents;
float z_height;
float temp1;
float temp2;

But that's straight forward. And if the JSON config file is changed just to have the IP, the rest of the URL can be provided by the code depending on which call it is doing.

I will continue to have a play with it, see what I can do.

You can see my updated battery code in my fork here https://github.com/richard-mckenna/misc/tree/master/duet3d_buddy/arduino

Would you be able to separate Duet Buddy into it's own git repo?

zapta

Hi Richard, I create a separate duet_buddy repository here https://github.com/zapta/duet_buddy

If you will send me your github id I can add you as a contributor.

richardmckenna

@zapta excellent thanks. GitHub id is just "richard-mckenna".

zapta

@richardmckenna, sent you an invite via github.

Please feel free to touch anything, including the project page and documentation files.

DK90

This post is deleted!

PastThePoint

I know I am late to the party, but did this ever get figured out for the Duet 3's? Mine just keeps saying "Bad response from duet"??

PastThePoint

@pastthepoint @zapta

PastThePoint

@pastthepoint I'm an idiot. I'm running a Duet 3 w/ SBC. I don't know if it means this will not work or changes need to be made.

zapta

@pastthepoint, this one will require code changes to support Duet3 which has a different HTTP/Json format.

I believe that this one, which is newer, works with Duet 3 but didn't try it myself. https://forum.duet3d.com/topic/15198/reppanel-a-diy-alternative-to-the-paneldue-with-wifi-support

richardmckenna

@pastthepoint @zapta I’ve rewritten this recently (I know it’s taken me a while to get round to it) and it works with duet3. I don’t use an SBC so can’t confirm if it works. Not sure what the difference, if any is with the returned json between duet3 in standalone mode and with an SBC. I can share the code tomorrow.

zapta

@richardmckenna, do you want to send a github pull request with the changes? Or you can get write access if you don't have it already.

o_lampe

I must confess I haven't read all the thread, but wanted to ask if it's possible with M5stack to poll a ESPCAM or other WiFi webcam to display the current print as background-pic and show the json-info as insert ?
The other thing I was wondering reading the first few posts was, why not use a smartphone to poll json-status? Is it harder to write an app, than buying an M5stack and program it?

richardmckenna

@zapta yeah I will send a pull request, it uses ArduinoJSON now so it’s just 1 file and very easy to add extra items to parse. My plan next is to have multiple printers in the config file so you can use the buttons to switch between them.

@o_lampe yes that is possible. With regards to hardware the M5Stack is a nice cheap, portable unit with a battery and display, so ideal for a simple monitoring tool, yes you could use a phone but would you want to leave your phone display on all the time? You could in fact use anything with a display and WiFi to do something similar.

o_lampe

Thanks for the prompt answer. I feel a snapshot of the printbed would be helpful...

@richardmckenna said in Duet Buddy - a proof of concept remote monitor:

you could use a phone but would you want to leave your phone display on all the time

Do you stare on the M5 display all the time? I thought, it was mainly used to inform you about a change into pause mode (with a melody), or to check the job progress frequently. Same could apply to a smartphone app.

richardmckenna

@o_lampe for me my printers are upstairs in my office. If I’m downstairs I put the M5Stack somewhere in my line of sight so a quick glance would give me an update on the status of the print. With a phone, I would either have to leave it on with the app running propped up somewhere or have to pick it up, unlock it and switch to the app if it’s not the active app. In this scenario it makes more sense to me to have a small dedicated display.

PastThePoint

@richardmckenna Have you shared the new code on github? I have everything setup, I just need to know the address to request from for the Duet 3's.

richardmckenna

@pastthepoint yes just done it, apologies for the delay you can find the pull request here https://github.com/zapta/duet_buddy/pull/1 and the .ino file from the pull request here https://github.com/zapta/duet_buddy/blob/261d93e3068ab4e7ba31b516a9a3a7061c9fcd3a/arduino/arduino.ino

@zapta any issues give me a shout

richard-mckenna opened this pull request in zapta/duet_buddy

closed Re-write for RRF3. #1

zapta

Thanks Richard. The pull request should be in now. Let me know if there is any problem.

Since you are now the active developer, would you like me to point my repository to yours (via a link in the main page), making yours the main one?