RepRapFirmware 3.0 port for LPC1768/9 based boards

We now have a discord channel if anyone is interested.
[discord.gg]

---

Based in Darlington, North East

Version 3.1.1 now available: [github.com]

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

Wifi server repos here:
[github.com]
[github.com]

When using "firmware-wifi.bin" versions 3.01 RС11 and older, the printer strates for 15 seconds. Starting from version 3.01 RС12 and newer, the printer for two minutes in a cyclic reboot and then normally starts and everything works. What could be the problem?

Sorry, I don't understand what you are asking.

Are you saying that on pre RC11 versions it starts and is ready within 15 seconds but on newer versions it takes 2 minutes to start up?
What hardware? Are you running the newest release of the ESP code?

---

Based in Darlington, North East

All right
Newest Versions
SKR 1.3, ESP8266, tmс2209
During these 2 minutes, the hot-end fan starts and stops constantly. It is connected to HE1. Also, if you connect to the computer, the device "serial" then appears then disappears. Then everything starts and works fine

Could you provide the output from M122 please once its started up?
Also could you provide your board.txt and config.g
Thanks

---

Based in Darlington, North East

https://youtu.be/W25N7L_A1dY

M122
=== Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.1.1 running on LPC176x at 100Mhz
Used output buffers: 3 of 16 (10 max)
=== RTOS ===
Static ram: 3876
Dynamic Memory (RTOS Heap 5): 2648 free, 2624 never used
Exception stack ram used: 352
Never used ram: 332
Tasks: NETWORK(ready,632) HEAT(blocked,1360) MAIN(running,1460) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:49 ago, cause: [software]
LPC Flash Slot[22]: 
Last software reset time unknown, reason: Watchdog timeout, spinning module GCodes, available RAM 460 bytes (slot 0)
Software reset code 0x00a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04415810 BFAR 0xe000ed38 SP 0x2007d6a4 Task MAIN
Stack: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 
Error status: 0
Driver 0: standstill, read errors 0, write errors 1, ifcount 67, reads 658, timeouts 0
Driver 1: standstill, read errors 0, write errors 1, ifcount 67, reads 658, timeouts 0
Driver 2: standstill, read errors 0, write errors 1, ifcount 47, reads 658, timeouts 0
Driver 3: standstill, read errors 0, write errors 1, ifcount 47, reads 658, timeouts 0
Driver 4: standstill, read errors 0, write errors 1, ifcount 47, reads 658, timeouts 0
Date/time: 2020-05-22 11:46:35
Slowest loop: 7.98ms; fastest: 0.32ms
=== Storage ===
Free file entries: 4
SD card 0 detected
SD card longest read time 3.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0, FreeDm: 100, MinFreeDm: 100, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 220.37ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0)
HTTP sessions: 1 of 2
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23-01L-D
WiFi MAC address 90:94:e4:3d:93:2e
WiFi Vcc 64.00, reset reason Unknown
WiFi flash size 4194304, free heap 37728
WiFi IP address 192.168.0.152
WiFi signal strength -70dBm, reconnections 0, sleep mode modem
Socket states: 0 0

board.txt

lpc.board = biquskr_1.3; 

//                    Bed   E0    E1
heat.tempSensePins = {0.23, 0.24}; //tb, th0, th1
stepper.numSmartDrivers = 5
leds.diagnostic = NoPin; 

//wifi pins
8266wifi.espDataReadyPin = 0.28
8266wifi.lpcTfrReadyPin = 1.30
8266wifi.espResetPin = 1.31
adc.prefilter.enable = true

config.g

G90                                        ; send absolute coordinates...
M83                                        ; ...but relative extruder moves
M550 P"HyperCube"                          ; set printer name

M669 K1 								   ; switch to CoreXY mode

; Network

M552 S1                                    ; enable network

; Drives
M569 P0 S1 T0.1:0.1:0.02:0.02        ; physical drive 0 goes forwards using TMC220x driver timings
M569 P1 S1 T0.1:0.1:0.02:0.02        ; physical drive 1 goes forwards 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 S1 T0.1:0.1:0.02:0.02 D2           ; physical drive 3 goes forwards using TMC220x driver timings (spread cycle)
M569 P4 S1 T0.1:0.1:0.02:0.02        ; physical drive 3 goes forwards using TMC220x driver timings
M584 X0 Y1 Z2:4 E3                         ; set drive mapping
M92 X80.00 Y80.00 Z800.00 E398.00          ; set steps per mm
M566 X1200.00 Y1200.00 Z12.00 E600.00      ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z900.00 E3000.00  ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000.00   ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z800:800 E1000 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 X302 Y302 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 Z2 S1 P"zstopmax+xstopmax"                         ; configure active-high endstop for high end on Z via pin zstopmax

