Re: Phoebus 4.7 — `lsi`/`lso` long strings, `.$` PV names, and macro “not fully resolved” warnings

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

Hi Kay,

Thank you for investigating this and for the clarification.

It's good to know that using NameOfLongString.$ (or NameOfLongString.VAL$) is the correct approach for reading EPICS long strings, and that the Phoebus "not fully resolved" warning is simply a false positive caused by the trailing $ being mistaken for an unresolved macro.

That explains the behavior we were seeing. We'll continue using the .$ syntax and ignore the warning for now. It's also great to hear that this has already been addressed and will disappear in an upcoming Phoebus release.

I appreciate your help.

Best regards,
Kaz

---

From: Kasemir, Kay <kasemirk at ornl.gov>
Sent: Friday, June 12, 2026 9:53 AM
To: Gofron, Kaz <gofronkj at ornl.gov>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Phoebus 4.7 — `lsi`/`lso` long strings, `.$` PV names, and macro “not fully resolved” warnings

 

Hi:

To read long strings, you do need to use NameOfLongString.VAL$ or NameOfLongString.$

The display warning is misleading, it mistakes any remaining ‘$’ for an unresolved macro.

You can simply ignore the warning, it will go away in an upcoming phoebus update, https://github.com/ControlSystemStudio/phoebus/pull/3831

-Kay

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Gofron, Kaz via Tech-talk <tech-talk at aps.anl.gov>
Date: Tuesday, June 9, 2026 at 1:31 AM

`caget -S TAS:Plot:SelectedFile.$`

...

On **every screen reload**, however, the Phoebus terminal logs warnings such as:

Widget 'SelectedFile' (textentry) 'pv_name' is not fully resolved: 'TAS:Plot:SelectedFile.$'