Jump to content

zeke

Members
  • Content count

    1,748
  • Joined

  • Last visited

  • Days Won

    95

zeke last won the day on May 9

zeke had the most liked content!

About zeke

  • Rank
    Electron Wrangler

Contact Methods

  • Website URL
    http://www.randomelectrons.com

Profile Information

  • Gender
    Not Telling
  • Location
    Calgary, Canada

Recent Profile Visitors

1,474 profile views
  1. @tm4c I think you have a copy-paste error in your code. Check out the error message. Are you using an AVR or a TM4C129? Reconcile that problem and you should be better off.
  2. @dmalawey If you are using the code from the link you provided then I bet you haven't setup the wifi credentials properly. This is a snippet from that code: Is your wifi router called "energia1"? Is its password "launchpad"? Check those two details first and then try again.
  3. CoRTOS: An open source minimalist RTOS

    @NicholasLindan Do you have any blog posts or example projects that you can show case for us? It's kind of like a new flavour of ice cream - "you are not sure that you want to get it if you don't know what it tastes like so I'll just take vanilla".
  4. @ckd, Extra pullups on the SDA and SCL lines will make things worse, so don't do that. On the J1 (SHUTTLE_COM) connector, there are assignments for the I2C signals: SCL (Pin 18) and SDA (PIN 17). There should be only one set of pullup resistors on those lines. If they are on the ARM board then that is okay. If they are not installed then they need to be installed. As a quick test, use your voltmeter and measure the value of the SCL and SDA lines with no traffic on them. Are they the same value as VDD? If yes, then that is a good sign the resistors are installed. If no, then that is a good sign the resistors are not installed. If possible, wire up your logic analyzer to SCL and SDA and record some I2C bus traffic. See if your logic analyzer software can interpret the information properly. If you do not have a logic analyzer then use your oscilloscope and attempt to see signals transitioning between a low and high signal value. Side note: I have to do this very same process to a project that I am working on right now. Fingers crossed, we will both get our circuits running!
  5. Section 4.1.3 of the BMG250 datasheet says I do not see any pullup resistors on the schematic in the first post. I have attached a screen grab of one of my circuits for reference. Are they installed in your circuit?
  6. Thank you Sir! Topic edited successfully. With regards to the temperature display, I still have to figure out that. Spontaneously, I imagine that I would display the average temperature of the entire grain container. If there were a hot spot then I would have to figure out how to indicate a problem to the user. The challenge is to figure out a paradigm that hides the complexity of the data initially but allows the User to dig deeper to reveal more detail. Kind of like the zooming function of a satellite map - you start out at 30,000 meters and zoom in. New data is presented as you zoom in. I think this is called Data Decimation. The best example I have found is the iOS application called Netatmo - a weather station app. When you look at the temperature graph over a month span, it presents the data with a few data points. As you pinch to zoom, more data points are included and the trending line is recomputed. I admire them for their engineering.
  7. Additionally, I performed some tests in node-red. Using a python program, I published data to five MQTT temperature streams. I did this at a rate of five samples every 250ms, 500ms, and 1 second. It liked a 1 second update rate the most. I composed a node-red dashboard sketch that would display all five streams simultaneously using both a chart and a gauge for each stream. The dashboard displayed all the data successfully but there was a noticeable lag between publishing and displaying of the data. The lag has me thinking that chrome may be overloaded during this process. I had a lot of tabs open. I should note that I am doing all of these tests locally on my Ubuntu desktop machine and RAM isn't a problem. I might have to upgrade the spinning hard disk to an SSD though. Hmm... I just realized that we are talking about node-red more than DeviceHive in this thread. Does it matter to anyone?
  8. @Rei Vilo Good points! I had been imagining a transparent 3D image of a grain bin or silo that had vertical lines arranged inside of it. The vertical lines would have a number of data points along their lengths. Each data point would change its colour based on the sensor reading. When viewed as a whole, the sensors that are hot would trend towards the red colour and sensors that are normal would trend towards a green or other neutral colour. At a glance, the user would understand the relative temperatures inside the grain bin. I agree that viewing all of the sensor data at once would be foolish and overwhelming. I also agree that the data should flow into a database for safe keeping before being processed and passed into the User Interface.
  9. MSP432E4

    Has anyone had a go at the msp432e4 launchpad yet? It's got on-board ethernet. It could become a perfect edge router.
  10. @hmjswt I am presently making use of the ds18b20, ds28ae00, and max31851 sensors in my prototype system. Most IoT demonstration projects that I see online are using just a couple of sensors. I'm kind of sad about that because I intend on using a boatload of sensors. I am thinking that my dashboard will become very complex. So, I have to spend some time designing what the user interface could be and then research the readily available options. My instincts tell me that I will probably have to roll my own dashboard interface because of the massive quantity of data that could be shown to the user. I don't think that I can just display a single graph with a lot of traces on it. I have to come up with a 3D interface or similar abstraction. Maybe use colour as well as position to show the data?
  11. Good questions! I would like to monitor the temperature of a silo full of grain. Maybe a million bushels? Any pile of grain is a gigantic thermal sink therefore the temperature ought not to change very rapidly. I would expect the temperature to be sampled no more than once every hour. But, that time interval should be user configurable. The neat thing about the logger design is that it has a large on board FRAM chip and an SD card slot that I can use as a data buffers. I haven't worked out the capacity yet because I haven't figured out the expected size of one measurement record. The FRAM is a 256Kbyte unit. The SD card is whatever an MSP430 can work with. The overarching goal is to watch the temperature and humidity of a grain pile. If it gets too wet then it can spoil. If the spoiling gets out of hand then the grain will spontaneously combust. Here are a number of interesting and, in some cases, deadly examples: [1], [2], [3], [4], [5], [6], and [7].
  12. One Wire Controller booster

    I know, it's silly. But I am trying to surround myself with motivation.
  13. One Wire Controller booster

    It's Alive! I was able to get the FR5989 to program with some rudimentary code that blinks the LEDs and echos characters from the serial port. So I am pretty happy!
×