Printing from SD card

Printing from SD card

[repetier]

The changes had nothing to do with the SD command and didn't change anything of the related code. I even rechecked the sd card on my board and it is still working flawless.

The first question is when do you get the error.

1. The start print command issues it - just restart
2. You get it during print - hardware problem
   The data is stored including checksum. Could be a write or read error on that file. Try uploading a small file and recheck. Try also with fan disabled (I remeber you having added a fan). SD cards are quite sensitive on voltage fluctuations.
   That you succeded uploading a file shows that your card is more or less working. The only questions is what triggers your error.
   You could also upload a file on your pc eliminating possible upload errors.

Thanks Repetier, I'll try that. BTW with the latest release the extruder hotend (pin 13) no longer works. Adding the simulate pwm for the fan/heater seems to have stopped it working? The previous release works OK with the simulate_pwm_fan defined.

I have had a further look at this. I can use the SD card to print using Sprinter firmware, so the actual SD card/hardware is OK. There are two issues- firstly with repetier firmware, I'm using binary comms - this gives binary files on the SD card. Changing the comms to ASCII gives ASCII files, but they still don't print and simply seem to be ignored. I'm wondering whether this is somehow related to the timer interrupts and the changes to allow simulated PWM?

I will do some further investigation and let you know which version of repetier work on my hardware with SD card and which don't.

[repetier]

Just for your information. If you upload to sd card, the file is always written in binary mode independent of the communication settings. Running ascii files is nonetheless possible.

Connection to simulated PWM - maybe. The PWM simulation needs computation time in interrupts. Maybe the interrupts disturb the sd reading timings, but I doubt it is the reason. To validate that, you could disable the software PWM in the configuration and test.

Tried disabling PWM simulation, but this didn't make any difference. I'm using sangiunololu 1.3a. I wondered about communication as the files generated by repetier on SD card contained rubbish - looked like binary. I copied some gcode directly onto card and while it seems to 'print' from SD card, it doesn't actually print anything. Using same file/repetier host to sprinter firmware prints OK. I'll keep looking at this. What hardware are you using?

[repetier]

Yes, files send through repetier-firmware are stored in binary format including checksums (which is why you can get checksum errors reading them).
The firmware is also able to print ascii files just copied on your computer to the card.

What did you mean with "it seems to 'print' from SD card, it doesn't actually print anything". Did the printer move and extruder didn't do anything? This can happen if the temperature is not set correctly.

My hardware? A Gen6 board and sd card with bidirectional level shifter and short connection. With longer connections I always had errors with my card.

By "it seems to print" I mean that with ascii files the program shows that it is printing the correct file, and then appears to send it (very quickly) and shows print finished, but he reprap doesn't make any movement or changes. With binary files I get checksum errors, with ascii, I get no errors but no motions etc. I have manually ensured everything was at working temperature before trying to print, but had same result.

BTW I much prefer the prints from repetier than sprinter - much better quality, which seems to result from better control of steppers and if I can't get SD card going will probably remove it rather than use sprinter - keep up the good work :-)

BTW I using http://reprap.org/wiki/Sanguinololu_SD for SD card.

Repetier will print OK if the file was saved on SD card using Sprinter,but if saved using Repetier I get:

19:27:00.265 : File opened:rep2.cod Size:34201
19:27:00.265 : File selected
19:27:00.984 : Unknown command:
19:27:01.062 : Error:Binary cmd wrong checksum.
19:27:01.062 : Unknown command:
19:27:01.062 : Unknown command:
19:27:01.078 : Error:Binary cmd wrong checksum.
19:27:01.078 : Error:Binary cmd wrong checksum.
19:27:01.078 : Unknown command:
19:27:01.078 : Unknown command:
19:27:01.078 : Unknown command: F0.00
19:27:01.078 : Unknown command: P0
19:27:01.078 : Error:Binary cmd wrong checksum.
19:27:01.078 : Unknown command:

Almost like it is incorrectly parsing the command from the start. Is it useful to see the actual files?

[repetier]

Ok, what we could do is the following. You send me the original G-Code you send to the printer (please add start and end code in this file at the proper position). And a copy of the uploaded binary file.I will then try to upload the same g-code and compare the binary files and try to run them. Let's see what will happen or if the binaries differ. Depending on that, we should set our further search strategy.

Thanks, how do I upload files for you to look at? I can email you if that's easier my email is [email protected] regards

Wayne

[repetier]

Yes email is better. Mine is [email protected]
I will check the files when I'm back from work.

[repetier]

The sd card errors are solved in version 0.49.