Topics created by AaronGreen

NETGEAR15 was at my folk's house where I used to be completely set up and operational.

Eve 22802 is where I am now, and it's 100% reception for all devices, and all able to connect. The other devices see the networks as case sensitive. I think the Netgear SSID was in caps from memory. So that's different.

SENDING:M587 S"EVE 22802" P"*****"

M552 S1
SENDING:M552 S1
WiFi reported error: no known networks found

I'd say maybe the case change is affecting the authentication. I'll have to try Terminal again.

*EDIT: I'm in. It took me a while to figure out the command steps in the start up guide, and the invisible commands there after, but got through it and now it's assigned and IP address and connecting. Now I can see that the bed is also running a 2000degs, which must of come lose when transporting.

@AaronGreen, I am sorry to hear you are giving up. Have you considered asking your local Makerspace/Hackspace for assistance, if there is one?

Building your own printer and getting it to work well does often require a lot of effort. It took me two redesigns and over £1000 of expenditure to get my Kossel to the state in which "it just prints" - all due to mechanical issues of various sorts - and even now the Titan extruder still gives me problems occasionally (Bondtech extruder on order).

If designing parts is where your real skill lies, then unless you have well over £1k to spend on a good ready-built printer, getting them printed by others instead may be a wise decision.

Good luck!

Downloaded 19.2 firmware and server, and copied them to the /sys folder of the SD card, ran M997 S0, and also M997 S1 and got this error:

Connecting…
Printer is now online.

M115
SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.19 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-08-14
M997 S0
SENDING:M997 S0
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
M997 S1
SENDING:M997 S1
[ERROR] Can't write to printer (disconnected?) (SerialException): WriteFile failed ([Error 22] The device does not recognize the command.)

I then tried M997 S1 first and it worked.

@Whitewold:

Make sure your slicer is configured for relative extrusion and not absolute…. M83 in your slicer start gcode if it doesnt have a check box like S3D does.... if its Cura then you will need to set M82 for absolute mode in config.g instead of M83

Once done change your steps back to 800 and retest then do the formula again

I did the extrusion test using the Duet console, but I'm glad you mentioned slicers, because I don't know how to set up a slicer for the Duet. I've been using Cura for my Marlin/MKS set up so far and it has been going well. Is there a set of instructions for using Cura in conjunction with the DuetWiFi?

I actually tried printing a test cube with the Duet console and it started printing a baseless, hollow test cube, and smeared filament all over the area, like a fire hose.

@MiR:

You may also want to check extrusion speed in the web interface of duet, before extruding hit the button for lowest extrusion speed or the one with 2nd lowest speed.

As you describe it you perhaps were using a too high extrusion speed.

I believe the extrusion speed was set to the default 100%. I'm not sure if that means it represents my max extrusion setting or not.

@dc42:

Ok, so you need to raise the BLT more between probing. The Duet homing files let you define the homing sequence yourself, so this is easily done. To raise it after Z homing, just put a G1 Zxxx command after the G30 commands in homez.g and homeall.g, where xxx is a suitable height.

To ensure that the head moves upwards sufficiently between probing when running G29 or G31, increase the H (dive height) parameter in the M558 command.

Ah, fantastic. Thanks very much for your help!

In firmware series 1.18 and earlier the IP address is always chosen by your WiFi router. Most routers allow you to reserve IP addresses for particular devices so that they always get assigned the same one.

@CaLviNx:

The LED's along that side all pertain to end stop switch states,

Wiring Diagram available here –-------------> https://duet3d.com/wiki/Duet_WiFi_wiring_diagrams

From the SD card end of the board

LED 1 = E1 Stop
LED 2 = E0 Stop
LED 3 = X Stop
LED 4 = Y Stop
LED 5 = Z Stop

The LED's along the end Starting from the "erase" button then going up are as follows

LED 1 = +3.3v
LED 2 = +5v
LED 3 = VIN
LED 4 = E0 HEAT
LED 5 = E1 HEAT

Found the problem. It's a faulty Y End Stop. It's hardly been used and it's decided to quack.

I've swapped it out with the original Z End Stop I took off for the BLTouch for now.

Thanks for your help, couldn't have done it without you.

OK, thanks very much for your help.

I've made those updates as well, and I'll go back over them again in finer details once I have a first pass of the entire printer working.

At the moment, one additional thing keeps breaking down after I fix something else.