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
Posts made by Schickfus
-
RE: Made a mistake while upgrading, my system from 3.4.2 to 3.4.6
-
Made a mistake while upgrading, my system from 3.4.2 to 3.4.6
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 boardPart 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?
-
Getting the same state.time when doing echo>>"file" state.time
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 -
Analog switch controlling Extraktion before printing
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 1XDSorry 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 70Trigger14 (Schematic)
while (not printing and not bussy with extortion)
G1 E100 F2000Would this be the easy way to do it?
-
RE: Problem with escape characters for password for Wi-Fi card.
@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 quotesIf 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.
-
RE: Problem with escape characters for password for Wi-Fi card.
It is the right. WiFi firmware version 2.1beta3
-
RE: Problem with escape characters for password for Wi-Fi card.
I guess that makes my question obsolet.
-
RE: Problem with escape characters for password for Wi-Fi card.
Is there a way to know that I have installed the right wifi code?
The files:
DuetWiFiServer_32S3.bin
DuetWiFiServer.bin -
RE: Problem with escape characters for password for Wi-Fi card.
No I have done some testing.
M587.1
M587.2
And gett ssid string in the beginning chopped offed. Does this mater.
-
RE: Problem with escape characters for password for Wi-Fi card.
I used
M98 P"Gcodes/Wifimacro.g"
; wifimacro.g
; tell the Duet to connect to the wifi
;M118 S"Wifimacro turn off Wifi"
M118 S"Wifimacro turn off Wifi"
M552 I1 S0 ; Turn off the wifi module
M588 "*" ; forget all current SSID networks
M587 S"SurfSpaceGuest" P"Test"
M552 I1 S1 ; turn the wifi module back on
;M118 S"Wifimacro turn on Wifi"
M118 S"Wifimacro turn on Wifi" -
RE: Problem with escape characters for password for Wi-Fi card.
Yes I did. But this does not work.
It won't run the file -
RE: Problem with escape characters for password for Wi-Fi card.
@T3P3Tony said in Problem with escape characters for password for Wi-Fi card.:
M997 S1
M587.1
Error: M587.1: failed to start scan: WiFi module is disabledok
M552 I1 S0
ok
MWiFi module startedError: Bad command: M
ok
M587.1
ok
M587.2
Network Scan Results:
ssid=fSpace rssi=-47 phymode=n auth=Unknown
ssid=ceGuest rssi=3 phymode=b auth=Unknown
okBut it is not whole ssid. It is shopped
-
RE: Problem with escape characters for password for Wi-Fi card.
Ok thanks. I have gone to a network with just a 2.4 GHz
-
RE: Problem with escape characters for password for Wi-Fi card.
Ok the stars get filtered out in the chat.
So I am connected via the serial tool on a Mac to the board.
So I do
M587
Remembered networks: none
okThen I do
M552 I1 S0
okM587 S"SGuest" P"Test"
Don not get an ok
M552 I1 S1
Don't get an answer
M587
Remembered networks: none
okWhat is wrong?
-
Problem with escape characters for password for Wi-Fi card.
Hi
I have been trying out the wifi card. But I have hard time configure it. Or getting to connect.
I have a 6HC and 3.5beta2
In a wifi that I can’t change there are a star character and an equal character.
In a extra wifi.gcode file I do.
M552 I1 S0 ; Turn off the wifi module
M588 "" ; forget all current SSID networks
M587 S"Surf" P"=U2raA44Ae*”
M552 I1 S1 ; turn the wifi module back onBut it won’t find the network
I think it is a 5 GHz and not 2,4 GHz
Can this be a problem. -
RE: Loosing end stop sensors during power down and up a 1XD
@T3P3Tony said in Loosing end stop sensors during power down and up a 1XD:
If this is something you need to do routinely, then I would split your config.g file up into sections, and those sections that configure each 1XD move into individual macros, and call each of those in turn. That way you can then call just the specific 1XD configuration macro when a 1XD is reset.
Not routinely but it is part of a stop function to cut power to the stepper engins. But I do not want to lose the control of the stepper counting and positioning as if I would send a M112. I thought that I would trigger on an input on the 6HC and store the actual positions as I cut the power to the stepper engins.
As I write this I think you may already have run in to this problem?
-
RE: Loosing end stop sensors during power down and up a 1XD
Sorry I should say that I am using a 3.4 version and a SBC.