Fmilburn

Members
  • Content count

    544
  • Joined

  • Last visited

  • Days Won

    66

Fmilburn last won the day on June 19

Fmilburn had the most liked content!

About Fmilburn

  • Rank
    Level 3

Profile Information

  • Gender
    Male
  • Location
    Seattle
  • Github
    https://github.com/fmilburn3/

Recent Profile Visitors

1,160 profile views
  1. Tiara Prototype Assembled I assembled one of the tiaras in more or less final form last week and while everything is working, and it meets the original criteria, I am working on additional modifications to improve ease of fabrication. Here is what it looks like at the moment: The fabrication problems are mostly around the wiring between the PCB and the LEDs. Soldering to the WS2812s is fussy and the wiring isn't too attractive as seen in this photo from the back: In addition, I've hot glued a pin header to the PCB and wired to that. All very unprofessional looking. There was also a potential problem with shorts when inserting and removing the battery. So, I've modified the PCB as follows and put them on order: This will allow soldering in a pin header or in the case of the TSOP 38 direct soldering. The three LEDs on the old receiver PCB have been replaced by a four pin 5050 SMD version of the WS2812. In addition, I am switching to the same LED for external lights and designed a small PCB to make attachment easier - they are a bit more than 11 mm in diameter: There was a recent blog on Hackaday about cables and I am thinking about ordering some custom ones to tidy up the wiring: http://hackaday.com/2017/06/25/dirty-now-does-cables/. Of course this will require yet another spin of the PCBs to accommodate the new cables but in the end it is all easier to assemble and neater. Meanwhile, the prototype I built for the transmitter looks crummy and I am still waiting on some parts. Plus, it was suggested that I needed to simplify the programming by the user further and perhaps have an automatic mode that would somehow work without programming on behalf of the user. So, I've ordered some MSGEQ7 Band Graphic Equalizer chips with the idea of using that plus volume to create some kind of automatic light show (feature creep alert). I will probably switch to a Raspberry Pi for the transmitter.
  2. I plan on going ahead and fitting it all together - it is the quickest way for me to put something together that won't fall apart and demonstrate the concept.
  3. Receiver Prototype Working After some stop and start I am back on this project and making progress. Here is the latest iteration: The wearable IR receiver and WS2812 controller at bottom runs off of a single 2032 battery. With only one LED lit at a time it is capable of easily running for an hour since current is down in the 10-15 mA range. It also transmits and receives with high reliability at 10 meters with two IR LEDs as shown. The transmitter is battery driven at the moment. I have a large number of IR LEDs on order so as to build a transmitter with a larger array of LEDs. It uses 2400 Baud UART for transmission. The transmitter code was written with CCS and is done in software with two timers. One timer maintains 2400 baud. To transmit a 1 bit the second timer is turned on and outputs a 38 KHz square wave over the IR LEDs until time for the next bit. For a 0 bit nothing is transmitted. The LEDs are rated for 100 mA each continuous but are being driven here at about 70 mA each with a NPN transistor hidden behind the jumper wires on the breadboard. On the receiver side the IR receiver turns the transmission into input that can be directly input into the UART peripheral on the MSP430G2553. A single byte is used to select the color and display mode of the WS2812 LEDs. The driver for the WS2812s uses the SPI method which I have posted elsewhere. There are some areas for improvement in the receiver PCB which I will incorporate in the next board spin but everything is working. A feature of this approach is that the receiver uses Energia with no tricks and even works on an Arduino Uno without modification other than pin changes. For the transmitter, I am still thinking about how best to implement. One approach would be to continue using a microcontroller such as the MSP430F5529 I am currently using with a keypad and display. Something like this mock-up: Alternatively, I could use something like a Raspberry Pi 3 and use Python to give Bluetooth LE access control over a phone.
  4. Mine is Rev 1.6 but I should point out that RX,TX only ceased working when I accidently applied 5 volts to a pin - it worked fine before that. I have several F5529 LaunchPads and all were working on receipt Why use a F5529? The LaunchPad itself Costs $3 more but it is faster, has more memory, more and better peripherals (eg faster UART and higher resolution ADC), has USB, etc. It is easy to use if you are familiar with the G2553 and need the features.
  5. A while back I damaged two pins on this board and dutifully marked it on the back. Unfortunately it was only visible from the back. Some time later I picked it up and was trying to use it unsuccessfully. After tearing my hair out for a while I eventually turned it over and noticed the markings. Now it is marked front and back.
  6. PUSH is not a variable in the example / library that I suggested above so you must not be following the suggestion. In your first post it is not defined. It needs something like #define PUSH xxx where xxx is a pin number / designation. Doing a search for "DHT does not name a type" on the internet will give multiple hits and solutions to the problem so you apparently did not do the search as suggested. The library is probably installed incorrectly.
  7. As stated above, I tried the library that I linked above with a TM4C123 / DHT22 the same day I made the post and it worked. Use the example code that comes with the library. I was probably using Energia V17. Do a search with google with the error message text if you want to understand what it means.
  8. @Rickta59 I would not have caught that It works for me in V17 but not in V18. When I move it in V18, it works. What is happening?
  9. @energia I just tried compiling the nRF24L01 library in V18 and got the following error: In file included from C:\Users\Frank\Documents\Energia\MSP-EXP430F5529\Enrf24_RXdemo\Enrf24_RXdemo.ino:16:0: C:\Users\Frank\Documents\Energia\libraries\Enrf24/Enrf24.h:32:17: fatal error: SPI.h: No such file or directory compilation terminated. exit status 1 Error compiling for board MSP-EXP430G2553LP. @ghjkl67 You should not have to add SPI. Try using Energia V17 as I suggested above. You will find it here under previous releases: http://energia.nu/download/ Energia V18 still seems to have some bugs. I just flashed the sample code on two G2553s with nRF24L01s using Energia V17 and they are working fine. EDIT: I would remove the old versions of Energia before loading a new V17.
  10. How do you know it works as a receiver if you don't have anything working as a transmitter - what are you receiving without a transmission? Have you gone back and double checked that one of my suggestions isn't the cause? I can assure you that the library works when connected properly with the nRF24L01+ modules I have and a G2553 LaunchPad. The datasheet for the nRF24L01+ has all the details and can be found with a google search - it uses SPI. SPI keeps the chip select pin high until it is ready to transmit and then pulls it low. It then returns to high following transmission. The code for the library is in Enrf24.cpp. Look inside at the code, e.g. void Enrf24::_writeReg(uint8_t addr, uint8_t val) { digitalWrite(_csnPin, LOW); rf_status = SPI.transfer(RF24_W_REGISTER | addr); SPI.transfer(val); digitalWrite(_csnPin, HIGH); } It pulls it low before transmitting then returns to high. One more suggestion - if you do a search on the internet you will find various people have found this helps: https://forum.arduino.cc/index.php?topic=376068.0 I include a decoupling capacitor in my designs and normally power the radio from a battery. Nonetheless, I have also had success powering off of the LaunchPad.
  11. I have used this library with both custom MSP430G2553 boards and the LaunchPad. Hardware setup is the same whether receiver or transmitter. Among the possible problems and solutions are the following: Bad nRF24 - the very first one I bought was bad damaged pin on MSP430 - don't apply 5V to a pin - this is a 3V3 device nRF24 wired wrong or wrong pin in software - easy to do poor transmission between modules - too far apart, object in between, or even too close together. modules set on different channel or other incompatibility in way software is set up In general though, I have found the library easy to use and reliable. I suggest you concentrate on getting the examples working first without any modification. I haven't tried it with Energia V18, you might try Energia V17. The following are the pins I normally use: nRF pin pin# Std color F5529LP pin G2553 pin ------- ---- --------- ----------- --------- Vcc 1 Red 3V3 3V3 GND 20 Black GND GND CSN 9 Yellow P4.2 P2_1 CE 8 Green P2.7 P2_0 MOSI 15 White P3.0 P1_7 SCK 7 Orange P3.2 P1_5 IRQ 10 Brown P4.1 P2_2 MISO 14 Purple P3.1 P1_6 I use the same wire color every time to ease checking that the connection is correct. If CE is not going high then try setting up a simple pin toggling program (e.g. the "hello world" pin wiggling and check with multimeter) to see if it works without the library. This will tell you if the CE pin on the MSP430 has been damaged. If so, changing to a different pin will fix it until you get a new $2 chip. EDIT: Some multimeters can be quite slow to update. When toggling pins to see if they are reaching a full on state, keep the toggling frequency to 1 Hz so the meter can keep up. For monitoring an application like the one above an oscilloscope or logic analyzer is a better tool.
  12. You haven't provided enough information to get help.... Most importantly you have not stated what about the code is not working. Is it failing to compile? Is it giving bad results? Is it failing to print? You haven't stated which library you are using, etc... So, anyone attempting to answer your problem would just be guessing. Try using the Adafruit library without changing anything and have it print directly to the serial monitor: https://github.com/adafruit/DHT-sensor-library Use pin 2 (PB5) on the LaunchPad. I just tried it on my TM4C123 and it worked. Once that is working, try adding in the code for the LCD.
  13. Texas Instruments has standard shipping for $3.14 and 10% off selected tools through March 19th: http://www.ti.com/lsds/ti/store/march-ti-store-pi-week-promotion.page?HQS=ecm-tistore-promo-piweek17-bti-lp-null-wwe
  14. Hi iKlepto and welcome to 43oh... You can get jumpers M-M, M-F, F-F. For example.... https://www.addicore.com/Jumpers-and-Cables-s/1837.htm and many other places
  15. Hi @jBrizzle and welcome to 43oh... Maybe use a little module? Depending on your needs in terms of recording length and number of recordings that might work. I have used these although not from this vendor: https://www.amazon.com/Sound-Voice-Recording-Playback-module/dp/B018Q6TAEQ/ref=sr_1_2?ie=UTF8&qid=1489447073&sr=8-2&keywords=isd1820 They are cheap and work for a single recording but the amplification and quality isn't great. They can be controlled with a microcontroller. Maybe this: http://processors.wiki.ti.com/index.php/Audio_Capacitive_Touch_BoosterPack_Hardware I don't have experience with it but it looks interesting. I usually have a look at what Sparkfun and Adafruit are doing as well, even if I decide to make it myself.