EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2024-02-15T10:43:48Zhttps://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 brokenhttps://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_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_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_DIM/-/issues/2No link info is not propagated by CSPP_DIMMonitor.2021-11-22T09:59:12ZHolger Brandh.brand@gsi.deNo link info is not propagated by CSPP_DIMMonitor.DIM reports whether a command or service is available or not.
**CS++** PVConnection abstraction does not provide such information.
In case of no link the CSPP_DIMMonitor.lvclass sends a message with empty variant instaed, but no error is...DIM reports whether a command or service is available or not.
**CS++** PVConnection abstraction does not provide such information.
In case of no link the CSPP_DIMMonitor.lvclass sends a message with empty variant instaed, but no error is set in PV and therefore good quality and status.https://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/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/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/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_Tools/-/issues/5Create accessors for Self-Addressed Msg.lvclass2021-10-13T08:10:52ZHolger Brandh.brand@gsi.deCreate accessors for Self-Addressed Msg.lvclassWhen thinking about sequencer, one could (programmatically) setup an array of self-addressed callback messages to be executed by a corresponding sequencer actor. It could be possible that such a sequencer needs read access to the attribu...When thinking about sequencer, one could (programmatically) setup an array of self-addressed callback messages to be executed by a corresponding sequencer actor. It could be possible that such a sequencer needs read access to the attributes of Self-Addressed Msg.lvclass.
Such accessors could be easily manually created by a LabVIEW developer, but it would be very convenient if it could by done during installation of the CSPP_Tools.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/ESRBB/ESRBBRT/-/issues/1Configuration file2021-09-24T13:06:20ZHolger Brandh.brand@gsi.deConfiguration fileConfiguration parameters are stored as default values in a global variable, which has the advantage that everything is encapsulated in the RT.exe. The disadvantage is, that these parameters can not be changed without compiling.
Proposal...Configuration parameters are stored as default values in a global variable, which has the advantage that everything is encapsulated in the RT.exe. The disadvantage is, that these parameters can not be changed without compiling.
Proposal:
Parameters to be changed without recompiling the RT.exe are stored in an ini.file which is read at startup, respectively reboot, of the RT.exe into the global variable. Parameters can be changed by uploading the ini-file to the RT system. A login is neccessary for file-upload.
Question:
Which parameters must be configurable at runtime?Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/39CSPP_MessageMaker support for Callback Messages with no return parameter exce...2021-09-17T08:30:03ZHolger Brandh.brand@gsi.deCSPP_MessageMaker support for Callback Messages with no return parameter except error clusterThere are scenarios in which you would like to get the error out from a callback message calling a public VI with no other return parameters. The creation of such callback messages are currently not supported by the CSPP_MessageMaker.
I...There are scenarios in which you would like to get the error out from a callback message calling a public VI with no other return parameters. The creation of such callback messages are currently not supported by the CSPP_MessageMaker.
I attached two template-VI's illustrating my proposal.
- [CB_Message.vit](/uploads/929b2323f27422df9c5f6a378c0ffabe/CB_Message.vit)
- [CB_Message_Do.vit](/uploads/dba1daf7a045d13194c53e19e4cd751c/CB_Message_Do.vit)Dennis NeidherrDennis Neidherrhttps://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/GSI_VAC/VacuumHeating/-/issues/2Zuordnung Heizkanäle2021-11-24T16:59:41Zg.savinoZuordnung HeizkanäleBeim löschen gewisser Heizkreise aus der Liste rücken die anderen in der Anzeige auf, das soll so nicht sein.
Die Zuordnung muss fest bleiben.Beim löschen gewisser Heizkreise aus der Liste rücken die anderen in der Anzeige auf, das soll so nicht sein.
Die Zuordnung muss fest bleiben.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/38Improve message dialog2021-08-30T13:38:16ZHolger Brandh.brand@gsi.deImprove message dialogPlease add a bookmark comment in the dialog VI's frontpanel to review it for adjustment.
This can hopefully easily done by adding it to the corresponding template.viPlease add a bookmark comment in the dialog VI's frontpanel to review it for adjustment.
This can hopefully easily done by adding it to the corresponding template.viDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Acquisition/-/issues/2AutoScale in GUI2021-06-30T08:48:35ZDennis NeidherrAutoScale in GUICut data which is outside of a special window (autoscale should still work)Cut data which is outside of a special window (autoscale should still work)Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CS/CS/-/issues/1UserGOG:Window settings (XML)2021-05-07T14:40:04ZHolger Brandh.brand@gsi.deUserGOG:Window settings (XML)A UserGOG instance reads in its constructor sub-vis an XML file with window position and bounds.
If file is not existing the file is not read, that's fine.
If file is existing, but corrupted, it causes error unflatten from XML string.
Pr...A UserGOG instance reads in its constructor sub-vis an XML file with window position and bounds.
If file is not existing the file is not read, that's fine.
If file is existing, but corrupted, it causes error unflatten from XML string.
Proposal: Ignore settings file on error.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DeviceBase/-/issues/6Feature request: Safe-State2021-05-07T11:45:26ZHolger Brandh.brand@gsi.deFeature request: Safe-StateCSPP_DeviceBase actor provide several option to initialize a first state or query the current state only without altering it.
**Proposal: Safe-State**
- Add an abstract method the set a device in a pre-defined safe-state.
- Add a parame...CSPP_DeviceBase actor provide several option to initialize a first state or query the current state only without altering it.
**Proposal: Safe-State**
- Add an abstract method the set a device in a pre-defined safe-state.
- Add a parameter to optionally set safe state during actor stop.
This could be implemented by using an additional safe-state setting object.
What do you think?https://git.gsi.de/EE-LV/CSPP/CSPP_FGen/-/issues/2CSPP_FGen:Initialize Device Core.vi - Execute Apply Settings2021-05-07T08:32:10ZHolger Brandh.brand@gsi.deCSPP_FGen:Initialize Device Core.vi - Execute Apply SettingsWhy is the Apply Settings Msg send to self in case of ignore?
Bug or feature?
Wrong case assignment?![CSPP_FGen.Initialize_Device_Core](/uploads/faf07b49511ab5ce2e47b7fbd289ddb9/CSPP_FGen.Initialize_Device_Core.PNG)Why is the Apply Settings Msg send to self in case of ignore?
Bug or feature?
Wrong case assignment?![CSPP_FGen.Initialize_Device_Core](/uploads/faf07b49511ab5ce2e47b7fbd289ddb9/CSPP_FGen.Initialize_Device_Core.PNG)Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DeviceBase/-/issues/5CSPP_Fgen.lvclass:Get Phase .vi: Attribute assignment2021-05-05T08:10:40ZHolger Brandh.brand@gsi.deCSPP_Fgen.lvclass:Get Phase .vi: Attribute assignmentStartPhase is replaced in Set_StartPhase array.
All other Get..vis' replace the corresponding Get_... array element.
Bug or intention?StartPhase is replaced in Set_StartPhase array.
All other Get..vis' replace the corresponding Get_... array element.
Bug or intention?Dennis NeidherrDennis Neidherr