; Z-Probe
M558 P0 H5 F120 T6000                      ; disable Z probe but set dive height, probe speed and travel speed
M557 X30:272 Y30:272 S20                   ; define mesh grid

; Heaters
M308 S0 P"TB" Y"thermistor" T100000 B4138  ; configure sensor 0 as thermistor on pin TB
M950 H0 C"HBED" T0                         ; create bed heater output on HBED and map it to sensor 0
M140 H0
M143 H0 S150                               ; set temperature limit for heater 0 to 120C
M307 H0 B0 S0.70                           ; disable bang-bang mode for the nozzle heater and set PWM limit
;M308 S1 P"TH0" Y"thermistor" T100000 B4700 ; configure sensor 1 as thermistor on pin TH0
M308 S1 P"TH0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin TH0
M950 H1 C"HE0" T1                          ; create nozzle heater output on HE0 and map it to sensor 1
M143 H1 S280                               ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00                           ; disable bang-bang mode for the nozzle heater and set PWM limit

; Fans
M950 F0 C"FAN" Q500                        ; create fan 0 on pin FAN and set its frequency
M950 F1 C"HE1" Q500                        ; create fan 0 on pin HE1 and set its frequency
M106 P0 S0 H-1                             ; set fan 0 value. Thermostatic control is turned off
M106 P1 T50 H1                             ; автоматическое включение при температуре хотенда 50

; 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						
M575 P1 B57600 S0	
M703	
M501

Edited 1 time(s). Last edit at 05/22/2020 04:57AM by bcmob.

How are you powering things? That sounds like when the WiFi module powers up (and starts transmitting), it is drawing too much current and the system reboots. What happens if you remove the m552 s1 from your config.g? If your system boots like this, then try issuing the m552 from the USB console and see if that causes a reboot.

Thanks for the low voltage idea.
The ESP turned out to be nothing to do with, even its complete shutdown did not help.
Turning off the TFT screen helped. I will think how to fix the problem.
It is surprising that on older versions there is no such problem. Looks like the controller is loaded there later and the screen is already running by then. )

Moved the line "M575 P1 B57600 S0" to the beginning of the config file and started to run normally in 30 seconds.
https://youtu.be/xp1qgX_J39Y

Are you using the bigtreetech TFT?

Quote
PCR
Are you using the bigtreetech TFT?

Yes TFT24 with modified firmware github

I am running a SKR 1.3 with wifi and the latest firmware 3.1.1.

The printer has started stopping mid print, it has now happened 3 times and the error is always software reset.

This is the relevant part of the diag:

=== Platform ===
Last reset 00:01:08 ago, cause: [software]
LPC Flash Slot[86]:
Last software reset at 2020-05-23 13:33, reason: Watchdog timeout, spinning module GCodes, available RAM 180 bytes (slot 0)
Software reset code 0x08a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442a010 BFAR 0xe000ed38 SP 0x10007f6c Task MAIN
Stack: 0002ca29 0002c948 61000011 10005418 8441f32e 10004aac 0002c3c1 2007c1dc 10004aac 10000a9c 00000000
Error status: 0

Any thoughts as to what is the problem?

Thanks.

Edited 1 time(s). Last edit at 05/23/2020 10:54AM by Micktol.

This sounds like a very similar problem to one being discussed (and worked on) on the discord server. But the people there are mainly using the SBC module and SKR V1.4 Turbo. This is the first example of the problem (if it is the same) on the hardware you are using. This is a good thing because I've not been able to reproduce the problem seen by others and I have similar hardware to yours. Can you please test the following. If you simulate the gcode does the problem happen then? If not what happens if you simulate the same gcode but with the bed and nozzle heaters turned on? Basically I'm looking for a test case I can use to track down and understand what is going on.

Also have you been using the same setup without error with earlier versions of the firmware? If so can you provide details of the build you were using before?

I did not have any problems until I had to change a driver, I was using 5 tmc2100 and one just started to make the motor buzz. I am now using 3 tmc2100 and 2 drv8825. I am waiting on the tmc2209's that I have ordered.
I thought it might be overheating so I put a big fan on to cool the drivers, but it still happens randomly so it is very difficult to say exactly what conditions cause the problem.
The first time was with version 3.0.1 rc12 but it then stopped for a while. Today it happened twice! I am going to check all the connections to exclude them from the equation.

I've been trying to match up your stack trace to work out what was happening when you had the crash, did you have any sort of debug output enabled at the time? Are you using the standard build or have you built the firmware yourself?

I did not have any debug enabled and have been using your builds. I just finished a short one hour print with no problems.

I've just seen your post about changing drivers etc. Are you using a build of the firmware with the TMC22XX support disabled? If not you may be getting a lot of errors/timeouts because of that (which will not be helping things). You may be able to disable the support by setting stepper.numSmartDrivers to zero in your board.txt file, but I've never tried running like that.

In which case the M122 output does not make a lot of sense to me, can you post the full output please.

Ok I have added stepper.numSmartDrivers = 0 to board.txt. M122 does not list the driver info as before, I will try another print.



5/23/2020, 1:34:28 PM: M122: === Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.1.1 running on LPC176x at 100Mhz
Used output buffers: 3 of 16 (10 max)
=== RTOS ===
Static ram: 3876
Dynamic Memory (RTOS Heap 5): 2712 free, 2688 never used
Exception stack ram used: 352
Never used ram: 332
Tasks: NETWORK(ready,632) HEAT(blocked,1360) MAIN(running,1452) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:08 ago, cause: [software]
LPC Flash Slot[86]:
Last software reset at 2020-05-23 13:33, reason: Watchdog timeout, spinning module GCodes, available RAM 180 bytes (slot 0)
Software reset code 0x08a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442a010 BFAR 0xe000ed38 SP 0x10007f6c Task MAIN
Stack: 0002ca29 0002c948 61000011 10005418 8441f32e 10004aac 0002c3c1 2007c1dc 10004aac 10000a9c 00000000
Error status: 0
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 135
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 135
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 135
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 134
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 134
Date/time: 2020-05-23 13:34:28
Slowest loop: 6.25ms; fastest: 0.32ms
=== Storage ===
Free file entries: 4
SD card 0 detected
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 1, FreeDm: 100, MinFreeDm: 99, MaxWait: 59921ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 3, completed moves: 3, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0, chamberHeaters = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 98.47ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0)
HTTP sessions: 1 of 2
- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 5c:cf:7f:b1:1d:de
WiFi Vcc 2.89, reset reason Unknown
WiFi flash size 4194304, free heap 24792
WiFi IP address 192.168.0.15
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 4 0
5/23/2020, 1:37:05 PM: M122: === Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.1.1 running on LPC176x at 100Mhz
Used output buffers: 3 of 16 (16 max)
=== RTOS ===
Static ram: 3876
Dynamic Memory (RTOS Heap 5): 2712 free, 2688 never used
Exception stack ram used: 352
Never used ram: 332
Tasks: NETWORK(ready,632) HEAT(blocked,1360) MAIN(running,1452) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:44 ago, cause: [software]
LPC Flash Slot[86]:
Last software reset at 2020-05-23 13:33, reason: Watchdog timeout, spinning module GCodes, available RAM 180 bytes (slot 0)
Software reset code 0x08a3 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442a010 BFAR 0xe000ed38 SP 0x10007f6c Task MAIN
Stack: 0002ca29 0002c948 61000011 10005418 8441f32e 10004aac 0002c3c1 2007c1dc 10004aac 10000a9c 00000000
Error status: 4
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 310
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 309
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 309
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 310
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 310
Date/time: 2020-05-23 13:37:04
Slowest loop: 4.99ms; fastest: 0.32ms
=== Storage ===
Free file entries: 4
SD card 0 detected
SD card longest read time 1.6ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0, FreeDm: 100, MinFreeDm: 99, MaxWait: 50589ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 11, completed moves: 11, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0, chamberHeaters = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 203.79ms; fastest: 0.09ms
Responder states: HTTP(2) HTTP(0)
HTTP sessions: 1 of 2
- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address 5c:cf:7f:b1:1d:de
WiFi Vcc 2.89, reset reason Unknown
WiFi flash size 4194304, free heap 24792
WiFi IP address 192.168.0.15
WiFi signal strength -58dBm, reconnections 0, sleep mode modem
Socket states: 0 4

Edited 1 time(s). Last edit at 05/23/2020 12:57PM by Micktol.

I think that make a little more sense, unfortunately it doesn't really tell me very much about what the problem was. If you have any more crashes please do a m122 after you reboot and post them here.

@ gloomyandy. Thank you for your help. I have a print running at the moment, (update) it finished. I will keep you updated if there are any more problems.

Edited 1 time(s). Last edit at 05/23/2020 03:43PM by Micktol.

