Cannot Contact LWDAQ Driver
Posted: Thu Aug 10, 2023 10:04 pm
A customer writes:
"On Monday, as I was trying to continue following the set-up instructions (been a while since the last time I did that, so I wanted to do a refresher upon returning from my annual leave) and ultimately test the SCT. Whilst doing that, I experienced an error whilst pressing the Contact button on the Configurator Tool (see attached picture). It seemed to be working just fine and was successfully producing a script, but after some time the error messages kept coming through.
"The IP address and subnet mask were changed a while ago according to the website's instructions in order to make the configurator contact the driver. This seemed to be successful as the software was producing script alike the website instructions (last time I practised that was end of July).
"I had someone from IT to come over and see if they can figure out on how to solve this. The first thing that came to my mind was whether the admin rights for the IP and subnet mask got revoked and ultimately changed the values I originally inserted. This didn't seem to be the case as the IT person double checked and all values (10.0.0.2 and 255.255.255.0) were the same as last time. We tried a couple other alternatives to see if this fixes the issue, such as turning everything off, resetting the LWDAQ's EEPROM configuration file by following the website's instruction, switching cables, re-downloading the software and following the set-up instruction from the beginning. Upon trying all the above, there were unfortunately still error messages coming through.
"The person from IT believes there might be a network issue as we could not ping the instrument and we could before. He also found it suspicious that the link light was permanently on and constantly lit - even after removing the Ethernet cable. He suggested that there might be a hardware fault with the network function in the driver, but again he is not sure about it.
"It was working just fine and then all of the sudden I kept receiving error messages, so I thought it might be best contacting you and see if you have any advice on the matter or if I am missing something."
"On Monday, as I was trying to continue following the set-up instructions (been a while since the last time I did that, so I wanted to do a refresher upon returning from my annual leave) and ultimately test the SCT. Whilst doing that, I experienced an error whilst pressing the Contact button on the Configurator Tool (see attached picture). It seemed to be working just fine and was successfully producing a script, but after some time the error messages kept coming through.
"The IP address and subnet mask were changed a while ago according to the website's instructions in order to make the configurator contact the driver. This seemed to be successful as the software was producing script alike the website instructions (last time I practised that was end of July).
"I had someone from IT to come over and see if they can figure out on how to solve this. The first thing that came to my mind was whether the admin rights for the IP and subnet mask got revoked and ultimately changed the values I originally inserted. This didn't seem to be the case as the IT person double checked and all values (10.0.0.2 and 255.255.255.0) were the same as last time. We tried a couple other alternatives to see if this fixes the issue, such as turning everything off, resetting the LWDAQ's EEPROM configuration file by following the website's instruction, switching cables, re-downloading the software and following the set-up instruction from the beginning. Upon trying all the above, there were unfortunately still error messages coming through.
"The person from IT believes there might be a network issue as we could not ping the instrument and we could before. He also found it suspicious that the link light was permanently on and constantly lit - even after removing the Ethernet cable. He suggested that there might be a hardware fault with the network function in the driver, but again he is not sure about it.
"It was working just fine and then all of the sudden I kept receiving error messages, so I thought it might be best contacting you and see if you have any advice on the matter or if I am missing something."