RepRapFirmware 3.0 port for LPC1768/9 based boards

Well you've definitely got a functioning connection between the pi and the SKR.

Have you uploaded the config.g file etc through the web interface?
The only files that should be on SKR sd card is the board.txt file in sys. I use a 128mb on mine so I'm not wasting a card.
All the other files are held on the pi and loaded on to the SKR on boot up.

---

Based in Darlington, North East

No I missed that. I had it configured like standalone - I worked on it for a while to be sure it's ok.

Thank you! It reads endstops and homes!

Glad its all sorted.

Just be warned that there currently seems to be an issue with RC10 + SBC setup.
See here [forum.duet3d.com]
I have been getting this with my duet 3 and SBC setup so just be warned that the system may become unresponsive until the whole setup is rebooted.

---

Based in Darlington, North East

@jay_s Thank you, I might have blamed board.txt files for this, I will redo the tests.

@rudenick So what problems do you have?

I don't think you should need anything other than the following in your board.txt file:

lpc.board = biquskr_1.4
8266wifi.lpcTfrReadyPin = 1.30
8266wifi.espResetPin = 1.31
sbc.lpcTfrReadyPin = 0.28
adc.prefilter.enable =true

Have you created a config.g file (and placed it in the sys directory on the rPi)? Please post the contents of that file.

EDIT: Ah looks like Jay beat me to it!

Edited 1 time(s). Last edit at 04/27/2020 12:45PM by gloomyandy.

Quote
cd_edwards
Just started fooling around with a MKS Sbase board and RRF. I found that the M552 P192.168.1.18 S1 which I have in my config.g is ignored and I need to send this with a USB serial connection in order to have networking work. This is with gloomyandy's RC9 RRF version and DWC 2.1.3. FYI connection is a wired connection not wifi. Once I send the appropriate M552 command, everything works.

I have the same board.

How fast to connect to it via DWC ?

For me it takes 14minutes for the script to load in my browser (tried Chrome, Firefox). Then it works fine. I can power off the printer and when On it reconnects directly. Details in the version 2 thread. Same issue with 3.

---

"A comical prototype doesn't mean a dumb idea is possible" (Thunderf00t)

@gloomyandy board.txt from wiki you recommended finally worked during random reboot. It did not work on few reboots and pi overheated.

When it succeeded I got following initial errors and warnings:

4/28/2020, 9:59:39 AM 	Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
4/28/2020, 9:59:39 AM 	Error: M552: Networking is not supported on this hardware
4/28/2020, 9:59:39 AM 	Warning: M918: Command is not supported
4/28/2020, 9:59:38 AM 	Error: M550: Machine name must consist of the same letters and digits as configured by the Linux hostname

Test print did not stop but revealed following errors:

4/28/2020, 9:54:15 AM 	Error: M141: No chamber heater has been configured for slot 0
4/28/2020, 9:51:19 AM 	T:24.4 /200.0 T0:24.4 /200.0
4/28/2020, 9:51:19 AM 	T:24.4 /0.0 T0:24.4 /0.0
4/28/2020, 9:51:19 AM 	Error: M140: No bed heater has been configured for slot 0

(hotend keeps stable 200C and bed does not work)

Is this all related to config.g?

Edited 3 time(s). Last edit at 04/28/2020 04:23AM by rudenick.

@MKSA

Sorry I haven't be able to do any more work on this.
My Sbase has given up on acquiring an IP address or working with a static one.
My other Sbase locks up as soon as I try to use the ethernet connection.

I've moved to using a wireless connection with the board and it's a lot quicker.
I will be adding instructions on how to do so once @gloomyandy has added some extra settings to the config.

To warn you now though, a hardware modification of the board is required to be able to do so and it prevents the use of the xmin endstop.
Having said that, its a relatively simple modification so shouldn't be too difficult for anyone with a soldering iron.

---

Based in Darlington, North East

@rudenick

There is an issue with DSF 2.1.1 where the pi becomes unresponsive and locks up which is what I think you're seeing.
For me, commenting out

CPUSchedulingPolicy=fifo
CPUSchedulingPriority=20

with a # or a ; worked for me.
They are in duetcontrolserver.service and can be found in either /usr/lib/systemd/system or /lib/systemd/system

The warning about overpowered heaters is normal and something I get on my original duet 3 system.

