As I do a lot of radio monitoring stuff (hardware, software) even my keyboard and mouse are wired. And UTP cables tend to be quite noisy so everything in here is FTP or STP. Unfortunately that comes with a lot more rigidity if keeping the costs within reasonable limits! 😞

I am closing this thread because 121RC3 is now available.

3C isn't much overshoot and is unlikely to affect the print significantly. But if you want to reduce it, increase the A parameter in the M307 command for that heater a little. Try increasing it about 2%.

On windoze boxen …

Command Prompt

type "ipconfig"

Ping your IP - At prompt > type >ping 192.168.1.2 [ example IP ]

next prompt - type >arp -a

Shows all connected devices

Use M588 to remove a ssid from the list, and M587 to add a new one.

Everything worked, the results are perfect.
I have exchanged all 5 BL-Touch against the Mini IR Probe and am now really happy with the workflow.
Thank you very much for the prompt and friendly support.

I only have one. I believe the issue is biting me more than others because I am keeping my duet on all the time with a 5v PSU – and I use M80/M81 commands to control the 24v PSU + other components -- I have a raspberry pi listening to the power on pin and then it turns on relays for the 24v PSU + a 12v PSU for cooling fans, as well the relays for the AC SSR to the bed -- I find even the best SSRs leak, so I like to cut their power off completely. The Pi also does some other functions like web cam streaming and emails when print starts/ends (it polls the duet every 30 seconds).
I like having the screen and buttons on the screen turn the printer on/off -- I made macros for that.
I will switch to static IP -- I also have no option in my router to change the DHCP lease time -- it's locked to 24 hours...kinda sucks that it's an expensive home office router and doesn't have that option...

@paboman:

thx!
after m115 i get:

[[language]] FIRMWARE_NAME: RepRapFirmware for Duet WiFi and Duet Ethernet FIRMWARE_VERSION: 1.21RC2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-02-15 build 2 ```is it ok to have 1.21rc2 as firmware and 1.02 as wifi ?

In that output, the ELECTRONICS: Duet WiFi 1.02 or later refers to the board, and not the WiFi firmware.

Here's what I receive, for comparison:

[[language]] FIRMWARE_NAME: RepRapFirmware for Duet WiFi and Duet Ethernet FIRMWARE_VERSION: 1.21RC2 ELECTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2018-02-15 build 2

And yes, that's OK.

you need to double the steps/mm in the M92 commands for the axis that you changed the motors on!

Good point, that page doesn't properly cover the Duet Ethernet. To update you need to:

1. Upload the new DuetEthernetFirmware.bin file through the button on the Settings General page, and accept the invitation to install it;

2. When that is complete, upload the new DuetWebControl.zip file through the same button.

There are no special actions needed when crossing firmware version 1.19.

Okay so this is my homez.g

;z max homing to switch

G91
G1 Z240 F1000 S1
G92 Z162
G1 Z-4 F600
G1 Z10 S1
G90
G92 Z162

This is my probe config in config.g

M558 P5 I1 R1.0 H10 F700 T1500 X0 Y0 Z0 ;digital piezo sensor, output falls on contact, probing speed, not used to home axes
G31 X0 Y0 Z-0.1 P50 ;sensor is nozzle and debounce value.

As you can see I do not define the probe as an endstop in M558.

My bed.g only contains the mesh definition

M557 X10:260 Y20:180 S20 ;define mesh
M500 ;save

My start gcode contains amongst other things:
G28
M98 P0:/macros/SETZ ; run z fine tuning

That macro looks like this:

G1 X130 Y97.5 Z15 F1000 ;move to be centre slowly.
G30 ; probe for z=0
G1 Z10 F1000 ; raise nozzle
G30 S-1 ;check z gap
G1 Z10 F1000 ; raise nozzle

And here's how it works:

https://youtu.be/y3kCXAp0sZo

I tried sending G32 but since my bed.g does not contain discreet points to probe, it does nothing, but I regularly run a G29, save the mesh and then use G28, then G30 as above and print and get very nice first layers each time. I have no extra axes defined, just X, Y and Z and E0.

What am I missing?

I'll test this again before I release the next beta.

After a lot of testing and moving things around, I have to say that you're right after all, it must be the signal. While signal dB values change, and I can maintain the connection for quite some time - even seemed fixed at some point - while uploading new config via web interface I've noticed something very telling.

In the batch of text files being uploaded, some would pass some would fail - retry - different batch would pass and different fail, and so on…

Got it going now but resigned myself to running it via usb.

Thank you for your time mate, you can close this thread 🙂

Yes, right resistor (R37). You see the 330 ohm value in the photo. Not sure about the solder bridge.

But one other thing, if I boot from just a 5V input (usb), it boots up fine. All the endstops trigger and show hit in the machine properties.
–---
10 mins later...

Mmm, after more testing I'm not quite sure what to think. Could be a weak wifi possibly. I just rebooted with the usb and 15v connected and it's fine and dandy. Repeated it with the usb disconnected and again fails to boot. Plugged it in again and bingo!

TBH, if that's all it takes I'll live with that. It's just an OctoPi I use for the camera, so it'll stay on the printer anyway. Be nice to have an explanation though...! 😉

For anyone else who finds this via Google, the way to determine your port on a Mac is :

Open Terminal (cmd+space, type terminal, hit enter)

Type 'ls /dev/tty.*' without the single quotes obviously. Hit enter.

You should see a not too large list of ports that are in use. Mine looked like:
/dev/tty.Bluetooth-Incoming-Port /dev/tty.SOC
/dev/tty.MALS /dev/tty.usbmodem1442345

You're probably looking for one like /dev/tty.usbmodem1442345, but it will have a different number. If you have multiple ports that look like possibilities, just try them in pronterface.

Good Luck!

Put M401 near the start of bed.g, and M402 at the end.

That seems right, I did a restart and it showed up at the same IP address. Very pleased so far. Much easier than I thought it was going to be.

Excited for tomorrow to try it out and configure the firmware.

If it is a Duet WiFi then you will need to re-enter the WiFi network connection details. You may also need to make some changes to your config.g file to account for firmware changes.

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware