-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Today's merger of PR has created new problems. #1297
Comments
The lost machine settings switching from marlin to touch mode is due to PR 1244 that moved the initMachineSettings funtion from main.c to mode.c |
It looks like the commands are getting mixed. can you try with reverting changing from this PR #1276? |
The |
I'm having also different Problems now with New FW from TFT (will create a new Ticket) Layer 1, Layer High 0,16 shows me 2,00mm and if i click on preheat bed only preheat PLA its starting tonpreheat and jumps lo load/unload extruder window. If i'm canceling print it unloads the filament completely. |
Hi, I don't know if you saw my last post in Issue #1294 that I reported, but for the issue where the SD card on the board is not available from the touch mode; if you disable "#define LONG_FILENAME_HOST_SUPPORT" in the Marlin firmware, the SD card becomes available again, at least for me. I think this is a big clue into what is going on here, but more importantly, can give users a work around while a fix is being developed. The only other thing I noticed with the SD card on the board, and maybe this is expected behavior, is that if you switch SD cards without restarting the machine, it freezes on the screen Loading... when you try to access the SD card from touch mode. |
New finding |
@radek8 |
Even if I turn off long name support on TFT, the behavior is still the same. |
Hi Radek. What is the status of the reported issues?
Please let me know Thank you |
|
OK, thank you. |
Yes, PR #1305 solves the problem of losing printer parameters when switching from Malin mode to touch mode. |
The problem with loading SD on board persists. |
Thank you BTT for merging the two PR's. Radek I have some time today, so I can help you with the SD Card issue. Just checked and I am using a firmware from nov. 15th at the moment and everything works fine. I can select a file from the on board SD card directly after power on, without selecting another storage device first. I will check the fw which is available right now with the two PR from above and let you know. |
Somehow my printer is not good for testing. I can not reproduce the issue with the on board SD card using SOR E3 DIP mainboard Marlin 2.0.7.2 and TFT 35 E3 v3 with FW from today. I was able to select the on board sd card without the need to select another storage before. |
Oldman if you can't reproduce the same error with an SD card, with the same FW in TFT, there will be a difference in Marlin |
nono. I can reproduce it now.... SORRY! Does not matter if the sd card is already inserted at startup or not, accessing it as the first possible "storage" device brings up the LOAD... forever. Could you please try to find out which PR caused this? Thank you |
demonstration of SD card behavior on board |
@radek try to revert pr 1272. It changed m27 polling interval. Maybe it causes the freeze. You should see the polling from the terminal. However I don't have that problem |
I have another finding. |
Please edit you messages so PR numbers link to the respective PR. Test and report pls. |
Just for a correct information, It was a Heap/Stack issue not a RAM issue. However in a new PR, line 300 on parseAck.c must be removed. It sets m27 auto report even during no print.You can see the periodic reports on terminal menu. |
All filenames are presented in a new line, so there's an "\n" after each filename. There is no single message from Marlin that can exceed 512 bytes. |
So I tested. 1combination 2nd combination 3combinations |
Other findings. It's crazy behavior. |
I finally saw the issue with 1 and 2 files on the sd card. |
I still think it's a RAM issue. Filesystems need a lot of RAM. |
Why does it work when you select another storage device before? |
I really don't know. I do no t have SD Onboard so cannot test this issue. On my side everything works fine (no onboard SDCard). |
It is L1 handled as a circular queue in function SynchL2cacheFromL1 in parseAck.c |
??? |
I updated my TFT firmware yesterday. |
@kisslorand |
OK. I have been testing a lot with my TFT35 E3 v3 based printer and I would like to add @mehmetsutas to this ticket. Seems that his code brought a great new feature, but also caused some new issues. In general I can see 3 issues:
Or in terms of issues introduced by the PR's: Latest firmware: I have also seen issues where the filename on the storage was destroyed after a print and also that the print time was not reset after a print, but I am not able to reproduce them at the moment. @mehmetsutas |
@kisslorand |
@oldman4U about the layer issue I will create a new PR. I will keep the old logic for TFT SD and TFT USB prints and use the new logic only for BOARD SD prints. I think this will solve the issue. About the new screen please send it to [email protected]. Let me have a look If I can manage and if there is enough space for new icons on TFT, I will do it. |
@oldman4U |
Jut an update. |
#1319 is there for updating the layer during print from onboard SD, not for the onboard SD browsing bug. |
Okay, I'll revert to a working version. Thanks |
The integrated card works if you open the SD card to TFT first |
Cheers @radek8 I'll do that for now. |
Thanks for the 48K hint, I think I am on something.
I think I found something. Later edit: |
👍🏻
kisslorand <[email protected]> schrieb am Mi. 2. Dez. 2020 um 00:09:
… @digant73 <https://github.com/digant73>
on BTT TFT35 you have at least 4 serial port used, so (with a 4K buffer
size) a minimum of 16K will be allocated on the heap. Adding other
dynamically allocated data here and there, the system goes out of heap
space.
You (and me) don't have the problem because our TFT uses 3 serial ports.
If from the total amount of RAM (48K) you also remove the stack space (a
minimum of 4K on BTT TFT35) there is even less space reserved to the heap
(a minimum of 20K on BTT TFT35)
Thanks for the 48K hint, I think I am on something.
@oldman4U <https://github.com/oldman4U>
1. Accessing the on board sd storage
build from Nov. 18 and build incl #1272
<#1272>:
No problem at all, all storage option can be access at any time
build incl all PR from Nov. 30th: Accessing the on board SD card right
after turning the printer on gives a Loading ... forever. Accessing another
storage before accessing the on board SD card solves the problem. This is
independent of the number of files and happened also with a single very
very small file (less than 400kbytes).
I think I found something.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1297 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM6XKZAGEPXIZLPGTT7XJI3SSVZSPANCNFSM4UFJDBJA>
.
|
@kisslorand Thanks for your hard work. |
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. |
Today's merger of PR has created new problems.
If the map has a connected display, after turning on or restarting the printer, I sometimes run the command M1 - pause, which is waiting for confirmation.
This is due to the fact that after switching on, the command M105 is sent, which is damaged and changed to M1, see the picture.
Further communication is without errors ....
It may be caused by interference to the cabling, but did not occur before the update. I'm trying a shielded cable.
Another problem is that when switching to marlin mode and back, the display loses configuration information and therefore SD on board, autoleveling and more are not available. the configuration must be restored with command M115
The SD card on the board is not available from touch mode.
freezes on the screen Loading ...
https://youtu.be/mmgQ0Ade15k
https://youtu.be/sUg0jyHNQCg
The text was updated successfully, but these errors were encountered: