![\"snapshot1\"](\"https:\/\/www.beer.org\/blog\/wp-content\/uploads\/2015\/09\/snapshot1-300x296.png\")
<\/p>\nI thought it might be useful to explain how Snap! works in my device control scenario. I’ve ever so slightly modified Snap! to be able to query my server and get an inventory of inputs and outputs available. These are known as “Phrob Ins” and “Phrob Outs” for lack of a better name.<\/p>\n
<\/p>\n
On the left is a list of all inputs that were discovered during the inventory process.<\/p>\n
In the center are the logic blocks I’m currently working with. There are 4 logic blocks there. Two of them are outlined in Green. These two are presently executing. The other two are not. The smallest logic block on the bottom has a speech bubble next to it. I simply clicked on the “Office:temperature” input and the speech bubble popped up and said “2214” which is DegreesC multiplied by 100. I’m currently experimenting on whether to transmit data as integers or floating point decimals. The jury is out. There is a logic block on the middle right that is not executing. I can simply click on a logic block to start or stop the block.<\/p>\n
On the right top is a white canvas which presently displays some temporary variables that my logic blocks use. It’s handy to see those variables displayed because it makes debugging easier.<\/p>\n
The top running logic block is responsible for collecting some statistics and transmitting a single text message out to the APRS IS network. On this network, I can remotely see what’s happening at the cottage:<\/p>\n
![\"graph\"](\"https:\/\/www.beer.org\/blog\/wp-content\/uploads\/2015\/09\/graph-300x211.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"