M918 is around the connection of an LCD which i'm not sure about. @gloomyandy can tell you better but I don't think theres enough memory to run it the conventional way.
M552 isn't supported with an SBC as the SBC sorts out the network connection, not the main board.
M550 shouldn't be used and the host name should be modified on the pi. See [duet3d.dozuki.com]

An M143 H0 is needed for the bed to function. See here [github.com]

---

Based in Darlington, North East

@rudenick I think jay has covered pretty much everything. As far as I can see all of those warnings/errors are either normal (heater overpowered) or related to config.g settings. As jay mentioned there is not sufficient RAM available on the LPC boards to allow networking (ethernet, WiFi or SBC) and the display support at the same time (at least that was the case the last time I checked and I doubt if memory usage has gone down).

@MKSA I retested the SBase ethernet stuff the other day, and on the router I was testing against it was not able to obtain an IP address using DHCP but did work happily enough if you assign a static address (no idea why that was, DHCP worked fine on my home router). The load time for DWC was nowhere near as fast as when using WiFi but was nothing like 14 minutes. Perhaps what you are seeing is related to the the issues that are causing DHCP to fail for me (some sort of timeout perhaps). Unfortunately due to the current lockdown situation I don't really have the equipment to investigate this sort of problem much further at the moment.

Quote
gloomyandy
@rudenick I think jay has covered pretty much everything. As far as I can see all of those warnings/errors are either normal (heater overpowered) or related to config.g settings. As jay mentioned there is not sufficient RAM available on the LPC boards to allow networking (ethernet, WiFi or SBC) and the display support at the same time (at least that was the case the last time I checked and I doubt if memory usage has gone down).

@MKSA I retested the SBase ethernet stuff the other day, and on the router I was testing against it was not able to obtain an IP address using DHCP but did work happily enough if you assign a static address (no idea why that was, DHCP worked fine on my home router). The load time for DWC was nowhere near as fast as when using WiFi but was nothing like 14 minutes. Perhaps what you are seeing is related to the the issues that are causing DHCP to fail for me (some sort of timeout perhaps). Unfortunately due to the current lockdown situation I don't really have the equipment to investigate this sort of problem much further at the moment.

I use fixed IP. In fact I tried fixed IP, DHCP, direct PC connection with a cross cable, via the router, different PCs, different microSD card ... The script downloads at the same speed as a 19.2kb modem !
Once done, I can transfer gcode files at megabit/s speed !!!
I prefer DWC to Repetier or Pronterface ! I can even upload direclty via Slic3r although this sometimes blocks ???

---

"A comical prototype doesn't mean a dumb idea is possible" (Thunderf00t)

Thank you! your tips helped! Printer is working, I get ugly prints Now I got to solve minor more duet oriented errors and tweaks

For those waiting for the non-paneldue UART mode in RRF3 to use TFT32, ESP3D, etc etc, these should hopefully be working again as of 3.01-RC11 as DC42 has just implemented UART "raw" mode. I've just done some testing with 3.01RC11 on the LPC port and is working well for me. This replaces the need for the old "lpc.uartPanelDueMode" board.txt setting that was used in LPC-RRF2.

To use raw mode, this can be configured with M575, i.e. M575 P1 B115200 S2.

Quote
sdavi
For those waiting for the non-paneldue UART mode in RRF3 to use TFT32, ESP3D, etc etc, these should hopefully be working again as of 3.01-RC11 as DC42 has just implemented UART "raw" mode. I've just done some testing with 3.01RC11 on the LPC port and is working well for me. This replaces the need for the old "lpc.uartPanelDueMode" board.txt setting that was used in LPC-RRF2.

To use raw mode, this can be configured with M575, i.e. M575 P1 B115200 S2.

On the Duet 2 series there is a bug in this new feature, which is that if you want to change the baud fate from the default of 57600 then you have to give the M575 command twice. I don't know whether this affects the LPC build or not. It will be fixed in the 3.01 stable release.

Edited 1 time(s). Last edit at 05/01/2020 09:54AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

RC11 is now available: [github.com]

Tagged repos here:
[github.com]
[github.com]
[github.com]
[github.com]

Is it possible to port the server from ESP8266 to ESP32? In my opinion, ESP32 is much more stable and faster.

I'm sure it is possible, but the question is... is anyone willing to do the work and what is the gain in doing that work.

