RepRapFirmware 3.01-RC6 released

[tobias_munich]

have issues after updating the SBC version. DWC, DCS and RRF
seem DWC/DCS has problems connecting the DUET3 Board.

SD-Only version has no problem

[chrishamm]

@tobias_munich Please make sure you are on the unstable package feed, DSF 1.3 is not on the stable (default) package feed yet. To check, have a look at /etc/apt/sources.list.d/duet3d.list and make sure you have unstable instead of stable in there.

@bearer DWC 2.1.0 remains compatible with previous firmware versions but be aware that I have not tested everything in depth with RRF2.

[A Former User]

@tobias_munich said in RepRapFirmware 3.01-RC6 released:

seem DWC/DCS has problems connecting the DUET3 Board.

verify the ribbon cable connecting the Duet and the SBC is installed correctly.
verify the SPI drivers are loades ( ls /dev/spi*)
check the logs for DCS (service duetcontrolserver status)

edit: also, which SBC?

[tobias_munich]

@bearer it has run for weeks now. its not a new installation. will go deeper to understand the issue...

[chrishamm]

RRF 3.01-RC6 is NOT compatible to DSF 1.2.x. If you want to give it a try, make sure you are on the unstable branch and if you can, do NOT upgrade the firmware manually. The provided reprapfirmware package updates it automatically.

[A Former User]

@tobias_munich DWC is running otherwise you'd not get a web page, so issue is with DCS, logs are likely most relevant, checking the SPI drivers are just to dot the t's in case something external to the duet packages got updated to cause an issue

[tobias_munich]

@chrishamm seems that's my problem. will fix it..

[Dougal1957]

@chrishamm Chris I have upgraded mine to 1.3 of DSF but when attempting to upgrade to RC6 I get a failure due to no IAP file

Any advise

	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC5 running on Duet 3 MB6HC v0.6 or 1.0
Board ID: 08DGM-9T66A-G63SJ-6J1DA-3SD6R-TV0BA
Used output buffers: 1 of 40 (5 max)
=== RTOS ===
Static ram: 154084
Dynamic ram: 160892 of which 52 recycled
Exception stack ram used: 216
Never used ram: 77972
Tasks: NETWORK(ready,2076) HEAT(blocked,1196) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,216) MAIN(running,4956) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 124:09:52 ago, cause: software
Last software reset at 2020-03-03 18:27, reason: User, spinning module LinuxInterface, available RAM 79528 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 38.4, current 41.6, max 43.2
Supply voltage: min 23.6, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: standstill, reads 1090, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 1090, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 1091, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 1091, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 1092, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 1092, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-04-03 13:26:07
Slowest loop: 2.33ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.80ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 1787965, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 2
Last transfer: 16ms ago
RX/TX seq numbers: 36774/40855
SPI underruns 3, overruns 3
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v1.3.0.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.88

Doug

[dc42]

@bearer said in ReprapFirmware 3.01-RC6 released:

Will future DWC releases like 2.1.0 retain full support for RRF2? At least until RRF3 goes mainstream perhaps? Couldn't see anything about compatibility except for 2.0.3 stated supporting 0.6/0.8.5 boards

That's unlikely. Future versions of DWC will provide features (e.g. the object cancellation interface) that are not supported by RRF2.

I expect RRF 3 to go "mainstream" shortly after RRF 3.01 stable is released. That release may be as little as a week away.

[dc42]

@Dougal1957 said in RepRapFirmware 3.01-RC6 released:

I have upgraded mine to 1.3 of DSF but when attempting to upgrade to RC6 I get a failure due to no IAP file

That file should be included in the DSF release. I can provide it if necessary.

[Dougal1957]

@dc42 please but it definitly fails and I have tried to do the Sudo Apt-get Update sequence twice as well I have appended the M122 log to my post above.

I will probably need simple instruction on what to do with the file mind.

Doug

[chrishamm]

@Dougal1957 Sorry, looks like like this file was missing in the RRF package, I've just added it back and uploaded it to another location: http://pkg.duet3d.com/Duet3iap_spi_MB6HC.bin You may need to rename it to Duet3iap_spi.bin.

[A Former User]

if the issue is stable/unstable package feed run grep duet3d -r /etc/aptto check and echo "deb https://pkg.duet3d.com/ unstable armv7" | sudo tee /etc/apt/sources.list.d/duet3d-unstable.listto fix if needed.

or what that guy said

[chas2706]

@Dougal1957 said in RepRapFirmware 3.01-RC6 released:

RepRapFirmware for Duet 3 MB6HC version 3.01-RC5 running on Duet 3 MB6HC v0.6 or 1.0

You M112 suggests you are running 3.01-RC5.

[A Former User]

@chrishamm said in RepRapFirmware 3.01-RC6 released:

To check, have a look at /etc/apt/sources.list.d/duet3d.list and make sure you have unstable instead of stable in there.

btw that conflicts with the wiki that says to create another file duet3d-unstable.list

[Dougal1957]

@chas2706 exactly the point the upgrade to rc6 is failing

[Dougal1957]

@bearer Defo on the Unstable branch

pi@duet3:~ $ grep duet3d -r /etc/apt
/etc/apt/sources.list.d/duet3d.list:deb https://pkg.duet3d.com/ stable armv7
/etc/apt/sources.list.d/duet3d-unstable.list:deb https://pkg.duet3d.com/ unstable armv7
Binary file /etc/apt/trusted.gpg.d/duet3d.gpg matches
pi@duet3:~ $ echo "deb https://pkg.duet3d.com/ unstable armv7" | sudo tee /etc/apt/sources.list.d/duet3d-unstable.list
deb https://pkg.duet3d.com/ unstable armv7
pi@duet3:~ $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease        
Hit:3 https://pkg.duet3d.com unstable InRelease                        
Hit:4 https://pkg.duet3d.com stable InRelease    
Reading package lists... Done
pi@duet3:~ $ 

Doug

[A Former User]

@Dougal1957 said in RepRapFirmware 3.01-RC6 released:

Defo on the Unstable branch

yeah

do wget http://pkg.duet3d.com/Duet3iap_spi_MB6HC.bin -O /opt/dsf/sd/sys/Duet3iap_spi.bin

[chrishamm]

@Dougal1957 The stable list is still in there: sudo rm /etc/apt/sources.list.d/duet3d.list followed by sudo apt-get update should work for you

[A Former User]

@chrishamm said in RepRapFirmware 3.01-RC6 released:

The stable list is still in there

is that a problem, more importantly, should it be a problem?