7 replies to this topic

[adam8797]

I'm coming here, because I couldnt find a dedicated support email anywhere. 

 

As far as I can tell, my go is dead. Im not sure what happened, but here is what it does:

 

1. I plug the go! in.

 

2. The lights turn on briefly, and then go out.

 

3. the STM32 chip gets very very hot very very fast. I cant keep my finger on it for more than a few seconds before I have to pull back.

 

 

Is there any way I can get this replaced, or will I have to buy a new one. I only got it a few days ago.

[Chris Walker]

Hi adam8797, No fun at all If you just got it, give your Netduino authorized reseller a call and they can swap you out for a new one. BTW--any idea what you were doing right before the board died? Chris

[adam8797]

I really cant say, I was working in porting some arduino code for the [Nwazet daq, I went to deploy and I noticed that the lights were off. It may have been a fault with my computer, I dont know. Also, I got the Go! starter pack from adafruit, do you know if they will take just the main board back or will I have to package everything and ship it back?

[adam8797]

Also, I had two modules attached at the time. If there was some kind of power surge or a short somewhere, I want to make sure the modules are OK too.

 

I had a [Nwazet daq, which appears to be OK. I attached 3.3V and Gnd from a regular arduino to its jtag and it lights up, but I cant confirm everything works.

 

Second I had a shieldbase hooked up. There are not leds on it, so I cant get feedback from that. Did I hear somewhere that it can run as a standalone netduino? If so, I could confirm that it works that way.

[Chris Walker]

Hi adam8797, One of the nice things about Netduino Go is that it has self-contained modules which take care of the kinds of electrical issues that could damage a board. But that doesn't apply to GoBus modules like the Shield Base (which lets you attach more modules and access power rails directly) or 3rd-party accessories like the [nwazet DAQ. Chris

[Chris Walker]

Regarding the damaged mainboard...we rarely ever see Netduino Go boards get damaged. Let's make the exchange simple for you. You have PM.

[DaveFer]

Chris -

 

I have the exact same problem: My Go! appears to be dead. (Perhaps also my ShieldBase, no way to tell.)

 

When I plug in my Go! none of the port lights illuminate, only the main white LED by the micro USB port.

 

It is not recognized by MFDeploy nor the STDFU tools.

 

Yes, I've tried putting it in bootloader mode by holding down the button while plugging it in.

 

The last thing I was doing was I had the LadyAda Motor Shield attached to the ShieldBase. I was attempting to use a MotorShield.cs port that I had gotten from this forum. I had made some changes to make it compatible with my Netduino Go!

 

First attempt to deploy my project failed and that's when I realized it's dead.

 

I bought my Netduino Go! around last Christmas. Can't remember where I bought it from.

 

Please tell me I don't have to buy a new one.

Should we not be using the LadyAda Motor Shield with our ShieldBase? It has a PWR jumper near its external power block ... I had the jumper OFF so as not to damage the Netduino components.

 

Thank you!

 

    - Dave Ferreira

[Chris Walker]

Hi Dave,

Is the motor shield trying to pull a high amount of current (motor power, etc.) from the Shield Base?

On Netduino Go...if you plug it in and the blue LEDs do not turn on briefly (using the current firmware) then it is either in a bad state or damaged. Do you hear any buzzing from the board? Are any of the components abnormally warm? If you press the pushbutton with extra force while plugging in the board via USB, does it then go into bootloader mode?

BTW the components you plug into Netduino Go do share electrical resources--but we tend to over-engineer things so there's a reasonable chance that--if some board was damaged--that some or all of the remaining boards are okay.

We never like to see a board get damaged though. No fun at all

Chris

P.S. You have PM. This may be a circumstance where our engineers can get more input on how boards are used in-field...and I have an offer for you