Hi, I'm using ITA 9.0.6 on prem in the latest version of chrome and found that when I try to use the "Find Equipment on the Floor" search box, nothing happens when I hit enter.  This was in the latest version of  Chrome Version 83.0.4103.61 (Official Build) (64-bit)         ... View more

I have  a customer running DCE 7.8.0 that has frequent modbus lost comm alarms using the 3rd party vendors modbus tcp gateway..  The customer had larger polling intervals/time outs and retries, but I lowered them to 10 mins, 15 sec timeout, 3 retries.   Looking at the messages log, its flooded with messages modbus connection failed/timed out so I assume that's just the end device failing to respond or some other physical layer related issue, not a problem with DCE.   On another note, this is a Virtual DCE server, are these serial port related processes terminating/respawning anything to be concerned with?     Any assistance would be appreciated.   Apr 29 05:42:35 zz-struxureware nbModbusScan: modbus_process_conn_cbk: connect failed - Connection timed out Apr 29 05:42:35 zz-struxureware nbModbusScan: modbus_process_conn_cbk: open session failed - Connection timed out Apr 29 05:42:35 zz-struxureware nbModbusScan: async_connect_response: Connect failed retry attempt 0 of 10. Apr 29 05:42:41 zz-struxureware init: ttyS0 main process (25955) terminated with status 1 Apr 29 05:42:41 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:42:51 zz-struxureware init: ttyS0 main process (25957) terminated with status 1 Apr 29 05:42:51 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:01 zz-struxureware init: ttyS0 main process (25960) terminated with status 1 Apr 29 05:43:01 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:11 zz-struxureware init: ttyS0 main process (25966) terminated with status 1 Apr 29 05:43:11 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:21 zz-struxureware init: ttyS0 main process (25969) terminated with status 1 Apr 29 05:43:21 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:31 zz-struxureware init: ttyS0 main process (25977) terminated with status 1 Apr 29 05:43:31 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:38 zz-struxureware nbModbusScan: modbus_process_conn_cbk: connect failed - Connection timed out Apr 29 05:43:38 zz-struxureware nbModbusScan: modbus_process_conn_cbk: open session failed - Connection timed out Apr 29 05:43:38 zz-struxureware nbModbusScan: async_connect_response: Connect failed retry attempt 1 of 10. Apr 29 05:43:41 zz-struxureware init: ttyS0 main process (25985) terminated with status 1 Apr 29 05:43:41 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:51 zz-struxureware init: ttyS0 main process (25995) terminated with status 1 Apr 29 05:43:51 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:43:55 zz-struxureware nbSNMPScan: failScan: Marking scan of 10.x.x.x with SCAN_FAILED resultcode. Apr 29 05:44:01 zz-struxureware init: ttyS0 main process (26003) terminated with status 1 Apr 29 05:44:01 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:44:11 zz-struxureware init: ttyS0 main process (26012) terminated with status 1 Apr 29 05:44:11 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:44:21 zz-struxureware init: ttyS0 main process (26020) terminated with status 1 Apr 29 05:44:21 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:44:24 zz-struxureware nbSNMPScan: failScan: Marking scan of 10.x.x.x with SCAN_FAILED resultcode. Apr 29 05:44:31 zz-struxureware init: ttyS0 main process (26036) terminated with status 1 Apr 29 05:44:31 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:44:41 zz-struxureware nbModbusScan: modbus_process_conn_cbk: connect failed - Connection timed out Apr 29 05:44:41 zz-struxureware nbModbusScan: modbus_process_conn_cbk: open session failed - Connection timed out Apr 29 05:44:41 zz-struxureware nbModbusScan: async_connect_response: Connect failed retry attempt 2 of 10. Apr 29 05:44:41 zz-struxureware init: ttyS0 main process (26039) terminated with status 1 Apr 29 05:44:41 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:44:51 zz-struxureware init: ttyS0 main process (26043) terminated with status 1 Apr 29 05:44:51 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:45:01 zz-struxureware init: ttyS0 main process (26046) terminated with status 1 Apr 29 05:45:01 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:45:11 zz-struxureware init: ttyS0 main process (26048) terminated with status 1 Apr 29 05:45:11 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:45:21 zz-struxureware init: ttyS0 main process (26049) terminated with status 1 Apr 29 05:45:21 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:45:31 zz-struxureware init: ttyS0 main process (26051) terminated with status 1 Apr 29 05:45:31 zz-struxureware init: ttyS0 main process ended, respawning Apr 29 05:45:41 zz-struxureware init: ttyS0 main process (26052) terminated with status 1 Apr 29 05:45:41 zz-struxureware init: ttyS0 main process ended, respawning     ... View more

I'm having an issue with DCO support for measured power data not working as expected for a DC Rectifier in DCE.    After some more testing, it appears that when the the device is type in DCE is "DC Rectifier", DCE web services ignore the setProductData fields for inputPhaseCount and outputPhaseCount in the DCE Device Definition File (DDF).    Using the same device and same ddf, If I change the device type in DCE to a Rack PDU, those supplemental fields show up in web services when I use the getAllDevices request.  This was the same if I changed it to a UPS, PDU, Power Meter, and Transfer Switch.   This was with DCE 7.8.0.  Is this a bug or is it working as designed?       ... View more