EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2018-09-25T13:06:15Zhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/27Action-VI name has to be saved in xml file2018-09-25T13:06:15ZDennis NeidherrAction-VI name has to be saved in xml fileFor return messages an invers search algorithm is implemented. Unfortunatly we have several messages in the system which do not follow the naming convention and therefor the MM will not find the corresponding action VI. An idea would be ...For return messages an invers search algorithm is implemented. Unfortunatly we have several messages in the system which do not follow the naming convention and therefor the MM will not find the corresponding action VI. An idea would be to ask the user for the correct name and save everything in the xml file of the message.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/29Abstract Message with no class constant on blockdiagram2018-10-01T07:55:02ZHolger Brandh.brand@gsi.deAbstract Message with no class constant on blockdiagramError 1055 occurrs in FindAllMessages.vi, if Msg:Do.vi has **no** class constant on its blockdiagramm.
This can happen if an abstract message was created manually by developer, calling only the acestors Do.vi.
Abstract messages obvious...Error 1055 occurrs in FindAllMessages.vi, if Msg:Do.vi has **no** class constant on its blockdiagramm.
This can happen if an abstract message was created manually by developer, calling only the acestors Do.vi.
Abstract messages obviously need special treatment.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/19Actor Core.vi: PanelBounds2021-11-05T11:26:24ZHolger Brandh.brand@gsi.deActor Core.vi: PanelBounds_Actor Core.vi_: PanelBounds are stored in _CSPP_GUIActor Settings.lvclass_.
Most PHELIX classes have inherited from _BaseGUI_. Many class will decorate the _Actor Core.vi_ with GUI functionality. It is required to restore the PanelBoun..._Actor Core.vi_: PanelBounds are stored in _CSPP_GUIActor Settings.lvclass_.
Most PHELIX classes have inherited from _BaseGUI_. Many class will decorate the _Actor Core.vi_ with GUI functionality. It is required to restore the PanelBounds after launching.
It is not jet clear if all PHELIX classes allow separating the GUI in an independent _CSPP_GUIActor_. Therefore it would be good to move the PanelBound setting to _CSPP_BaseActor_.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/20Add more PV for performance monitoring for CS compatibility reason.2021-11-04T16:35:40ZHolger Brandh.brand@gsi.deAdd more PV for performance monitoring for CS compatibility reason.Following PV are used by CS Inpector and/or [DMS](https://wiki.gsi.de/CSframework/DomainManagementSystem)
- Classname
- Date of birth
- Event counter
- System ID, which is supplied by CS_Start FP or command line parameter.Following PV are used by CS Inpector and/or [DMS](https://wiki.gsi.de/CSframework/DomainManagementSystem)
- Classname
- Date of birth
- Event counter
- System ID, which is supplied by CS_Start FP or command line parameter.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/21Publish received message class to PV.2021-11-10T14:25:36ZHolger Brandh.brand@gsi.dePublish received message class to PV.Message counter is already published in CSPP_BaseActor.Receive Message.vi.
The nam od the received message class should be published, too.Message counter is already published in CSPP_BaseActor.Receive Message.vi.
The nam od the received message class should be published, too.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/22Remote Controlled2021-11-12T17:10:30ZHolger Brandh.brand@gsi.deRemote ControlledMany PHELIX classes are derived from CS class `PH_RemoteControlled`.
This is a feature we could support in general in `CSPP_BaseActor`.
Explanation:
- <b>This is a self-commitment!</b> It cannot be enforced.
- Main purpose: An actor cl...Many PHELIX classes are derived from CS class `PH_RemoteControlled`.
This is a feature we could support in general in `CSPP_BaseActor`.
Explanation:
- <b>This is a self-commitment!</b> It cannot be enforced.
- Main purpose: An actor class can implement a GUI as decoration in its Actor Core.vi. The GUI should disable certain controls that should not be used by an operator, if actor is remote controlled.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/23CSPP_ProcessVariables.lvlib:PVConnection.lvclass:Write.vi URL Problem2022-07-05T13:53:25ZHolger Brandh.brand@gsi.deCSPP_ProcessVariables.lvlib:PVConnection.lvclass:Write.vi URL ProblemThe relevant information for publishing a PV is contained in PVConnection.lvclass.
The PV from caller provides Data, Timestamp, Sttaus, quality and error.
In the actual implementation type descriptor and name are copied from PVConnection...The relevant information for publishing a PV is contained in PVConnection.lvclass.
The PV from caller provides Data, Timestamp, Sttaus, quality and error.
In the actual implementation type descriptor and name are copied from PVConnection to PV, only.
The URL ist missing, but need to be copied, too.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_MQTT/-/issues/1Optimize connection handling to MQTT Broker2022-08-02T17:41:19ZHolger Brandh.brand@gsi.deOptimize connection handling to MQTT BrokerThe actual implementation creates a new client connection for every CSPP_MQTTConnection and CSPP_MQTTMonitor actor. This leads to very many client connections maybe exhausting the limits of number of conections to the broker.
Proposal: ...The actual implementation creates a new client connection for every CSPP_MQTTConnection and CSPP_MQTTMonitor actor. This leads to very many client connections maybe exhausting the limits of number of conections to the broker.
Proposal: Cache the connection to each broker in an FGV instead.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_Documentation/CSPP_QuickStart/-/issues/1Hyperlinks in PDF document are not working2024-02-15T10:56:26Zw.geithnerw.geithner@gsi.deHyperlinks in PDF document are not workingThe hyperlinks in the PDF document seem not to work I tried them in the browser and in a downloaded document opened in Adobe AcrobatThe hyperlinks in the PDF document seem not to work I tried them in the browser and in a downloaded document opened in Adobe AcrobatDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/24Link in README is broken2024-02-15T10:43:48Zw.geithnerw.geithner@gsi.deLink in README is brokenLink https://github.com/HB-GSI/CSPP/wiki used in README is brokenLink https://github.com/HB-GSI/CSPP/wiki used in README is broken