Posts made by Phaedrux

What do your fan settings look like in simplify?

Firmware version?

@Rseur said in Extruder stopping mid print, fixed after reboot:

checked with different cable

Phase disconnected usually means what it says, so I would suspect an intermittent break in the cable, especially seems likely if the cable chain has been in use for a long time. But you say you've tested with a new cable?

Just to confirm the situation.... Is this correct?

• you have two old Duet 2 wifi boards that worked with the wifi network in question previously.
• you have two new Duet 2 wifi boards with external antenna that both show No known networks found?

The network in question is a 2.4Ghz network?

Can you test in access point mode to remove your network from the equation?

https://docs.duet3d.com/User_manual/Reference/Gcodes#m589-configure-access-point-parameters

Do you have a M122 report from after the problem?

@Michael-P said in SBC connection issues:

connection to the Raspberry Pi via IP address

You should go into your router control panel and set the Pi to a reserved address so that it doesn't change.

Have you been in touch with Modix support yet?

@VasDrafts said in Sensor Open Circuit, only when E0, E1, and bed fire at once:

but it shows random spikes to 2000c on the bed temp graph.

This makes it sound like interference, or possibly a faulty or intermitent sensor/wire.

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@CreateAndCarveCNC said in Failed to initialise WiFi module:

December last year with my CNC machine from Ooznest.

Meaning December 2024, a few months ago? If so, we can do a warranty replacement.

Can you share your config.g and an example gcode file generated by simplify that shows it trying to execute fan commands?

I'm not a simplify user, but something may become obvious what it's trying to do with those two files in hand.

Did you follow this section to add your SSID and password to get connected again?

https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-5-connect-duet-to-network

How fast are you printing? That's a lot of retraction to make and adjust. The extruder is going to be trying to move quite a bit and quite rapidly to make the PA adjustments. If the jerk value isn't high enough the print will need to slow down to accommodate.

Other than the noise, is the print quality still good?

Can you also send the following commands via usb terminal and report what they return?

M552 S-1
M552 S0
M588 S"*"
M552 S1
M997 S1

@GBusy24 said in 2 NEW DUET 2 WIFI's W/EXTERNAL ANTENNA WILL NOT CONNECT:

@Phaedrux so I guess maybe I could just switch out the cards right?

For the most part yes as long as the firmware version was at least close in version.

The wifi SSID and password need to be re-added because they are stored on the module, so you'd still want to use the getting connected guide I linked above.

Is this a new board, or one that worked previously?
When and where did you purchase it?

I'm a bit confused now about what state you're currently in.

Have you been following this guide?
https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

If you are replacing a board, do you already have an existing configuration from the old board?

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-09-18 11:25:32
ok
M587
Error: M587: use M552 to abandon the current connection attempt before using this command
ok
M552
WiFi module is changing mode
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M587
Error: M587: use M552 to abandon the current connection attempt before using this command
ok
M552 S0
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M587
Remembered networks:
<ETX><ETB><STX> IP=0.23.2.0 GW=5.45.2.0 NM=0.23.2.0
Gregs WIFI IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
TNCAPF318D9 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
ok
M552 S1
ok
M552 S0
ok
Error: WiFi module reported: Timed out
WiFi module is idle
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later
Board ID: 0JD6M-99APT-NU4SN-6J9F4-3SN6M-14QKK
Used output buffers: 1 of 26 (10 max)
Error in macro line 1 while starting up: Bad command: 
=== RTOS ===
Static ram: 23376
Dynamic ram: 71596 of which 0 recycled
Never used RAM 15652, free system stack 180 words
Tasks: NETWORK(1,ready,6.9%,344) HEAT(3,nWait 5,0.0%,378) Move(4,nWait 5,0.0%,359) MAIN(1,running,92.7%,500) IDLE(0,ready,0.3%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:26 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 21.3, current 26.3, max 26.5
Supply voltage: min 0.3, current 1.6, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/40/12, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 80.54ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 0.66ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: idle
Module is idle
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 00:00:00:00:00:00
Module reset reason: Power up, Vcc 2.66, flash size 2097152, free heap 47772
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

This error

Error in macro line 1 while starting up: Bad command: 

It looks like you have some bad characters in your config.g that may be causing it to stop executing correctly?

Can you upload your config.g file?

Can you try and configure it to work in access point mode? This will have the Duet create a wifi network that you then connect to. This will help determine if the module is having the problem or something else.

https://docs.duet3d.com/User_manual/Reference/Gcodes#m589-configure-access-point-parameters

I see you already have a thread started here. Please keep it limited to one thread per issue.

https://forum.duet3d.com/topic/37842/printer-not-hitting-any-of-the-endstops

@rodneysramosj said in After Homing will not manual Move away from endstop:

we cannot manually move away from the end stop only towards it

It sounds like your end stops and/or your axis directions may be misconfigured. I'm guessing it's hitting the endstop and it's thinking it's at the min, when it's actually at the max, or vice versa.

1. Decide where you want X0 Y0 to be. Popular choices are the front left corner of the bed, or the centre of the bed.
2. Decide which direction you want to be positive X and which direction should be positive Y. Usually positive X is to the right and positive Y is away from you. Other directions are possible but be sure to choose a right hand coordinate system. Keep it simple -X should move left, +X should move right, -Y should move to the nozzle to the front of the bed, +Y to the back.
3. Adjust the motor directions in config.g to get positive X and Y movements in the desired direction.
4. Establish whether your endstop switches are high end (at axis maximum) or low end (at axis minimum) and configure the endstops accordingly in the M574 commands in config.g.
5. Now in your homing files the homing moves should move towards the endstop.

What do you want it to do that it isn't doing now? It looks like a passable start to tweak.