Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by amstan

  1. It's not that great. I tried it for my rgb clock project. You have to do a lot of work for it. You basically trade your project documentation(which you have to customize for their site) for the boards. They're not that good of boards, green only, take quite a while to get(elecrow was faster). http://www.electronics-lab.com/projects/mcu/025/index.html I eventually went with elecrow since they had black available and I didn't feel sketchy basically selling my design.
  2. When i dabbled into I2C it seemed that the hardware for it is really inflexible(it even contains bugs). So i just made/adapted my own bit banging library. I don't care that it's bit banging because it's probably fast enough. The bonus is that you can use it on any pins that you like. https://github.com/amstan/binaryclock/blob/master/firmware/i2c.h
  3. When I counted there were 81. I guess you have 80 now. heh. How do you limit current on them? Aren't you worried that you get uneven brightness if you just use the pin current limit? At least the anodes should have a resistor for current limit(ideally a transistor as well, if you want higher currents). Also.. a battery like the CR2032 can only give like 5mA, anything more and the voltage should drop. If the voltage drops too low you might have glitches in the mcu and have problems with the program execution. You could solve that with a big cap. I included the leftover parts for my binary clock. You might be missing a bunch of things(like the smpsu chip). But you should be able to get most of it operational with the bare minimum of parts. You don't really need the smpsu if you don't run on battery and you already have 5V available. You can also bypass that mosfet on the 5V rail; it's completely useless, doesn't do what i wanted. I haven't checked if i gave you a light sensor as well, for that you need a heat gun. Take note of the changes you need to make of the pcb, i had some pins swapped. I also included 20 ws2812 leds for you to populate that board. I also included a bunch of hitachi based lcd modules that I had laying around(i had a box with at least 50).
  4. @@simpleavr Why don't you jump on IRC to discuss donating arrangements? #43oh on irc.freenode.net
  5. Would this be of interest? I have a bag of them (80, all pictured). In various stages of pin bending(i don't think any are broken though). I didn't really have any plan for them, totally forgot I had them for a while there. I'm open to donating them for this group buy. At least part of them(I don't think there's a need for 80, heh). The catch is that they're 3 digits, this board calls for 4 digit displays.
  6. Yeah, same. I have too many things i don't have a purpose for.
  7. I had mine working on 18MHz using the ti sample code and my own xtal.
  8. Unfortunately it doesn't look very well when it's stationary. Perhaps I'll get some videos in a few days.
  9. I got mine a few days ago. I wrote a python3 driver for it: https://github.com/amstan/pynoritake I also tried to emulate the squiggle from this lcd megademo 2, Just run ./squiggle_noritake.py to see it on ttyUSB0, you'll need numpy as well.
  10. You need to install http://processors.wiki.ti.com/index.php/MSPDS_Open_Source_Package aka tilib. It replaces the uif method in mspdebug. Energia comes with a binary of it. If you don't want to go the energia route, and you have archlinux you can install https://aur.archlinux.org/packages/mspds/. If you're on another distro you could look inside here and run the compiling commands manually.
  11. ld.exe: CC3000FirwareUpdate.cpp.elf section `.rodata' will not fit in region `rom' ld.exe: section .vectors loaded at [0000ff80,0000ffff] overlaps section .rodata loaded at [0000e6b0,00011a29] ld.exe: region `rom' overflowed by 6840 bytes Seems to me that something won't fit. The CC3000 firmware might be too big to be used with the fr board(which only has 16k of code space). I might be wrong though.
  12. You know the drill. Same kind of promotion as http://forum.43oh.com/topic/4358-noritake-graphic-vfd-128x32-free-sample/. Link: http://www.noritake-elec.com/evalkit-sample.php?id=sample Expires 31 Jan 2014 at 7:00 PM CST. Description from the site:
  13. Is there a schematic out there for this? I would like to know how the 3.3V and 5V are generated and what kind of topologies they have. I want to see if i could make a booster pack with some ws2812 leds(ala my binary clock) powered by this.
  14. I could, but there are a few problems i though of: The design I have right now can be battery powered. None of the launchpads have that unless you use the new fuel tank booster pack. Maybe that's an option. I could also integrate the battery charger on my board(same chip from the olimexino). I need 5V for the RGB leds, the original 20-pin launchpad only have low current(less than 100mA) at 3.3V. Even though the original launchpad could probably drive the display just fine, it will have to be a 40 pin booster pack. Perhaps i could add a 5V pin for external powering(maybe from the fuel tank booster pack, if used with the original launchpad). Stuff like this makes me lean more on a standalone board maybe. So far I designed this with not a lot of input from others. It would be nice if I had some feedback: Do you guys like the smpsu? If removed one could still kinda drive the leds(blue still lights up at 3.3V), but some kind of software would have to compensate for the color(and full white will not be possible anymore). The PWM for the dimmer. I still think this is required, dimming all leds in order to achieve a higher brightness resolution at lower intensities. I order for this to work properly it should be capable of PWMing the 5V rail at at least 100kHz(to avoid aliasing with the built in ws2812 leds). The 5V rail uses 500mA when all leds/channels are on. Is this a worthwhile thing to include, given that i already failed implementing it in v2.0 As i mentioned earlier, one of the reasons I did this project was for a class in school. I attached the report I submitted for that in case anyone wants even more details about it. PS: Yay, i'm on the frontpage. tr1-report-withdiagrams.pdf
  15. I would like to enter my Binary Clock. Here's my project page: http://forum.43oh.com/topic/4832-binary-clock/ Video might follow.
  16. This project is an update to the binary clock that I used on my desk. The new version has a lot of new features including RGB leds(WS2812), a bigger microcontroller(The Olimexino-5510 board), capacitive touch and light sensor. My first idea was to have something based on the MSP430G2553, a couple of WS2812 leds and capacitive touch. But after comparing the work i would have to do, and very few rewards to the Olimexino-5510 functionality I quickly reconsidered. The Olimexino-5510 provides quite a few things I wanted: MSP430F5510 Battery Charger USB capabilities Arduino Form Factor So all I had to do was make a nice board that went on top with the stuff I wanted for the clock functionality. WS2812 RGB LEDs The main feature of the Clock is the 6x3 WS2812 RGB led matrix. These leds contain a little controller that accept a serial protocol for the color data and they handle the PWM. They're also chainable meaning that only one pin(D11, LED-DATA) is required to quite all of them. In my using @@oPossum's library Power Supply The Olimexino-5510 has a connector for a battery. But it just connects the battery to the 5V rail, the battery could go as low as 3V. The WS2812 aren't meant to run that low, specifically the Blue led get a lot dimmer. In order to fix this I incorporated a SMPSU that can get 5V from the battery voltage. It could in theory handle as much as 2A. The design was done with TI Webench, all parts are the same as the suggested ones. I had to modify the Olimexino a little to actually give me the raw battery voltage on the shield connector, on battery there's no voltage on the 5V pin, i assumed there was. It all works quite well now except it's kinda whiny. The WS2812 leds are very bright, so in the darkness this might be a problem. One could dim them by sending them a darker color but this reduces resolution. Q2's purpose is to PWM is the 5V that the LEDs in order to dim them externally. This essentially gives another scaling factor for the brightness. It's a similar principle to how dynamic contrast works in TVs. Unfortunatelly this did not work as I wanted, the mosfet was too slow to PWM the leds fast enough without aliasing. My next design will probably contain a mosfet driver. Capacitive Touch Pads I have 4 pads acting as buttons. I originally connected them directly to some pins assuming I had PinOsc hardware like on the value line. Unfortunately I discovered this was not the case too late. I fixed it by adding 2 resistors between each of the pairs. This allows me to do a pretty crappy RC measure. It still works quite good though, i can get about 200 discrete values of the reading. As suggested by TI I had a non solid ground plane of the backside to reduce the intrinsic capacitance. Light Sensor The shield also has a light sensor, meant to measure ambient brightness. One can use this to make the display's brightness match the room. The sensor is connected via I2C, since neither the Arduino nor the Olimexino-5510 have I2C exposed on the pins I will have to do a software solution for this. The TCS34725FN sensor is also capable of measuring RGB color; I'm sure something fun can be accomplished using that. Of course I managed to do the footprint wrong for this, so it required some cutting traces to swap some pins; after that it worked just fine. Eagle Files I also have the schematics in PDF format. Code The current code is mostly made to prove the hardware. It could use a lot more work for the UI. Features Clock Functionality with fading SMPSU Off demo Capacitive Touch Demo Light Sensor Demo USB CDC ported from Energia that i used for debugging so far Everything was compiled with msp430-gcc. I uploaded the firmware using the new f5529 launchpad board due to the fact that mspdebug does not support the olimexino usb bootloader. Parts Most parts I got from digikey, except the Olimexino-5510, the beefy 6600mAh battery and the WS2812 leds. I got a pretty good price for the LEDs from Alibaba at only 13 cents each. I ordered the board through Elecrow, I really needed it to be black. Meta My old clock was this boring thing with an attiny44, using a matrix of green leds. I originally started this version(v2.0) as a school project, but I wanted to share it. Due to the many issues I had I'll probably make a version 2.1(if i fix the shield) or a v3 if I make a standalone board. I'm open to ideas. I still have quite a few board leftover(about 7), i'm open to sending them to people if postage is cheap/free/easy. Imgur album for non-users.
  17. I don't think it's possible to do RO method using the comparators(without interrupts every osc) with the default capacitive booster pack. R10-R15 are not populated, they allow you to use RC with it because they connect to ground. If you wanted RO method you would need R10-R15 to be connected to CBOUT instead(the wire that goes to all the leds). If you wanna be messy it is possible, all the pins are there, but it won't be pretty. RC is not that bad, i've done it before in a pinch.
  18. Totally what it was! I am very grateful! All my pins work properly now!
  • Create New...