I am running the wifi version. Is then any advantage if I change to the SBC version?

Thanks.

The connection to DWC is faster for file transfers etc.
It also allows ethernet connections through the pi.
But other than that, at the moment I don't think there's any other advantages.
Conditional gcode works on both.
Once general RRF changes settle down and plugins start to get written then there will be more of a distinction between the two.

---

Based in Darlington, North East

@Micktol One other difference is that the DWC interface is slightly more stable than when using WiFi, we don't really have enough memory on the LPC and so when running WiFi from time to time the DWC interface tries to use more connections than we have available (and you get a lost connection message), that does not happen with the SBC version, as most of the web interface is running from the rPi.

When printing after 1 hour 43 minutes, printing suddenly stopped and the printer rebooted.
firmware-wifi.bin RRF3.1.1 SKR1.3 TMC2209 ESP8266 TFT24

Status immediately after reboot

M122
=== Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.1.1 running on LPC176x at 100Mhz
Used output buffers: 3 of 16 (13 max)
=== RTOS ===
Static ram: 3876
Dynamic Memory (RTOS Heap 5): 2648 free, 2624 never used
Exception stack ram used: 328
Never used ram: 356
Tasks: NETWORK(ready,632) HEAT(blocked,1360) MAIN(running,1460) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:39 ago, cause: [software]
LPC Flash Slot[13]: 
Last software reset at 2020-05-25 13:34, reason: Watchdog timeout, spinning module Move, available RAM 204 bytes (slot 0)
Software reset code 0x00a4 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442a010 BFAR 0xe000ed38 SP 0x10007f6c Task MAIN
Stack: 0002c3c1 0002ca1e 61000011 10005aa8 78659206 10004aac 0002c3c1 2007c1dc 10004aac 10000a9c 00000000 
Error status: 0
Driver 0: standstill, read errors 0, write errors 1, ifcount 22, reads 519, timeouts 0
Driver 1: standstill, read errors 0, write errors 1, ifcount 17, reads 519, timeouts 0
Driver 2: standstill, read errors 0, write errors 1, ifcount 17, reads 518, timeouts 0
Driver 3: standstill, read errors 0, write errors 1, ifcount 15, reads 518, timeouts 0
Driver 4: standstill, read errors 0, write errors 1, ifcount 17, reads 518, timeouts 0
Date/time: 2020-05-25 13:35:14
Slowest loop: 8.44ms; fastest: 0.32ms
=== Storage ===
Free file entries: 4
SD card 0 detected
SD card longest read time 3.9ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0, FreeDm: 100, MinFreeDm: 100, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 224.29ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0)
HTTP sessions: 1 of 2
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23-01L-D
WiFi MAC address 90:94:e4:3d:93:2e
WiFi Vcc 64.00, reset reason Unknown
WiFi flash size 4194304, free heap 37040
WiFi IP address 192.168.0.152
WiFi signal strength -72dBm, reconnections 0, sleep mode modem
Socket states: 0 0

Hmm interesting, I'll take a proper look at it later as I will need to regenerate a map file for that build (must change the build system to save the map files as well as the bins).

And again. Already on another part more than 2 hours of printing and the printer restarted. M122 forgot to do.
Angry a little).

Hi, I've looked at the map file and there is nothing that I can see that is obviously wrong. Basically the system was generating steps at the time that the watchdog fired. That typically only happens if the system gets itself into some sort of loop or is unable to complete things fast enough and should not normally happen. Something you may want to do is to try some shorter prints (perhaps ones with similar gcode to whatever it is you are printing) and keep an eye on the output from m122 during the print (or at completion if it makes it). Things to look at are the stats under "Move" and "DDARing" in particular Hiccups may indicate that the system is struggling to keep up. I notice that you have both WiFi and a TFT24 display attached both of these will be generating load on the system, so you may want to perhaps try running without one or the other to see if that makes things more stable.

I do have some changes that have helped with other problems and I will be producing a build that incorporates them soon. However without being able to reproduce a problem it is very hard to know how to fix it. All I can do is ask that people that are having problems try and help by narrowing things down as much as possible and collecting data when problems happen. It may also help to know a little more about your printer and how you have it set up. Basically is there anything about it that is unusual (have you made any changes to things like the SPI or PWM speeds), do have any additional hardware etc.

If what you are looking for is firmware that you can rely on then at this point the LPC RRF port may not be the best solution and you may want to try something else. I know it is frustrating when a print fails, but trust me it is even more frustrating trying to work out what is going on when you can't reproduce a problem. But if you can help then hopefully we can get to the bottom of issues like this.