EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2019-06-17T11:05:48Zhttps://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_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/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_DN/CSPP_FPGA/-/issues/1External Trigger2019-05-23T08:54:18ZDennis NeidherrExternal TriggerI think after sending a new pattern to the card, the external trigger flag is always set to on, so that in the GUI one has to switch it on and off again.
But this needs to be confirmed.I think after sending a new pattern to the card, the external trigger flag is always set to on, so that in the GUI one has to switch it on and off again.
But this needs to be confirmed.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CS/PHELIX/PH_Devices/-/issues/5PH_AWG100d: Button "Send Wfm" mechanical action2019-04-10T16:09:21ZUdo Eisenbarthu.eisenbarth@gsi.dePH_AWG100d: Button "Send Wfm" mechanical actionIch bin nicht ganz sicher aber evtl sit die mechanical action des "Send wfm" buttons nicht richtig. Entweder er soll direkt nach dem Drücken wieder "herausspringen" oder nahc Beendigung des "Send" Vorgangs.Ich bin nicht ganz sicher aber evtl sit die mechanical action des "Send wfm" buttons nicht richtig. Entweder er soll direkt nach dem Drücken wieder "herausspringen" oder nahc Beendigung des "Send" Vorgangs.https://git.gsi.de/EE-LV/CSPP/TASCA/UTCS/-/issues/5Interlock reason logging2019-03-25T08:59:04ZHolger Brandh.brand@gsi.deInterlock reason loggingInterlock reason should be logged to historical database.Interlock reason should be logged to historical database.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://git.gsi.de/EE-LV/CSPP/TASCA/UTCS/-/issues/4BeamControlGUI:ChopperStatus inverted2019-03-25T08:59:14ZHolger Brandh.brand@gsi.deBeamControlGUI:ChopperStatus invertedThe display of Chopper status is displayed incorrectly (inverted)
Temporary solution: invert SV UTCS_AE:Chopper_output via scaling.The display of Chopper status is displayed incorrectly (inverted)
Temporary solution: invert SV UTCS_AE:Chopper_output via scaling.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/29Abstract Message with no class constant on blockdiagram2018-10-01T07:55:02ZHolger Brandh.brand@gsi.deAbstract Message with no class constant on blockdiagramError 1055 occurrs in FindAllMessages.vi, if Msg:Do.vi has **no** class constant on its blockdiagramm.
This can happen if an abstract message was created manually by developer, calling only the acestors Do.vi.
Abstract messages obvious...Error 1055 occurrs in FindAllMessages.vi, if Msg:Do.vi has **no** class constant on its blockdiagramm.
This can happen if an abstract message was created manually by developer, calling only the acestors Do.vi.
Abstract messages obviously need special treatment.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/27Action-VI name has to be saved in xml file2018-09-25T13:06:15ZDennis NeidherrAction-VI name has to be saved in xml fileFor return messages an invers search algorithm is implemented. Unfortunatly we have several messages in the system which do not follow the naming convention and therefor the MM will not find the corresponding action VI. An idea would be ...For return messages an invers search algorithm is implemented. Unfortunatly we have several messages in the system which do not follow the naming convention and therefor the MM will not find the corresponding action VI. An idea would be to ask the user for the correct name and save everything in the xml file of the message.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/26Class for ReturnMsg not listed2018-08-27T14:48:17ZHolger Brandh.brand@gsi.deClass for ReturnMsg not listedIt seems that only actor classes from the CSPP_Core are listed for selection of an ancestor Message class.
Expert mode lists only one more actor class. Deactivation of expert mode leaves the list of possible actor class empty.It seems that only actor classes from the CSPP_Core are listed for selection of an ancestor Message class.
Expert mode lists only one more actor class. Deactivation of expert mode leaves the list of possible actor class empty.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/25Bug in DIM I162018-08-09T11:59:03ZDennis NeidherrBug in DIM I16The error for the MainSelect has to be modified. In fact the case for the I16 DIM will never be executed...The error for the MainSelect has to be modified. In fact the case for the I16 DIM will never be executed...Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CS/PHELIX/PH_Devices/-/issues/4Class for Millennia2020-09-30T11:01:04ZDennis NeidherrClass for MillenniaCreate such a class. Note that there is no driver available...Create such a class. Note that there is no driver available...Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/23Object Out is wired wrong2018-08-03T11:32:35ZDennis NeidherrObject Out is wired wrongThere is a problem which occurs if there is an output of the MainVI of an object type (for Return Masgs?!): In this case he wrongly connects it to the ActorOut.There is a problem which occurs if there is an output of the MainVI of an object type (for Return Masgs?!): In this case he wrongly connects it to the ActorOut.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/22Problem with AccessorVI names in return messages2018-08-03T11:33:55ZDennis NeidherrProblem with AccessorVI names in return messagesThere is a huge problem which will lead to major changes in the source code:
Everything is right now so designed that parent and child message classes posses the same Accessor VIs (because both share partly the same attributes). Problem...There is a huge problem which will lead to major changes in the source code:
Everything is right now so designed that parent and child message classes posses the same Accessor VIs (because both share partly the same attributes). Problem is that LabVIEW thinks that I want to overwrite the parent methods, because there are child methods available with the same name. And I get an error because they are not dynamic dispatch.
This is a very nasty behavior... but has to be corrected somehow...Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/20Error when clicking on Abort of ReturnMsg Panel2018-08-03T11:36:36ZDennis NeidherrError when clicking on Abort of ReturnMsg PanelNot sure wether this error is new...Not sure wether this error is new...https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/19Test what happens if one has two messages with the same name but in different...2018-07-19T11:55:33ZDennis NeidherrTest what happens if one has two messages with the same name but in different librariesI have a feeling that this is not working...I have a feeling that this is not working...https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/18Create automatic test sequences2018-07-19T11:56:13ZDennis NeidherrCreate automatic test sequencesFor this purpose create a special CSPP package and a new function within the MM.For this purpose create a special CSPP package and a new function within the MM.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/17Bug: Creating FP with unforseen elements can result in a crash2018-06-14T14:57:48ZDennis NeidherrBug: Creating FP with unforseen elements can result in a crashCreate a "Configure dialog" FP with only a timestamp, or waveform or class and the "BuildFP.vi" will crash. These types are not forseen in the source code and therefore it crashes.Create a "Configure dialog" FP with only a timestamp, or waveform or class and the "BuildFP.vi" will crash. These types are not forseen in the source code and therefore it crashes.Dennis NeidherrDennis Neidherrhttps://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_DSC/-/issues/1Feature request for DSCAlarmViewer2018-05-18T08:23:57ZGhost UserFeature request for DSCAlarmViewerDSCAlarmViewer modification to provide warning message when attempting to stop actor as all existing alarm messages will be missing from the Viewer (but still available in principle in the historical database if logging activated).DSCAlarmViewer modification to provide warning message when attempting to stop actor as all existing alarm messages will be missing from the Viewer (but still available in principle in the historical database if logging activated).