EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2019-04-10T16:09:21Zhttps://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_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/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/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 Neidherrhttps://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/CS/CS_Afg/-/issues/1SetTrigger Delay function2018-09-11T09:04:36ZDennis NeidherrSetTrigger Delay functionThis function is needed for the AFG3352X class for both channels.This function is needed for the AFG3352X class for both channels.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/24Return message of a return message2018-07-26T12:46:45ZDennis NeidherrReturn message of a return messageThis is right now not working due to naming (I think).
Question is if this is really needed.This is right now not working due to naming (I think).
Question is if this is really needed.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/21Check the performance2018-09-04T11:38:44ZDennis NeidherrCheck the performanceThe MM is now already relatively large and complex and therefore it gets slower and slower. It would be a good idea to find out where the performance bottle necks are and try to correct them. For this timing measurement VIs have to be in...The MM is now already relatively large and complex and therefore it gets slower and slower. It would be a good idea to find out where the performance bottle necks are and try to correct them. For this timing measurement VIs have to be included.
(I think there is a major bottle neck in the "change icon".vi)...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.