-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Repetier firmware configured with SD_EXTENDED_DIR=1 M20 returns filenames with sizes, sdprint <filename> fails #848
Comments
This should be fixed in the 2.x branch - can you verify? |
|
Well spotted, just changed that. |
Thank you. My specific testcase was with a uSD card that came with Anet A8 and Repetier FW that I installed to it. I hoped to use pronsole to script enabling the bed heater, then uploading a file to the card, then starting the actual print (so that relatively slow upload speed wouldn't matter as the bed takes time to heat no matter what). However, the firmware reports busy when heating the bed and so pronsole doesn't try uploading during that, heh. Regarding the filenames, I haven't removed anything from the card and here's what the firmware replies to M20:
This obviously leads to "Got rubbish reply" from pronsole when it tries to parse this reply. Also, all filenames are truncated to 26 characters. |
You can set the bed temperature without waiting for it to reach it, do |
I know it should be possible, and I have seen it working few times, and few times not working (with the same script), and I was too demotivated to dig it further, I had an impression it's the firmware itself preventing the upload. BTW, the gcode already has command for waiting for the setpoint, so starting sd print should be enough. |
Well I can't help you with your firmware unfortunately, but thanks for helping make printrun better. |
You might want to consider this usecase as essential and add a special feature to printrun so that a user could just press a button and have his or her bed heated while transferring the gcode to SD card and then print it safely from there. I've seen few requests like that on "the forums". Then if some firmware would be misbehaving it would be easier to spot and fix, I guess. |
I don't see the use case as essential at all - most people that do that sort of thing make a macro to preheat everything and have a button trigger that macro, and everyone seems to have their own opinion of what should be happening when preparing for a print, and that's okay. I'd rather not add a special case like this. |
Yeah, ok, I'm not someone to judge, thanks for your attention :) |
Example M20 result line:
This makes sdprint require not only filename but also size because this is what gets stored in the sd card file list.
I suggest to strip off a decimal number if it's appended after a space to a filename.
The text was updated successfully, but these errors were encountered: