This is a follow-up, in case anybody has similar problems. In brief:

• I've ended up getting the best results with the Thro42 variant of the TFT35-E3 firmware; however....
• Contrary to the documentation, I need to use "M575 P1 S1", not "M575 P1 S3" (plus "B{baudrate}") in config.g to enable support. Using "S3" results in flaky behavior.
• The Thro42 variant (as well as its immediate predecessors, the bcmob and JimmymadDness variants) disable the ability to print from the TFT's own SD card and USB slots. They also lack some of the more recent feature additions of the main BTT branch. OTOH....
• The point of these forks is to enable RepRapFirmware-specific functionality, including the ability to start prints from files stored on the mainboard's micro-SD card, a print status screen when a print is underway, and (for the Thro42 variant) the ability to run RRF macros. These features more than make up for the ones lost.

It took me many hours of experimentation to get to this point, so I hope these tips will smooth the way for somebody else.

Note also that the BTT github page for their TFT-series displays is quite active. Somebody recently submitted a merge request for some changes to improve RRF compatibility, but those changes don't come close to doing what the Thro42 fork does. It's possible that a future merge will do so, though.

Whenever I try to post, my posts are getting flagged as spam. Why?

I bought something similar, but it's not really helped. I can't seem to find my order confirmation, so I'm not positive exactly what I got, but I think it was this:

https://www.digikey.co.uk/product-detail/en/molex/2451320605/WM15769-ND/6565376

It helped with one fan connection that was similarly unreliable, but it didn't really help with the heater cartridge connection. I tried this originally with the v1.3 board that's now completely shot. When the problem began to recur with the v2 board, I started over with a new Molex connector, but it's not helped. I'm considering bypassing the Smart Effector entirely and wiring the heater cartridge straight into the supply wires.

I really wasn't expecting that to go through. More details (we'll see if the forum relents and lets me post): I've tried posting a couple of messages in the past few days, but they've always been flagged as spam (until just now -- see below). I've tried:

