-
Raspi 3
03/22/2016 at 14:07 • 0 commentsI picked up a couple of Raspberry Pi 3's at MicroCenter this weekend. I had some issues getting them started (I switched one of my installs with the new board). It turns out that they're going to be finicky about power supplies (duh). My previous Raspi 2 was running on a .7 amp power supply. The 3 did not like that and booted erratically.
However, I eventually figured it out, and got things running and configured (anyone know a great way to apply the same configuration to multiple Pi's, quickly?). I cloned the project repo to the Pi, and ran it. Typically, the Raspi 2's have been scanning the network over 25 seconds or so (scanning just the final octet, or /24 CIDR, or the last 255 addresses). That's a LOT slower than I wanted. Switching over to the 3, and it is scanning the same network space in just over a second. That is going to work. However, I'm getting different results from the two systems, and I can't explain that.
So... more work to be done! I'll keep this page updated with progress on this portion of the home sensor network project: https://hackaday.io/project/9754-raspberry-pi-sensor-network
-
Finally got something done!
03/18/2016 at 22:43 • 0 commentsOK, I've finalized the beta for the stand-alone network query portion of the project. Right now, running "sudo python initialtest.py" will run the network scanner. It will spit back MAC's, hostnames (if found), and IP's. It will save these items to a "previously seen" file. You can then run the "checkFile.py" to give your own names to the MAC addresses. If you then run the initialtest.py program again (you gotta use "sudo python etc.etc.etc", not sure why), it will recognize the previously seen MAC's, and give you their given names and IP's.
Next step is to port this over to my newer project, a Pi based sensor network (https://hackaday.io/project/9754-raspberry-pi-sensor-network). The Network Monitor project is going to be rolled into that one as a sensor, giving you near real-time data on your network.
The new code is up and available at GitHub: https://github.com/StaticDet5/DET5PiNetworkMonitor
-
Not sure what happened there
02/26/2016 at 12:40 • 0 commentsI set the project up, and never documented a damned thing.
Sorry about that. My programming documentation tends to be bad, but not negligent.
It stinks that the first log is going to be about merging this project in with another:
The goal (for this project) is to develop both a standalone capability (which is largely done), and integrate this capability with the larger sensor network. Currently I've got a couple of code issues to clean up (like testing for previous save files, instead of crashing like a spazzed out 4yo who is told "no").