EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2020-02-17T10:19:11Zhttps://git.gsi.de/EE-LV/CSPP/TASCA/UTCS/-/issues/6UXADT2 Current Indicator of FPGS value can be removed from FP2020-02-17T10:19:11ZHolger Brandh.brand@gsi.deUXADT2 Current Indicator of FPGS value can be removed from FPReason: FPGA used UX8DT3 Range bits also for UXADT2 which is not always the same. Range bit for UXADT2 are not availbale for FPGA.
Remove corresponding indicator from BeamControlGUI front panel.Reason: FPGA used UX8DT3 Range bits also for UXADT2 which is not always the same. Range bit for UXADT2 are not availbale for FPGA.
Remove corresponding indicator from BeamControlGUI front panel.r.a.cantemirr.a.cantemirhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/10Reset PPG card if error2019-11-13T11:01:38ZDennis NeidherrReset PPG card if errorIf an error occures (for example time to short) it is not possible to reset it.
Maybe it would be a good idea to reset the card automatically if an error occured.If an error occures (for example time to short) it is not possible to reset it.
Maybe it would be a good idea to reset the card automatically if an error occured.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DIM/-/issues/1Write PV with unit causes conversion error 91 if PV.Data has unit.2019-11-07T15:10:57ZHolger Brandh.brand@gsi.deWrite PV with unit causes conversion error 91 if PV.Data has unit.In `CSPP_DIM.lvlib:DIMConnection.lvclass:Write Core.vi` PV is converted to Data as string and Quality as I32. The conversion is implemented in `CSPP_DIM.lvlib:DIMConnection.lvclass:PV 2 Data.vi`.
`CSPP_DIM.lvlib:DIMConnection.lvclass:2DI...In `CSPP_DIM.lvlib:DIMConnection.lvclass:Write Core.vi` PV is converted to Data as string and Quality as I32. The conversion is implemented in `CSPP_DIM.lvlib:DIMConnection.lvclass:PV 2 Data.vi`.
`CSPP_DIM.lvlib:DIMConnection.lvclass:2DIMData.vi` returns ERROR in `DIM Type Descriptor Out` and error code=91 if PV.Data has a unit. Example: PollingInterval has unit:s (second).Dennis NeidherrDennis Neidherrhttps://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_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_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/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_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/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_Acquisition/-/issues/1TDCGui: Fit SumX/Y2019-07-03T10:13:33ZDennis NeidherrTDCGui: Fit SumX/YA small gaussian fit would be niceA small gaussian fit would be niceDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/9PPGGUI should indicate MaxCycle Length2019-07-03T07:55:22ZDennis NeidherrPPGGUI should indicate MaxCycle LengthThis is an always needed infoThis is an always needed infoDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/3PPG GUI Info Indicators2019-06-05T12:00:24ZDennis NeidherrPPG GUI Info IndicatorsDelete SelfTestResult Code + Message
and
add maybe info about the FPGA card (version, clock rate etc).Delete SelfTestResult Code + Message
and
add maybe info about the FPGA card (version, clock rate etc).Dennis 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/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/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/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_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/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_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/28Overwrite Do.vi2018-09-28T11:28:04ZDennis NeidherrOverwrite Do.viSimilar to the Configure Dialog.vi it could be interessting to make the overwriting of the Do.vi optional.
On top of this there was the idea to use a user specific comment on the block diagramn to tell the MM to not overwrite the Do.vi...Similar to the Configure Dialog.vi it could be interessting to make the overwriting of the Do.vi optional.
On top of this there was the idea to use a user specific comment on the block diagramn to tell the MM to not overwrite the Do.vi.
Unfortunatly the amount of work needed to implement this outwights right now the gain in my opinion so I will pospone it.Dennis NeidherrDennis Neidherr