Member Since: January 2, 2009

Country: Finland



  • RX pin is 5V tolerant , Reset pin is not ! ( it has an internal pullup to 3.3V ) You can control the reset with a micro , but do not feed it with 5V , only 0V , 4148 in series to let only gnd pass could be the easiest solution ... or toggle the micro pin only to 0 or no pullup float .

  • Works great , even with my mac . Decodes serial & other signals without trouble . Highly recommended !

  • I suggest You use MAX6675 ( up to 1020'c ) or MAX6674 ( up to 125'c or so ... )

  • Mail me and i will reply with some pictures of my preliminary layout ...

  • I bought this display for a HUD project . But as cool as the display is , it is not bright enough to be seen clearly in daylight . It also dims very slightly but visibly to the end opposite the flat cable ... ( if You have big fonts displayed the digits dim a bit to the end of the display ) Anyway i will install it shortly to my car and i will post back more user experiences .

  • I had problems with the previous version C2 ( could also be user related :) but this C3 works great . The speed is around 550ms , quite fast . Works for me !

  • Worked well while it worked . I connected the reader by usb and run the demo software . I enrolled a few fingers and it worked surprisingly well , after a while of fiddling with the unit i closed the usb connection and unplugged the unit . I thought of many places where i could put a fingerprint reader , i decided to install this one in my car . Today i tried the demo software again , when i open the connection it displays serial and firmware versions , displays enroll count , deletes fingerprints , but does not enroll or read fingerprints any more . When i click enroll the blue led flashes briefly in the reader and the software displays Device error! , if i click verify the blue led comes on but does not recognize a finger and after awhile displays time out ... I may buy another but it would be nice to know why this one died ... Maybe the writer of the demo software has not read the special note ?

  • Well i may have been a bit harsh . Usually change and development is good , but i would have welcomed if the old protocol would have worked also with the new one . I got frustrated because i had a simple project that should not taken more than a few hours to build ... copying bits and peaces from old programs to the new , but when i discovered the old commands would not work with my new display batch , i did not have time to research and implement the new protocol ... Just later i found that i could use the V3 workshop to update the G2 displays to the old serial protocol . In my opinion , i would like a display that is easy to use , preferably ascii commands ( this is just my preference ) , has some built in fonts ( adding your own is great but i would rather buy a display with some pre installed fonts ) , and has input buffer ( this would be welcome !! ) ( and getting rid of the reset line would be an asset too ! )

    I meant with the bad transmission that my program decided not to wait any longer for the ACK and issue a new command to the display causing it to crash , this is not the displays fault but my programming . ( Reach displays have a 512 byte input buffer , You can send continuous data to the display @19.2kbps with just a TX line without any lost commands . ( of course You should read the ACK , but not necessary with a big input buffer ))

    I have a 1.7" OLED display housed in a water tight enclosure in my sauna installed at a height of 2m ( temp about 70-90'c ) , it has performed very well in my abuse test for 3 years now . Now that i know it can withstand high temperatures i will install a lot more to my friends saunas .

    I did not realize you could write your own protocol , all i see and hear is the serial protocol . Do people use the other modes ? Standalone anyone ??

  • Not that i want to speak bad about 4D systems , but the language this serial display uses is horrible compared to Reach Tech displays . I have used many 4D systems OLED displays and i like the displays but the protocol is awful , the old protocol was a bit simpler but the new "Serial" is more clumsy than the old one , this applies to the OLED displays , these new displays come only in "Serial" = new protocol . It does not survive a few bad transmission but crashes the display , never happened with Reach Tech displays , the price is a bit higher but so is the quality of the firmware .

  • Nice project , but the leds are poor quality . Mine's been running nonstop a bit over 2 years now , and now there are 5 blue leds that are broken . The good news is that the first blue died a short while ago , but the rest are following fast . I have not measured the current fed to the blue's but still i think it's just that the leds quality is not good .

No public wish lists :(