[Arkadiusz]

It is not about physically connecting the wifi adapter to the motherboard.
It is rather software support in the Marlin firmware.
For BeePrint to work with each board, it only needs to work on TX / RX sending
and receiving Gcode. It cannot use the MKS_WIFI protocol.

BeePrint only applies to “some” MKS Robin boards that they use
LVGL graphic libraries mainly connected via the FSMC connector.

At present, the boards produced by MKS have a variety of Wifi adapters and no FSMC,
There are very few FSMC motherboards compared to others.
In my opinion, MKS_WIFI does not work with a board that does not have a display with LVGL libraries.
Boards based on e.g. LPC1768 do not support FSMC. This is what Marlin says when compiling.
MKS_WIFI has its own data transfer protocol. That’s why I consider the display software daemon
oversees send and receive between motherboard and MKS_WIFI adapter.

in brief

 

LVGL must be enabled for MKS_WIFI to work. LVGL must have an LCD connected via FSMC

This is how the Marlin software for the MKS_WIFI adapter was written.

This situation significantly limits the use and popularization of BeePrint software.
I know that you wrote BeePrint with your FlyBear Ghost 5 in mind. I have such a printer myself.

It would be good to develop the BeePrint project and focus on Wifi support only after RX / TX,
just like in OctoPrint.

 

 

[Arkadiusz]

In my opinion, it is not only a matter of connecting additional pins. Marlin firmware does not support MKS_WIFI without LCD display with LVGL libraries. There must be an LVGL display. I have made many attempts to no avail. I think so, maybe I’m wrong. What do you think about it.

[Author]

Posts