Just got mine all hooked up tonight and am having these exact issues. I tried all of the above and still get the sd init error and the halted message. I just came here to ask about it and seen this post
@jeffeb3 Rambo 1.4 and the same screen that op showed. I can start it all up move to opposite corner, click home and about halfway I get the halt error and have to reset. Also no card I try can be initialized. This was just ordered a few weeks ago so not sure if it is from the same batch as the op
You just move the tool within 12" of the home before you home.
It needs to be set to something in the firmware. We chose 300mm arbitrarily. We just changed it to 600mm, but we haven’t released that change yet.
The reason for this limit is that without it, if you have a problem with your endstops, the machine will try to move 300mm/600mm past the endstops before quitting.
Unfortunately, it isn’t something you can change in gcode. But if you want your machine size in the firmware, then you can change BED_SIZE and recompile it.
This is getting pretty off topic though. Feel free to open another topic to debug your issues.
I had some time this morning. I tested a few previous versions of firmware. No luck. Best I can figure is a bad board.
Since I do not have any Rambo’s in stock, and won’t for a while we have a couple options. I can take it back and refund you, or I can try to get a direct swap from Utimachine. Let me know what you prefer and your order number so I have all your info.
Yeah I tried the firmware too same issue, is it possible it could be the screens? I really like the layout of the board and would like to have the same one My order number is 15472
Ok weird thing happened tonight, I turned it on just to move the axis to the back so I could use the workspace for a project and no more SD init error. I unplugged and removed the memory card a few times and no issue. What could of changed?
So it’s a random thing, tonight it has the error again. Maybe I’ll let it get cold in here again and see if that is a factor. @vicious1 have you tried the screen you had the problem with on a different brand board? Just wondering what the possibility of it being the screen or card slot.
Ok scratch my last thought I am just the FNG here trying to figure it out and help lol. So I tried a micro sd card in an adapter and reads fine every time, put any full size sd card in and error. I can read the gcode files now off anyone of my micro sd. Hope this helps everyone
I had mixed results with different SD cards. I had an ancient 7 year-old SD card that would initialize, and the machine could apparently read. However, during the cut, the cutter started carving randomly all over the work - destroying it. Reading the very same GCODE file from the computer, off the very same SD card and printing over the USB cable produced a quality cut. If you can do with shorter ribbon cables, I would shorten them as much as you can tolerate. These ends are cheap and fairly easy to press-on. A vice is a great way to press them with even pressure.