Member #57306

Member Since: January 7, 2009

Country: United States

  • This uses the same LEDs as the Luminati line you've sold for some time, does it not? (e.g.

    Can the LumiDrive LED Driver (the device this comment is under) drive them?

    Can the setups recommended on your pages for driving the Luminati devices drive the things you sell under the LuMini LED line?

  • Clarification, in case the following is an issue for anyone: First- YES, it remembers the "fingerprints" you asked it to, even across the power going off and then on again. BUT: It is NOT storing images of the fingerprint. It does a mathematical thing when you show it a fingerprint, and it remember the result of that. When you later show it a new fingerprint scan, and ask "do you know this?", it does the mathematical thing again, and checks the answer obtained from the new scan to the answers from old scans. It only stores the answer from the "thing".... BUT, BUT.... Yes: It CAN "give you" a copy of a scan, a copy of the raw image, as captured. (Being able to see the raw images is very useful when you are learning how to "do it".) And you can save that. But the device is not storing the fingerprints, in their raw form.

  • Loved the earlier GT-511C1R... apart from the fact that it just didn't work at all well for me right at the "source"... it didn't scan my fingerprints very well. Everything else was first class, and very sophisticated. (With that come the fact that hooking into the interface is not trivial, but it IS (very) "do-able".

    As this device seems to use the same, or nearly the same SDK_Demo (Windows) software, I am hoping that it has all of the strengths of the old device.

    Have people found, once they have mastered the SDK_Demo software, and the fairly trivial hookup issues, that this reads prints well? Anyone with experience of this and the older device have any comments to share?

  • Tell the truth!... This is security cam footage of employees struggling to get out when someone's engineering Thursday project with super bright white LEDs went critical, isn't it?

  • Note that if you look on the two sides of the OpenLog PCB, you will see that some of the pads labeled by alternative sets of labels. E.g. the pad for supplying the board with it's connection to the grounds elsewhere (of power supply, of connected host (e.g. Arduino) is labeled "-" on one side, "GND" on the other.

    In similar news... be careful that you don't mis-read GRN for GND or vice versa. (The GRN pad, as M-Short noted, is connected to the reset of the AtMega328 at the heart of the OpenLog.)

  • I "only" wanted.. for a starting point, anyway, the "plug n play" logging device... and it worked out of the box for me. (Well, admittedly, it only worked the SECOND time I tried to run by sketch, which was a great relief because the reason it didn't run the first time was that I had the Vcc and Data (From Arduino to OpenLog) wires connected up reversed.) Details of the Really Really Simple use of OpenLog at

  • And if you only want to write to the device, then you don't need the data line for data from the OpenLog to the Arduino (or whatever source of serial data you are using.)

  • Bought the old OpenLog (DEV-09530), ages ago. Looked Great! When I FINALLY got around to trying to try it out (!), I found the new documentation overwhelming. Great to have all those features, but I just want to walk before I run, use it in the simple way that the (current) OpenLog wiki says it can. And "need" to know if the simple things I think I can do with the 09530 will still work if I need more, and by the replacement.

    A few questions arise, though... all of this in the context of simple use. Data lines... a) The old documentation said 3v3 or 5v acceptable. Present doc only mentions 3v3. Is the DEV-13712 really a 3v3 only device? b) Is sending data to the TXI input of the OpenLog "enough"? Do I NEED to connect to DTR, or the OpenLog's TX0 output?

    And... c) Default data rate: Still 9600? d) Can the new device still manage, however crudely, to create new files "by itself" at each reboot?

    The "basic" is really all I needed, wanted. As I say: Congratulations on all that the OpenLog can now ALSO do... but I'm not ready for that. I just wanted what the old one was said to be able to do.

    (I have some of the old, DEV-09530's. These questions primarily about using one of them. If, say, the 09530 can accept a 5v input, but the DEV-13712 can only tolerate 3v3, please be clear about that (and other) differences? (Apart, of course, from the fact that the 13712 can do MORE than the -09530 could))

    P.S. Greatly encouraged by Nate's helpful reply below, I went further with my OpenLog, and along the way generated a "Simple use- an intro" webpage...

  • Re second photo, the one of your workbench...

    How do you keep it so uncluttered? I know from your blogs that you're not one of those people who maintain tidiness by never DOING anything.


  • Re- the "Arduino Weather Station Data Analysis" example... lots of Good Stuff there, if you are very serious about weather logging. But the "how to I capture data in the cloud?" answer only a minor part of it. (Not a deal killer... nice to see the "high end"!)...

    But that project requires Matlab. Things you may want to ask yourself before going too far into this example: Matlab: 30 day free trial, but after that serious money... GBP 100 for home user. Lifetime licence? One PC (so buy again when Windows 11 makes us upgrade hardware?) Or one SEAT, on pc of our choice, for life, transferable.

    I dug for a bit, but never did quite figure out how/ where the readings from my IoT device WENT, or WHERE I would see the pretty graphs Matlab can generate. Or how I set up whatever it would be that would display the graph.

No public wish lists :(