RoboxDual › Forums › Technical Support › "Firmware: GCode line too long error"
This topic contains 7 replies, has 4 voices, and was last updated by Andrew Adey 2 months ago.
-
AuthorPosts
-
March 1, 2017 at 9:15 pm #37363
Has anybody seen this error? I just started getting it out of the blue. Tried everything I could think of (unplugging the machine, changing the cable, changing heads, reinstalling software and firmware) but every time I try to do anything this error pops up. Also, home button is irresponsive and axis tests in maintenance don’t go through, the bed moves and then nothing.
I opened a support ticket but I thought I’d ask here. Any suggestions?
Thanks for your help.
Attachments:
You must be logged in to view attached files.March 1, 2017 at 9:20 pm #37366@luis-bustamante Check that the SD card is seated properly and open a support ticket.
I operate two Betas and four Production Robox.
I am the US/Canada Technical Support engineer for the Robox.
See my 3D Hub site at https://www.3dhubs.com/phoenix/hubs/benMarch 1, 2017 at 9:29 pm #37367Thanks for the quick reply. I tried to reseat the SD card but still no luck. I already opened the ticket so let’s see what they say.
May 1, 2017 at 11:06 am #39002I have just started to get this too. Updated to version 3 recently. Three consecutive prints failed at pretty much the same place. I`ll “switch it off and on again” and try to print a small test. Will let you know what happens……
May 1, 2017 at 12:20 pm #39003Hi, I had to phisically replace the micro SD card inthe back of the printer. That fix the problem for me.
May 2, 2017 at 8:42 am #39018@luis-bustamante did you buy a new one or just take the existing one out and put it back again?
If anyone has issues with the microSD card it can be replaced easily. Nearly any type will work. As soon as Robox detects a new card it will put a Robox specific file system on the card which will destroy any other data on the card. No user input is needed, it should work as normal almost immediately.
May 2, 2017 at 12:03 pm #39023Hi Pete, it had to be a new one, the old one was busted.
May 4, 2017 at 3:36 pm #39127Well I jiggled the card in it
s socket gently, AND uninstalled then reinstalled ver 3 of the software and its working OK at the mo. -
AuthorPosts
You must be logged in to reply to this topic.






