<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>LPC port of RepRapFirmware</title>
        <description>An experimental port of RepRapFirmware v1.21RC2 for LPC1768 boards. Sources: [url=https://github.com/sdavi/RepRapFirmware/tree/LPC]RepRapFirmware for LPC[/url] and [url=https://github.com/sdavi/CoreLPC]CoreLPC[/url].

Attached below are firmware binaries for:
[list]
[*] Azteeg X5 Mini (Tested normal cartesian only on AzteegX5Mini V1.1)
[*] Smoothieboard (Tested on Smoothieboard 4XC on my CNC, 2 drivers for Y-axis - only movement tests X,Y,Z)
[*] ReArm (UNTESTED don&#039;t have one) - Best guess, configured based on provided smoothie config files
[/list]
Uploading firmware is same procedure as Smoothieware, i.e. copy appropriate firmware file as firmware.bin to the SDCARD and reset. 

Notes:
[list]
[*] Very Experimental at this stage - Use at own risk - Do not leave unattended etc etc etc.
[*] The &quot;Play&quot; LED (on ReArm? and Azteeg X5 Mini) or LED1 (on Smoothieboard) should blink every 500ms which is controlled via the Systick interrupt.
[*] RRF doesn&#039;t mount the SD card as a MSD like smoothie does. You may need physical access to the SDCard, if things go wrong and can&#039;t upload a new firmware.bin to the SDCard, or, want to revert back to smoothieware.  
[*] Currently the following features are disabled: SPI thermocouple; ethernet; and, Reset/fault Diagnostics.
[*] RRF only supports 3 endstops + probe, so on boards with both max and min endstops, the MAX endstop headers are used by default for XYZ endstops (as either max or min), and Z-Min being used for zprobe. The X Min and Y Min pins are free for other purposes.
[*] Currently no mapping of spare pins to Special pins controllable with Gcode for Smoothieboard and ReArm.
[*] Zmin (currently configured for z-probe) is not ADC capable. If need Analog In for probe then update header files to switch to a spare ADC pin.
[*] I&#039;ve tried to pack RAMs AHB0 and AHB1 leaving around 8k main RAM free which hopefully will be enough for auto-calibrations etc?????
[/list]
Unfortunately, I don&#039;t have a spare printer for testing, but I did have it temporarily connected on my printer and was able to home, heat hotend+bed, probe bed with piezo probe and print a hollow cube test print. I don&#039;t have a delta, corexy etc so haven&#039;t been able to test those.</description>
        <link>https://reprap.org/forum/read.php?147,810214,810214#msg-810214</link>
        <lastBuildDate>Sun, 08 Mar 2026 12:13:36 -0400</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881504#msg-881504</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881504#msg-881504</link>
            <description><![CDATA[ Its listed on the wiki.<br />
Teamgloomy.github.io]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:48:06 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881503#msg-881503</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881503#msg-881503</link>
            <description><![CDATA[ yes! that worked, servo0 although it didn't say in the BIQU_SKR.h file.<br />
<br />
Thanks a million! I guess I can start playing with it.]]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:43:53 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881502#msg-881502</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881502#msg-881502</link>
            <description><![CDATA[ Its servo0 I think]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:41:56 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881501#msg-881501</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881501#msg-881501</link>
            <description><![CDATA[ servo says unknown pin<br />
M591 P7 C"servo" S1 L100 E3 D0<br />
Error: M591: Unknown pin name 'servo']]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:41:29 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881500#msg-881500</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881500#msg-881500</link>
            <description><![CDATA[ It only receives data during a print]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:41:24 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881499#msg-881499</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881499#msg-881499</link>
            <description><![CDATA[ servo didn't work, for some reason it's undefined so I tried "probe"<br />
M591 D0<br />
Pulse-type filament monitor on pin probe, enabled, sensitivity 1.500mm/pulse, allowed movement 60% to 160%, check every 3.0mm, no data received<br />
M591 P7 C"probe" S1 L1.5 E3 D0]]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:40:29 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881498#msg-881498</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881498#msg-881498</link>
            <description><![CDATA[ Just use the servo.<br />
You can use either the name or pi number to refer to it as both are supported]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:34:21 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881497#msg-881497</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881497#msg-881497</link>
            <description><![CDATA[ Okay, how do you suggest I define a pin? as far as I understand the M591 accepts only a pin name for the C parameter.<br />
Can I let's say define "e0det" in board.txt to be e0det= then call in in config.g?<br />
or I could just use the "servo" which is P2_0?]]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:33:23 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881496#msg-881496</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881496#msg-881496</link>
            <description><![CDATA[ in that case, it has to be a pin that starts with 0 or 2. 1.26 won't work as it can't driver interrupts]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:07:39 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881495#msg-881495</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881495#msg-881495</link>
            <description><![CDATA[ Well, I'm just making my own, using an encoder. it should be the pulse generating one.]]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 10:01:39 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881491#msg-881491</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881491#msg-881491</link>
            <description><![CDATA[ What filament sensor are you trying to add?]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 02:12:56 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881490#msg-881490</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881490#msg-881490</link>
            <description><![CDATA[ Hello,<br />
<br />
I was wondering if anyone was able to get the filament sensor working on SKR 1.4T. as per RRF; it should be enabled by M591, however when I try to create the sensor in config.g then issue M591 D0 to show the status of the filament sensor in Drive0 or E0; it says that E0 has no filament sensor.<br />
Then I tried running the setup M591 which I have in config.g from the console &amp; this is what I get: M591: unsuitable pin<br />
this is what I have in config.g : <br />
M591 P7 C"e0stop" S1 L100 E3  D0 A1<br />
Although in RepRapFirmware/src/LPC/Boards/BIQU_SKR.h the "e0stop" is defined to be correctly pin 1.26, not sure why it says unusable.<br />
<br />
Is there another way to actually define the pin &amp; use it as filament sensor?<br />
<br />
Regards,<br />
Molafa.]]></description>
            <dc:creator>Molafa</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 13 Feb 2021 00:38:45 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,881270#msg-881270</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,881270#msg-881270</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>MKSA</strong><br />
<blockquote class="bbcode"><div><small>Quote<br /></small><strong>svs072477</strong><br />
Hi, you wrote that you wanted to experiment with ESP 32. Is anything working?</div></blockquote>
<br />
What controller board uses this chip ?</div></blockquote>
[<a href="https://github.com/FYSETC/FYSETC-E4" target="_blank"  rel="nofollow">github.com</a>]<br />
The E4 board is a minimal 3D printer control board based on the ESP32 microcontroller from ESPRESSIF, with built-in Wi-Fi and Bluetooth. The controller speed is up to 240MHz, 16M flash.]]></description>
            <dc:creator>dbo7lwzs</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 06 Feb 2021 03:33:16 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,870569#msg-870569</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,870569#msg-870569</link>
            <description><![CDATA[ deleted]]></description>
            <dc:creator>bcmob</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Fri, 10 Apr 2020 11:32:45 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,869281#msg-869281</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,869281#msg-869281</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>jay_s</strong><br />
@sdavi<br />
<br />
I definitely saw a difference in response times between RRF2 and RRF3 but I was using two different MKS boards.<br />
I thought the slow down I saw was of a result of the board I used for RRF2 having a borked driver (amongst other things).<br />
<br />
For me, on RRF2, it took about 5 minutes to load DWC. After that, everything was fine.<br />
<br />
I have a spare MKS board and will do a comparison test between RRF2 and RRF3 this evening.</div></blockquote>
<br />
Did you get a chance to look at this issue ?<br />
<br />
I tried V3.0, tried also with the machine hooked up to the router, tried DHCP, different cables ... to no avail.<br />
<br />
It always takes 14min to load the script (about 2MB) but once loaded all seems fine but sometime com errors then it reconnects. Upload of a 1 Megabyte file in 5s but cannot download it back or edit it ?]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Mon, 23 Mar 2020 06:17:52 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868651#msg-868651</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868651#msg-868651</link>
            <description><![CDATA[ @sdavi<br />
<br />
I definitely saw a difference in response times between RRF2 and RRF3 but I was using two different MKS boards.<br />
I thought the slow down I saw was of a result of the board I used for RRF2 having a borked driver (amongst other things).<br />
<br />
For me, on RRF2, it took about 5 minutes to load DWC. After that, everything was fine.<br />
<br />
I have a spare MKS board and will do a comparison test between RRF2 and RRF3 this evening.]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Mon, 09 Mar 2020 08:04:14 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868650#msg-868650</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868650#msg-868650</link>
            <description><![CDATA[ @MKSA<br />
<br />
Hmmmmm, that is strange - I don't see anything out of the ordinary there. Based on those snippets, it looks like its working properly (on the LPC), but for some reason just very slow when loading up the web files. <br />
<br />
I tested on mine (v3.01) connected directly to laptop with a static address and can confirm that part of networking is still working quickly. <br />
<br />
Since the upload speeds etc are all good once its up and running, I'm out of ideas what could be the cause. This is how mine looks for comparison:<br />
<br />
[attachment 114735 ScreenShot2020-03-09at10.14.57PM.png]]]></description>
            <dc:creator>sdavi</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Mon, 09 Mar 2020 07:59:19 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868648#msg-868648</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868648#msg-868648</link>
            <description><![CDATA[ @sdavi<br />
<br />
<br />
I use Pronterface via USB as a console. Here is what I get:<br />
I connect, issue the debug command:<br />
<br />
Connecting...<br />
Printer is now online.<br />
&gt;&gt;&gt; M111 P1 S1<br />
SENDING:M111 P1 S1<br />
Debugging enabled for modules: Network(1)<br />
Debugging disabled for modules: Platform(0) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15)<br />
<br />
I sent M552 and I get:<br />
<br />
&gt;&gt;&gt; M552<br />
SENDING:M552<br />
Network is enabled, configured IP address: 192.168.2.2, actual IP address: 192.168.2.2<br />
<br />
Then with Chrome I connect to the printer:<br />
<br />
This loops for 10 minutes plus. but is quite slow. Not much displayed on Chrome debug network screen.<br />
<br />
Accepted Connection from 192.168.2.1:49098 on Skt: 1<br />
Queued 205 bytes (of 205 bytes) on Skt: 1<br />
Queued 512 bytes (of 512 bytes) on Skt: 0<br />
Queued 256 bytes (of 256 bytes) on Skt: 1<br />
Queued 512 bytes (of 512 bytes) on Skt: 0<br />
Queued 256 bytes (of 256 bytes) on Skt: 1<br />
Queued 512 bytes (of 512 bytes) on Skt: 0<br />
Queued 8 bytes (of 8 bytes) on Skt: 1<br />
Waited 0 ms for Graceful Shutdown<br />
Queued 512 bytes (of 512 bytes) on Skt: 0<br />
Queued 512 bytes (of 512 bytes) on Skt: 0<br />
Accepted Connection from 192.168.2.1:49610 on Skt: 1<br />
<br />
Then once the DWC control panel is displayed. (Couldn't catch the exact moment), plenty of "stuff" on Chrome debugscreen. <br />
, this loops fast:<br />
<br />
Graceful Shutdown<br />
Accepted Connection from 192.168.2.1:60650 on Skt: 0<br />
Queued 205 bytes (of 205 bytes) on Skt: 0<br />
Queued 256 bytes (of 256 bytes) on Skt: 0<br />
Queued 256 bytes (of 256 bytes) on Skt: 0<br />
Queued 8 bytes (of 8 bytes) on Skt: 0<br />
Waited 0 ms for Graceful Shutdown<br />
Accepted Connection from 192.168.2.1:60906 on Skt: 1<br />
<br />
<br />
Gcode file upload is done at about 110KiB/s according to the console.<br />
<br />
If I turn the printer OFF, then ON again, DWC reconnects immediatly but sorry, no Pronterface console as no time to reconnect via USB.<br />
<br />
Same with Firefox or an other PC.]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Mon, 09 Mar 2020 05:31:55 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868636#msg-868636</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868636#msg-868636</link>
            <description><![CDATA[ From memory, the last time I did fixes for networking I applied it to the V2 branch as well. The initial load on mine is only about 6 seconds to fully load and display DWC2.  <br />
<br />
When it's up and running, what are the speeds like when upload and download a gcode file?  <br />
<br />
Enable debugging for Networking: M111 P1 S1. Attempt to connect, when its working you should see accepted connections and data queued on sockets 0 and 1 when its sending the web files. <br />
<br />
Also there is debugging for WebServer: M111 P2 S1.<br />
<br />
Open the debugging console in Chrome or Firefox and look at the network tab and see the progress of the initial DWC files being downloaded to see what the browser is doing. <br />
<br />
Watch the Link LED on the network port and make sure it's not dropping the link for some reason.]]></description>
            <dc:creator>sdavi</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Mon, 09 Mar 2020 00:00:55 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868625#msg-868625</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868625#msg-868625</link>
            <description><![CDATA[ which version of DWC are you running? I am on 1.22.5 or 1.22.6 . there was one release that was not on the git site listed, but on dc42's page or linked somewhere else. <br />
<br />
RRF3 is probably the way to go for a lot of reasons, but right now I am staying with it until i get my HW issues worked out.]]></description>
            <dc:creator>sinned</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sun, 08 Mar 2020 16:59:50 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868624#msg-868624</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868624#msg-868624</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>jay_s</strong><br />
I've powered mine with 24v and had the issue of it taking a while to connect on the network. With RRF3, I don't get that issue. Once loaded it works fine.<br />
<br />
It may need @sdavi to come in as I don't know what changes have been made in RRF between version 2 and 3. <br />
<br />
@MKSA<br />
If you like DWC, might be another reason to look at upgrading to RRF3.</div></blockquote>
<br />
Obviously it is not a power issue !<br />
<br />
Anyway, my MKS SBASE is properly wired, one 24V supply and the USB not even used (and when in use my USB cable has the V+ cut BTW). NO noisy ground loop either. I used a portable PC to check too.<br />
<br />
And same issue you experienced. It takes time to load the script but once done, all is fine. I can power off and on, the printer, DWC reconnect asap but if I close Chrome and reopen, again takes forever !<br />
<br />
If RRF 3 is OK, I will move on then.]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sun, 08 Mar 2020 16:42:12 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868622#msg-868622</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868622#msg-868622</link>
            <description><![CDATA[ I've powered mine with 24v and had the issue of it taking a while to connect on the network. With RRF3, I don't get that issue. Once loaded it works fine.<br />
<br />
It may need @sdavi to come in as I don't know what changes have been made in RRF between version 2 and 3. <br />
<br />
@MKSA<br />
If you like DWC, might be another reason to look at upgrading to RRF3.]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sun, 08 Mar 2020 16:28:22 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868620#msg-868620</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868620#msg-868620</link>
            <description><![CDATA[ I think you might have a voltage issue then. <br />
<br />
How are you powering the controller? If you are using 5V from USB it might not have enough capacity. <br />
<br />
I found that with the ReArm board with the ethernet controller module. With UBS only, it was constantly misbehaving. <br />
<br />
Once I put dedicated 12V adapter on the controller and used PS_ON to control the main PSU power, it got reliable.]]></description>
            <dc:creator>sinned</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sun, 08 Mar 2020 16:12:06 -0400</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868604#msg-868604</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868604#msg-868604</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>jay_s</strong><br />
@MKSA<br />
<br />
Sorry I haven't replied earlier. <br />
I had this happen with one of my boards with it taking forever to show DWC. <br />
You could try what sinned recommended and statically assign an IP address and see if that fixes the issue. I upgraded to RRF 3 (to match the rest of my machines) and the issue went away.<br />
I don't think it's related to speed as the issue doesn't exist on RRF 3. <br />
I suggest going the static IP address route and see if that fixes it</div></blockquote>
<br />
I did assign static IP to my PC Ethernet port and MKS SBASE . I also disabled the WiFi, the Firewall, no change.<br />
<br />
I just added the M550 command, no change.<br />
<br />
As I wrote and this is strange, once I get DWC console on the PC (Chrome browser but same with Firefox), if I turn the 3D printer off, DWC detects it and resume as soon as the printer is turned on again. If I close DWC, then reopen it then it takes for ever to finally load ?<br />
<br />
Note that the TFT32 and USB connection with Pronterface are working OK with the network ON. I did try to disable it to see if it was the reason but no change.]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 07 Mar 2020 16:04:41 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868602#msg-868602</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868602#msg-868602</link>
            <description><![CDATA[ @MKSA<br />
<br />
Sorry I haven't replied earlier. <br />
I had this happen with one of my boards with it taking forever to show DWC. <br />
You could try what sinned recommended and statically assign an IP address and see if that fixes the issue. I upgraded to RRF 3 (to match the rest of my machines) and the issue went away.<br />
I don't think it's related to speed as the issue doesn't exist on RRF 3. <br />
I suggest going the static IP address route and see if that fixes it]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 07 Mar 2020 15:25:46 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868599#msg-868599</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868599#msg-868599</link>
            <description><![CDATA[ <blockquote class="bbcode"><div><small>Quote<br /></small><strong>MKSA</strong><br />
@jay_s<br />
<br />
Looks like this huge delay is due to how slow the scripts are transferred to the PC ???<br />
Am I the only one facing this ?</div></blockquote>
<br />
Did you try to define all your network parameters in your config file? <br />
<br />
I had better luck hard coding the static IP and gateway with M552, M553 and M554 in the config file than with DHCP.  I also forced compatibility with M550 <br />
<br />
I think I did it this way- <br />
<br />
M552 S0 ; disable networking<br />
M550 P"Duet_Printer"<br />
M553 P255.255.255.0 ; netmask<br />
M554 P192,168,1,254 ; Gateway<br />
M552 S1 P192.168.1.30   ; Assign IP Addy and enable<br />
M550 P0]]></description>
            <dc:creator>sinned</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 07 Mar 2020 12:06:09 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868597#msg-868597</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868597#msg-868597</link>
            <description><![CDATA[ @jay_s<br />
<br />
Looks like this huge delay is due to how slow the scripts are transferred to the PC ???<br />
Am I the only one facing this ?]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Sat, 07 Mar 2020 11:39:56 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868512#msg-868512</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868512#msg-868512</link>
            <description><![CDATA[ @jay_s<br />
<br />
I installed DWC, tried different browsers, ended up with Chrome ( I was sure it works with Java) could see that definitely there was something going on  but nothing just the rotating arrow and no timeout. <br />
<br />
After different attempts, I gave up and went to something else while it was still "running".<br />
<br />
Then big surprise after about FIVE if not more minutes, I got the Web control panel ??????<br />
<br />
Note I am using a direct Ethernet connection from my PC to the MKS SBASE board (X cable). I fixed the IP address on both end  PC: 192.168.2.1 MKS 192.168.2.11 no conflict with my Wifi. Ping less than 1ms<br />
<br />
Once I get the Web console, it works fine, is very responsive. If I close Chrome, then open it again, same long wait BUT is I turn the 3D printer off, DWC says connection lost, trying to reconnect and reconnected quickly when I turn power on !<br />
<br />
In config.g<br />
<br />
; Network<br />
M552 S1 P192.168.2.11   <br />
<br />
Didn't define anything else. May be I should ? Not easy to connect directly the printer to my router.<br />
<br />
Here the result of M552 and M122 command:<br />
<br />
&gt;&gt;&gt; M552<br />
SENDING:M552<br />
Network is enabled, configured IP address: 192.168.2.11, actual IP address: 192.168.2.11<br />
&gt;&gt;&gt; M122<br />
SENDING:M122<br />
=== Diagnostics ===<br />
RepRapFirmware for LPC176x based Boards version 2.05 running on LPC176x at 100Mhz<br />
Used output buffers: 2 of 16 (10 max)<br />
=== RTOS ===<br />
Static ram: 2940<br />
Dynamic ram: 29192 of which 0 recycled<br />
Exception stack ram used: 416<br />
Never used ram: 188<br />
Main SRAM         : 32548/32768 (220 free, 188 never used)<br />
RTOS Dynamic Heap : 40016/46720 (6704 free, 5272 never used)<br />
=== LPC PWM ===<br />
HWPWM:500Hz T1:10Hz T2:0Hz T3:250Hz<br />
Tasks: EMAC(blocked,52) NETWORK(ready,556) IP-task(blocked,88) HEAT(blocked,1352) MAIN(running,2260) IDLE(ready,164)<br />
Owned mutexes: RTOSPlusTCPEthernet(NETWORK)<br />
=== Platform ===<br />
Last reset 00:51:14 ago, cause: [power up]<br />
Flash Slot[29]:<br />
Last software reset at 2020-03-05 08:23, reason: User, spinning module GCodes, available RAM 360 bytes (slot 0)<br />
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task 0x2007cfc0<br />
Stack: 00000000 00000002 00017f71 2009c000 2007c310 00000000 10003410 10004348 10003450 00000001 0001810b 00000000 10003410 10003e88 00000050 00000007 10003e88 10003410 2007eb94 00000001 a5a5a5a5 000003e7 a5a5a5a5<br />
Error status: 0<br />
[ERROR] Error status: 0<br />
<br />
Free file entries: 4<br />
SD card 0 detected<br />
SD card longest block write time: 0.0ms, max retries 0<br />
Date/time: 2020-03-05 15:57:45<br />
Slowest loop: 57.71ms; fastest: 0.05ms<br />
=== Move ===<br />
Hiccups: 0, FreeDm: 100, MinFreeDm: 99, MaxWait: 277730ms<br />
Bed compensation in use: none, comp offset 0.000<br />
=== DDARing ===<br />
Scheduled moves: 22, completed moves: 22, StepErrors: 0, LaErrors: 0, Underruns: 0, 0<br />
=== Heat ===<br />
Bed heaters = 0, chamberHeaters = -1 -1<br />
Heater 0 is on, I-accum = 0.0<br />
Heater 1 is on, I-accum = 0.2<br />
=== GCodes ===<br />
Segments left: 0<br />
Stack records: 2 allocated, 0 in use<br />
Movement lock held by null<br />
http is idle in state(s) 0<br />
file is idle in state(s) 0<br />
serial is ready with "M122" in state(s) 0<br />
aux is idle in state(s) 0<br />
daemon is idle in state(s) 0<br />
queue is idle in state(s) 0<br />
lcd is idle in state(s) 0<br />
autopause is idle in state(s) 0<br />
Code queue is empty.<br />
=== Network ===<br />
Slowest loop: 59.32ms; fastest: 0.02ms<br />
Responder states: HTTP(2) HTTP(0)<br />
HTTP sessions: 1 of 2<br />
Interface state: active, link 100Mbps full duplex<br />
Socket States: Connected(86ms)  Listening<br />
NetBuffers: 3 lowest: 1<br />
IP Event Queue lowest: 9<br />
EthDrv: Dropped packets (no buffer): 3<br />
=== Filament sensors ===<br />
Extruder 0 sensor: no data received]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Thu, 05 Mar 2020 10:05:01 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868042#msg-868042</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868042#msg-868042</link>
            <description><![CDATA[ @MKSA<br />
<br />
Its very convenient. Using the network connection would also allow you to upload gcode directly from the slicer if its supported. <br />
Prusaslicer/slicer++ support it natively, Cura has a plugin which can be installed and Simplify3D can upload using the script found <a href="https://forum.duet3d.com/topic/867/duet-wifi-s3d/38?_=1582621367943" target="_blank"  rel="nofollow">here</a>.<br />
<br />
Of course you can just upload gcode through DWC. <br />
You'll also be able to edit the config.g file and the board.txt file if required through DWC.<br />
<br />
I'll be interested to know how you get on using both DWC and the TFT.]]></description>
            <dc:creator>jay_s</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Tue, 25 Feb 2020 04:05:36 -0500</pubDate>
        </item>
        <item>
            <guid>https://reprap.org/forum/read.php?147,810214,868041#msg-868041</guid>
            <title>Re: LPC port of RepRapFirmware</title>
            <link>https://reprap.org/forum/read.php?147,810214,868041#msg-868041</link>
            <description><![CDATA[ @jay_s<br />
OK, will have to try then. <br />
Currently I have to remove the SD card to copy the file to be printed on it to be able to use the filament monitoring.]]></description>
            <dc:creator>MKSA</dc:creator>
            <category>Firmware - experimental, borrowed, and future</category>
            <pubDate>Tue, 25 Feb 2020 03:53:21 -0500</pubDate>
        </item>
    </channel>
</rss>
