I¡¯m not familiar with the module in question, but -62d = 65473d
-62d is a signed value, 65473 is its unsigned equivalent.
_____
From: Crestron@... [mailto:Crestron@...] On Behalf
Of neil.dorin
Sent: Tuesday, February 15, 2011 4:02 PM
To: Crestron@...
Subject: [Crestron] Re: New Crestron Weather Device Module
HA!
If only a simple Fahrenheit to Celsius conversion would work!!
Ironically, the module has a parameter that defines the output format
already, and yes, I tested it with Fahrenheit, but guess what, I fed it the
Latitude and Longditude of somewhere in the Arctic Circle and Lo and
Behold!!!! CRAP, it does exactly the same thing with negative Fahrenheit
values....
Apparently -62?F is 65473?F according to Crestron's Weather Device...
BTW that's the forecast low temp for tomorrow morning in Rankin Inlet,
Nunavut, Canada if anyone was curious lol.
-Neil
--- In Crestron@... <mailto:Crestron%40yahoogroups.com> , "Stig"
<stig.karlsen@...> wrote:
Hi,
I have just posted a file in the module directory that converts Fahrenheit
to Celsius. It is based on serial strings but it explain the math.
-Stig
--- In Crestron@... <mailto:Crestron%40yahoogroups.com> ,
"neil.dorin" <neildorin@> wrote:
So, as part of the new software release yesterday, the Crestron Weather
Device is now available and operational (After I spent a day two weeks ago
updating and customizing the old Yahoo Direct Socket module...).
Anyway, I'm testing it out on my home system today and discovered an
interesting glitch. When displaying temperatures in Celcius (I imagine this
would also occur in Fahrenheit but you'd have to have temps below 0?F) and
negative values output as serial text are displayed as negative subtracted
analogs (i.e. -5?C is displayed as -65530?C, or 0 - 5).
There's two modules, one is the Crestron Weather Processor v1.2 (cm) and
the other is the Crestron Weather Touchpanel Interface v1.0 (cm).
The Processor v1.2 module has analog outputs for temp values that
display as the same negative value (-65530d) in debugger, but if I right
click on the signal and set the display format to signed decimal, then it
corrects to -5d.
I haven't opened them up in SIMPL to have a look at what's going on yet
(I imagine this is a S+ issue), but does anyone have an obvious clue as to
the error or how to correct it?
I'm sending a bug report to TB too.
Thanks,
-Neil
