EE-LV issueshttps://git.gsi.de/groups/EE-LV/-/issues2018-01-19T08:48:31Zhttps://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/7PH_Backreflection measurement2018-01-19T08:48:31ZUdo Eisenbarthu.eisenbarth@gsi.dePH_Backreflection measurementChange mechanical action of "Reset warning" button. It's not a switch.
"BR State" is not written to PSDB.Change mechanical action of "Reset warning" button. It's not a switch.
"BR State" is not written to PSDB.https://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/6PH_gentec_Powermeter: Status wrong?2018-01-19T08:45:34ZUdo Eisenbarthu.eisenbarth@gsi.dePH_gentec_Powermeter: Status wrong?Device not found -> Status goes to "off" but not "failure" ....Device not found -> Status goes to "off" but not "failure" ....https://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/5Integrate new beam size measurement (ellipse fitting) in PH_ImageOperator2017-10-11T12:24:57ZUdo Eisenbarthu.eisenbarth@gsi.deIntegrate new beam size measurement (ellipse fitting) in PH_ImageOperatorhttps://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/4PH_VacuumControl2017-10-02T11:03:46ZUdo Eisenbarthu.eisenbarth@gsi.dePH_VacuumControlSend status field to PSDB. Otherwise readout/device errors can only be indentified through "impossible" pressure values (99999,-1,etc.).Send status field to PSDB. Otherwise readout/device errors can only be indentified through "impossible" pressure values (99999,-1,etc.).https://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/3PH_Waveplate-GUI_6P: send waveplate setting to PSDB also in percent.2017-10-02T07:26:23ZUdo Eisenbarthu.eisenbarth@gsi.dePH_Waveplate-GUI_6P: send waveplate setting to PSDB also in percent.https://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/9New DialogPanels are sometimes chaotic2017-07-31T13:44:53ZDennis NeidherrNew DialogPanels are sometimes chaoticSometimes the algorithm to sort the controls on the the Dialog.vis is not working. See for example some panels for in DMM messages.Sometimes the algorithm to sort the controls on the the Dialog.vis is not working. See for example some panels for in DMM messages.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/2Message Maker on RT Targets2017-07-24T09:03:56ZDennis NeidherrMessage Maker on RT TargetsCopied from Github:
This is right now not working. He obviously tries to include the Messages to the host System.Copied from Github:
This is right now not working. He obviously tries to include the Messages to the host System.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CSPP/CSPP_MessageMaker/-/issues/1Multiple URLs per message2018-09-28T11:31:14ZDennis NeidherrMultiple URLs per messageCopied from Github:
This Feature has to be included in the Message Maker. This means in fact that only the Do.vi has to be modified slightly in order to send the complete URL Name (with the channel Name) to the public method.
(see CS++...Copied from Github:
This Feature has to be included in the Message Maker. This means in fact that only the Do.vi has to be modified slightly in order to send the complete URL Name (with the channel Name) to the public method.
(see CS++Motor Update Messages).
The problem here is that I would also have to modify the Action method of the actor (I would need to add a string input for the URL), I think this is not very conveniant, so I will think further about this topic...
One can sava the information about the connected URLs in the attribute data of the original actor, make the read access to this public, and use it in the Do.vi of the generated message to check which channel has to be executed.Dennis NeidherrDennis Neidherrhttps://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/2Vacuum measurement: Typo2017-06-21T14:36:27ZUdo Eisenbarthu.eisenbarth@gsi.deVacuum measurement: TypoThe mouseover text on the "status" field of the vacuum measurement frontend contains a typo: "Yellow...at least one value TOO high".The mouseover text on the "status" field of the vacuum measurement frontend contains a typo: "Yellow...at least one value TOO high".https://git.gsi.de/EE-LV/CS/PHELIX/PH_Basics/-/issues/1Performance issues with ImageStatistian2017-06-21T14:34:40ZUdo Eisenbarthu.eisenbarth@gsi.dePerformance issues with ImageStatistianIf more than about 8000 points are written to a graph, the performance drops dramatically.
E.g. Open ImagStati1 on fsFEfrontend PC. Select Energy. Press "Start" -> the more measurements are taken (>8000) the slower the machine becomes. C...If more than about 8000 points are written to a graph, the performance drops dramatically.
E.g. Open ImagStati1 on fsFEfrontend PC. Select Energy. Press "Start" -> the more measurements are taken (>8000) the slower the machine becomes. CPU load also goes up to 100%.