RepRapFirmware 3.0 first official beta is out

kraegar

Heater faulted this time, print shows 100%, but it still moving as if printing.

9/15/2019, 5:20:46 PM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 v0.5 version 3.0beta10 running on Duet 3 prototype v0.5
Board ID: 08DGM-9T66A-G63SJ-6J1FJ-3SD6M-KS0BA
Used output buffers: 1 of 32 (7 max)
=== RTOS ===
Static ram: 67696
Dynamic ram: 133764 of which 60 recycled
Exception stack ram used: 592
Never used ram: 191104
Tasks: NETWORK(ready,2044) HEAT(blocked,1108) CanReceiv(suspended,3804) CanSender(suspended,1496) CanClock(blocked,1432) TMC(blocked,456) MAIN(running,1856) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 02:57:41 ago, cause: power up
Last software reset at 2019-09-13 01:57, reason: Unknown, spinning module Platform, available RAM 191532 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
MCU temperature: min 47.1, current 57.2, max 58.3
Supply voltage: min 22.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, reads 26365, writes 25 timeouts 0, SG min/max 0/1023
Driver 1: ok, reads 26366, writes 25 timeouts 0, SG min/max 0/1023
Driver 2: standstill, reads 26367, writes 25 timeouts 0, SG min/max 0/1023
Driver 3: standstill, reads 26368, writes 25 timeouts 0, SG min/max 0/877
Driver 4: standstill, reads 26370, writes 25 timeouts 0, SG min/max 0/312
Driver 5: standstill, reads 26379, writes 17 timeouts 0, SG min/max 0/1023
Date/time: 2019-09-15 22:20:44
Slowest loop: 285.52ms; fastest: 0.19ms
=== Move ===
Hiccups: 366674, FreeDm: 354, MinFreeDm: 285, MaxWait: 354199ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 19586, completed moves: 19533, StepErrors: 0, LaErrors: 0, Underruns: 0, 1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file* is doing "G1 X119.443001 Y109.000999 E0.012100" in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon* is ready with "M122" in state(s) 0
queue is idle in state(s) 0
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 79.80ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

Ethernet -
State: 0
Socket states: 0 0 0 0 0 0 0 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 113ms ago
RX/TX seq numbers: 30927/30927
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 1760/64-2024
=== Duet Control Server ===
Duet Control Server v1.0.3.1
File:
Pending code: G1 X129.877 Y112.387 E0.0176
Pending code: G1 X130.284 Y112.666 E0.0197
Pending code: G1 X131.002 Y112.891 E0.0301
Buffered code: G1 X123.744 Y110.305 E0.0091
Buffered code: G1 X124.791 Y109.809 E0.0463
Buffered code: G1 X125.212 Y110.439 E0.0303
Buffered code: G1 X125.880 Y110.144 E0.0292
Buffered code: G1 X125.991 Y110.120 E0.0046
Buffered code: G1 X126.642 Y110.149 E0.0261
Buffered code: G1 X127.095 Y110.256 E0.0186
Buffered code: G1 X127.175 Y110.861 E0.0244
Buffered code: G1 X126.957 Y111.087 E0.0126
Buffered code: G1 X126.976 Y112.073 E0.0394
Buffered code: G1 X127.879 Y112.308 E0.0373
Buffered code: G1 X128.115 Y112.413 E0.0103
Buffered code: G1 X128.511 Y112.350 E0.0161
Buffered code: G1 X128.605 Y112.302 E0.0042
Buffered code: G1 X129.359 Y112.364 E0.0303
Buffered code: G1 X129.418 Y111.958 E0.0164
Buffered code: G1 X129.802 Y111.953 E0.0154
=> 748 bytes
Code buffer space: 1104
Configured SPI speed: 1000000 Hz
Full transfers per second: 269.94
Processing print job /opt/dsf/sd/gcodes/forbiddentower-whole-02_100mm.gcode

wilriker

