1-wire success, sort of (and info on XTension crash)

[Rob Lewis]

I used “Find” to look for any stray occurrences of the “send data” command and didn’t find any. So the mystery described below about B50 errors continues. 

But while doing the script search (of all scripts), XTension hung partway through. It found three occurrences of “send data”, in three different scripts. In two, the command is commented out. The third is in your “create Barionet units for XTension” script that is never run. 

XTension became unresponsive with the search progress bar at maybe 60%. Had to force-quit it and relaunch, but it did the exact same thing twice in a row. Thought you’d like to know. 


On Nov 17, 2014, at 12:14 PM, Rob Lewis <rob at whidbey.com> wrote:

> Very cool that XTension automatically handles subscribed updates from the Barionet 50. It is however doing some puzzling things, as shown in this log excerpt: 
> 
> Nov 17, 2014 11:59:10 AM Barionet 50 Temp 5 (floater) ON script activated
> Nov 17, 2014 11:59:13 AM Barionet 50: Quitting. Unspecified response from port drivers.
> Nov 17, 2014 11:59:13 AM Interface "Barionet 50" has quit: (with no message) code: 0
> Nov 17, 2014 11:59:18 AM Retry connection to interface "Barionet 50". Tries left: 9
> Nov 17, 2014 11:59:18 AM Barionet 50: Ready !
> Nov 17, 2014 11:59:18 AM Barionet 50: Received Command Error
> Nov 17, 2014 11:59:18 AM Barionet 50: Received Command Error
> Nov 17, 2014 11:59:18 AM Temperature sensor not found for this address: Barionet 50 Temp 6 (Barionet 50)
> Nov 17, 2014 11:59:18 AM Temperature sensor not found for this address: Barionet 50 Temp 7 (Barionet 50)
> Nov 17, 2014 11:59:18 AM Temperature sensor not found for this address: Barionet 50 Temp 8 (Barionet 50)
> Nov 17, 2014 11:59:18 AM Barionet 50 Temp 5 (floater) ON script activated
> Nov 17, 2014 11:59:19 AM Barionet 50 Temp 3 (outside) ON script activated
> Nov 17, 2014 11:59:19 AM Barionet 50 Temp 3 (outside) ON script activated
> Nov 17, 2014 11:59:23 AM Barionet 50 Temp 1 (fermenter) ON script activated
> Nov 17, 2014 11:59:24 AM Barionet 50 Temp 2 (brewery) ON script activated
> Nov 17, 2014 11:59:28 AM Barionet 50 Temp 1 (fermenter) ON script activated
> Nov 17, 2014 11:59:29 AM Barionet 50 Temp 2 (brewery) ON script activated
> Nov 17, 2014 11:59:35 AM Barionet 50 Temp 2 (brewery) ON script activated
> Nov 17, 2014 11:59:46 AM Barionet 50 Temp 2 (brewery) ON script activated
> Nov 17, 2014 11:59:57 AM Barionet 50 Temp 2 (brewery) ON script activated
> Nov 17, 2014 12:00:05 PM Executing 'Process Updated Temps' script
> 
> First puzzling thing: why the "quitting" message? With no message and a code of 0? 
> Second thing: the connection retry seems to immediately succeed. What's going on? 
> Third thing: what's the "Received Command Error"? 
> Fourth thing: what explains the timing of the received updates? The "outside" sensor is activated twice in the same 1-second interval. The "brewery" sensor is updated five times in 33 seconds. Does this seem right? 
> 
> Maybe I shouldn't obsess over these things because XTension does seem to be getting good data. But I'd like to understand what's going on. 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at shed.com
> http://shed.com/mailman/listinfo/xtensionlist

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shed.com/pipermail/xtensionlist/attachments/20141119/31871471/attachment.html>