name: Bug report 02 “Connecting …M115” Forever

[B-rad888]

name: Bug report 02 about: Switching to marlin mode after power on TFT = “Connecting …M115” Forever title: switching screens is not seamless labels: 'bug' assignees: '''BIGTREETECH”

Powering on the TFT screen works great in touch screen mode. Then switch to Marlin mode and you will see “Connecting…M115” while it never connects. Requires a reboot to connect. However, booting into Marlin mode first, then switching to touch mode and you won’t get the bug. This is not ideal as most users including myself would like to boot into touch screen mode, and have the ability to switch to marlin mode to make fine adjustments and go back to touch screen mode without having to reboot the printer. Until it is fixed seamless operation requires booting into marlin mode on startup and switching to touch mode. Using this work around will not produce the bug.

Steps to reproduce

1. Power on TFT in touch screen mode
2. Wait for TFT to say ready
3. Switch to marlin mode either: Hold scroll wheel for 3 seconds and select marlin mode Press on screen for 3 seconds and select marlin mode
4. Turn scroll wheel to initialize screen in marlin mode
5. Select Info screen
6. Stare at the connecting…M115 in confusion for eternity.

Expected behavior After powering on into touch mode and switching to marlin mode:

I would expect the screen to say “CoM115” and to work properly. If “serial_always_on:1” is set in config or I would expect the screen to say “Printer name Ready” and to work properly. If “serial_always_on:0” is set in config Actual behavior After powering on into touch mode and switching to marlin mode: Screen displays “connecting…M115” for eternity. Requiring a reboot. Or abandoning marlin mode and navigating back to the touchscreen.

Hardware Variant

TFT35_V3.0_E3

TFT Firmware Version & Main Board Firmware details

BIGTREE_TFT35_V3.0_E3.26.x SKR 1.4 Turbo Marlin bugfix-2.0.x

Additional Information

This may have to do with an error I see after updating the config file. Unknown Command “MM115” If there is an extra M in the M115 code somewhere it might be causing issues. I haven’t seen anything like that in the code however.

[radek8]

For starters, put it on the screen, it will be easier

[B-rad888]

That is true. I think it needs to be re-flashed though. I think the wrong setup is what cause all the issues.

[radek8]

If you wanted to put it in SKR 1.4 turbo, you would have to change the port pins for serial port3 in Visual Studio. Also, you could not use the USB Connector

[B-rad888]

So, no octoprint then if its on the SKR 1.4 board?

[radek8]

Marlin defines only 2 serial inputs. on one you have a display and on the other a USB connector or WIFI

[B-rad888]

That makes sense

[radek8]

The display expands another 3 serial inputs, which it sends to one

[B-rad888]

So I already had this set up with the tutorial. The comment I saw on said,

"I thought the ESP3D guys recommended running it at the 160mhz"

and the response was...

"i think they do, but there are so many different ones of these, I was going with the doc I found, honestly I have tried a bunch of different ways and can't see where it makes a whole lot of difference."

Would the wrong frequency be causing this? Because its all set up. I can control the printer and everything. However the TFT has all those issues when its connected.

Im logged into the web interface now and I cant see any setting to change that. Would I have to re flash the Wifi card?

[B-rad888]

This is the tutorial: https://www.youtube.com/watch?v=NGgzw-XayEo

It was all set up through VS code and not the program to flash it

[radek8]

napřed nastav Marlin dle obrázku. SSID a pasword nastav dle své wifi

[radek8]

connect to the AP sent by the Wifi card and open the address 192.168.0.1 upload files 401.html favicon.ico index.html.gz

[B-rad888]

I'm not sure what you mean. I already have the interface operational with those files. I dont have the info in configuration_adv,h though.

[B-rad888]

Are you saying to

1. define ESP3D_WIFISUPPORT

2. define WIFI_SSID

3. define WIFI_PWD

4. flash firmware
5. delete or replace 404.htm, fav ico, and index.html.gz

[radek8]

delete comment

define ESP3D_WIFISUPPORT

add rows

define WIFI_SSID namewifi

define WIFI_PWD password

[radek8]

On the wifi tab, set the configuration of your own wifi network (same as in marlin)

[radek8]

Attention BaudRate must be the same everywhere, on Wifi, display and Marlin

[radek8]

wifi.zip

[B-rad888]

OK I did all of that. However nothing changed. Everything was already configured like that and I'm still getting the same bugs that I was getting before.

[radek8]

If you map the virtual COM port to the Wifi address and port 8888, you can also connect with the Pronterface.exe software, which has more options than a web interface and replaces the USB cable.

[B-rad888]

How would I do that?

[radek8]

if you have it well set up it works like this

VID_20200611_204557.zip

[radek8]

when you disconnect wifi and switch to the touch screen. Does the display communicate with the printer?

[B-rad888]

when I remove wifi card everything works. When Wifi card is connected I still get all of the bugs like before

[radek8]

Wifi card communication in touch mode

VID_20200611_205324.zip

[radek8]

Will the Wifi card connect to your network?

[radek8]

Do you have an original bin file in the wifi card or the one you edited?

[oldman4U]

B-rad888.

My advise. Define a "must have" setup and make it work. From there, add one feature after the other always with the ability to fall back to the working setup. Also, keep it simple and learn every day - like we do.

Regarding WIFI Module. You get more or less a Pronterface/Printrun like user interface over WIFI. I am not using Octoprint, but I believe that there is not a single feature the WIFI connection offers, which Octoprint does not have. I can not see the need to have WIFI in case you have Octoprint. I use the same WIFI/TFT combination you have and I never saw the issues you described. Does not matter if the WIFI module was out of the box, only with the firmware installed or working properly like today. This makes me believe that there is something wrong with this module.

The way you described your problems makes me believe that you could be a very useful part of this community. Please think about it, it would be great to have you "on board".

Regards

[oldman4U]

Thats not exactly true. Guru is always everywhere and he knows almost everything.

;-)))

On 11.06.2020, at 19:17, B-rad888 notifications@github.com wrote:

@oldman4U https://github.com/oldman4U lol. Yes @guruathwal https://github.com/guruathwal came out of nowhere and solved it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/780#issuecomment-642820003, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM6XKZDCADHCTNX7KXCJVPLRWEGRDANCNFSM4N257OQQ.

[oldman4U]

@radek8

I believe we should let B-rad888 sleep a bit. Was a long day;-)

Greetings

[B-rad888]

lol I did fall asleep. Then I had to life. I gave up on the wifi module. I set up Octoprint instead on a raspberry pi. I works good. No problems with it.

[oldman4U]

Hi.

Good to hear.

Please close this ticket

Thank you

[B-rad888]

It was fun, not solved, but the issue was diagnosed. Closing thicket. Thanks again for all the help and support! @oldman4U @guruathwal and @radek8 You guys rock! 💯

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.