@kraegar said in RepRapFirmware 3.0 first official beta is out:

Heater faulted this time, print shows 100%, but it still moving as if printing.

IMHO "heater faulted" is a bit misleading since it has a specific meaning usually. Maybe something more descriptive like "heaters turned off" would be better.

=== Move ===
Hiccups: 366674, FreeDm: 354, MinFreeDm: 285, MaxWait: 354199ms

Not sure if that's the cause for the problem but this section does not look good either way.

EDIT: the hiccups might be a result of the extruder drive not being moved because of too low temp.

dc42

@wilriker said in RepRapFirmware 3.0 first official beta is out:

EDIT: the hiccups might be a result of the extruder drive not being moved because of too low temp.

That shouldn't cause hiccups. A hiccup is a deliberate delay introduced by the step pulse generator when it finds that it can't keep up with step rate demanded. They typically happen when microstepping is set too high.

T3P3Tony

@kraegar thanks for persevering. I note that you are showing :

=== Duet Control Server ===

Duet Control Server v1.0.3.1

in your M122, even though earlier you reported 1.0.3.3 as installed. can you try a restart and confirm that you are now using 1.0.3.3

I am not 100% sure this is fixed in 1.0.3.3 but it should be better

kraegar

I have seen two failure scenarios.

It says heater 0 faulted, temps all drop, % complete goes to 100% and it keeps on moving in x/y/z through the gcode file. I can't cancel the print, even though it's still chugging along
It just stops entirely. Also reports 100% complete.

@T3P3Tony - good catch. It's interesting, yes I have only 1.0.3.3 installed now according to apt list, but it reports back as running 1.0.3.1. This was after multiple full reboots since I'd pulled 1.0.3.3. It must not have updated right when I switched repo's. I uninstalled it (sudo apt-get remove duetsoftwareframework; sudo apt autoremove ), rebooted for good measure, then pulled a fresh copy. M122 now reports the correct version that matches the CLI.

T3P3Tony

@kraegar ok, at least some of those issues are supposed to be fixed in 1.0.3.3 so please try again!

kraegar

Yep, already starting a print!

Sorry, if I'd noticed M122 had a different version earlier I wouldn't have bothered till that was fixed!

