You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happened one time: I tried to enable the DM row with the context menu (a test for the observation above) and I got the update error message. Normally “closing and opening” the Device Configurator fixed the problem. But this time, when I initially tried to update the registers, an error was displayed: Failed to read standard registers of device. When I tried to scan for the devices (through the daemon) no devices where found. But the strange thing is that all events (temperature and buttons) where still received (in the VSCP Sessions window). ???
Attempts to fix this (chronologically:
Restarting VSCP Works did not work.
Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
Stopping daemon and cycling the power of the Frankfurt module and restarting the daemon
Scan found 2 devices.
The text was updated successfully, but these errors were encountered:
This happened one time: I tried to enable the DM row with the context menu (a test for the observation above) and I got the update error message. Normally “closing and opening” the Device Configurator fixed the problem. But this time, when I initially tried to update the registers, an error was displayed: Failed to read standard registers of device. When I tried to scan for the devices (through the daemon) no devices where found. But the strange thing is that all events (temperature and buttons) where still received (in the VSCP Sessions window). ???
Attempts to fix this (chronologically:
The text was updated successfully, but these errors were encountered: