With the recent surge in Omicron cases, shipping may be slower than stated times. We are working to build, ship and respond to everything as quickly as possible. Please see all COVID-19 updates here. Thank you for your continued support.

Member #533067

Member Since: March 18, 2014

Country: United States

  • Agree with everyone here: I bought these some time ago and threw them in my parts bin. I just broke them out to use and saw the crazy pinout. Well past any exchange date now, but had I noticed the difference (and who would ever even look, because who would ever lay one of these out non-standard?) I would never ever have bought this, and I'll never buy this again. Why don't you fix it and offer a new product, and why haven't you even responded to all these people who have a very valid grievance? You guys are better than this!

  • So to ask the obvious but unasked question, since the specs of the wiznet 5200 and 5500 chips (and therefore the shields based on them) are so similar, is there a burning reason to switch to the 5500-based shield? Is the 5200 chip or 5200-based shield going obsolete? I make a product built around an Arduino Ethernet board; does the 5500 shield do something better/cheaper/faster/more reliably (notwithstanding the issue of Mega reset compatibility -- I'm using Unos)?

  • Excellent article. Months ago I had peeked at this and got scared and ran away. Nice to have a friendly guide with a machete. A related question: I've routinely done C programming for Atmel in other environments like Imagecraft and have never figured out how to use the Arduino IDE to upload a plain old hex file produced elsewhere. Reasons for doing this range from being able to upload via serial instead of an AVRISP Mkii, and notably the incompatibility between the AVRISP's JUNGO USB Driver and Arduino's. Any tips on how to take a standard hex file and cover it with the secret sauce to make the Arduino uploader eat it like a regular Arduino .ino file? Are there structural reasons that make that too hard (or impossible) or is it just a matter of say, renaming it and making some associated files and putting them in some special place (like the temp folder)? Thanks!

  • Looks cool; but while the data sheet indeed says 46VDC, and 2A continuous per channel, it also says 25W TOTAL dissipation. If that is per device not per channel, I interpret that to mean that if you are running at (for instance) 12.5V, you get 2 amps total to work with for continuous power, not 4 amps continuous; and to get 4 amps continuous, you'd have to be running at no higher than 6V and a 46V you'd be limited to around .5A total for both channels (all of which might be just fine for your app) but definitely NOT 46V continuous at 4A (184W). But I've never even played an electrical engineer on TV, so am I misinterpreting this?

    And for us unfortunate non-EE's can somebody at Sparkfun please, please translate the data sheet's note:

    "The external bridge of diodes D1 to D4 is made by four fast recovery elements (trr ≤ 200 nsec) that must be chosen of a VF as low as possible at the worst case of the load current. "

    into "buy this part number diode for a 12V motor between .5 and 2A, this p/n diode for 24V 4A," etc. (This is why I'm still using LMD18200s with all that integrated :-). Thanks!

No public wish lists :(