I have an issue with how the gemHwMonitorWeb is treating the button clicking.
Here is my current situation:
Start up the application, set the config file, get crate configuration, click on the active crate.
In the log messages, I see that the two GLIBs in the config are initialized
From here, I have two GLIB options to select.
I select GLIB02 (corresponding to IP address 192.168.0.162, while the other one in the config is 192.168.0.164)
It turns out that the GLIB that I've selected, now is assigned 192.168.0.164 (it seems that there is a loop at some previous step and is never renewed)
See, e.g.,
gemHwMonitorWeb::glibPanel() {
...
glibDevice_->setDeviceIPAddress(glibIP);
...
}
glibIP is only set in other locations, so it seems that the flow between clicking on a specific GLIB does not really select this GLIB.
Before we release v0.0.1, we need to have a mechanism for correctly doing this operation.
Maybe keeping the pointers to the various HW devices and on button click, associating the correct pointer?
Screenshot of the hyperdaq page showing the incorrect IP address is attached
I have an issue with how the gemHwMonitorWeb is treating the button clicking. Here is my current situation: Start up the application, set the config file, get crate configuration, click on the active crate. In the log messages, I see that the two GLIBs in the config are initialized From here, I have two GLIB options to select. I select GLIB02 (corresponding to IP address 192.168.0.162, while the other one in the config is 192.168.0.164) It turns out that the GLIB that I've selected, now is assigned 192.168.0.164 (it seems that there is a loop at some previous step and is never renewed) See, e.g.,
gemHwMonitorWeb::glibPanel() {
...
glibDevice_->setDeviceIPAddress(glibIP);
...
}
glibIP is only set in other locations, so it seems that the flow between clicking on a specific GLIB does not really select this GLIB.
Before we release v0.0.1, we need to have a mechanism for correctly doing this operation.
Maybe keeping the pointers to the various HW devices and on button click, associating the correct pointer?
Screenshot of the hyperdaq page showing the incorrect IP address is attached