EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2019-11-13T11:01:38Zhttps://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_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/-/issues/4Add helper function for PV publish2019-10-11T14:02:09ZUdo Eisenbarthu.eisenbarth@gsi.deAdd helper function for PV publishSimplify the setting of PVConnection (Value, Timestamp,Error,etc...) and publishing in order to reduce code doublication.Simplify the setting of PVConnection (Value, Timestamp,Error,etc...) and publishing in order to reduce code doublication.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP/-/issues/7Notifier for the AF2019-10-11T12:41:56ZDennis NeidherrNotifier for the AFImplement mechanism to add notifiers in the original AFImplement mechanism to add notifiers in the original AFhttps://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/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/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_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_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/2PPG GUI Save button greyed out2019-06-17T11:05:48ZDennis NeidherrPPG GUI Save button greyed outI think the save button stays to be greyed out after a file was openedI think the save button stays to be greyed out after a file was openedDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/5Asterix in title if pattern or times change2019-06-17T11:05:39ZDennis NeidherrAsterix in title if pattern or times changePut an asterix behind the file name if someone changed the timining or output tablePut an asterix behind the file name if someone changed the timining or output tableDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/4PPG save files2019-06-17T11:05:29ZDennis NeidherrPPG save filesmaybe the ending .ppg would be good?maybe the ending .ppg would be good?Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/6Keybinds for functions2019-06-17T11:05:20ZDennis NeidherrKeybinds for functionsAdd keybinds for FPGA functionsAdd keybinds for FPGA functionsDennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_DN/CSPP_FPGA/-/issues/7Add a digital wafveform to show pattern2019-06-17T11:05:12ZDennis NeidherrAdd a digital wafveform to show patternCheck how much work this is.
It would help to see how the pattern really loooks likeCheck how much work this is.
It would help to see how the pattern really loooks likeDennis NeidherrDennis Neidherr