• Using multiple browsers. (Normally I used Firefox, but I've tried Chromium and Safari.)
• Using multiple OSes (Ubuntu Linux, macOS, and Android).
• Creating a secondary account (I'm using that now; my original account was srs5694).
• Connecting via my normal ISP (Cox Communications in Rhode Island) and via my cellular ISP.

Until this thread, my posts were all incorrectly flagged as spam. When my first post to this thread went through, I went back and tried my latest post, and the forum accepted it, with no changes whatsoever to the text.

This problem has spanned several days and has been very frustrating! The forum maintainers really need to look into it.

Thanks for the suggestions. I'm using a Zesty Nimble, so there's no Bowden tube, but the Nimble's drive cable should serve the same purpose. FWIW, I've been using this with the wires tied to one of the diagonal rods for strain relief, but I suppose the Bowden tube/Zesty Nimble cable might work better.

This is a follow-up, in case anybody has similar problems. In brief:

• I've ended up getting the best results with the Thro42 variant of the TFT35-E3 firmware; however....
• Contrary to the documentation, I need to use "M575 P1 S1", not "M575 P1 S3" (plus "B{baudrate}") in config.g to enable support. Using "S3" results in flaky behavior.
• The Thro42 variant (as well as its immediate predecessors, the bcmob and JimmymadDness variants) disable the ability to print from the TFT's own SD card and USB slots. They also lack some of the more recent feature additions of the main BTT branch. OTOH....
• The point of these forks is to enable RepRapFirmware-specific functionality, including the ability to start prints from files stored on the mainboard's micro-SD card, a print status screen when a print is underway, and (for the Thro42 variant) the ability to run RRF macros. These features more than make up for the ones lost.

It took me many hours of experimentation to get to this point, so I hope these tips will smooth the way for somebody else.

Note also that the BTT github page for their TFT-series displays is quite active. Somebody recently submitted a merge request for some changes to improve RRF compatibility, but those changes don't come close to doing what the Thro42 fork does. It's possible that a future merge will do so, though.

FWIW, I've now done a test print with the filament runout sensor properly configured and connected, and my temporary thermistor installed. It all worked fine this time. I've still got to fine-tune the printer in various ways, but that's another matter....

@dc42, the configuration does have an M591 line for a filament runout sensor that I hadn't actually plugged in at that point, so that's likely the cause. I've now hooked up a spare thermistor in place of my PT1000 probe, but I haven't yet had time to do anything else with the printer. I'll be sure to either comment out the M591 line or hook up the filament runout sensor before my next attempt. Thanks for the tip; but as a suggestion: If possible, it might be good to make the error message point a little more unambiguously at the cause.

On my first test print (of a Benchy) from a SecKit SK-Go2 that I've built with a Duet 2 WiFi, I received the following error two or three times on the first layer:

Printing paused
Extruder 0 reported 'noDataReceived'

I was able to resume printing and it would work again for a few more seconds, but after this happened a few times on just the first two layers, I canceled the print.

Eventually, on a subsequent attempt with a fresh slice of the model from a different slicer, I got a heater fault and noticed that one of the very thin wires to the PT1000 temperature probe I'm using had detached from the PT1000 probe. Obviously, this is a bummer, since I've now got to get a new PT1000 probe. (I may have a spare thermistor I can use in the meantime, but I'm not sure it's worth the effort to wire it up for just a few days.)

I'm assuming that the "noDataReceived" error was related to the eventual total hardware failure -- that the connection was weak and so I was getting sporadic failures that didn't quite trip the full-on heater fault. Does this assumption seem correct, or is there some other probable cause of the "noDataReceived" error that I should be investigating?

Thanks, @Phaedrux. Oddly, the problem seems to have disappeared; I've posted a couple of threads and some replies in those threads this afternoon with no problems, although I was banging my head against the wall with this issue earlier today.

Thanks for the suggestions. I'm using a Zesty Nimble, so there's no Bowden tube, but the Nimble's drive cable should serve the same purpose. FWIW, I've been using this with the wires tied to one of the diagonal rods for strain relief, but I suppose the Bowden tube/Zesty Nimble cable might work better.

I'm doing some upgrades on a Robo3D R1+ printer, including replacing the motherboard with a BigTreeTech SKR Pro running RepRapFirmware, along with a BTT TFT35-E3 display panel. I've verified the below using another printer with a genuine Duet 2 WiFi, so I don't think it's specific to the BTT SKR Pro or the STM32 port of RepRapFirmware. Both motherboards are running RRF 3.2-beta3.2.

The problem I'm having is that the TFT35-E3 can't reliably get a list of .stl files from RepRapFirmware. When I go into the "print" menu on the panel, I can print from a USB flash drive or SD card, but when I click the option to display objects on the main control panel, it displays a "Loading..." message and then hangs. I can issue other commands (to move the head, heat the bed, etc.) without problems, so it's not a general communication issue; it seems to be limited to the M20 command specifically. This is with the very latest firmware from BTT's github, as well as with the bcmob and jimmymadDness forks of BTT's firmware recommended on the gloomyandy RepRapFirmware fork's wiki. (These forks make changes designed to make the display more friendly to RepRapFirmware.) I've also tried both with and without an "M555 P2" command in config.g. I've also tried a variety of baud rates, from 19200 to 115200.

Furthermore, the panel includes a g-code entry feature. Most commands (G28, M115, etc.) produce reasonable and expected output and/or printer activity; but if I type M20 in the g-code entry area, I get nothing back; it just hangs at that point. I'm able to print files from the SD card slot on the TFT35-E3, so I don't think the connection is generally flaky.

I have no problems with a PanelDue, even when I set "M575 S3", the same as I use on the TFT35-E3. I've tested all combinations of the TFT35-E3 and PanelDue on both the Duet 2 WiFi and BTT SKR Pro, and the problem follows the TFT35-E3; it's not restricted to the BTT SKR Pro.

I find it odd that the RRF-specific variants of the TFT35-E3 firmware don't work. I've examined the source code, and those variants include lots of code that's obviously designed to better handle RRF file listings. My best guess is that something has changed in RRF, perhaps with the shift from 2.x to 3.x, that's causing them to stop producing output because of some quirk of how the TFT35-E3 is feeding its commands, but I'm pretty much out of ideas at this point.

Does anybody else have any suggestions? Thanks!

I bought something similar, but it's not really helped. I can't seem to find my order confirmation, so I'm not positive exactly what I got, but I think it was this:

https://www.digikey.co.uk/product-detail/en/molex/2451320605/WM15769-ND/6565376

It helped with one fan connection that was similarly unreliable, but it didn't really help with the heater cartridge connection. I tried this originally with the v1.3 board that's now completely shot. When the problem began to recur with the v2 board, I started over with a new Molex connector, but it's not helped. I'm considering bypassing the Smart Effector entirely and wiring the heater cartridge straight into the supply wires.

I really wasn't expecting that to go through. More details (we'll see if the forum relents and lets me post): I've tried posting a couple of messages in the past few days, but they've always been flagged as spam (until just now -- see below). I've tried:

• Using multiple browsers. (Normally I used Firefox, but I've tried Chromium and Safari.)
• Using multiple OSes (Ubuntu Linux, macOS, and Android).
• Creating a secondary account (I'm using that now; my original account was srs5694).
• Connecting via my normal ISP (Cox Communications in Rhode Island) and via my cellular ISP.

Until this thread, my posts were all incorrectly flagged as spam. When my first post to this thread went through, I went back and tried my latest post, and the forum accepted it, with no changes whatsoever to the text.

This problem has spanned several days and has been very frustrating! The forum maintainers really need to look into it.

I'm having problems with the power to my hotend heater cutting out. I originally had a v1.3 with this problem. I repeatedly re-wired and replaced the cable-end connector, tested continuity, etc. It appeared that the connectivity would break as the effector moved around. After a thermal fault event, I could usually recover temporarily by jiggling the "input 1" connector, but the problem would always recur, often multiple times per print. The only thing I could find that would help for longer periods was to jam a small amount of aluminum foil into the connector, which presumably made for a more stable connection. Eventually, though, the Smart Effector gave out completely; it failed and I just couldn't get it to recover.

I replaced it with a new v2 Smart Effector, but it's begun to develop the same problem. Again, I completely replaced the cable-end connector with one with a built-in strain relief, but the problem has recurred and is just getting worse, after less than a month with the new Smart Effector.

Does anybody have any tips on how to get this to work reliably? Thanks!