Rep 2,problem with mighty board (Rev g) / Mb support just wants to sell me stuff…Desperate for HELP!
960 views
Skip to first unread message
Afra Hackl
Feb 11, 2016, 9:09:23 AM2/11/16
to Makerbot Users
Hey Guys! I would be really glad if you could help me understand the problem! I am not a native englisch speaker and neither a tech geek but I ll try my best to explain.
I have an rep2 from 2013 with a Mighty-board Rev G
Problem description:
1.Power the rep2
2. Display shows firmware version 7.5
3. Red light from M button turns off
4.Display turns off, same moment the SD6 LED on the mighty board starts blinking like crazy
The mighty board doesn’t show any signs of burns, voltage LEDs are working, the fuse is in tact so my guess is its an Firmware issue…?????
BUT I can not update Firmware because neither MB Desktop nor Replicator G are detecting the Rep2, though my Mac book does…(strange!!??)
Shortly before this accrued I Updated from Makerware to MB desktop and I guess I ran a firmware update…maybe it did not receive the update right???
MB support suggested to update Firmware…(funny because no detection!) and next solution was ”buy a new mighty board”…
What are you thinking?
Does someone know what SD6 LED Blinking means?
Should I get an AVR Programmer and try to refresh firmware and if yes do you think i can do it without having much knowledge of code/hardware or is it too risky to get shorts? Or is a new Board the solution?
Just don’t want to waste money and resources if not necessary…
so I would be really thankful for any hint and suggestion!
Afra
Dan Newman
Feb 11, 2016, 1:28:51 PM2/11/16
to Makerbot Users
DS1 - +24V
DS2 - + 5V
DS3 - Debug4 (PH7)
DS4 - Debug3 (PG3)
DS5 - Debug1 (PG4)
DS6 - Debug2 / EXTRA BLINK (PB7)
DS7 - USB TX
DS8 - USB RX
DS9 - Cooling fan
DS10 - Heater A
DS12 - Fan A
DS11 - Heater B
DS13 - Fan B
DS14 - HBP
On 11/02/2016 6:09 AM, Afra Hackl wrote:
>
> Hey Guys! I would be really glad if you could help me understand the
> problem! I am not a native englisch speaker and neither a tech geek but I
> ll try my best to explain.
>
> I have an rep2 from 2013 with a Mighty-board Rev G
>
> Problem description:
> 1.Power the rep2
> 2. Display shows firmware version 7.5
> 3. Red light from M button turns off
> 4.Display turns off, same moment the SD6 LED on the mighty board starts
> blinking like crazy
Sounds like corrupted firmware. DS6 is the "Debugging" LED but it won't
be blinking wildly. There's two cases where it will blink:
a. From USB a ABORT, RESET, or CLEAR_BUFFER command is received. It then
blinks on 4 times, pauses, then 4 times, pauses, repeat....
b. If a heater failure occurs, then it blinks 6 times, pauses, blinks 6 times,
pauses, repeat....
So, if it's doing 6 blinks, pause, 6 blinks, pause then it may be trying to
report a problem with a temp sensor. However, you'd see a message on the
LCD screen as well. It sounds more to me like the firmware needs to be
re-installed.
> BUT I can not update Firmware because neither MB Desktop nor Replicator G
> are detecting the Rep2, though my Mac book does…(strange!!??)
There's USB working and there's Desktop and RepG being able to connect to
the printer. They are two different things.
USB working means that the USB chip working.
Being able to talk to the bot requires (1) USB working, and (2) the bot's
printer firmware working. If the printer firmware isn't working -- is
corrupted -- then you cannot expect to be able to talk to the printer
with Desktop or RepG.
As long as the USB is working, then you should be able to load
new firmware UNLESS the bootloader on the printer is also corrupted.
And if something corrupted the printer firmware then it may well have
corrupted the bootloader as well. To put a bootloader back on just
requires A $10 - $20 AVR ISP programmer and a little knowledge.
Jetguy regularly posts the instructions. Here's a link to a recent post
of his with the directions. (They're for a WanHao printer but they are
the same for your printer.)
https://groups.google.com/d/msg/wanhao-printer-3d/DWLSyOWFbaI/15z81CJFCgAJ
Dan
DS2 - + 5V
DS3 - Debug4 (PH7)
DS4 - Debug3 (PG3)
DS5 - Debug1 (PG4)
DS6 - Debug2 / EXTRA BLINK (PB7)
DS7 - USB TX
DS8 - USB RX
DS9 - Cooling fan
DS10 - Heater A
DS12 - Fan A
DS11 - Heater B
DS13 - Fan B
DS14 - HBP
On 11/02/2016 6:09 AM, Afra Hackl wrote:
>
> Hey Guys! I would be really glad if you could help me understand the
> problem! I am not a native englisch speaker and neither a tech geek but I
> ll try my best to explain.
>
> I have an rep2 from 2013 with a Mighty-board Rev G
>
> Problem description:
> 1.Power the rep2
> 2. Display shows firmware version 7.5
> 3. Red light from M button turns off
> 4.Display turns off, same moment the SD6 LED on the mighty board starts
> blinking like crazy
be blinking wildly. There's two cases where it will blink:
a. From USB a ABORT, RESET, or CLEAR_BUFFER command is received. It then
blinks on 4 times, pauses, then 4 times, pauses, repeat....
b. If a heater failure occurs, then it blinks 6 times, pauses, blinks 6 times,
pauses, repeat....
So, if it's doing 6 blinks, pause, 6 blinks, pause then it may be trying to
report a problem with a temp sensor. However, you'd see a message on the
LCD screen as well. It sounds more to me like the firmware needs to be
re-installed.
> BUT I can not update Firmware because neither MB Desktop nor Replicator G
> are detecting the Rep2, though my Mac book does…(strange!!??)
the printer. They are two different things.
USB working means that the USB chip working.
Being able to talk to the bot requires (1) USB working, and (2) the bot's
printer firmware working. If the printer firmware isn't working -- is
corrupted -- then you cannot expect to be able to talk to the printer
with Desktop or RepG.
As long as the USB is working, then you should be able to load
new firmware UNLESS the bootloader on the printer is also corrupted.
And if something corrupted the printer firmware then it may well have
corrupted the bootloader as well. To put a bootloader back on just
requires A $10 - $20 AVR ISP programmer and a little knowledge.
Jetguy regularly posts the instructions. Here's a link to a recent post
of his with the directions. (They're for a WanHao printer but they are
the same for your printer.)
https://groups.google.com/d/msg/wanhao-printer-3d/DWLSyOWFbaI/15z81CJFCgAJ
Dan
Dan Newman
Feb 11, 2016, 1:38:11 PM2/11/16
to Makerbot Users
P.S. I know for a fact that I one time lost the bootloader on my Rep 2. And, I had
to use an AVR ISP to reload it. (Since it's something I'm quite familiar with doing,
it was not a hassle for me.) But spending $400 for a new board from MakerBot is not
something you want to do; especially if all that needs to be done is to reload the
bootloader.
to use an AVR ISP to reload it. (Since it's something I'm quite familiar with doing,
it was not a hassle for me.) But spending $400 for a new board from MakerBot is not
something you want to do; especially if all that needs to be done is to reload the
bootloader.
Afra Hackl
Feb 16, 2016, 11:45:03 AM2/16/16
to Makerbot Users
Hallo Dan,
first of all many,many thanks for the great, precise explanation and the LEDs list!
I ordered an AVR programmer right away!
I checked the link you send me and started diving deeper into the topic in general.
So far I guess I understand the basics of what Jetguy explains but some new questions came up too.
Am I right that I don’t have to flash the 8U2 with the hex file because my USB connection is working?
As I am a Mac user I am not able to work with AVR burn-O-Mat as Jetguy does, so I installed AVRFuses and I am already failing in giving AVRFuses the right direction to the avrdude conf file… frustrating :) … so I kept searching and found a similar discussion about a Rep1 with the same problem from back in 2013 where Jetguy states:
"…you have 2 options for getting A bootloader onto the mega1280. Both require the same AVR programmer, but one stupidly easy way is use the Arduino IDE and choose atmega1280 as board type, then choose your programmer type, then burn bootloader with the AVR programmer plugged into the 1280 header on the mainboard."
https://groups.google.com/d/msg/makerbot/tBTVx85-hpg/kIglXUGsr0MJ
Is using Arduino IDE still a possibility with the rep2? I am more familiar with Arduino, therefore it would be much easier for me, then getting into communicating via Terminal…
Its amazing that you guys aren’t tiering in spreading your knowledge to everyone interested and in need!
THX A LOT!
Afra
first of all many,many thanks for the great, precise explanation and the LEDs list!
I ordered an AVR programmer right away!
https://groups.google.com/d/msg/wanhao-printer-3d/DWLSyOWFbaI/15z81CJFCgAJ
I checked the link you send me and started diving deeper into the topic in general.
So far I guess I understand the basics of what Jetguy explains but some new questions came up too.
Am I right that I don’t have to flash the 8U2 with the hex file because my USB connection is working?
As I am a Mac user I am not able to work with AVR burn-O-Mat as Jetguy does, so I installed AVRFuses and I am already failing in giving AVRFuses the right direction to the avrdude conf file… frustrating :) … so I kept searching and found a similar discussion about a Rep1 with the same problem from back in 2013 where Jetguy states:
"…you have 2 options for getting A bootloader onto the mega1280. Both require the same AVR programmer, but one stupidly easy way is use the Arduino IDE and choose atmega1280 as board type, then choose your programmer type, then burn bootloader with the AVR programmer plugged into the 1280 header on the mainboard."
https://groups.google.com/d/msg/makerbot/tBTVx85-hpg/kIglXUGsr0MJ
Is using Arduino IDE still a possibility with the rep2? I am more familiar with Arduino, therefore it would be much easier for me, then getting into communicating via Terminal…
Its amazing that you guys aren’t tiering in spreading your knowledge to everyone interested and in need!
THX A LOT!
Afra
Jetguy
Feb 16, 2016, 1:54:33 PM2/16/16
to Makerbot Users
No because the arduino boot loader is not correct for the board
Afra Hackl
Feb 26, 2016, 6:45:03 AM2/26/16
to Makerbot Users
Hallo Dan and Jetguy,
I really need some further help with the final execution please!
I managed to install the driver for the programmer (AVR ISP mkII clone), downloaded Avr8 burn-o mat, learned basics for cmd line… (already quite a challenge.)
So now I tried flashing the board and burn-o-mat simply tells me error flashing, no further specification/explanation in the cmd line…and no orange signal light on the programmer that shows something is being programmed ( check Foto attached)
So just to verify that I understand right:
-Both steps Jetguy explains (first cmd line then burn-o-mat), are executed while the programmer is attached to the atmega 1280 Icsp pin on the board?
I have doubts because Yetguy states that for the first step the programmer should be attached to atmega 1280 pin and then says this gets the 8u2 ready?
-disable auto erase before programming (-D) should be checked/active??? seems a little strange to me if firmware is corrupted, would`t i need to erase first in order to clean up?
furthermore i found this conversation, the guy has exactly my problem and he also refreshed the usb chips firmware (RepG doesnt find usb neather, check foto)
…maybe i should do that too? would you happen to have the .hex for that?
what do you think?
Would be really glad for further help!!!
THX a lot
Afra
I really need some further help with the final execution please!
I managed to install the driver for the programmer (AVR ISP mkII clone), downloaded Avr8 burn-o mat, learned basics for cmd line… (already quite a challenge.)
So now I tried flashing the board and burn-o-mat simply tells me error flashing, no further specification/explanation in the cmd line…and no orange signal light on the programmer that shows something is being programmed ( check Foto attached)
So just to verify that I understand right:
-Both steps Jetguy explains (first cmd line then burn-o-mat), are executed while the programmer is attached to the atmega 1280 Icsp pin on the board?
I have doubts because Yetguy states that for the first step the programmer should be attached to atmega 1280 pin and then says this gets the 8u2 ready?
-disable auto erase before programming (-D) should be checked/active??? seems a little strange to me if firmware is corrupted, would`t i need to erase first in order to clean up?
furthermore i found this conversation, the guy has exactly my problem and he also refreshed the usb chips firmware (RepG doesnt find usb neather, check foto)
…maybe i should do that too? would you happen to have the .hex for that?
what do you think?
Would be really glad for further help!!!
THX a lot
Afra
Afra Hackl
Feb 26, 2016, 6:48:02 AM2/26/16
to Makerbot Users
furthermore i found this conversation, the guy has exactly my problem and he also refreshed the usb chips firmware (RepG doesnt find usb neather, check foto)
…maybe i should do that too? would you happen to have the .hex for that?
Reply all
Reply to author
Forward
0 new messages