Blog Post Actions
Group Actions
Engagement
  • Author Author: funinalaska
  • Date Created: Date Created
  • Views 419 views
  • Likes 0 likes
  • Comments 6 comments
Related
Recommended

back to the project, successes and frustrations.

funinalaska

So I had some time off work and I decided to get back to my weather project.

So far I have incorporated this hardware:

     Arduino Mega 2560

     Arduiino W5100 Ethernet Shield with micro SD card slot

     Adafruit LCD shield

     DS18B20 sensors

     DHT11 Sensor

 

I have it currently set up so it can display 2 of the sensor's data on the LCD screen I am using the 2 DS18B20s One is outdoors and the other is mounted to a breadboard right next to the Arduino.

Then I also have the Ethernet shield set up as a server on my local network so anywhere I am connected to my wifi I can access a webpage with the info from all 3 sensors on it.

 

I want to get the sd card set up to record the data from the sensors once every 10 minutes but I am having issues with figuring out how to get the Ethernet shield to switch from the Ethernet to the SD. Even just installing a sd card in the slot causes me to get all kinds of gibberish on the serial monitor and on the webpage. I have no idea what is going on here.

 

The things I am still wanting to work on adding to this project:

     First, Getting the SD data logging portion up and running

     Second (and it is a close second) Get the Arduino to access and decode METAR (airport weather) data and display wind information as well as severe weather alerts.

     Third, figure out how to get the webpage I have on my local network available on the Web but in a way that will not kill my limited satellite bandwidth.

     Fourth, add a couple additional sensors (additional DS18B20s, a DHT22, a barometer(pressure) sensor, a light sensor)

     Fifth, add an alert function that if any of my indoor sensors reach below a certain temp I am notified on my cell phone (email)

     Sixth, before completing the project get a larger display or multiple displays to allow more information to be easily read locally at the device as well as buttons to force certain info to be displayed on demand.

 

For now I am going to continue frustrating myself over getting the SD card to work and trying to figure out how to access METAR data.

  • in reply to DAB

    To be totally honest I didn't even know that multitasking was possible with an Arduino, even on a MEGA.

    I still have so much to learn.

    Starting my experimentation with MCUs is the first time I am attempting anything involving any sort of programming since I was in High School and playing with Basic on the TI computer we had at home.

    And even that language has escaped me in my endeavor to work on these projects.

    But then again 10 years ago even I would have never thought I would be programming a stand alone chip (Attiny85) to control addressable integrated driver chip LEDs (WS2811) and incorporating them into Christmas decorations.

    So I guess I have learned a lot already, just a matter of continuing to learn and trying to keep myself from getting too frustrated.

  • in reply to funinalaska

    Hi Andrew,

     

    Finding timing problems was my specialty when I was working.

    Demanding interfaces like Ethernet can demand the full capability for the MCU.

    In most designs, those high demanding tasks are usually split off into a separate MCU to keep it responsive without killing all the other tasks running.

    You might get away with using interrupts for handle the functions instead of delay loops and the like, but it still depends upon your overall MCU load.

     

    Good designs use interrupts and multitasking to avoid the problem you are seeing.  However, I have found many a design where the resources were just overloaded and all the levels of interrupts, priority and multitasking cannot compensate.  With inexpensive MCU's, you can quickly separate the tasks into separate processors and regain all of your needed responsiveness and still maintain continuous communications with other devices.

     

    Once you learn these tricks, a whole new world will open up and give you options you did not know you had before.

     

    DAB

  • in reply to DAB

    Well, you are giving me ideas.

    Not too worried about the data logging as I am only planning to have the SD card record one set of reading every 10 minutes. however you are giving me another idea.

    One of the problems I am having is that any time a network client accesses the data the LCD display stops updating until the the client disconnects.

    I would like to have the LCD display more information and be able to change and scroll through information once I get the whole METAR thing figured out, but the only things I can figure out will cause problems in that either the LCD portion of the program will add drastic delays in the net client portion or the net client will cause delays in the LCD display.

    Granted I have no idea how to do this or solve either of those problems.

    I do have additional MCUs at my disposal, everything from some UNOs to a couple Trinkets and even some basic ATtiny85s I have been playing with for neopixel projects.

    I never thought of using multiple MCUs on one project other than the eventual goal of incorporating some NRF24L01s to make a couple wireless sensors, but that is not a priority as of now.

  • in reply to funinalaska

    Hi Andrew,

     

    Sorry I got the projects screwed up.

    The PSOC is the Cypress programmable system on a chip.  Currently being used for a project challenge for everyday use.

    If you are using any MCU, then you can always use a second to work with your overall design.  Breaking up the tasks gives you more options for implementing tasks.

    DAB

  • in reply to DAB

    DAB,

    I am going to demonstrate my level of knowledge here...

    What is PSOC?