Kuler SQL stack info

Looks promising… a lot of features!

1 Like

Not only does it ‘look promising’, it is indeed AWESOME! :+1:t2:

Very much worth the investment. I have been able to get wonderful results in very little time.

2 Likes

Just spent some time viewing part of the Datably video tutorial. The dev(s?) have spent a lot of time on this much-needed stack.

Since I began this thread I have come to realize that a visual representation of the sensor data I will be gathering would be more beneficial than pasting numerical data into a database. That said, I am currently working on a D3.js webpage to make the data more ‘consumable’, so to speak. It will also be more meaningful in this format.

Static data vs dynamic data? Dynamic/interactive wins hands down, again, IMO.

I will, however, purchase Datably to show my support for the developers because stacks such as this are, IMO, much needed and great compliment to RW.

Thanks!

1 Like

Sorry I missed your very interesting post. I will admit to being quite busy with this nearly completed project.

“Can you clarify exactly which Arduino kit you are using ( name and model ). I say kit, because you stated it was easy to set up so I’m guessing it might have been an Uno or similar?”

I am using the Adafruit Feather MO WIFI board. My comment about “easy to set up” may be somewhat misleading because I have been involved with electronics, in one form or the other, for most of my life. Having a good attitude also makes difficult a bit easier to overcome.


“I suspect that you’ll be able to demonstrate the fluctuations in the tank levels with additional insight into humidity and temperature. That alone probably won’t reveal the cause.”

Each tank will have its own precison temp/humidity sensor. I did the math to verify how the air density/temperature will affect the ultrasonic distance values. Bottom line: the affect is minimal/inconsequential within the short range of these tanks (18 ft). However, these data points were not collected over a long period of time, so these algorithms will remain in the code, just as a precaution. We live in an area where temperature can vary 40-50ºF in 24 hours.


“If your aim is to solve the problem you are going to need additional (downstream) data points to correlate tank volume to demand or other physical factors.”

Monitoring tank water levels will not solve the water loss issue. You are correct to point out that several downstream sensors would be necessary to get the ‘big picture’ on the entire water system. This has been discussed, but nothing has come of these meetings. I am not a board member, but these downstream sensors could be setup but would have to be solar powered. Again, not a difficult thing to do. Until they get serious about solving this water loss problem, it will not get solved.

This, IMO, is a classic case of being able to take the horse to the water trough, but not being able to make him drink.


I have decided it would be much more beneficial to view the data using D3.js. I hope that by the end of today I will have a good grasp of how this will be done.

This project has been an interesting one.

Thanks!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.