Due to the impacts of the coronavirus outbreak, we are experiencing longer than normal lead times on certain products. We encourage back-ordering out-of-stock items to receive them as soon as possible.



Member Since: January 25, 2013

Country: United States

  • I own one of these Swift Pro's. I got in on the kickstarter. I have had it for about 2 months now. It sort of surprises me that SparkFun would offer this product at this time. The reason being is that it simply is not ready for prime time. The software is very buggy, Many things just aren't implemented yet. Documentation is simply not there. I have been working with uFactory people to resolve many of the issues I had immediately run into. We were able to get some resolved, but others are still in the process of being fixed. Two words come to mind here, "Buyer Beware". This is not a full working robotic arm and is not able to perform some functions described in the marketing data. I knew this from the start and bought one anyway. I like my uArm Swift Pro. However, you shouldn't expect to get what they say you will be getting. It's probably best to wait for a while until the software settles down. Mechanically, it's solid. Which is why I choose this particular arm to get. The company is for real and trying feverishly to fix everything. There's just way to much they need to do to get everything working as stated. I will recommend this product for anyone getting into robotics, just be ready to do lots of downloading, searching, updating and communicating with the uFactory people.

  • Hello Kye, Thank you for the reply. A comment from the President of the company is quite impressive and reinforces my confidence in your product.

    Now, as far as the Python "types" being complicated isn't what I was actually trying to get at. It's the "use" of the types that gets interesting. Just look at your example for instance. You have a "List", an iterator calling a method for use in comparison, and your "slicing" that list to use the first to max_blobs items. At least I think that's what it appears to be doing. Again. it's how these data types are used or "assembled" together to form a really cool yet complicated "rvalue'.

    Now, put that line of code in front of a 12 or 13 year old and see what happens. That's why I will not say Python is easy. I won't lie to those trying to learn it. I've been coding since 1975 from Fortran written on punchcards and run on an IBM 360 to Machine code to Assembly language to Cobol, Pascal, Basic, Lisp, C and C with classes, er C++. It's the "obfuscation" issue made so popular by C.

    The fact that Python can allow one-line statements to be constructed with such power can be concerning when trying to promote the technology. Sometimes it's better to have "easy-to-read" code then compact super-duper fast code. But, your example really isn't clever or unique or even impressive. It's pretty much standard stuff for Python. And that's the crux of my point.

    In any case, good luck with the M7. I look forward to receiving mine soon. And thanks again for the link to the code on GitHub.

    PS - Shouldn't there be a colon ":" at the end of your example statement above? :))

  • In defense of the M7, I humbly submit this reply... ><> Yes, your right in some aspects. I hear what your saying. However... The speed issue based on compiled versus interpretive isn't an issue for a 216Mhz headless embedded micro. At least not with me. Forced indentation is ok with me. Eliminating the curlies just seems to clean up the code by getting rid of some noise. And it tends to help conformance issues resulting in common coding tactics. Compile time errors are syntax errors. Good coders like you and me don't make a lot of them. So, no biggy here either in my view.

    Now, I will say this. uPOS is not, in my view, an "Operating System". It's more of an "Operating Environment". I like the Arduino world for the simple fact that there is no OS per see. You have Setup() and Loop(). Period. Perfect. The embedded micro does one thing and it does it very well. Just like micro-python where it runs main.py. Period. I have a pyBoard and am learning Python using the uPOS it provides. I am doing this while I wait for my uArm Swift Pro robotic arm to arrive which will be coming with an M7. I got in on the kickstarter which is shipping product now. I'm going to have the M7 talk to the pyBoard which will talk to the Arm to simulate an autonomous entity. The M7 will be its eye, a microphone for an ear, an Emic 2 for a voice, and a whole lotta code for enhanced interaction with the real world. And that's where things get hairy with Python. Ok, 2 + 2 is a very simple "rvalue". But when an rvalue contains Lists of mutables filtered by regular expressions used as part of a comprehension for generating a set of tuples, the glaze begins to form over your eyeballs. How did they put it, "This makes it easier to deal with the complex outputs of machine vision algorithms and working with high-level data structures." Yeah, easy once you get the hang of it. And that's what isn't so easy. Which brings me to another point on the speed issue. When Python iterates through these data-structures, it's using pointers, C++ pointers, and we all know how much faster things execute using pointers. So, again, speed isn't an issue with me.

    A huge bug, naaa, just a different way of doing things. Not a feature, no, of course not. It's the way it is. A terrible blemish? Strange way to describe software. Not sure how to respond to that so I won't.

    In any case, the M7 is a very cool "sensor" for vision. And it's only going to get better. As for uPOS, there is a lot of work going on in this area which will only further its appeal to the Maker World. One last thing. I do want to give SparkFun a kudos for providing this device. Even though they went for my primary source to my tertiary source and pretty much no longer use them to provide me with my parts, I do want them to know they made a good choice here.

  • Got mine last week. Cool little device. Paired it with Nexus 4. Programmed it with Surface. Even got the edge connector that works with it. Three cheers for the Brits.

  • I got my micro:bit last week. Works like a champ. Temperature, direction, orientation, buttons, 5x5 LEDs, and even light sensing. Don't set brightness to 0 though. Use 1 for the minimum. A timing bug is getting fixed.

    I paired it with my Nexus 4 and also programed it with my Surface. I made a nice faceplate using my XYZ Jr. 3D printer.

    However, there is just one little itty bitty thing. I sort of felt like Alexander Graham Bell when his first phone didn't work. Of course not, I needed a second one to send and receive with. Should of bought two. Oh, well. If any of you out there remember the Sinclair ZX80, this is another cool contribution from the Brits.

    Also, you can get an edge connector here. https://www.adafruit.com/product/3342

  • I have a micro:bit and it works great. Got it this week from Adafruit. Those people over there are great. They even had the edge connector for it. Which I also bought. So far I have made a faceplate for it with my 3D printer. I made a compass out of it. I used the temperature sensor for a thermometer. I also found a few bugs. But this little 32 bit processor is quite the interesting device. Reminds me of the Sinclair ZX80 I had. Those Brits are always coming up with something unusual. I suggest checking it out.

  • Worked like a champ for me. Also had the Battery Shield, big-boy LiPo, nice size Solar Panel, and of course the weather gizmos'. The Photon sends the data to the cloud and my local html reads the data and populates some really cool controls and indicators. Extremely fun project. I call it MANFRED for ...








    --- MANFRED ---

  • WOW, SparkFun getting political, how disappointing. And here I thought this was one site I could come to and get away from all those crybabies who don't give a rats ass who's coming into this nation to try and kill us. And your comment about the "right" to disrespect the law is just plane asinine. Never thought I'd have to tell you of all people to "Grow up" but hey, you want to look like complete idiots I suppose it's your prerogative.

    Goodbye SparkFun.

    AdaFruit, Element14, look out because I'm coming at you with all my future orders. Damn you SparkFun.

    NorthernPike has left the building.... .><>..

  • Sorry to hear you won't be able to attend the event in Chicago. Would have been great to meet some of you people. I understand the retail decision. But remember, it is a growing market and who knows, someday it may very well be worth it. If I ever am in your neck of the woods I will certainly stop by. Problems is, you may not be able to get me to leave. :))

  • Hello,

    I just found out that there is going to be a Maker Faire in Chicago on the weekend of April 22nd and 23rd. Is SparkFun going to be there?

    One other thing. I know you guys used to have products for store shelves but did you ever contemplate the idea of opening a SparkFun specific store? Maybe call it SparkGap so your products are available over the counter. It could also have a small Makerspace inside for people to Make. Just a thought. Had two Radio Shacks close down recently so electronic parts are no longer 5 minutes away.

    Take care, NorthernPike.. ><>..

No public wish lists :(