CSPP_Core issueshttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues2018-03-06T15:48:26Zhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/1DeviceGuiActor (copied) template should also basically work even if no Device...2018-03-06T15:48:26ZUdo Eisenbarthu.eisenbarth@gsi.deDeviceGuiActor (copied) template should also basically work even if no DeviceProxy is defined.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/2StartActor: Shutdown order is important2019-04-24T07:33:04ZUdo Eisenbarthu.eisenbarth@gsi.deStartActor: Shutdown order is importantKnown issue: If you stop the first actor (in alphabetical order!) in the start actor list, other active actors aren't properly stopped.
Remedy: Be sure to name the application actor to be the (alphabetical) first one in the start actor l...Known issue: If you stop the first actor (in alphabetical order!) in the start actor list, other active actors aren't properly stopped.
Remedy: Be sure to name the application actor to be the (alphabetical) first one in the start actor list. See comment in CSPP_Core.ini.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/3Return warning if proxy enabled but not defined for DeviceActor in CSPP.ini.2018-03-07T08:35:06ZUdo Eisenbarthu.eisenbarth@gsi.deReturn warning if proxy enabled but not defined for DeviceActor in CSPP.ini.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/4Error code bug -89662019-04-24T07:33:04ZGhost UserError code bug -8966Error code -8966 (actor already existing) should be different.Error code -8966 (actor already existing) should be different.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/5CSPP_PVProxy.Activate2019-05-02T11:54:48ZHolger Brandh.brand@gsi.deCSPP_PVProxy.ActivateThe proxy should set its PV:Activate to false when stopping.The proxy should set its PV:Activate to false when stopping.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/6Proposal for CSPP_BaseActor.Stopping Mode2019-10-11T12:29:55ZHolger Brandh.brand@gsi.deProposal for CSPP_BaseActor.Stopping ModeBaseActor may provide a method to indicate stopping mode.
If an actor launches nested actors and receives a Stop-Msg, it should not actually stop itself, but change to stopping mode and ignore all incoming messages except Handl Last Ack...BaseActor may provide a method to indicate stopping mode.
If an actor launches nested actors and receives a Stop-Msg, it should not actually stop itself, but change to stopping mode and ignore all incoming messages except Handl Last Acknowledge Msg. It would stop after all nested actor have stopped/returned.
This extension would be usefull to avoid unnecessary message errors like -1608 etc.
The MessageMaker could generate Do.vi's checking for stopping mode.
What do you think Dennis?Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/7Publish error flag and complete error2019-10-11T11:40:22ZDennis NeidherrPublish error flag and complete errorPublish the error flag as well as the error cluster and move the PublishError VI and all associated functionalities to the BaseActor level.Publish the error flag as well as the error cluster and move the PublishError VI and all associated functionalities to the BaseActor level.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/8Automatic Stopping of StartActor2019-07-09T13:00:22ZDennis NeidherrAutomatic Stopping of StartActorRight now he stopps himself if he gots a handle last acq msg from the first nested actor in an alphabetical list.
This works but seems rather unintuitively. Wouldn't it be better to include a boolean flag for all nested actors of the sta...Right now he stopps himself if he gots a handle last acq msg from the first nested actor in an alphabetical list.
This works but seems rather unintuitively. Wouldn't it be better to include a boolean flag for all nested actors of the start actor indicating if this is a "Main-Actor" which should stop also the StartActor?Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/9GUIActor: Associated Proxy Actor Name2019-07-09T13:25:12ZDennis NeidherrGUIActor: Associated Proxy Actor NameThis information is redundant, or? Because the GUI actor inherits from the BaseActor and the BaseActor already has a PVProxyNameThis information is redundant, or? Because the GUI actor inherits from the BaseActor and the BaseActor already has a PVProxyNamehttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/10GUIActor: Create Msg PVs automatically with correct type2019-07-12T12:36:59ZDennis NeidherrGUIActor: Create Msg PVs automatically with correct typeIf the list is empty he uses variants for everything.
This could be done like in the AfterLunchInit of the PVProxy
==> One could also modify it so that the type is not needed at all in the GUIIf the list is empty he uses variants for everything.
This could be done like in the AfterLunchInit of the PVProxy
==> One could also modify it so that the type is not needed at all in the GUIhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/11CSPP_GUIActor:Connect Set-PVs.vi2019-10-09T07:20:30ZSoenke BeckCSPP_GUIActor:Connect Set-PVs.viError=1 occurrs if empty message in Set-Message array. (Set Variant Attribute)
Please report error, or ignore such elements and generate warning.Error=1 occurrs if empty message in Set-Message array. (Set Variant Attribute)
Please report error, or ignore such elements and generate warning.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/12Better Error messages2021-07-15T10:52:17ZDennis NeidherrBetter Error messages1) If someone wants to create an actor without an entry in the ini file, one just gets -8999 without the name of the actor who wanted to create and the name of the actor which should be created.
2) The error message if a not-optional UR...1) If someone wants to create an actor without an entry in the ini file, one just gets -8999 without the name of the actor who wanted to create and the name of the actor which should be created.
2) The error message if a not-optional URL was not found needs to be improved...Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/13Introspection Core.vi2020-06-15T15:43:04ZHolger Brandh.brand@gsi.deIntrospection Core.viRequire descendant classes to override this dynamic dispatch VI.Require descendant classes to override this dynamic dispatch VI.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/14Show warning if no minimum polling interval set2020-06-16T09:26:04ZUdo Eisenbarthu.eisenbarth@gsi.deShow warning if no minimum polling interval setIf polling interval is set != -1 you almost always have to set a minimum polling interval. Otherwise the system runs with maximum speed. It would be nice to show a message if the mininum polling interval is not set.If polling interval is set != -1 you almost always have to set a minimum polling interval. Otherwise the system runs with maximum speed. It would be nice to show a message if the mininum polling interval is not set.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/15Show message if GUI ref is not set.2020-06-17T17:19:37ZUdo Eisenbarthu.eisenbarth@gsi.deShow message if GUI ref is not set.If "Open FP" for an actor in the object manager is selected and the actor does not have its GUI ref set nothing happens. It would be nice to display a message in this case, that the GUI ref has to be set before.If "Open FP" for an actor in the object manager is selected and the actor does not have its GUI ref set nothing happens. It would be nice to display a message in this case, that the GUI ref has to be set before.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/16Error shown if "classical" message is sent to actor.2020-06-16T08:28:28ZUdo Eisenbarthu.eisenbarth@gsi.deError shown if "classical" message is sent to actor.If a "classical" actor message (generated by NIs message maker) is issued through th object manager an error appear because of casting issues. It would be nice to show a message that the CSPP message maker should be used.If a "classical" actor message (generated by NIs message maker) is issued through th object manager an error appear because of casting issues. It would be nice to show a message that the CSPP message maker should be used.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/17Messages without config dialog are not executed by ObjectManager2020-06-15T15:29:59ZUdo Eisenbarthu.eisenbarth@gsi.deMessages without config dialog are not executed by ObjectManagerIf a message is generated by the CSPP message maker the option "generate config dialog" is disabled (e.g. because the message has no input parameters) it cannot be sent by the object manager. The reason is the the ConfigureDialog.vi of t...If a message is generated by the CSPP message maker the option "generate config dialog" is disabled (e.g. because the message has no input parameters) it cannot be sent by the object manager. The reason is the the ConfigureDialog.vi of the message base class return OK? -> false. Is this a useful standard?https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/18CSPP_BaseActor_Nested Actor Index by Name.vi2021-11-06T19:02:58ZHolger Brandh.brand@gsi.deCSPP_BaseActor_Nested Actor Index by Name.viIndicator Nof Relaunches is not set.Indicator Nof Relaunches is not set.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://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_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