EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2018-10-05T08:00:04Zhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/30Crash if a message class is locked2018-10-05T08:00:04ZDennis NeidherrCrash if a message class is lockedThis can happen if a msg is already used somewhere else in the project, someone deletes the msg and restarts the project. Then the msg class can not be loaded (since it is not anymore on disc). If one wants to recreate the msg class one ...This can happen if a msg is already used somewhere else in the project, someone deletes the msg and restarts the project. Then the msg class can not be loaded (since it is not anymore on disc). If one wants to recreate the msg class one gets an error.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/31Non-expert list when creating a return msg is sometimes not working2019-04-12T06:54:44ZDennis NeidherrNon-expert list when creating a return msg is sometimes not workingTried it with 4 inputs I just copied from the outputs of an already existing msg and the list was empty....Tried it with 4 inputs I just copied from the outputs of an already existing msg and the list was empty....Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/32Error when the ActionVI has more than 4 inputs and / or outputs2019-04-12T06:56:39ZDennis NeidherrError when the ActionVI has more than 4 inputs and / or outputsIn such a case an error should be created and everything already created should be deleted
==
A far more advanced solution would be to open an additional window and force the user to bundle some inputs (outputs)...In such a case an error should be created and everything already created should be deleted
==
A far more advanced solution would be to open an additional window and force the user to bundle some inputs (outputs)...Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/33Add MM Version number to Front panel titel2019-04-12T07:15:13ZDennis NeidherrAdd MM Version number to Front panel titelJust a small improvementJust a small improvementDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/34Description for generated messages2019-04-15T14:46:47ZHolger Brandh.brand@gsi.deDescription for generated messagesI would be convenient if the message class description is filled with the description of the corresponding public VI.I would be convenient if the message class description is filled with the description of the corresponding public VI.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/35ERROR: Inputs and Outputs need to have different names2019-07-09T11:21:02ZDennis NeidherrERROR: Inputs and Outputs need to have different namesOtherwise one can get an error message.
Within the attribute data the label of the second control/indicator is changed from "Lock" to "Lock 2" for example.
The BuildSend.vi on the other hand searches for the original "Lock" output and n...Otherwise one can get an error message.
Within the attribute data the label of the second control/indicator is changed from "Lock" to "Lock 2" for example.
The BuildSend.vi on the other hand searches for the original "Lock" output and not for "Lock 2" therefore an error is produced.
Ideas to overcome this problem:
1) Include an error message telling the user to rename the output
2) Better would be to modify the BuildSend.vi for this caseDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/36ERROR: An error is shown if the VirtualFolder is called "Messages" and not "M...2019-07-09T11:52:57ZDennis NeidherrERROR: An error is shown if the VirtualFolder is called "Messages" and not "Message"nTnTDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/37Parsing of PV date of type variant needs special treatment.2019-10-22T09:05:12ZUdo Eisenbarthu.eisenbarth@gsi.deParsing of PV date of type variant needs special treatment.If the received PV.Data is of type variant, it needs special parsing.
Instead of *Variant to Data* one need to compare to *empty variant* in order to decide to used the PV.Data or data from message attribute. A possible implementation is...If the received PV.Data is of type variant, it needs special parsing.
Instead of *Variant to Data* one need to compare to *empty variant* in order to decide to used the PV.Data or data from message attribute. A possible implementation is attached and tested within the Wombat project.![CSPP_MessageMaker_Variant_Datatype_Parsing](/uploads/6f804491d71c3f614552daca427a9d92/CSPP_MessageMaker_Variant_Datatype_Parsing.PNG)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_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_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/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_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/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