I doubt if using an ESP32 with an LPC based board will be any faster as the limiting factor is the SPI transfer speed between the LPC and ESP8266 and the lack of available memory (for buffer space) on the LPC. In terms of stability I've never seen any ESP8266 related issues, the only problems I've seen are due to only having a limited number of sockets available and this is limited by the available memory on the LPC side of things not the ESP8266.

In terms of doing the port I think there will be fair bit of work involved as the last time I looked the toolkits for the ESP32 and ESP8266 are different (this is particularly true of the toolkit currently used by the current ESP8266 code). One of the things I have on my list to look at is to port the WiFi code to the more recent version of the toolkit, this would probably make a switch to ESP32 a little easier, but the above comments about performance would still be true.

Are you running a setup using the RRF/LPC with an ESP8266? What problems have you seen?

Just installed RC11 (from RC9) and my Heated bed is missing...
The temp chart shows its temperature, but no option to power the heater...
It was running correctly on RC9, nothing changed but the firmware version and Framework.
I had it configured as:

M308 S0 P"TB" Y"thermistor" T100000 B3950 A"HotBed" F1 R4700 C0 ; configure sensor 0 as thermistor on pin TB
M950 H0 C"H-BED" T0                         ; create bed heater output on HBED and map it to sensor 0
M143 H0 S120                               ; set temperature limit for heater 0 to 120C
; disable bang-bang mode for the bed heater and set PID 
M307 H0 A145.6 C616.9 D2.3 S1.0 V0.0 B0 ;

tried to modify as:

M308 S0 P"TB" Y"thermistor" T100000 B3950 A"HotBed" F1 R4700 C0 ; configure sensor 0 as thermistor on pin TB
M950 H0 C"P2.5" T0                         ; create bed heater output on HBED and map it to sensor 0
M143 H0 S120                               ; set temperature limit for heater 0 to 120C
; disable bang-bang mode for the bed heater and set PID 
M307 H0 A145.6 C616.9 D2.3 S1.0 V0.0 B0 ;

with no luck.

Any idea would be appreciated

Chema.

M140 H0 should get it working

I've been looking through the threads here and I've not been able to find out if the paneldue is supported or not with the LPC port. My board is a MKS sbase 1.3.

Many thanks! it works now!

This kind of thing is the only cons I have with RRF, I like it, but many features need to make lots of workarounds to had them working. Documentation is huge but little things like this one I couldn't find explanation...

About the panel due, don't know, but I'm using a BigTreeTech TFT 3.5v2 connected in the RS232 on the SKR1.3, so as the Panel due is serial too, I think it would work...

Once again, many thanks for your trick.

Chema

@cd_edwards I've just tested my PanelDue with an SKR V1.4 board (with the WiFi build) and it seemed to work fine with that, can't be sure about the SBase, but I would have thought it should be OK. Note however that you will probably need to add an extra line to your config.g file for RC11 see:
[github.com]
I'm also not sure if there is firmware update for the PanelDue or not (I've only tested the basics just now).

There was a version 1.24 update to PanelDue firmware recently, but it's only needed for systems using an attached SBC. It surprised me that quite a few users with Duet 3 + SBC want to connect a PanelDue too.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hello,

i want to test this on a SKR 1.3 in a CoreXY! Is Dual Z Possible? The LPC Configurator does not have the Option?


Best

@PCR

Yes, perfectly possible.
You can assign e.g. Z and E1 to operate as Z.
The drivers would be numbered 0 to 4 so you would have

M584 X0 Y1 Z2:4 E3

---

Based in Darlington, North East

Thank you! This could be fixed in the Config Tool too

I use dual Z on my printer. I'm not sure that the "standard" RRF config tool has support for it (I seem to remember not finding it when I looked for it). So if anyone has plans to fix it, you might want to get it fixed in the main tool first.

Easy! looking forward to the project! Already made a little PCB Design for connecting the EXP1 and EXP2 easliy to the 8266! If everthing works i will upload the files!
Is there any discord server, irc server, facbook group etc for it?

Best Peter

RC12 is now available: [github.com]

In addition to the usual updates to track RRF this release also includes the capability to update the LPC firmware using DWC when uaing RRF in SBC mode.

Tagged repos here:
[github.com]
[github.com]
[github.com]
[github.com]

Quick question. Why is there a 2.2k Resistor between GND and Reset when i am connecting a skr via 8266?