(It may be worth investigating how your updates work, since the CLI showed a later version than what was running, something didn't get overwritten properly)

T3P3Tony

@kraegar yes - i think we need to force stop the service before the update runs

kraegar

Is it possibly to query against the duet services from the CLI now? A diag script to list versions, compare the running version against the installed version, etc would be trivial, and handy if so. I'm sure more could be added to it over time, too.

A Former User

@kraegar said in RepRapFirmware 3.0 first official beta is out:

Is it possibly to query against the duet services from the CLI now?

maybe the link in this post has some inspiration; not been updated to reflect the new repository however https://github.com/chrishamm/DuetSoftwareFramework/issues/31#issuecomment-513701442

if you meant to run g-code from the console you might want to look at this (CodeConsole is very unpolished)

pi@duet3:/opt/dsf/bin $ sudo ./CodeConsole
Connected!
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 ...
pi@duet3:/opt/dsf/bin $

beikeland created this issue in chrishamm/DuetSoftwareFramework

closed M115 does not work on serial/USB #31

T3P3Tony

@kraegar you can see what services are running in the normal linux way. but not what firmware is on the duet w/o writing a plugin for DSF (or as @bearer says use codeconsole)

kraegar

@T3P3Tony Yeah, I meant querying the duet itself. I'll take a look at codeconsole, and the other threads. Sounds like there's been some good work done already, so I probably won't muddy the waters.

kraegar

Longest completed duet3 print @ 3h 5m without issue now that I'm running the latest software. I'll keep on testing!

smoki3

I have problems with the thermistors on this build on my Duet2Wifi. T0,T1 and Bed shows -273 °C. The thermistors on the duex5 are fine. They are defines as:

; Thermal Sensors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700                    	; Set thermistor + ADC parameters for heater 0
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 1
M308 S2 P"e1_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 2
M308 S3 P"e2_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 3
M308 S4 P"e3_temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700       	; Set thermistor + ADC parameters for heater 4

; Hardware
M950 H0 C"bed_heat" T0
M950 H1 C"e0_heat" T1
M950 H2 C"e1_heat" T2
M950 H3 C"!exp.heater3" T3
M950 H4 C"!exp.heater4" T4

If I ask for the Statuts with M308 S1I get correct values:

M308 S1
Sensor 1 type Thermistor using pin e0temp, reading 22.1, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:4700.0 L:0 H:0

tdybare69

I NEED HELP MY SD CARD CRASHED. HOW DO I START WITH A BLANK SD CARD.

A Former User

@tdybare69 said in RepRapFirmware 3.0 first official beta is out:

I NEED HELP MY SD CARD CRASHED. HOW DO I START WITH A BLANK SD CARD.

You start by turning off your Caps Lock. Then you format the SD card, download Raspbian - write the image to the SD card, and add the Duet3D repository and install DuetSoftwareFramework according to the Wiki. (Or wait for the Duet3d guys to make the image available as a download)

wget -q https://pkg.duet3d.com/duet3d.gpg
wget -q https://pkg.duet3d.com/duet3d-unstable.list
sudo mv duet3d.gpg /etc/apt/trusted.gpg.d/
sudo mv duet3d-unstable.list /etc/apt/sources.list.d/duet3d-unstable.list
sudo chown root:root /etc/apt/trusted.gpg.d/duet3d.gpg
sudo chown root:root /etc/apt/sources.list.d/duet3d-unstable.list
sudo apt-get install apt-transport-https
sudo apt-get update

jannau

The only option I currently see is start with a new Raspbian image and install Duet Software Framework as described here: https://duet3d.dozuki.com/Wiki/Duet_3_prototype_guide_for_OEMs

I'm currently doing that since my Duet3 apparently came without SD card and it seems to work. I have not connected any Hardware to the Duet yet.

T3P3Tony

@tdybare69 I have just finished writing the documentation to help with this:

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

Please let me know how you get on.

@bearer thankfully we have the SD image so hopefully it will be a bit quicker now. Also welcome feedback on the linked documentation.

T3P3Tony

@jannau I am surprised your Duet 3 came without an SD card, I will pass that on. Please see this documentation:

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

Feedback welcome I have just written it!

A Former User

Looks good at a glance, minor formatting glitch in the list way at the bottom, has visible [code] tags.

DuetPi.img 3.2G - this could probably be compressed to save some bandwidth and or time.

Edit:

You will need at least an 8Gb class 10 SD card.

If using a larger card you may wish to expand the filesystem to utilize the adittional space. Run sudo raspi-config nonint do_expand_rootfs to expand the filesystem to span the whole card.

One this is complete Windows may prompt you to format the disk. Do not do this, it is because Windows does not recognise one of the partitions on the image.

Once

Create a new file named “wpa_supplicant.conf” (exact naming is critical, do not have a ".txt" at the end of the file).

This file already exists in the image btw

In a text editor add the following:
country=GB
Replacing the SSID_OF_NETWORK with your wifi SSID and PASSWORD_OF_NETWORK with your password.
Save and safely eject the SD card

Might be obvious to some, but changing the country code for compliance with wifi certifications might be mentioned here. Which channel the driver will allow the wifi chip to use is dependent on this setting. Two letter country code from https://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements

If none of these steps work see the Troubleshooting Duet 3 - SBC communications documentation.

dead link

Image Size and compression: DuetPi.img 3,447,717,888 vs DuetPi.img.bz2 864,099,605 - maybe not everyone is living in purgatory with a 4Mbit downstream. Also consider adding MD5/SHA1 signature files to help verify the download.