×

SparkFun Customer Support will be in a staff training from 2pm-5pm MST today Sept 17th. Please feel free to reach out to us via email during that time or reach us through phones and chats starting again tomorrow at 9am MST.

avatar

CrustyCarbuncle

Member Since: January 4, 2006

Country: United States

Profile

Bio

Aging medical / communications applications programmer with a strong predisposition towards embedded hardware.

Role

Stealth programming consultant with strong desire to remain undisturbed in my basement.

Organizations

Not much of a joiner...

Spoken Languages

English, nothing else useful.

Programming Languages

C, C++, various ASM's, Python, JS, others I'd prefer to forget.

Associations

Association of Persons with Dissociative Personality Disorders (ADPDP).

Universities

Various, all of which would rather forget I ever attended except when they want money.

Expertise

Telemedicine applications, embedded wireless machine-to-machine applications. Some user interface, HAM radio, CNC & 3d related (gcode! yegads! the worst language design of all time!)

Interests

CNC machining, thinking about making stuff.

Publications

Nothing memorable.

  • @Santa Claus Impersonator: Thanks for fixing the documentation links. There are still several points of confusion for me as a new user of this board. The chip has so much flexibility it leaves me somewhat muddled. Programming through the Linux version of the Arduino IDE (1.89) using the default variant.cpp file it seems that the async port known as 'Serial1' corresponds to the D1 & D0 pins. The compiler does not recognize 'SerialUSB' as on the SAMD21 Pro RF, but opening & writing to just 'Serial' appears to send output to the onboard USB connector which appears in Linux as some variant of /dev/ttyACM[x]. Is this correct?

  • Where is the datasheet and the Graphical datasheet? Links: https://cdn.sparkfun.com/assets/c/a/8/6/8/ThingPlusSamD51a.pdf and https://cdn.sparkfun.com/assets/0/0/5/9/2/60001507C.pdf are dead as rocks!

  • Nice board! Love the Feather compatibility. But it seems even harder for old fingers to get the bootloader right than the SAMD21's!

  • It is probably just my fat fingers, but I have been concerned for some time that the reset button would eventually fail. Now it has.

    I'm not certain what the logic of the narrow 'neck' of the board is, it looks reasonable to keep the switches out of harm's way, but it (for me) awkward and causes me to have to hold the board very tightly when I have to 'double click' to initiate an upload. Since I have to do this about ten times for each successful upload, this puts a LOT of stress on the switch.

    From now on I am going to wire an off-board reset for development on M0 boards.

  • What is an H.FL connector? How is it different from a u.FL/IPX connector?

  • I completely agree. I have purchased several of these, but it is impossible to understand the pin out without recourse to the Eagle files. At least I hope they will make things clearer. I don't have Eagle installed so I haven't had a chance to check.

    SparkFun should be ashamed about situations like this.

  • Yes, I have the same experience. This definitely does not fit the ServoCity/Actobotics (now sold by SF, as well) 'HiTec' compatible accessories. Neither do some Spektrum servos I have.

    Are they 'Futaba' compatible? I don't know...

    This arbitrary lack of compatibility between seemingly interchangeable devices is frustrating to me as someone not otherwise in RC planes, etc.

  • I've been fiddling to make this capability for myself for a long time. Never got it finished, of course. I picture it attached to an app that would respond only to selected SAME region codes and pop up a web page that aggregates relevant information. Useful for Ham radio people and weather spotters and anyone interested in such things.

  • I just received two of these along with two of the medium servos. Quite a nice claw for the price! But I'm not so sure the claw and the servo are such a match made in heaven. Though I can assemble things to generally resemble the stills and the video, everything seems twitchy at best.
    The servo does not really fit the existing hole in the assembly as I would expect it to. The long screws holding the servo in place are not quite straight, and it seems that a good bit of screw re-tightening would be required to keep everything working for very long.
    Perhaps someone with more experience using servos can say if this kind of spec mismatch is the norm, or just me worrying. This isn't a criticism of the arm, it just doesn't seem to be such a perfect fit to the servo as is indicated.

  • What about the memristor, the properties of which depend on both current state and the history of the system? HP announced their implementation two years ago today.
    See:
    http://en.wikipedia.org/wiki/Memristor