Hi guys,
Anyone using this filament diameter sensor with duet? Is there a possibility to get this data utilized in realtime by the firmware including a distance offset (sensor installed near the spool/beginning of the bowden tube etc)?
https://www.prusaprinters.org/prints/57154-infidel-inline-filament-diameter-estimator-lowcost
Thanks
@hector Ohhhhhh man.....finally 
been waiting for this for a long time (first raised a request for some sort of notification back in 2017.
Please let me know once the image is available. I have a Pi Zero connected to the duet already and use it as webcam so it should be a quick install (hopefully) 
Hi guys,
Resurrecting this as I found very little other info on this (coming from Octoprint, Telegram was super useful)
I just tried to install and run the bot on a Pi Zero but it failed.
Here is the process I used (might help others to spot my error or serve as instructions - once fixed):
Duetbot then started:
Connecting to duet...
Checking for upload dir...
Uploads enabled
Bot started...
followed by this error:
Failed to process updates. { Error: 401: Unauthorized
at buildConfig.then.then.then.then (/usr/local/lib/node_modules/duet-telegram/node_modules/telegraf/core/network/client.js:281:17)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
code: 401,
response: { ok: false, error_code: 401, description: 'Unauthorized' },
description: 'Unauthorized',
parameters: {},
on:
{ method: 'getUpdates?offset=0&limit=100&timeout=30',
payload: {} } }
I further checked that the duetwifi has no password set as I see from the notes that this is not yet supported. Unfortunately still no luck. Any help is apprechiated.
@luca79 said in Notification via Pushover or other service:
FYI, I am developing a telegram bot (in testing phase) to the purpose that can easily run on a RPI Zero. I will keep you posted as soon as the code is stable I will opensource it.
Hi Luca,
any news on the telegrambot? Looking so forward to it
Updated the first post. The IR Sensor mount as well as the config files are now available on Thingiverse for download.
Print away
Has anyone experience with the IR sensor and black color PEI sheet?
Like this: https://www.amazon.de/gp/aw/d/B06XHK217S/ref=mp_s_a_1_1?__mk_de_DE=ÅMÅZÕÑ&qid=1500030592&sr=8-1π=AC_SX236_SY340_FMwebp_QL65&keywords=pei+3d+druck&dpPl=1&dpID=31cdHAayG4L&ref=plSrch
Thanks
got my clear PC (no black available) today and did a first test print. Worked well. Sticks well.
Subsequent test prints had major issues with ABS with cold HB and also at 55C. I get the feeling that something else is off. This is very strange (went back to fixed Zheight as my probe had major issues with the clear sanded PC with variances of 0.9mm during mesh bed leveling).
More tests later…..
Perfect. Will get to it in the morning :-). Thanks!!
Hi guys,
getting some 3mm PC sheet tomorrow to hopefully get over the "non stick" issues I have.
Now the question is whether to sand or not? Apply heat or not for printing primarily ABS?
Thanks !
Good Now I have another project In the past I used OSH Park for my PCB creation…....maybe I will cook something up for the BLING
Thanks.
I'm a bit repelled by the price of the expansion board to just drive the LED's
Although it would be a nice added bling (maybe the developers could think about a future LED driver/expansion board?) for the printer.
I will probably stick to the plain white or fix an arduino into the circuit to control the colors (without the gcode integration).
My Makerbot Replicators 2x has served me well for many many years. Finally something broke down and it started to reset itself mid print. As replacing all the cables in the machine did not fix the problem I suspected a mainboard or PSU problem. Long story short: it was time for an upgrade.
The new Replicator 2X now runs a Duetwifi board with reprap firmware, utilizes a IR sensor to measure the bed height and provide mesh bed leveling and displays all the data on a 5'' color touch screen mounted at the same place the old Makerbot display was positioned.
What did I use for the conversion?
1x Duetwifi Mainboard - http://www.reprap.me/duetwifi-electronics-board.html
1x PanelDue 5'' Display - http://www.reprap.me/paneldue-with-5-screen-for-duetwifi.html
2x M3 Thermistor - http://www.reprap.me/m3-modular-screw-on-stud-thermistor-hot-end-screw-type-thermistors-for-3d-printer.html
1x 24V PSU - http://www.reprap.me/power-supply-24v-15a.html
connectors and new cables as I did not want to slaughter the stock makerbot cable set
Connections:
Extruder heaters, fans, extruder thermostor, heated bed and bed thermistor connection was straight forward
Steppers connection was straight forward as well. I simply connected the wires to the board in the same order as you see them on the stepper motor - minus the gap between the pins)
Endstop connection was done by combining the center 2 pins (these are the ground pins) from the Makerbot endstops to the gnd pin on the Duetwifi 3pin connector. signal and VCC according to the markings on the endstop and duetwifi mainboard
Zaxis homing was installed with both the makerbot endstop and the IR probe for duetwifi by DC42 (http://www.reprap.me/ir-probe-for-duetwifi.html). As I have some issues with my glass bed and printing ABS as it requires ABS juice which throws the sensor readings off, I currently use the fixed endstop for my prints and will switch back to the IR sensor once my Pei sheet arrives.
I mounted the board with stand-off to the bottom of the printer in-between the stock makerbot standoffs.4 holes are required in the bottom of the printer for that (M3). I also mounted the PSU beside it at the bottom to get a nice compact installation. There is enough space between PSU and bottom of the printer to allow the cooling fan to ventilate the PSU
Makerbot LEDs are hooked up to a spare fan connector on the board (plus minus leads only) for it to shine red while in operation. As duet wifi does not have the capacity to control the colors of the RGB LED's I will replace them with white ones going forward.
Last I removed the old Display and mounted the PanelDue.
For this I made an enclosure (modification of the enclosure made by DC42) - you can find it here: https://www.thingiverse.com/thing:2428995. It has a few slots to allow storage of SD cards (I still need to purchase the 10pin ribbon cable to actually use the PanelDue SD card slot - would be nice if the panel would come with them btw).
Finally I configured and tuned the printer with the reprap configurator and by hand with the editor.
Now I'm enjoying my new, wifi connected, Replicator
Update: I have uploaded the IR Sensor mount as well as the config files to thingiverse. The full "Replicator 2X Duet Wifi upgrade series" can be found here:
Part 1: DuetWifi Installation and PanelDue Mount (https://www.thingiverse.com/thing:2428995)
Part 2: Mini Differential IR Probe mount for Replicator 2X (https://www.thingiverse.com/thing:2475179)
Part 3: DuetWifi Configuration files for Replicator 2X (https://www.thingiverse.com/thing:2475257)
Part 4: Simplify3D Slicer Configuration for the Replicator 2X (https://www.thingiverse.com/thing:2476695)
Thanks for the tip. Went back to fixed z height for now till I have sorted the bed surface out. Pei sounds interesting
could be. can't recall to be honest.
4.99 USD for the client is a small price to pay though and the monthly API limitations (Each application registered to send Pushover notifications may send 7,500 messages per month for free) should be good enough I think.
As long as the Firmware supports the API (each Duetwifi board counts as single application with 7,500 messages FOC per month), each user would login to his/her own puahover account, add an application, and enter the API token into the firmware to receive 7500 messages per month FOC (after one time purchase of 4.99 USD).
API Info: https://pushover.net/api
Would be a nice option.
Thanks. To update, my issues went away after I updated the router. Happily pushing stuff over to the duetwifi now 
Thanks. Interesting. I'm using pushover since years, never paid a single cent (or was the app not free… Can't recall)
Maybe the apps I use do pay for api access? But I also use it by sending emails to my pushover account and it notifies me (my home servers daily raid updates for example). Maybe sending emails would be easier (pop3 pushmail client or so).
Thanks for looking into it
Ok. Thanks for the reply.
Not sure what to do. I could go back to the fixed z endstop and adjust the build table manually or maybe go with a pei sheet on the glass to keep it consistent as kapton alone is not ideal for keeping abs securely fixed (hence the need for abs juice).
Hi,
I completed the "Duet-ification" of my Replicator 2x recently.
After quite a bit of tuning etc. it is now printing like a champ.
However one issue I was not able to solve: the IR sensor.
While it is installed and sensing fine I have issues with the variance in trigger height.
My built surface is borosilicate glass on top of an aluminum heater bed.
As there are issues with aluminum reflections and the IR sensor as I understand from the blog, I have painted the aluminum black (BBQ black paint).
In addition I also painted the bottom surface of the glass black (the area that touches the heater). The top of the glass is covered in kapton tape.
Before I painted the bottom of the glass black I got trigger distances of 1.90 mm, after that it went up to 2.4mm. As I had trouble with ABS sticking to the tape I applied a bit of ABS juice (very very diluted, just makes the Kapton a bit cloudy) and the trigger distance went to 2.58mm.
From this I take it that the trigger distance changes heavily with the state the surface is in resulting in quite a bit of variance (e.g. after I pull a piece off and the ABS juice cloudiness is gone, I typically get failed first layers as the distance to the glass is wrong). Running meshbed compensation does not look to flat either making me not trust it (doubt that the glass plate has 0.2-0.3 delta at certain places).
Any suggestions how I can get this to become more reliable?
Thanks a lot,
Eric
This is the Nerd in me
But it would be cool if the board could send email notifications or push notifications. Example: when the print is done, when there is a fault etc…
Push clients for phones such as Pushover might be easily integrated via the available API (https://pushover.net/).