RE: Odd characters in temperatures showing in Phoebus

["Leblanc, Gregory via Tech-talk" <tech-talk at aps.anl.gov>]

Well, that gives me some interesting results. 

 

Full dump at: https://pastebin.com/4iqDBfem

 

TL;DR:

> caget -d CTRL_DOUBLE SP_Cesium:Oven_Heater:ProcessValue1

    Units:            ┬░

> ssh elsewhere & return

> caget -d CTRL_DOUBLE SP_Cesium:Oven_Heater:ProcessValue1

    Units:            °

 

Same behavior using PowerShell and command prompt.  I don’t see any change to $OutputEncoding before or after the ssh command, nor does manually setting $OutputEncoding = [System.Text.Encoding]::UTF8 make any difference.  Chcp reports the same active code page before and after ssh (437), so that doesn’t seem to be the right direction.  I don’t have hexdump on windows, yet. 

     Greg

 

From: Kasemir, Kay <kasemirk at ornl.gov>
Sent: Monday, October 4, 2021 3:43 PM
To: tech-talk at aps.anl.gov; Leblanc, Gregory <leblanc at ohio.edu>
Subject: Re: Odd characters in temperatures showing in Phoebus

 

> caget SP_Cesium:Oven_Heater:ProcessValue1

SP_Cesium:Oven_Heater:ProcessValue1 22.855

 

Try

   caget -d CTRL_DOUBLE SP_Cesium:Oven_Heater:ProcessValue1

and note the 'Units'.

Also try

   caget -d CTRL_DOUBLESP_Cesium:Oven_Heater:ProcessValue1 | hexdump -c

to see exactly what characters follow the "Units:"...

 

Fundamentally, phoebus will allow UTF-8 encoded text for the units.

 

-Kay