Hi Guys
hopefully this might be a simple thing to incorporate, could an upload date/time be added to the GCode files section & then maybe a sort function? I'm used to having this coming from octoprint & found this useful. If you have hundreds of GCode files its tricky without this to find what you want 
Thanks
Stuart
Hi Guys
First off I would say that I don't usually ask questions in forums I like to figure it out for myself. But at this point I'm totally stumped 
My experience has been for 2 years with the Printrbot Simple metal so I know M212 well Clearly need to forget that now with G31.
I fitted a inductive sensor to my D-Bot build followed the instructions to get it configured & working so far so good. Ive levelled the bed manually & carried out all the relevant steps to get mesh working & a height map built. However when I print my first layer is not quite squished enough, I baby step down 3 clicks & all is good. So m understanding is that I need to adjust the Z offset in the G31 command however it seems that what ever i adjust it to makes absolutely no difference. When I send a G31 T it does show the value stored in the config file but as i said seems to physically do nothing. Ive tried not use mesh & going for normal probing, added & removed G28 from my Simplify Start scripts and about a million other things including re-leveling the bed & doing the whole procedure 4 times now but still I'm stuck. My config file is below would appreciate any help you guys can give as Im at my wits end now
Thanks
Stuart
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Mar 27 2017 23:01:45 GMT+0100 (BST)
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y270 Z300 S0 ; Set axis maxima
; Endstops
;M574 X1 Y2 Z1 S0 ; Define active low and unused microswitches
M574 X1 Y2 Z0 S0 ; Define active low and unused microswitches
M558 P5 X0 Y0 Z1 H10 F120 T16000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P600 X28 Y10 Z0.49 ; Set Z probe trigger value, offset and trigger height
;M557 X15:285 Y15:235 S20 ; Define mesh grid
M557 X15:300 Y15:255 S20
; Drives
M667 S1 ; switch to CoreXY mode
M569 P0 S0 ; X motor runs forwards
M569 P1 S1 ; Y motor runs forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X100 Y100 Z1500 E417 ; Set steps per mm
M566 X600 Y600 Z12 E150 ; Set maximum instantaneous speed changes (mm/min)
M203 X8000 Y8000 Z400 E800 ; Set maximum speeds (mm/min)
;M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
;M201 X800 Y800 Z250 E2500 ; Set accelerations (mm/s^2)
M201 X800 Y800 Z200 E1500 ; Accelerations (mm/s^2). The acceleration, speed and jerk is a setting you can alter to try making the printer to print as nice as possible..
;M201 X500 Y500 Z100 E1000 ;n
M906 X800 Y800 Z800 E900 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M305 P0 T100000 B3988 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
; Network
M550 PDBot ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
; Custom settings are not configured
Just for ref here are the costs from Pushovers site, I don't work for them by the way just found it a great service
How much does Pushover cost?
Short answer: After a 7-day free trial, it costs $4.99 USD once, per-platform (iOS, Android, Desktop), to use on as many of your own devices1 on that platform as you want. There are no monthly or yearly fees and you can receive as many notifications as you want.
Long answer: As an end-user receiving push notifications, our iOS, Android, and Desktop clients are free to try for 7 days. After 7 days, you'll need to purchase a $4.99 USD license for each platform you wish to use it on. Once you've licensed a particular platform, you can use it on as many of your own devices that you personally use1 with no additional recurring fees. For example, once you make an in-app purchase in our iOS app on your iPhone, you can also use it on your iPad without having to pay again. If you also want to use it on your Android tablet, you would need to purchase an additional license for Android.
As an application developer or service provider sending notifications through our API, you can send a certain number of notifications for free each month. See our question about message limitations for more information.
For information on volume license pricing, please see this answer.
I think push notifications of some sort would be really useful, however pushover is probably not appropriate for most users
- it costs money to get an account as a user (after a 7 day trial)
- We would saturate the free message limits as a application very quickly, after that is costs money to send the messages:
https://pushover.net/faq#overview-limits
We might be able to get round #2 with some form of unique registration per Duet board but it does not seam worth exploring further.There are other options though:
https://aws.amazon.com/sns/
https://onesignal.com/
https://pusher.com/Presumably all of these would need some form of app to be installed on your mobile device to make the most of it.
I will be honest I can't totally remember what the deal was with Pushover & the charges but i paid around £5 one off charge and I have sent literally 1000s of notifications from my account all my home automation uses it too. I suspect this would have nothing to do with Duet, it would be down to the user to supply their unique API key from their account? Therefore no cost or implications to Duet. That said any sort of remote notification would be very helpful. Yes you would need the Fee (once you have a paid account) app installed but it is very good.
Stuart
Just bumping this up as I too need this really miss having pushover or in fact any kind of remote notification on Duet. This worked great on Octoprint.
That's great work Jackal, hopefully Christian will have a look at it and include it in a future version
Ive finally got my DuetWifi & new printer all built honestly Duet is just awesome if only Pushover were implemented it would be perfect for me. Appreciate the work Jackal has done but clearly that version of DWC is & has been left behind by the official release (loving FW 1.18 & DWC 1.15 BTW)
So my question any progress on implementation into the official release? Seems it should be a simple case of implementing & testing Jackal's code right? Or am I over simplifying Also appreciate it might not be top of the list, but if it were available i think many would move to use Pushover.
Thanks]
Stuart
I'm about to purchase a duetwifi and for me pushover integration is something I will miss a lot as I move away from octopi. I use pushover a lot sends notifications to all my iDevices when job status changes. Anyone got any sort of work around?