Changed ISP

markz

@Dizzwold Generally you can't set a computer name with a space character in it. Have you tried using M550 P"Duet3" ?

Also I'm confused by that .xxx - are you not showing it? That needs to be number like @Exerqtor shows.

Exerqtor

@Dizzwold Generally you can't set a computer name with a space character in it. Have you tried using M550 P"Duet3" ?

The space shouldn't be an issue, I've got one in my M550 as well, and it's working flawlessly

markz

@Exerqtor Huh, thanks. I took a look and in their usual clever fashion they display the m550 name but elide the space when setting the hostname.

Dizzwold

@markz @Exerqtor

The printer name with the space hasn't been an issue before and the last 3, or 4 if you include the dot (.xxx), these are numbers, I'm just not willing to disclose them to the worldwide web.

Ive created the runonce.g file in sys on the sd card and removed my network info from the config.g and added the network info above as mentioned.

If I open a browser on 192.168.0.14, the page just keeps searching.

I now get a link led illuminated on the ethernet connector, where I didn't before (the left green led).

This is only the usb cable for power and serial connection and an ethernet cable directly from the Duet to my computer.

In serial tools I get the following;
Screen Shot 2023-02-26 at 13.25.13.png

If I do an Angry IP scan the Duet isn't found, searching from 192.168.0.0 to 192.168.0.255

Edit,
I've just entered M552 in serial tools and it returns;
M552
Ethernet is enabled, configured IP address: 192.168.0.14, actual IP address: 192.168.0.14
ok

But searching in m,y browser for that address, it keeps searching.

Exerqtor

@Dizzwold

Hmm, i'm not sure if powering the board just with an USB connection will be enough (might be wrong on that one though).

Dizzwold

@Phaedrux

Can you offer any advice please?

Dizzwold.

Dizzwold

@Exerqtor @markz @Phaedrux

Wow, Well I have no explanation for this except I sent Now Broadband an email stating I have a 3d printer, what ip address it had and what new IP address I was now changing it to, ie in the new range of the new router;
Old ISP Talktalk was on 192.168.1.xxx
New ISP Now Broadband is on 192.168.0.xxx

Ten minuets later, all of a sudden the Duet could be found on the new static IP address I'd given it.

No email in reply or any explanation form Now Broadband, just suddenly worked and was found?

If I get an email at any point, I'll let you all know.

Really, really confused.

Dizzwold.

markz

This post is deleted!

Phaedrux

Can you send M122 and copy paste here?

Does it still think it's in SBC mode?

Dizzwold

@Phaedrux @Exerqtor @markz

@Phaedrux said in Changed ISP:

Does it still think it's in SBC mode?

No. It just all of a sudden worked on my network on the new static ip address I'd given it 192.168.0.xxx (on Now Broadband).
Before I was with Talktalk Broadband on 192.168.1.xxx, but when I changed ISP if I typed in my browser the duets static ip address it couldn't be found. Angry ip scanner couldn't find it. I had no network leds illuminated on the ethernet connector.
Here's the result from M122 in DWC using my browser on the new static ip address;

27/02/2023, 10:45:44 	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.4 (2022-10-20 16:19:01) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 0JD2M-999AL-D25SW-6J9D0-3SD6M-9PY70
Used output buffers: 8 of 40 (20 max)
=== RTOS ===
Static ram: 152824
Dynamic ram: 97204 of which 312 recycled
Never used RAM 100332, free system stack 200 words
Tasks: NETWORK(ready,27.1%,220) ETHERNET(notifyWait,0.2%,568) HEAT(notifyWait,0.0%,328) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,349) TMC(notifyWait,8.1%,91) MAIN(running,63.9%,925) IDLE(ready,0.7%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:18 ago, cause: software
Last software reset at 2023-02-27 10:45, reason: User, GCodes spinning, available RAM 100332, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 126
MCU temperature: min 27.3, current 28.5, max 28.6
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 35321, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 35321, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 35322, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 35322, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 35325, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 35325, writes 11 timeouts 0
Date/time: 2023-02-27 10:45:43
Slowest loop: 1.69ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock 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 idle 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 184, received 529, lost 0, boc 0
Longest wait 3ms for reply type 6026, peak Tx sync delay 622, free buffers 50 (min 49), ts 92/91/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 2.41ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 2 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

I'm really grateful for everyone's help and input.

Thank you.

dc42

@Dizzwold it will switch into SBC mode if it can't read the SD card. If the SD card was still in the socket at that time, it may be faulty.

Dizzwold

@dc42

@dc42 said in Changed ISP:

If the SD card was still in the socket at that time, it may be faulty.

Which would have been faulty, the SD card or the socket?

The SD card was in the socket at the time.

Phaedrux

@Dizzwold said in Changed ISP:

Which would have been faulty, the SD card or the socket?

Could be either.

Are you still having issues with it, or is it working fine now?

You could replace the SD card to be on the safe side. Usually if the socket is the problem it doesn't suddenly start working again unless it's a cold solder joint that gets affected by thermal expansion.

Dizzwold

@Phaedrux

Ah, Okay...

It's not been used for around 3 weeks and the cupboard I keep it in (my printer cupboard), is usually around 15˚c if its door is left closed and not in use (possibly lower than that overnight). It's a double wall to the outside, but a very small cavity, so I've studded this with Rockwool, soundproof plaster board and Tecsound mass loaded vinyl sound proof membrane. Yes you could say this is cold, but it's not damp.

The SD card has been left in the board untouched, not nocked or moved in anyway until last Saturday 25/2/23 when I had the issues.

I'll have to take the board of it's mounting to look and take some pictures of the SD card readers solder joints, and the reader itself.

Like I say, it all of a sudden sprang back into life and I've ran a 10 hour print today with no issues?

Dizzwold.