Are you connected to your network by LAN? Try unplugging your LAN cable and see if it boots up.
Thanks for your reply. I burned the img file, you provided, into a 32GB µSD card. Then opened the bottom of the cover of OLIMEX board and inserted the µSD card, then turned ON the system. Nothing happened, just as before no lights, no LCD, only fan at the start. What does this means, should I look further into opening the OLIMEX board and debugging the issue. Or this means some hardware is damaged in the board and I have to buy a new one?
@twlum I did try taking taking out the LAN cable and starting it, no luck.Edited by BirBikram
Does anyone have bought an Olimex board from either fbrc8.com or shop3duniverse.com ?
If I have to change the motherboard might as well start sourcing it.
fbrc8 is the official Ultimaker distributor for USA, so it should be your first choice if you're from USA. And @fbrc8-erin is very active and helpful in this forum.
- 2 weeks later...
@Enigma_M4 Thanks for letting me know.
Still not sure if my situation requires me to change the board, if it is then I will buy this board.
Can anyone confirm that this is the only option I have?
If the recovery image didn't work, then I think it's very likely you need the board at this point based on the LEDS not responding. If the LEDs were at least lighting then I'd recommend trying a new HDMI connect to the screen first.
@BirBikram is it a UM3 or an S3? Can you please confirm? I see S3 mentioned in your first post, but the S3 doesn't use an Olimex board.
Thanks for your reply. I have the Ultimaker S3, I thought I saw an Olimex board inside it too. I will go check properly on Monday.
Correction we have the Ultimaker 3 not S3.
- 2 weeks later...
Thanks for confirming @BirBikram. The UM3 does use the Olimex. The S3 uses a SOM board. If re-imaging the Olimex board doesn't do the trick, I'd go ahead and replace the board.
Rather than pay $500 you could just get a new main board. Which is a similar price I think. Anyway...
Did you update to firmware 7.X? There seems to be an issue with that. If not then it's probably the "hard drive" on the S3 (actually it's flash memory built into the linux computer). Usually you get a few bad blocks but the flash should know to use a new location next time so you can just do the "unbricking" procedure which reinstalls everything. more info here:
Also I wrote a TON about this here:
One (older) recovery image for S3 (213482 = S3):
Link to post
Share on other sites