EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2020-06-16T09:26:04Zhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/14Show warning if no minimum polling interval set2020-06-16T09:26:04ZUdo Eisenbarthu.eisenbarth@gsi.deShow warning if no minimum polling interval setIf polling interval is set != -1 you almost always have to set a minimum polling interval. Otherwise the system runs with maximum speed. It would be nice to show a message if the mininum polling interval is not set.If polling interval is set != -1 you almost always have to set a minimum polling interval. Otherwise the system runs with maximum speed. It would be nice to show a message if the mininum polling interval is not set.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/15Message Documentation2018-07-09T10:13:31ZHolger Brandh.brand@gsi.deMessage DocumentationCopy description of action VI to message call description.Copy description of action VI to message call description.https://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/15Show message if GUI ref is not set.2020-06-17T17:19:37ZUdo Eisenbarthu.eisenbarth@gsi.deShow message if GUI ref is not set.If "Open FP" for an actor in the object manager is selected and the actor does not have its GUI ref set nothing happens. It would be nice to display a message in this case, that the GUI ref has to be set before.If "Open FP" for an actor in the object manager is selected and the actor does not have its GUI ref set nothing happens. It would be nice to display a message in this case, that the GUI ref has to be set before.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/16Support for Asynchronous Callback Messages2018-07-06T12:22:01ZHolger Brandh.brand@gsi.deSupport for Asynchronous Callback MessagesDerived messages of CSPP_AsyncCallbackMsg would need to store return values of an action VI in it message class attribute. Example:https://git.gsi.de/EE-LV/CSPP/CSPP_DN/CS_Workshop/tree/AsyncCBMsg/Actors/CSPP_InstrSim%20Messages/Get%20DC...Derived messages of CSPP_AsyncCallbackMsg would need to store return values of an action VI in it message class attribute. Example:https://git.gsi.de/EE-LV/CSPP/CSPP_DN/CS_Workshop/tree/AsyncCBMsg/Actors/CSPP_InstrSim%20Messages/Get%20DC_Voltage%20Msg
The callback message would read the action VI's return values to be used as inputs for its own callback action VI. Example: https://git.gsi.de/EE-LV/CSPP/CSPP_DN/CS_Workshop/tree/AsyncCBMsg/Actors/CSPP_InstrSimCtrl%20Messages/DCVoltage-CB%20Msg.
When creating a callback message using the MassageMaker a dialog box could be display, so the developer can select the desired CS++ Message to inherit from. It an one to one association between return and own input parameters exist, the wiring could be dne automaticallay by the MM other wise the user would need to parse the return data manually.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_Core/-/issues/16Error shown if "classical" message is sent to actor.2020-06-16T08:28:28ZUdo Eisenbarthu.eisenbarth@gsi.deError shown if "classical" message is sent to actor.If a "classical" actor message (generated by NIs message maker) is issued through th object manager an error appear because of casting issues. It would be nice to show a message that the CSPP message maker should be used.If a "classical" actor message (generated by NIs message maker) is issued through th object manager an error appear because of casting issues. It would be nice to show a message that the CSPP message maker should be used.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/17Messages without config dialog are not executed by ObjectManager2020-06-15T15:29:59ZUdo Eisenbarthu.eisenbarth@gsi.deMessages without config dialog are not executed by ObjectManagerIf a message is generated by the CSPP message maker the option "generate config dialog" is disabled (e.g. because the message has no input parameters) it cannot be sent by the object manager. The reason is the the ConfigureDialog.vi of t...If a message is generated by the CSPP message maker the option "generate config dialog" is disabled (e.g. because the message has no input parameters) it cannot be sent by the object manager. The reason is the the ConfigureDialog.vi of the message base class return OK? -> false. Is this a useful standard?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_Core/-/issues/18CSPP_BaseActor_Nested Actor Index by Name.vi2021-11-06T19:02:58ZHolger Brandh.brand@gsi.deCSPP_BaseActor_Nested Actor Index by Name.viIndicator Nof Relaunches is not set.Indicator Nof Relaunches is not set.Holger Brandh.brand@gsi.deHolger Brandh.brand@gsi.dehttps://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/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/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/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/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/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/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/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/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/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/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.