Hi

I am using a 6HC and multipel 1XD.
During some sequence I want to power down and up 1XD. But not loos the over alla control of the status by not powering down the mainboard 6HC.

When doing this I loos control over the end stop sensors that I am using on the 1XD. Is there a way around this?

/T

@jay_s_uk

I think I solved it. I forced the upgrade with a terminal window with the /opt/dfs/bin/DuetControlServer -u

Then I flashed the SD card. Now everything is up and running with 3.4.0

Hi I am just wondering if the Wifi module prototype that was, I guess, prior to the Wifi boards that sells right now work with MQTT?

I have 3 Wifi modul prototype boards that I got early. Are there any differens between them and the ones that sells right now?

Can I get the board to send MQTT messages? (Have tried a little but id does not work. But I have the config in the config.g. I read that this will not work. Then I did a de activation of the MQTT and manually entered the information but it seams not to work. Somebody, in a forum post, was describing that it needs to gen 3 Wifi board. What does that mean?

Also a question regarding the wifi board. It takes an awful lot of time to it to get started. Sometimes about 1-2 min. Can this time be reduced some how? Since in prototype mode using soft reset of the Duet3 board seams to be used a lot.

/T

@Phaedrux @chrishamm

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9FJ-3S86S-T80Z8
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 66352 of which 0 recycled
Never used RAM 128068, free system stack 130 words
Tasks: SBC(ready,2014.0%,466) HEAT(notifyWait,9.4%,371) Move(notifyWait,1255.3%,214) CanReceiv(notifyWait,140.5%,773) CanSender(notifyWait,8.0%,327) CanClock(delaying,17.1%,344) TMC(notifyWait,23115.4%,90) MAIN(running,3453.6%,1231) IDLE(ready,29.3%,30), total 30042.6%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 15:54:45 ago, cause: power up
Last software reset at 2023-08-22 12:21, reason: User, GCodes spinning, available RAM 128036, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 136
MCU temperature: min 33.3, current 39.0, max 53.9
Supply voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.2, current 11.3, max 11.4, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/870/854, gc cycles 2607
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Date/time: 2023-08-24 01:20:35
Slowest loop: 61.41ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 6, maxWait 1702072ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4102, completed 4102, hiccups 0, stepErrors 0, LaErrors 0, Underruns [675, 0, 130], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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 428291, received 2749746, lost 0, boc 0
Longest wait 2ms for reply type 6023, peak Tx sync delay 30891, free buffers 50 (min 45), ts 286427/286417/0
Tx timeouts 0,0,9,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 63174/63174
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ab5c
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.50, max time between full transfers: 109.5ms, max pin wait times: 63.2ms/5.9ms
Codes per second: 0.80
Maximum length of RX/TX data transfers: 3676/1720

@chrishamm

Hi Chrishamm. How do I know how the DSF is installed correctly?

/T

Hi,

Made mistake upgrading, my system from 3.4.2 to 3.4.6 on my Duet 3 MB6HC v1.01 (SBC mode).

I can not do ssh so I hooked up a screen, keyboard and mouse. And made the upgrade.

Then I went to my wifi connected notebook and wanted to check what had happened. To see if I could down load the config.g
Made a M122 to see how far the installation had proceeded and by mistake I hit a M112.

There was not a immediate shutdown so the upgrade proceeded but the firmware on the 1XD board and the MB6HC did not get installed. The installation stoped at 98%.

I can't remember if I restarted the 1XD that could not have a firmware upgrade. But the installation ended.

I made manual upgrade to 1XD
M997 S0 to upgrade the main board

Part of the M122 say that the 3.4.6 is installed

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9FJ-3S86S-T80Z8
Used output buffers: 1 of 40 (13 max)

The printer runs. But I can't get the {state.time} to get updated. It is the same everytime my daemon.g echos it to the control.

Is that enough? Or do I have to check other things to be upgraded?

Hi

I am trying to logg some data. In my daemon.g I have a row like this.

echo "Time, ", {state.time},{move.extruders[0].factor} 

The result at the consol is. Did I Do something wrong?
The factor is changing but the time is not. Should it be casted to an other type as (string) or?

The consol gives this:

2023-08-22 02:10:19 Time, 0.00017975105 0.94
2023-08-22 02:10:17 Time, 0.00017975105 0.94
2023-08-22 02:10:14 Time, 0.00017975105 0.94
2023-08-22 02:10:12 Time, 0.00017975105 0.51
2023-08-22 02:10:10 Time, 0.00017975105 0.51
2023-08-22 02:10:07 Time, 0.00017975105 0.51
2023-08-22 02:10:06 Time, 0.00017975105 0.51

Hi,

I want an analog old fashion switch to run my extruder.
The printer is set up so that an 1XD is connected to the extruder.
There is longer than I can reach to a computer so it would be practical with a analog switch triggering the 1XD

Sorry I have seen something similar but can't find it....

I would want to be able to turn a switch when not running a print and just run the extruder un till I turn of the switch or start a print.

Is there an easy way?
I was thinking of making a code like this with a trigger.

in Config

M950 J16 C"^70.io1.in" ; create input pin 1XD board at CAN address 70 for manually extrude ^ Set resistor

; New triggers 2023-05-09
M581 T14 P17 S0 ; invoke trigger 14, for P17 input pin. Where P17 is equal to J17 for 1XD board at CAN address 70

Trigger14 (Schematic)

while (not printing and not bussy with extortion)
G1 E100 F2000

Would this be the easy way to do it?

@dc42 said in Problem with escape characters for password for Wi-Fi card.:

Try sending those commands from the console, but:

after the M552 I1 S0 command, wait for the "WiFi module started" message
change M558 "" to M588 S""
wait at least 10 seconds after the M588 command, it has to erase the flash file system
make sure that your terminal emulator doesn't change the straight double quotes to smart quotes

If you want to send them from a GCode file instead, you will need to add G4 delay commands after the M552 and the M588.

Thanks!

I got it to work. Just switched to a PC and dropped using serial tool on Mac and it all started to work.

Thanks for the G4. This will improve the code.

@dc42

It is the right. WiFi firmware version 2.1beta3

@dc42

I guess that makes my question obsolet.

@dc42

Is there a way to know that I have installed the right wifi code?

The files:
DuetWiFiServer_32S3.bin
DuetWiFiServer.bin