You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The question is about SKR MINI MZ V1.0 and TFT35-MZ V3.0
Symptoms:
When I add new .qcode file to my SD card and put in mainboard, then in touch mode I have error with card or files reading (I can print from card only in Marlin mode). After deleting any file the card worked properly in touch mode.
It looks like there is a limitation on the number of files or characters used in files for using the SD card inserted into the motherboard in touch mode. Can someone explain to me what is wrong with having more than 72 files and 4 directories?
I think, if it works well in Marlin mode, it should work well in touch mode too. Could I have messed something up in the configuration?
The text was updated successfully, but these errors were encountered:
I have noticed a new behavior after deleting a number of files, when SD cards inserted to mainboard is read and all files are visible correctly. In touch mode I try to start printing from file and I only hear short 3x BEEEP and it does not print. No other message.
Printing from this same file in Marlin mode without problems.
Where to look for the cause? Is it the fault of Marlin firmware or BIGTREETECH-TouchScreenFirmware?
The question is about SKR MINI MZ V1.0 and TFT35-MZ V3.0
Symptoms:
When I add new .qcode file to my SD card and put in mainboard, then in touch mode I have error with card or files reading (I can print from card only in Marlin mode). After deleting any file the card worked properly in touch mode.
It looks like there is a limitation on the number of files or characters used in files for using the SD card inserted into the motherboard in touch mode. Can someone explain to me what is wrong with having more than 72 files and 4 directories?
I think, if it works well in Marlin mode, it should work well in touch mode too. Could I have messed something up in the configuration?
The text was updated successfully, but these errors were encountered: