Skip to content

modifications to use custom_alarm_msg.#67

Open
alraco8444 wants to merge 13 commits into
epics-base:masterfrom
alraco8444:pva2pva_fix
Open

modifications to use custom_alarm_msg.#67
alraco8444 wants to merge 13 commits into
epics-base:masterfrom
alraco8444:pva2pva_fix

Conversation

@alraco8444
Copy link
Copy Markdown

@alraco8444 alraco8444 commented Jul 23, 2025

Summary
This PR includes modifications to enable the use of custom_alarm_msg.

Details

Updated relevant files to support custom_alarm_msg functionality.
This change was made to enable the use of long or alternate alarm messages. The alarm message will only be set if the corresponding INFO field is specified in the database (db) file. If the INFO field is not used, the behaviour remains exactly the same as the original pva2pva implementation. This approach allows existing systems to continue operating without any changes, while giving users the option to leverage extended alarm messages where necessary.

Testing

Confirmed existing tests pass.

Added/updated tests to cover custom alarm message handling (if applicable).

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.54 failed (commit ab676876c2 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.58 failed (commit 1c8f125779 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.55 failed (commit 1c8f125779 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.57 failed (commit 557721487d by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.62 failed (commit 0b0c26e440 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.58 failed (commit 79b93deca2 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.59 failed (commit 0b0c26e440 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.60 failed (commit 7ac4d5ae69 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.61 failed (commit 71185d7159 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.62 failed (commit dc0a1f9996 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.67 failed (commit 9431431c4a by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.63 failed (commit c704bbc978 by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.64 failed (commit 9431431c4a by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.65 failed (commit edd9324a8c by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.68 failed (commit edd9324a8c by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.66 failed (commit 1184fd851d by @jmkk2022)

@AppVeyorBot
Copy link
Copy Markdown

Build pva2pva 1.0.69 failed (commit 1184fd851d by @jmkk2022)

@anjohnson
Copy link
Copy Markdown
Member

EPICS Core Group: Are you really suggesting that we add these changes to the official epics-base/pva2pva repository? We suspect you may be meaning them for an ISIS-specific fork instead. Your description doesn't make the intention clear, and from our perspective we aren't sure that these changes are desirable for the wider community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants