Error m587 failed to add ssid to remembered list another spi transfer is pending

Having an issue, with activating ESP8266 wifi and Skr V1.4 Turbo
Spend hours trying to troubleshoot the error, rechecked all the connections, resistor values and config files, but always getting the error.

`Printer is now online.

M552 S0
SENDING:M552 S0
WiFi module started
ok T0:-273.1 /0.0 B:-273.1 /0.0
Error: Failed to initialise WiFi module, code -7`

M587 S»your SSID» P»your password» results in»
Error: M587: Failed to add SSID to remembered list

When I send «M552 S0», ESP8266 blue led flashes briefly.
Tried re-flashin the module multiple times, with the latest «DuetWifiServer.bin». Always success.

Skr V1.4 Turbo is flashed with the latest firmware-wifi.bin (renamed to firmware.bin)

board.txt

i connect in digital mode, but want to connect right in analog (same as to Duet board). If i connect the sensor in analog mode, sensor dosn`t work…
I change M558 P1 (from P1 to P10), but nothing change (sensor not working or pin does not support a connection )

In digital mode work with M574 Z1 S2 & M558 P1 C»e1temp» H5 F200 T9000 I0 R0.5

can be added options to redefine APIN_SBC_SPI_MOSI ,APIN_SBC_SPI_MISO and so ?

to be able to use other pins than the ones on exp2

Hi
Randomly, when I have completed a job and start a new one the SKR reboots. Sometimes this happens twice in a row then it will print just fine. This happens on 3 of my machines with the SKR 1.3 in SBC configuration with a Pi 3 A+
All have stable meanwell power supplies and Pi and aux power is connected via bespoke pcb.
Any advice would be appreciated.

My config.g of one of the smaller machines

`G90 ; send absolute coordinates…
M83 ; …but relative extruder moves
M550 P»Helios» ; set printer name

M667 S1 ; select CoreXY mode

; Drives
M569 P0 S1 T0.1:0.1:0.02:0.02 D2 ; physical drive 0 goes forwards using default driver timings
M569 P1 S1 T0.1:0.1:0.02:0.02 D2 ; physical drive 1 goes forwards using default driver timings
M569 P2 S0 T0.1:0.1:0.02:0.02 D2 ; physical drive 2 goes forwards using default driver timings
M569 P3 S0 T0.1:0.1:0.02:0.02 D2 ; physical drive 3 goes forwards using default driver timings

M584 X0 Y1 Z2 E3 ; set drive mapping

M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80 Y80 Z200 E430 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E2000.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z2000.00 E3000.00 ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z120.00 E1000.00 ; set accelerations (mm/s^2)
M204 P1000.00 T5000.00
M906 X1000 Y1000 Z1200 E900 I70 ; set motor currents (mA) and motor idle factor in per cent
;M84 S20 ; Set idle timeout
M593 F40.5 ;M593: Configure Dynamic Acceleration Adjustment

; Axis Limits
M208 X-17 Y-29 Z0 S1 ; Set axis max travel
M208 X330 Y330 Z300 S0 ; set axis maxima

; Endstops
M574 X1 S1 P»xstop» ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P»ystop» ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P9 H2 F680 T8000 X0 Y0 Z1 C»^zstop» A10 S0.03 ; disable Z probe but set dive height, probe speed and travel speed
M950 S0 C»servo0″ ; Setup servo 0 as servo port on SKR

;M558 P5 C»zstop» H2 F480 T9000 R1 A10 S0.03 ; set Z probe type to switch and the dive height + speeds
G31 P300 X-23.5 Y0 Z1.25 ; set Z probe trigger value, offset and trigger height
M557 X40:290 Y40:290 P5 ; define mesh grid

; Heaters
M308 S0 P»bedtemp» Y»thermistor» T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C»bed» T0 ; create bed heater output on bed and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
M308 S1 P»th1″ Y»thermistor» T95002.69 B4322.60 ; configure sensor 1 as thermistor on pin e0temp
;M308 S1 P»P1.21″ Y»thermocouple-max31855″
M950 H1 C»he0″ T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

; Fans
M950 F0 C»fan0″ Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C»e1heat» Q500 ; create fan 1 on pin he1 and set its frequency
M106 P1 H1 T50 ; set fan 1 value. Thermostatic control is turned on at 50 deg C

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
T0 ;select tool
M501 `

boards.txt
`lpc.board = biquskr_1.3;

//LED blinks to indicate Platform is spinning or other diagnostic
//Comment out or set to NoPin if not wanted.
leds.diagnostic = NoPin;

//Internal SDCard SPI Frequency.
lpc.internalSDCard.spiFrequencyHz = 25000000;

//LCD Pins (only ST9720 SPI currently supported)
//setup the Software SPI Pins for LCD

heat.tempSensePins = {bedtemp, e0temp}; //Max of 3 entries
//Soft SPI Temp sensor to use with MAX31865+PT100
//softwareSPI.pins = {1.18,1.19,1.20}
//heat.spiTempSensorCSPins = {1.21, NoPin }; //Max of 2 entries
//heat.spiTempSensorChannel = 2

//Analogue to Digital prefilter
adc.prefilter.enable = true
sbc.lpcTfrReadyPin = 1.31
//serial.aux.rxTxPins = { NoPin, NoPin }

//TMC Smart Drivers
stepper.enablePins = { 2.1, 2.8, 0.21, 2.12, 0.10 }
stepper.stepPins = { 2.2, 0.19, 0.22, 2.13, 0.1 }
stepper.directionPins = { 2.6, 0.20, 2.11, 0.11, 0.0 }
stepper.digipotFactor = 0.00
stepper.TmcUartPins = { 1.17, 1.15, 1.10, 1.8, 1.1 }
stepper.numSmartDrivers = 4; //Adjust to the correct number of smart drivers
stepper.TmcDiagPins = { NoPin, NoPin, NoPin, NoPin, NoPin }
`

• WiFi —
  Network state is changingMode
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 2
  Failed to get WiFi status
  Socket states: 0 0
  WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
  WiFi module is idle
  WiFi reported error: �
  WiFi module is in an unknown state
  Error retrieving WiFi status message: bad reply format version
  [ERROR] Error retrieving WiFi status message: bad reply format version

WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
Error retrieving WiFi status message: bad reply format version
[ERROR] Error retrieving WiFi status message: bad reply format version

WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
Attempted to write invalid text to console, which could be due to an invalid baudrate
WiFi module is idle
WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle
WiFi reported error: �
WiFi module is in an unknown state
Error retrieving WiFi status message: bad reply format version
[ERROR] Error retrieving WiFi status message: bad reply format version

WiFi module is connected to access point BEAGLE_2.4G, IP address 192.168.2.60
WiFi module is idle

I use a BTT Relay connected to pin 1.24 on my SKR 1.3

In Marlin i have defined:
#define PSU_CONTROL
#define PSU_NAME «Power Supply»
#define PS_ON_PIN P1_24
#define PSU_ACTIVE_HIGH true

Is this possible in RRF?
Thanks for Help!

Hi! thank you for your great job, I really love this firmware.
I’m trying to get a BTT touch screen display to work on a SKR 1.4.
Unfortunately for now without success.

It seems that the serial port don’t works as it should (clearly after enabling it with M575 P1 B115200 S1 in config.g).
I also tried with a classic USB / TTL converter but no reply from board.

What am I doing wrong?

I’ve used the wifi firmware without probe problem, but when I switched to the sbc firmware, the z probe value stay at 1000, whatever the probe state (retract / deploy / hit). I didn’t change wires during the switch, except replace the wifi board by the rpi cable.
I tried with another probe pin (e1det) and without connect the pin, that gives the same result.

M119
Endstops - X: at min stop, Y: not stopped, Z: no endstop, Z probe: at min stop

Using the last pre-release LPC_RRFv3.1.1-14.

Configuration:

• SKR 1.4 Turbo
• BL Touch v3.1 original, wired on dedicated servo and probe pins
• RPI3B+ prepared and wired following the wiki page.

config.g
M558 P9 F100 H3 R0.2 T6000 B1 C"^probe"
M950 S0 C"servo0"
G31 P500 X35 Y-33.5 Z3.55
M557 X35:285 Y15:265 S50

board.txt
lpc.board = biquskr_1.4;
sbc.lpcTfrReadyPin = 1.31
adc.prefilter.enable = true
stepper.numSmartDriver = 5
leds.diagnostic = NoPin;
heat.tempSensePins = {bedtemp, e0temp};

I expect the probe working the same way with both firmwares.

Hi,
Have experienced that the EXP-MOT-support is first implemented after last stable build.
From my point of view, this is only mentioned in the ToDo-list and the changelogs, but should also be mentioned in the wiki:

https://github.com/gloomyandy/RepRapFirmware/wiki/PCR-Driver-Adaptor

Also, it is written «The defining of the pins is not required on the latest unstable builds.»
This is correct, but from my experience, defining them makes things NOT work. This is recommended writing more explicit for new users.

I couldn’t find and option to make a pull request to the wiki, so I put it here. If there is an option, i can of course write a request, if i’m given the proper instructions 👍

I have defined a filament runout sensor, the message appears, but the printhead do not move to the position set in pause.g
It looks like pause.g is not called

;config.g
; Filament sensor Extruder 0
M591 P2 D0 C»xstopmax» S1

and my

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.1.3-LPC on Mon Aug 03 2020 18:49:08 GMT+0200 (Mitteleuropäische Sommerzeit)
M83 ; relative extruder moves
G1 E-10 F3600 ; retract 10mm of filament
G91 ; relative positioning
G1 Z5 F360 ; lift Z by 5mm
G90 ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

Hello guys. I and my mate having same problem with this firmware.
Warning: motor phase A may be disconnected reported by driver(s) 1
Warning: motor phase A may be disconnected reported by driver(s) 0

on original DuetWifi on same config there are no errors. Maybe someone has this issuaes and know how to fix?

Hi i followed this guide step by step:

also checkout out the documentation on sensorless homing, but it never triggers. I have connected the TMC2209 to skr 1.4 board like shown here:

But still no luck when running:

M574 X1 S3 ; configure endstop for stall detection
M915 P0 S-127 H10 R1 ; Set very sensitive stall detect
G1 X200 H1 ; Should stall pretty much immediately

Is there something I am missing here? It’s not a faulty driver since i’ve 3 seperate TMC2209’s

Hi,
I’ve installed SBC version on Raspberry Pi 3B+ and I’ve other services on RPi that http port 80 is busy.
May I know how to change Duet Web Server port on Raspberry Pi Duet Web Server config files?

Thank you

So i followd your new instruction on BLTouch. But its not trigering. Also when i unplug the probe pins its triggered.

Heres my config

; Configuration file for SKR v1.4 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.3-LPC on Sat Jul 11 2020 16:57:13 GMT+0200 (Midden-Europese zomertijd)

; General preferences
G90 ; send absolute coordinates…
M83 ; …but relative extruder moves
M550 P»Artillery genius» ; set printer name

; Network
M552 S1
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 T0.1:0.1:0.02:0.02 ; physical drive 0 goes backwards using TMC220x driver timings
M569 P1 S0 T0.1:0.1:0.02:0.02 ; physical drive 1 goes backwards using TMC220x driver timings
M569 P2 S1 T0.1:0.1:0.02:0.02 ; physical drive 2 goes forwards using TMC220x driver timings
M569 P3 S0 T0.1:0.1:0.02:0.02 ; physical drive 3 goes backwards using TMC220x driver timings
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.12 Y80.12 Z399.78 E445.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z1200 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X225 Y225 Z250 S0 ; set axis maxima

; Endstops
M574 X1 S1 P»!xstop» ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P»!ystop» ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure probe port for BLtouch output

; Z-Probe
M558 P9 H6 F120 T8000 X0 Y0 Z1 C»^probe» ; disable Z probe but set dive height, probe speed and travel speed ; set Z probe type to bltouch, set dive height, probe speed + travel speed
M950 S0 C»servo0″ ; create servo pin 0 for BLTouch
G31 P500 X-31 Y80 Z3.25 ; set Z probe trigger value, offset and trigger height (smaller number means nozzle further from bed)
M557 X35:275 Y35:300 S40 ; define mesh grid

; Heaters
M308 S0 P»bedtemp» Y»thermistor» T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C»bed» T0 ; create bed heater output on bed and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P»e0temp» Y»thermistor» T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C»e0heat» T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

; Fans
M950 F0 C»fan0″ Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C»he1″ Q500 ; create fan 1 on pin he1 and set its frequency
M106 P1 H1 T50 ; set fan 1 value. Thermostatic control is turned on at 50 deg C

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Miscellaneous
M575 P1 S2 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
T0 ; select first tool

i have SKR PRO with SBCC PI 3B+

issues

1-SKR PRO Print stop for no reason and marked as finished 100% its like the PI crash because i cant change anything in the DWC , i cant load any prints or reprint and i have to reboot both the SKR Pro and the PI
2-when i do the auto calibration g32 when its done it says response too long but it give value as if it passes
3-G29 i get a red error saying errors then it says successful my M558 is M558 P8 H2 F1000 T12000 R0.2 S0.03 A5 C»servo0″

my system is

Board: biquskrpro_1.1 (STMSBC)
DSF Version: 3.2.0-beta4
Firmware: RepRapFirmware for STM32F4 based Boards 3.2-beta4.1_1 (2020-12-03)

printer is Anyquibic Predator Delta

my m122

m122
=== Diagnostics ===
RepRapFirmware for STM32F4 based Boards version 3.2-beta4.1_1 running on STM32F4 (SBC mode)
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 26240
Dynamic ram: 77236 of which 76 recycled
Never used RAM 26492, free system stack 135 words
Tasks: Linux(blocked,115) HEAT(blocked,298) MAIN(running,653) IDLE(ready,20)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:07 ago, cause: [power on/off]
Last software reset time unknown, reason: User, none spinning, available RAM 28024, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0xffffffff Task Linu
Error status: 0x00
MCU temperature: min 36.0, current 37.8, max 38.1
Driver 0: position 124255, standstill, SG min/max 0/6, error r/w 0/0, ifcnt 14, cnt r/w 5814/14, timeout 0, failedOp 0xff
Driver 1: position 197892, standstill, SG min/max 0/8, error r/w 0/0, ifcnt 13, cnt r/w 5815/13, timeout 0, failedOp 0xff
Driver 2: position 124201, standstill, SG min/max 0/8, error r/w 0/0, ifcnt 13, cnt r/w 5814/13, timeout 0, failedOp 0xff
Driver 3: position 0, standstill, SG min/max 0/0, error r/w 0/0, ifcnt 11, cnt r/w 5816/11, timeout 0, failedOp 0xff
Driver 4: position 0
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Date/time: 2020-12-15 02:13:22
Slowest loop: 95.75ms; fastest: 0.05ms
=== Move ===
FreeDm 100 (min 97), maxWait 29600ms, bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves 4, completed moves 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0, chamberHeaters = -1
Heater 1 is on, I-accum = 0.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.
=== Filament sensors ===
Extruder 0 sensor: ok
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 3ms ago
RX/TX seq numbers: 2149/2149
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x07178
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0-beta4
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.61

If i hook up my pie to BIGTREETECH PITFT50 screen
is there a chans to have this screen to show like a original reprap screen?

Or is it nott supported?

Best regards Jan Noord/Sweden

Hi, I am using the latest firmware release (3.1.1-14) on my SKR 1.4 Turbo with DuetWebControl Version 3.1.1.
I flashed an ESP8266 with the latest release of Duet WiFi Socket Server for LPC1768 version of RRF, and wired it up on a breadboard according to the wiki.

When I connect to the printer through Pronterface and send M552 S0, the LED on my esp flashes once and I get

SENDING:M552 S0
WiFi module started
Error retrieving WiFi status message: bad reply format version
[ERROR] Error retrieving WiFi status message: bad reply format version

Error retrieving WiFi status message: bad reply format version
[ERROR] Error retrieving WiFi status message: bad reply format version

When i then try to send M587 S"SSID" P"password" (with my actual SSID and password), the LED on the esp stays off and I get

SENDING:M587 S"SSID" P"password"
Error: M587: Failed to add SSID to remembered list
[ERROR] Error: M587: Failed to add SSID to remembered list

Then, when I send M552 S1, the LED on the esp flashes once and I get

SENDING:M552 S1
Failed to change WiFi mode (code -10)

After turning the printer off and on again, when I send M552 S0, the LED on the esp flashes once and I get

SENDING:M552 S0
WiFi module started
Error: Failed to initialise WiFi module, code -10
[ERROR] Error: Failed to initialise WiFi module, code -10

I use the SKR 1.3 with the WIFI module from tindie

I noticed that when my computer, on which the WebFrontend is open, goes into standby, my filament runout trigger is executed.

;0:/sys/config.g
; Filament sensor Extruder 0
M950 J1 C»xstopmax» ; filament monitor connected to xstopmax

;0:/sys/start.g
M581 P1 S1 T2

New install , no matter how many times I press the move closer button nothing happens. Took it down 3.0 mm and it never moved

Board: biquskr_1.3 (LPCWiFi)
Firmware: RepRapFirmware for LPC176x based Boards 3.1.1-14 (2020-17-7b14)
Duet WiFi Server Version: 1.23-01L-D

I am running an SKR 1.3 board with sbc and a max3155 chip for the hotend.
The temperature is very stable if I heat the hotend and manually move the printer axis. Turning on the heatbed does not impact on the readings.
Once I start a print almost every second temperature reading is 2000c. Sometimes the print will fail due to disconnect being registered.
Any advice please?

board.txt
leds.diagnostic = NoPin;

//Internal SDCard SPI Frequency.
lpc.internalSDCard.spiFrequencyHz = 25000000;

heat.tempSensePins = {bedtemp}; //Max of 3 entries
//Soft SPI Temp sensor to use with MAX31865+PT100
softwareSPI.pins = {1.18,1.19,1.20}
heat.spiTempSensorCSPins = {1.21, NoPin }; //Max of 2 entries
heat.spiTempSensorChannel = 2

//Analogue to Digital prefilter
adc.prefilter.enable = true
sbc.lpcTfrReadyPin = 1.31

//TMC Smart Drivers
stepper.numSmartDrivers = 4; //Adjust to the correct number of smart drivers
stepper.TmcDiagPins = { NoPin, NoPin, NoPin, NoPin, NoPin }

config.g
M308 S1 P»P1.21″ Y»thermocouple-max31855″

Hi, i use the same Setup on a Duet Wifi with DueX5 and also on a Duet Maestro. All of the Printers are equipped with 2 Motors for Z and therefore i make use of the Leveling of the X-Axis Gantry before levelling the Bed.

Now my 3rd Printer is equipped with SKR v1.4 Turbo, 5 TMC 2209 Drivers and a Pi 4 as the SBC.

Everything seems to be working beneath 4 Facts:

1st: If in the Configuration

M584 X0 Y1 Z2:4 E3                              ; set drive mapping
M350 X16 Y16 Z16 E16 I1                         ; configure microstepping with interpolation

The Axis behaves normally incl. the Z — Axis

In the original Firmware i configure normally:

M584 X0 Y1 Z2:4 E3                              ; set drive mapping
M350 X16 Y16 Z16:16 E16 I1                         ; configure microstepping with interpolation

This leads to an error-Message if i use it in the LPC-Port cause then Driver 4 will run with «0 Steps»…

2nd: Normally i need to configure the Motor-Amps via M906 for both Z-Motors:

Like here:

M906 X900 Y1000 Z850:850 E1000 I30

But if i do this in the LPC-Port, the Z-Drives will only going down, never up. I have got headache from this

M906 X900 Y1000 Z1000 E1000 I30

3rd: My Bed-Leveling do noting. No Chance that the Gantry will be leveled.

I use this for G32:

M561 ; clear any bed transform
G29 S2
; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
	G28 ; home

; Probe the bed and do auto calibration
G1 X5 Y155 F6000        ; go to just above the first probe point
while true
	if iterations = 15 ;max 15 Testdurchläufe
		abort "Zu viele Auto-Kalibrierungs Versuche"
	G30 P0 X47 Y155 Z-99999 ; Spindel Z-1
	if result != 0
		continue
	G30 P1 X275 Y155 Z-99999 S2 ; Spindel Z-2
	if result != 0
		continue
	if move.calibration.initial.deviation <= 0.003 ;max abweichung Je nach Z-Probe anpassen!
		break
	else
		echo "wiederhole Kalibrierung da Abweichung zu hoch (" ^ move.calibration.initial.deviation ^ "mm)"
echo "Auto kalibrierung erfolgreich, Abweichung von: ", move.calibration.initial.deviation ^ "mm"
echo "Happy Printing"
;end loop
G29  ; probe the bed and enable compensation

But the outcome is frustrating:

  | M98 P"0:/macros/Level-Z"Error: Some computed corrections exceed configured limit of 0.50mm: 0.208 -0.792 Error: Some computed corrections exceed configured limit of 0.50mm: 0.210 -0.789 Error: Some computed corrections exceed configured limit of 0.50mm: 0.205 -0.789 Error: Some computed corrections exceed configured limit of 0.50mm: 0.207 -0.790 Error: Some computed corrections exceed configured limit of 0.50mm: 0.212 -0.789 Error: Some computed corrections exceed configured limit of 0.50mm: 0.209 -0.790 Error: Some computed corrections exceed configured limit of 0.50mm: 0.208 -0.792 Error: Some computed corrections exceed configured limit of 0.50mm: 0.213 -0.794 Error: Some computed corrections exceed configured limit of 0.50mm: 0.210 -0.795 Error: Some computed corrections exceed configured limit of 0.50mm: 0.209 -0.792 Error: Some computed corrections exceed configured limit of 0.50mm: 0.208 -0.795 Error: Some computed corrections exceed configured limit of 0.50mm: 0.206 -0.791 Error: Some computed corrections exceed configured limit of 0.50mm: 0.209 -0.792 Error: Some computed corrections exceed configured limit of 0.50mm: 0.208 -0.792 Error: Some computed corrections exceed configured limit of 0.50mm: 0.208 -0.792 Zu viele Auto-Kalibrierungs Versuche
-- | --

Even this one will missed completely between the different tries:

echo "wiederhole Kalibrierung da Abweichung zu hoch (" ^ move.calibration.initial.deviation ^ "mm)"

Any Ideas?

Regards
MoS-tekknix

I found a example bed.g in the Wiki to calibrate the bed.
If i run a G32 command i get the following output

G32
Leadscrew adjustments made: 0.120 0.119, points used 2, (mean, deviation) before (0.119, 0.000) after (0.000, 0.000)
Error: in file macro line 19 column 6: meta command: unknown value ‘calibrationDeviation’

My bed.g

M561                    ; clear any bed transform
; If the printer hasn't been homed, home it
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
  G28
while true
  if iterations = 5
    abort "Too many auto calibration attempts"
  G30 P0 X20 Y117.5 Z-99999 ; probe near a leadscrew, half way along Y axis
  if result != 0
    continue
  G30 P1 X215 Y117.5 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
  if result != 0
    continue
  if move.calibrationDeviation.deviation <= 0.02
    break
  echo "Repeating calibration because deviation is too high (" ^ move.calibrationDeviation.deviation ^ "mm)"
echo "Auto calibration successful, deviation", move.calibrationDeviation.deviation ^ "mm"
G29  ; probe the bed and enable compensation

SKR 1.3 How do you configure BLTouch in LPCConfigurator?

Z Probe pin assignment Input pin selection is there z stop

What are the correct selections for the Modulation Pin and PWM Pin?

Hi,
I’ve set up my Anycubic i3 with Dual Z and Dual endstops, configured by the book
config.g sections:

; Drives
M569 P0 S1 D3 V40                                             ; X physical drive 0 goes forwards using default driver timings
M569 P1 S0 D3 V40                                            ; Y physical drive 1 goes backwards using default driver timings
M569 P2 S0                                             ; Z1 physical drive 2 goes backwards using default driver timings
M569 P3 S1                                             ; E physical drive 3 goes forwards using default driver timings
M569 P4 S0                                             ; Z2 physical drive 4 goes backwards using default driver timings
M584 X0 Y1 Z2:4 E3                                       ; set drive mapping

M574 Z1 S1 P"!zstop+!pwrdet" 							   ; configure active-low endstops for low end on Z via pins zstop and e1stop

However what I try, while homing Z only one motor is driven while the other one is energized and locked.
In essence I switch to relative position in homez.g and
G1 H1 Z-210 F1800 ; move Z down until the endstop is triggered

If I just move the axis, everything is nice and dandy.
I don’t understand it. Endstops are reported fine and they are assigned to the correct motors.

Bords is a SKR 1.4 running 3.1.1-14

Sorry for bothring but is there any know issue with the SKR1.4 and a configured BL-Touch connection on the I/O mapping page of the RRF Config Tool (LPC-Port)?

When i configure any Pins for the BL-Touch there i get an error on the last Page saying that there are errors on the I/O-mapping page. When i leave the BLtouch unconnected anything is fine i can get the config tool to spit out the disired files.

Best regards
René

Hi
I am using an SKR 1.3 via SBC connection to a RPI 3A+
It was working fine and I was doing an update.
I ran the update as per the wiki:
wget https://raw.githubusercontent.com/P-C-R/LPC-DSF-Install_Script/master/LPC_DSF_update.sh
sudo chmod 755 LPC_DSF_update.sh
./LPC_DSF_update.sh

after the update to 3.2.0-beta+1 The browser just displays connection refused.
I then re-flashed the sd card with duetpi and tried every one of the stable/unstable wiki instructions with no luck.
Am I missing something here?

Sometimes i get this error message:

G30 P0 X20 Y117.5 Z-9999 ; probe near a leadscrew, half way along Y axis
G30 P1 X215 Y117.5 Z-9999 S2 ; probe near a leadscrew and calibrate 2 motors

Error: Some computed corrections exceed configured limit of 1.00mm: -0.737 -1.543

I’m running the SKR 1.4 Turbo in SBC mode with a raspberry pi 3b+. Running the simulation mode takes 2-3 times longer than the duet wifi im using with the same gcode. The results reported in the console are off and the gcode file isn’t updated with the simulation time and is not displayed in the web interface.
That’s all I’ve noticed so far and have been printing great! Thanks for this cool project!
Steven Smith

Hi. I have an SKR 1.4 configured with the great Reprap firmware.
Similarly to my Duet wifi I configured a dual Z axis to have independent Z axis compensation with a BLtouch.
I have assigned it the following way: M584 X0 Y1 Z2:4 U4 E3
My problem is that it is showing up in the Duet web control as a separate U drive and so due to the reason it is not homing it always drops an error that it is not homed and a G29 mesh bed leveling cannot be initialised.
Am I doing something wrong?

Thank you for your support in advance.

To support the number of different boards, a /sys/board.txt config file on the SDCard is used to configure the hardware pin assignments. Some example board config files can be found here

The example board config files are redirected to the «old» repo

Best

So this is my current list of the things I’m planning on working on (in a very rough priority order)…

1. Create single code base for STM/LPC versions and associated build system.
2. Track DC42 3.4 beta and beyond.
3. Add support for various expansion boards (GTR M5 and BTT expansion board)
   3a. Review/Change limits of various items in particular number of Fans
   3b. Find a better way to handle a variable number of drivers in the source to allow easier builds with different memory footprints
   3c Sort out MaxProbePoints and MaxCalibration points on LPC version (need to be the same to avoid firmware reset)
4. Add option to control initial state of PS_ON(complete V3.2-beta3.2).
5. Investigate why some/all SanDisk SD cards do not seem to work (complete V3.2-beta2
6. Enable support for NeoPixels
7. Add 5160 support.
8. SDIO support for SD cards.
9. Improved pin configuration (avoid need to list all pins in the various board.h files).
10. Use CRC32 hardware.
11. Update TMC22xx driver to match Duet3D version
12. Reduce LPC malloc overhead.
13. Provide defaults for WiFi/Linux interface and other settings. Identify board via signature.
    13a. Identify board via signature.
14. Shift Core to new Duet3D model.
15. Investigate firmware reset when issuing M552 S1 followed by M997 S1 when no firmware is present in the ESP8266 module.
16. Investigate why size reporting of SDIO drives is broken.
17. Investigate support for LCD displays (12864 based) for the STM32 port (not enough RAM for LPC).
18. Investigate possible problem with UART connections which gives «Bad response» messages when using a PanelDue.
19. Fix STM default DiagPin.
20. Allow use of Mixed case names in board definitions (force match to ignore case).
21. Investigate WiFi performance
22. Investigate adding support for object tracking.
23. Add support for Bigtreeetech SKR V2.0 (driver rotation detection and power on sequence).
24. Expand number of extruders per tool
25. Investigate adding support for object tracking to LPC build
26. Add support for RGBW NeoPixels
27. Test accelerometer support
28. Investigate integrating «power detect pins» with the 12/24V power monitoring
29. Allow selection of SPI channel for WiFi/SBC interface
30. Allow use of alternate pins for hardware PWM
31. Allow reading of any TMC register
32. Allow use of SPI3 for SD card access — investigate possible DMA access issues
33. Check setting of LPC peripheral clock. Consider increasing LPC PWM resolution
34. LPC: Consider allowing hardware PWM outputs for other than servos.
35. STM: Investigate SDIO errors when daemon.g is running
36. STM: Investigate loss of USB in later versions on SKR Pro (unable to reproduce)
37. STM: Investigate why TMC5160 in slot 2 of a CDYv2 board gets hot with 5 or more 5160s installed (unable to reproduce)
38. STM: Increase number of supported probes
39. STM: Improve TMC5160 detection
40. Investigate enabling I2C support
41. Investigate increasing number of axis
42. Investigate setting a fixed IP address for esp32 clients and restore functionality for esp8266 version
43. Clamp Vin reading when near zero to stop DWC flicker
44. H7 Enable 16bit ADC samples (currently 12 bit with oversampling to 14)
45. H7 Use processor d-ram for stacks etc.
46. H7 Consider using FIFOs for UARTS
47. H7 Investigate SD Card SPI mode high speed switching
48. H7 Test SBC Mode
49. H7 Build IAP for SBC mode
50. Allow use of shared timers per pin (find best match)
51. H7 Update hardware usage for H7
52. H7 Allow DMA with SPI1, SPI5, SPI6
53. Allow use of embeded config
54. Allow forcing pins to 0V/3.3V output on boot
55. Investigate BTT SKR 3 EZ operation with TMC220x stepsticks
56. Investigate Why a board in CAN expansion mode does not get restarted when main board is reset.
57. Investigate errors when setting access point parameters (esp32)
58. Fix MAC address not be returned in status message
59. Investigate using 3 timer/dma operation for neopixels(see https://sites.google.com/site/hubmartin/arm/improved-stm32-ws2812b-library and https://github.com/hubmartin/WS2812B_STM32F4/blob/master/Src/ws2812b/ws2812b.c)

Items 1 and 2 are my main focus at the moment. 3.3 is currently available and 3.4 in test.

I tend to work on things that interest me and that are easy for me to set up (so if I don’t have the hardware and it is not interesting/cheap I’m unlikely to work on it). I am also in the middle of setting up a new printer and have plenty of of other things to do!

Please do not post questions or requests for help or bug reports on this issue. Please use the discord server to ask questions or report possible problems. Thanks!

Hi,

I’m running 3.1.1-14 on an SKR 1.3 in SBC mode and am having issues the bed heater faulting out every time I try to heat it.

I’ve ran autotune starting from room temp numerous times, and I’ve even tried manually increasing the dead time but I’m still getting ‘heater fault, temperature rising more slowly than the expected 1.6deg/s’ on the bed heater.

Given that it heats up fine when auto-tuning but faults under normal operation I wanted to raise the issue in case it was a firmware problem?

I’ve manually checked the resistance of the bed and all looks within spec.