SparkFun Electronics will be closed on July 3rd, 2015 in observance of Independence Day. Any orders placed after 2:00pm MT on July 2nd will be shipped out after the weekend. Thanks!


Member Since: September 30, 2010

Country: Ireland

  • Personally I would not view Imp’s blinkup as the best feature of Imp. Having used TI’s cc3200, I found their Simplelink app easier and quicker.

    For me, the best feature of the Imp is that you can remotely develop firmware for the Imp device and upload it seamlessly. Then what is really helpful from a developer’s point of view is the “server.log( "message” + params );“ function which you can sprinkle throughout your code for remote debugging purposes (you view messages through cloud-based IDE), on top of the other imp functions which will tell you why the imp device rebooted or when it connected or disconnected from the WiFi network etc. This helps speed up development of a robust solution. Then there is the hidden feature that SSL is taken care of. With cc3000, cc3200 etc. and ESP8266, adding SSL has to be done manually, it is not easy to figure out how and it creates constraints elsewhere once implemented.

    A key point to note with the Imp Device is that it only talks to the Imp Agent and you cannot get it to talk to other devices locally on the LAN. If local network cross-talk IP functionality is required then you need to use other WiFi modules or connect another WiFI module to the IMP device via UART or SPI (such as ESP8266) to get best of both worlds (i.e. secure cloud server communication with IMP device without having to mess about with router port forwarding, and local LAN IP communication with ESP8266). Another thing to note is that Imp Agent only communicates with other web services using http/https and cannot use UDP or TCP functionality directly.

    Last but not least, forgot to mention that all imps come with their own unique URL so you can very quickly and simply create a web-browser interface to turn things on or off (i.e. remote secure user control) and/or get auto updates of sensor readings displayed on the webpage.

  • I see pcDuino3 supports a touch LCD using LVDS connector. Where do we find these touch LCD’s with this type of connector.

  • http://cubloc.com/product/01_01cb210.php

    This is a product that has been out for awhile. The CB210 combines a CUBLOC PLC controller with a USB interface on an “Arduino” format circuit board. Has 1kB available for your ladder logic.

    Anyone tried it?

  • +2 for Sketchup. Been using since 2008 and no complaints about its functionality and versatility. Perfect for modelling. There are also some tips found on the sketchup blog / newsletters on what to do and add-ons are available to get the right output for 3D printers, although getting this right is a little trickier.

  • We successfully applied the Electric Resistance Welding technique to attach sensors to the standard (uninsulated) conductive ribbon without problem.

  • According to Atmel ATSHA204 datasheet: There are 88 bytes in the configuration zone which contain manufacturing identification data, general device and system configuration, and access restriction control values for the slots within the data zone. Byte 14 (I2C_Enable) uses “bit 0” to tell you whether chip is set as either I2C or as single-wire. If bit 0 set as 0 then operates in single-wire interface mode, or set as 1 then operates in I2C interface mode).

    I checked the Arduino library and it has defined “ADDRESS_I2CEN” for this purpose, but it appears this is not used anywhere in the code… but then the writer does say “it is a bit bare-bones now”.

    So if you really wanted to be safe may be worth testing which protocol is being used in your code, as datasheet does say “Communications with the ATSHA204 achieved through one of two different protocols, and selected using the part number that is ordered”.

  • Just ordered one and it works quite well. However, both the connection wires were damaged when it arrived - appears to be pinched at different locations, especially at the point where the two wires come out at the back of the transducer. I think the wires are not strong enough with weight of transducer(thicker wire probably required - although through hole diameter limits options). Have others found the same with wires.

  • Does anyone know how fast you can write data to the SD card (speed in msec) using this product. Can’t find any specs. I read somewhere for another microSD type datalogger that they could achieve about 44 msec through serial port.

  • Its seldom I offer comment, but having just purchased and tried these I have to say that these “cutters” can’t cut the mustard. If you literally say what they do, then I suggest they should be called mini diagonal wire squashers. A little blunt… mind you casting my eye again on the description given above I think it’s correct they’re really solder cutters and not wire cutters.

  • I’m looking for a short cut to create a simple Wiegand Signal Generator and thought this kit might be a good starting point as it already gives the pulse at 0 to 5V.
    So basically want a simple module to produce me a square wave pulse at intervals that match the Wiegand protocol - pulse width (Tpw) range 20 μs to 100 μs & interval width (Tpi) range 200 μs to 20 ms.
    So instead of fiddling with potentiometers, I wondered would anyone know what resistor values I should replace them with. Also is there any clever way to split the signal for my Data 0 and Data 1 lines.
    And if there is any other components settings to build this interface please let me know - e.g do I need to have a start and stop delay, if so what is needed to do this.

No public wish lists :(