notifications upon start/pause/finish of print
-
@Torin said in notifications upon start/pause/finish of print:
Also added re-notify feature.
The re-notify feature does not appear to be working under windows. I receive the first notification for any new status, but no subsequent updates after status changes. I see a reference to time.Now().Unix() in the main.go source, could this be part of the issue?
-
@mct82 Basically yeah, you would also need to update struct for json payload.
In regards to windows, time.Now().Unix() should without any problem on windows. That's something I would need to check later during the week. but feel free to look around, add some timers maybe and logging
-
@Torin I'm not a programmer and I have never used the Go language, so I don't think you want me mucking up your code. I just don't have time to learn a new language right now, so I will have to wait for someone who knows what they're doing to do it properly.
I will mention that if I were to modify this tool in any way, it would be to pull the message content out so it can be edited w/o re-compiling. Perhaps read in a message template for each status (print, pause, finish), or a single template with multiple sections. It would be really powerful to be able to grab additional fields from the OM to include in (or conditionally modify) push notifications.
-
@mct82 Hey, so I got a bit of spare time today and I've looked into it. Renotifications didn't work because I forgot to add two more if's.
I've created new release here: https://gitlab.com/Toriniasty/reprap_notify/-/releases/v7
-
Hi, this is working great for me, but is there a way to make it poll for 2 duet boards? I have two printers I would like to use it on.
-
This is fantastic. Just what I was looking for.
I tried running this on windows from command line, but theres no feedback... so im not even sure its running?
I do have a spare raspberry pi lying around so which release would I use for that?
-
@thebaseddoge Simply start two programs with from two different directories with two different config files
@festivejelly There's no feedback unless there's a problem
If you want to run on rpi you need an arm build. -
@torin So do I run from command line? or do I just double click the exe? When I do either I dont see the process running in the list. Ill give the arm build a try instead on my rpi
-
@festivejelly You can run it both ways, either from command line or double click. If it doesn't quit and windows stay open it should just work.
-
@torin I don't know if you planned on maintaining this app, but it sure would be nice if it received an update.
I did some testing and got a contineous stream of JSON parse errors. After checking the sources it seems the program uses the GET /rr_status way of talking to the Duet. However, according to this page on the Duet Github, it is deprecated now.Should you decide to maintain it, I could make time to help out testing.
-Nxt
-
-
@madeinta1wan This is due to API changes introduces in RRv3. There's a chance but it requires few hours of work which I currently do not have, however I will try to squeeze that in somehow. The code is opensource so if someone would make an PR I will happily merge it.
-
@madeinta1wan @madeinta1wan rr_status is still supported in standalone mode AFAIK. We will add a support layer for rr_ requests to SBC mode in v3.5 but I'm afraid it won't support rr_status. If possible, I'd strongly recommend upgrading to rr_model which returns portions of the object model.
-
So I finally found some time and resurfaced my duet enabled printer so I have started updating the app.... So hopefully soon there will be something to show
@chrishamm How do I currently identify finished print? Previously it was in rr_status marked as 'I'(capital I), now I can see see only in rr_model?key=state status: idle, pause, printing.
-
@torin Those letters are abbreviations for the different machine states (see here), so
idleis equal toI. -
@chrishamm Many thanks for that, it definitely extends what I've seen.
However I am missing a 'final status' if that makes sense e.g. there's the status for cancelling yet there's no cancelled status or processing and no processed which makes it hard to understand and put the proper function in place to determine final status without hammering the API and making a request every let say 100ms which could still lead to some false positives. -
This may help. Its some of the logic in DuetLapse3. It ends up being a bit convoluted .... and of course I have a bunch of defensive coding in here (for other reasons).
The main logic starts at line 16.Any yes - it can do with a bit of tidying up
def captureLoop(): # Run as a thread global printState, duetStatus, captureLoopState if connectionState is False: return captureLoopState = 1 printState = 'Not Capturing' lastDuetStatus = 'idle' # logical state on start of each thread instance logger.debug('Starting Capture Loop') while captureLoopState == 1: # Set to 0 to stop. e.g By http listener or SIGINT or CTL+C if duetStatus != lastDuetStatus: # What to do next? logger.info('****** Duet status changed to: ' + str(duetStatus) + ' *****') # logical states for printer are printing, completed if duetStatus == 'idle' and printState in ['Capturing', 'Busy'] and terminateState != 1: # Capturing is finished without being commanded printState = 'Completed' logger.debug('****** Print State changed to ' + printState + ' *****') elif duetStatus in ['processing', 'idle'] or (duetStatus == 'paused' and detect == 'pause'): printState = 'Capturing' logger.debug('****** Print State changed to: ' + printState + ' *****') elif duetStatus == 'busy': printState = 'Busy' logger.debug('****** Print State changed to: ' + printState + ' *****') else: printState = 'Waiting' logger.info('****** Print State changed to: ' + printState + ' *****') if printState == 'Capturing': oneInterval('Camera1', camera1, weburl1, camparam1) if camera2 != '': oneInterval('Camera2', camera2, weburl2, camparam2) unPause() # Nothing should be paused at this point elif printState == 'Completed': logger.info('Print Job Completed') printState = 'Not Capturing' # use a thread here as it will allow this thread to close. startnextAction('completed') break # Do not want to wait to end if captureLoopState == 1 and terminateState != 1 and connectionState: # If still running then sleep lastDuetStatus = duetStatus time.sleep(poll) printState = 'Not Capturing' captureLoopState = -1 return # End of captureLoop -
Hey folks,
I want to share a download link with the version that should now work with v2 and v3 API.
If you could test it and let me know if it's all good that we'd be great and I will release it officially.Only change you need to make is additional entry in your configuration file adding api_version in the connection section(v2 or v3) e.g.:
connection: host: 192.168.0.11 polling_time: 30 error_count: 5 api_version: v3Without further ado:
https://1drv.ms/u/s!Aq3gq6mIQqpsisE-e3Adz3wsP6dAJwLink is going to expire in 2 weeks, after that I will just merge it
-
Don't know if this is interesting for you but may avoid having the user input the version /model info. Its Python, but the logic will be the same.
def getDuetVersion(model): # Used to get the API and version information from Duet if model == '' or model == 'rr_model': URL = ('http://' + duet + '/rr_model?key=boards') r = urlCall(URL, 3, False) if r.ok: #The API type is rr_model try: j = json.loads(r.text) version = j['result'][0]['firmwareVersion'] return 'rr_model', version except: pass if model == '' or model == 'SBC': # model = '/machine/status' URL = ('http://' + duet + '/machine/status') r = urlCall(URL, 3, False) if r.ok: try: j = json.loads(r.text) version = j['boards'][0]['firmwareVersion'] return 'SBC', version except: pass -
@stuartofmt Cool. I'll have a look tomorrow (that is if I will survive tomorrow heatwave...). Cheers buddy.
