Posts made by StephenRC

Some filament is transparent to infrared.

The text editor can mess up the SetNetwork macro by using the wrong double quote marks. It has been previously reported for a Mac editor and I've found for Windows that Notepad++ does it also. One cure is to copy/paste from the web page to make the macro.

@AaronGreen:

I rams the bed at G1 Z0.0 F1000, even though that's a different position to the place it rammed it on my test print (far right).

I haven't continued with the process for fear of ramming the bed again.

My hotend Z offset is: M307 H1 A250 C140 D5.3 B0 S1

Whereas it was originally 0.9. I found that every time I did the Z0 calibration, the nozzle would always return to 5.4mm above the bed. Even if I set the physical height to 0.1, then told it to recognise it as Z0, then save it, it still would return to Z5.4 as Z0.

Maybe I've done the Z0 calibration wrong and used the wrong setting to get it there…

M307 doesn't set the z height. What you show is the hotend heater setting.

The WiFi has two connectors for the z motor and they're driven by one driver.

You can type in the temp you want in the box.

Use a macro, call it in both places. With a macro, you'll only have one place to change.

After editing config.g, you have to reboot for the changes to be used. I use macros to set the z offset for each type of filament and call the appropriate one in the slicer.

For the fan see https://www.duet3d.com/forum/thread.php?pid=6412#p6412

Shutdown: turn off the power, nothing special needs to be done before doing that. If you have an all metal hotend, wait for it to get below 50c before turning off the power. This will help prevent the filament from jamming.

Restart: via the web, hit the emergency stop button. On the board, hit the reset button. Another way: open config.g in DWC and save changes and it should prompt to reboot the board. Then there is the ol' standby: turn it off, wait for all the leds to go out, then turn it on.

Found this: http://www.chitu3d.com/3d-printer-parts-general-add-on-heated-bed-power-expansion-module-2/
After following the url on the circuit board.

The only spec is 25A max and only mentions 12vdc in determining the load.

It's the second to last of the photos provided. The photo of the bltouch in the package hasn't been updated.

That cheap ssr will barely let a 12vdc MK2a get above 70C.

Now, if you go with an AC powered heater, then a DC-AC SSR will have no problems and the heat up time will be short. Mine does the full heat up of bed & hotend less than a few minutes. Of course, you do need to install a thermal fuse on the bed heater for the safety bit.

If the led didn't turn on, you may have connected the cable to the module backwards.

Hotend temp is at or higher than the set fan turn on temp, which could be caused by an incorrect thermistor setup in config.g.
See: https://duet3d.com/wiki/Connecting_and_configuring_fans

I have this in my config.g to make sure the fan1 is set correctly:
M106 P1 T45 H1 ; set fan1 thermal, turn on when hotend get to 45C

Fan0 should be off, and if you haven't changed fan1 settings, it should be off until the hotend temp reaches 45c.

Yes you can.

I found that I needed to increase the acceleration and jerk values when I started to use pressure advance, otherwise the printing speed was reduced.

Increase the E jerk setting. I had been getting that since I boosted the acceleration for the x & y, and never did change the jerk settings. I originally had it at a really low value of 20, and changing it to 200 practically got rid of it. I'm using Titan bowden setup to a 1.75mm e3vd6 with a pressure advance of 0.03.

I found a simple way of getting a web cam for using in the DWC: Raspberry Pi, any model that can run OctoPrint. It's already setup up to be able to use a web cam or raspi cam, once it's enabled. Using the current version, OctoPrint's setting page gives you what's needed. Get the snapshot url and copy it to DWC with it edited to use octopi.local or the pi's ip address instead of the local home address.

This has the generic setups: https://github.com/dc42/RepRapFirmware