RepRapFirmware 3.0 port for LPC1768/9 based boards

So board is working! The footprint of the 8266 v3 was a 8266 v2... So it works with the v2.

I use mkstft35 boot loader inorder to upload DuetWiFiServer.bin to esp12s
I am Actually ruining the ESP12s over aux1 port.
Is there any advice in order to enable the module.
I rebuild the firmware using ESP8266WIFI ?= true

Have you still got the screen connected?
The duet ESP software only works with an SPI connection

---

Based in Darlington, North East

Are you using the LPC specific DuteWifiServer.bin (the one linked from the Wiki)? I'm also not at all sure if the mkstft35 boot loader will be uploading the ESP8266 software correctly, what makes you think that it will? As Jay said you can't just connect that module to the aux port you need to connect it via SPI.

Thanks.
I will Build the esp12s programmer and uploadc DuteWifiServer.bin using the espressif/esptool latest repo
But let me ask a question
May I use the aux1 port directly?
Or must I use mks tft35?

Ok Sorry but i read tha there is some users using mks tft32 and tft35 in conjeuction with esp12s
Is there any way to find more info related

Yes, you can use those two together.
Connect the wifi as per here [github.com]
To connect the MKS TFT, first install the custom firmware found here [github.com]
Then connect the screen using the AUX1 connector on the screen (hardware info here [github.com]) to either the AUX1 connector or TFT connected (I've used the TFT connector).
In your config.g, add M575 P1 S1 B57600

---

Based in Darlington, North East

@DrDitto I think you need to take a step back and describe exactly what it is you are trying to do and how you think it will work. There are lots of possible options for using RRF with different displays (or none at all) and network connections. You should probably provide links to the actual hardware you are trying to use (the display, the esp12s module etc.).

I am not sure what you mean by "Build the esp12s programmer" the esp12s modules usually used with the LPC version of RRF do not need any programming hardware, they typically have a USB port that can be used to program the device using esptool.py as described in the wiki. As I have said above please show us exactly what hardware you are trying to use.

I am also not at all sure what you mean by "May I use the aux1 port directly". What do you want to use it for? What do you want to connect to it and why?

dc42 released 3.01

Version 3.1.0 (yes it is now 3.1.0!) available here...
[github.com]

tagged repos:
[github.com]
[github.com]
[github.com]
[github.com]

Duet WiFi Socket Server for use with the LPC RRF port:
[github.com]
[github.com]

No mine is the one made from maker base or btt so it was designed to be used using aux 1 or uart. I would like to have the chance to have a lcd and a wireless function together

Thaaank you!

Some questions.

Is the WiFi Socket Version different from the one on gdrive?
Is it possible to Update the WiFi Socket via DWC


PS. Sorry for the Typo

@PCR What version does the WiFi Socket server you are using report? You can find this by running M122 when WiFi is active.

To update the WiFi firmware via DWC you would need to have a UART connection to your WiFi board as well as SPI (and RRF that is setup to use it). Although this is possible I've never bothered (as the WiFi software is not updated very often).

@DrDitto I think that what you want to do could be made to work, but it is not something I have ever done. I'm not sure what firmware you will need for the WiFi board but it is definitely not the Duet WiFi Server Software as that is intended to be connected via SPI and can not be used at the same time as a dumb ST7920 type display. So I can't really help you much with what you are trying to do.

@PCR

I'm pretty sure the version on Google drive is the one built with version 2.6 (or around that number) of the ESP SDK. The one gloomyandy has uploaded is built with version 3. I think technically there should be no difference but when I used the version 3 one, I couldn't connect to my routers. I suggest trying the new version but be prepared to roll back to the old one of required.

@gloomyandy

Could you also build and upload the version 2.6 one? I can then put a note on the wiki about which version to use.

---

Based in Darlington, North East

@jay_s can you try the version 3 one again (I did fix a couple of problems, but I doubt if they would impact any connection issues). I'd really rather not have to have multiple builds out there if I can avoid it. The 3 version works for me with 3 different routers so far. If there is a problem I'd rather try and understand what is causing it.

@ Jay delete all old entries in the Router!

Best

@PCR I'd still like to know what version of firmware you have on your WiFi board, it would be good for you to also try the version 3 build to see if it works for you.

@gloomyandy

Just tried the latest build of the wifi and it doesn't work for me I'm afraid.
I can get connected this time but DWC does not load. The LED on the wifi module slightly flashes. With the older SDK build the light is rock solid.
No wiring changes. To flash the bin, I disconnect the RST pin.

---

Based in Darlington, North East

[forum.duet3d.com]


Will try it later. You can test it with a Hotspot on the Smartphone?

Do you get any sort of error message? I assume you reset the SID and password? I'm a bit confused when you say you can get connected, what do you see? Normally if you are connected the light will be on solid. What do you get from M122 and M552 also does M587 list the networks you have configured? What sort of network do you have (is 2.4 or 5GHz)? You might want to try clearing all of the memory and try it again (if you are feeling brave).

What are the version numbers of the two Wifi firmwares you are using?

Tested the new wifi and firmware

M122
=== Diagnostics ===
RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.1.0 running on LPC176x at 100Mhz
Used output buffers: 3 of 16 (10 max)
=== RTOS ===
Static ram: 3876
Dynamic Memory (RTOS Heap 5): 3008 free, 2984 never used
Exception stack ram used: 304
Never used ram: 380
Tasks: NETWORK(ready,248) HEAT(blocked,1400) MAIN(running,1460) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:11 ago, cause: [power up][reset button]
LPC Flash Slot[15]: 
Last software reset at 2020-05-16 11:20, reason: User, spinning module GCodes, available RAM 380 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0442d000 BFAR 0xe000ed38 SP 0x00000001 Task MAIN
Stack: 10002da8 2007c1dc 000108c9 00000000 00023243 2007da2c 000003e7 2007d7a4 00005f95 20083110 10002da8 
Error status: 0
Driver 0: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 22
Driver 1: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 22
Driver 2: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 21
Driver 3: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 21
Driver 4: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 21
Date/time: 2020-05-16 11:22:33
Slowest loop: 3.58ms; fastest: 0.31ms
=== Storage ===
Free file entries: 4
SD card 0 detected
SD card longest read time 1.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 = -1, chamberHeaters = -1
=== 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: 25.71ms; 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.23L263-302
WiFi MAC address ec:fa:bc:c5:11:72
WiFi Vcc 64.00, reset reason Unknown
WiFi flash size 4194304, free heap 38448
WiFi IP address 192.168.178.25
WiFi signal strength -59dBm, reconnections 0, sleep mode modem
Socket states: 4 0

So works on my side

[www.tindie.com]

I ordered some boards. Should be here next week. If someone needs one

Edited 1 time(s). Last edit at 05/16/2020 05:26AM by PCR.

Finally got it to load with the new wifi code.
On its first connection attempt it reported the wifi password was incorrect but then on its next connection attempt it connected (nothing typed in between etc)

But...
On the first connection I had the following in DWC

WiFi signal strength -48dBm, reconnections 0, sleep mode modem

I rebooted it and the second time I got

WiFi signal strength -92dBm, reconnections 0, sleep mode modem

I have a google wifi mesh network, with an access point in the garage (where I work) and an access point in the house.
This version doesn't seem to play well with mesh connections and it gets confused about where it should be connecting to.
On all subsequent reloads it connected to the wrong access point and if the tab was closed, DWC would never load again because the connection is too poor to support the initial loading.

The wifi version was 1.23R263.302 (or version number to that effect as I can't get it to reload).

I went back to the other version (1.23) and that connected first go and to the correct access point.

Before each firmware load to the ESP, I erased the flash.

---

Based in Darlington, North East

Hmm so it looks like the firmware is working just that for some reason it is connecting to the wrong access point? I don't have anything like that to test and I've never used a google mesh network. Is there no way to specify by name or anything which access point to connect to? What is the signal strength reported by the 1.23 version?

The version that you have that seems to work best is the original one built with a very old esp8266 SDK (as used by DC42). I've built a debug version using the later 2.XX libs which is here: [drive.google.com] If you get chance can you try it. Once you have flashed it you should be able to connect via USB and open a terminal to it (you need to use an odd baud rate 74880), it should list the access points it is seeing and the signal strength. It will be interesting to see what it picks up in your setup. To get it to do a scan you may need to issue an M552 s0 followed by M552 s1. I'm not sure how this build will compare with either of the others you have tried so far.

@gloomyandy

Here's the results

SocketServer.cpp(346): Scan found 4 SSIDs
SocketServer.cpp(359): found network Jays Wifi BSSID 70:3A:CB:2D:25:76 RSSI -91
SocketServer.cpp(359): found network Jays Wifi BSSID 70:3A:CB:2A:71:1B RSSI -48
SocketServer.cpp(373): No network found
scandone

I've filtered out all the none relevant SSIDs.
I'm assuming its picking the first one of my SSIDs it comes to rather than looking at signal strength and selecting the appropriate one.
The google wifi system is aimed at the average consumer so you have literally no control over what access point you connect to. In theory, it should hand you over the the correct access point but for whatever reason, that's not being done here.

The original wifi build gets a reading around -44

Edited 1 time(s). Last edit at 05/16/2020 01:29PM by jay_s.

---

Based in Darlington, North East

It will be picking out the one with the highest RSSI but it is just using the SSID from that, which in your case is the same for both. After that is just goes into the SDK and I'm guessing that just connects to the first match. I'll look into using both the SSID and the BSSID to do the connection as that may help. So was this the same as the 3.X build in terms of how well it worked? If so I'm not sure why the older SDK does things differently, could just be luck!

Thanks to all.
I will make a deep research.
At the moment I will work changing the new Open source mks tft firmware. Because the one that all mention at the messages did not work. It shows no images for the button.

@jay_s in the scan test you did above, had you added your network SSID as a network to connect to? If so I don't understand the "No network found" message, you should only get that if none of the scanned networks match any of the networks you added using M587 and it looks like the scan was finding your access points.

@gloomyandy

No, I just scanned that time.
I'll add it in the morning and rescan

---

Based in Darlington, North East