TFT Update now "No Printer Attached"

This morning I updated all 3 of my screens (MP3DP V4, Primo & LR3) to the latest TFT release from Ryan. New TFT release

Now on my MP3DP and Primo (Haven’t checked the LR3 yet) i get “No Printer Attached” I didn’t change anything in the firmware, just downloaded and copied to the card. there were no errors when they updated that I saw. No wiring was changed and they were working fine before hand. @jeffeb3 mentioned in the linked TFT post that it could be a baud rate issue but I’m not sure why that would be since I didn’t edit the firmware or how to fix it if that is the cause.

Thanks in advance for any assistance with this!

1 Like

Check that the baud rate in the screen settings is set to 250k. That should be right for our firmware.

The other possibility is that is somehow thinks there should be an extruder.

Both of those settings should come from the config.ini. so that is fishy.

1 Like

That was it. Took me a min to dig around and find it but it was set for 115200. Thats on my MP3DP. Will check the other 2 shortly. Thanks Jeff!!!

1 Like

@Ryan, I unzipped the release zip and looked at the config.ini. Am I reading this right?

#   Options: [OFF (port disabled): 0, 2400: 1, 9600: 2, 19200: 3, 38400: 4, 57600: 5, 115200: 6, 250000: 7, 500000: 8, 1000000: 9]
serial_port:P1:7 P2:0 P3:0 P4:0

It looks like P1 is set to 7, which is 500k, not 250k.

It reads 250000: 7, so the index follows after the baud rate. Should be fine

1 Like

Ah. Ok.

What was your set to? I wonder why the confi.ini didn’t set that correctly.

Hmmm, good question. I‘ve flashed my tft a couple of times in the last days. In some cases I saw the ‚no printer attached’ message and I had to manually change the baud rate in the tft settings menu which I normally never need to do. ATM it is set to 250000.

This is what i had to do. I still need to go check the Primo and LR3 to see if those need to be changed at all. I know the Primo said no printer attached but I didn’t pay attention to the LR3

I wonder if they changed the enum so a 6 is now a 7.

I confirm the config.ini sets the baud rate correctly in the Repeat TFT package. I’m confused that a reset.txt is present in the same directory. It resets the tft to default values.

Reset.txt should only reset the touch calibration.

From the BTT repo readme:

The hard reset process consists in:

  1. resetting the TFT’s configuration to the TFT’s default hard coded settings
  2. starting the touch screen calibration process (see Touch Screen Calibration) at startup before moving to Main menu

It does much more. It additionally starts the screen calibration. This is confirmed by the source code (settings.c, line 23 onwards).

Ok so Primo and LR3 were already set to 250000. My DA had the black TFT wire backwords on the Primo. I always run in marlin mode so i never noticed it before…but that is corrected now and works great.

I ran the CNC file on the LR3 and Primo and the Repeat file on the MP3DP. The repeat file is the only one that had the baud rate incorrect. I assume I was correct in using the different file for the printer but if not i can go back and flash with the CNC file.

I don’t think so. I looked at the source code (SerialConnection.c):

const uint32_t baudrateValues[BAUDRATE_COUNT] = {

The 250k is still at index 7.

I assume I was correct in using the different file for the printer

I would agree, that’s why there are 2 different ZIP files (Ryan to confirm).

I’ve looked at the startup procedure of the tft (boot.c, line 370).

It firstly reads all bmp’s, fonts, the config.ini and processes them. All processed files are being renamed to ‘*.cur’.
Finally the software checks whether a reset.txt exists. If so, the tft is being reset to standard parameters (haven’t found the standard baudrate setting yet). The reset.txt is renamed to reset.done.

If the user cycles power the screen will startup again, but will not find a config.ini (as this was renamed before). This means the tft operates with standard settings until the config.ini file is copied to the SD card again.

If the above is correct, the reset.txt should be removed from the package. It hasn’t been part of the previous release which explains why there haven’t been issues before.

I don’t like the BTT implementation. If a reset.txt is available, why is the config.ini read? I would change the sequence.


Interesting. I have no issue taking it out. Give me a few minutes to update the packages.

Only the Repeat V4 tft package has the reset file. I will re-upload that one.

1 Like

Trying Repeat_TFT_Package2 now

@vicious1 That one works!

1 Like