SensorGateway v3/v4 not functional after reset attempt

WNKSUWNKSU
in InfraSensing Sensors
Previously we were testing a SensorGateway in our environment - either a v3 or a v4 according to photo found on page 94 of the InfraSensing Sensors Platform manual. After following the reset instructions for these models our device has been left with the Online/Sensor LEDs blinking green and yellow in unison. The device is not attempting to leverage the fixed address assigned via DHCP and cannot be reached over the network. It is obtaining PoE from the switch that it is connected to, but it is not attempting to communicate with a DHCP server.

We found a few other threads indicating that others had similar issues wherein a RMA was required after attempting to reset a device. Is this a common issue with these units?

Comments

  • AdministratorAdministrator
    Based on your order it is a unit purchased 7 years ago. So it would be a v3. These devices are no longer covered by support or repair.

    As per user manual you can check the IP address it is using, by running the Sensor Discovery tool.
  • WNKSUWNKSU
    Administrator said:

    Based on your order it is a unit purchased 7 years ago. So it would be a v3. These devices are no longer covered by support or repair.

    Thanks for this information.
    Administrator said:

    As per user manual you can check the IP address it is using, by running the Sensor Discovery tool.

    The tool was unable to locate the device.

  • StreliziaStrelizia
    https://drive.google.com/open?id=1RpvIlDlctjGTON6PuUw7oo1l7AbEwwEO try this discovery tool
    if you can't still locate your device try checking User Manual on page 7 - Category 1.5
  • WNKSUWNKSU
    Strelizia said:

    https://drive.google.com/open?id=1RpvIlDlctjGTON6PuUw7oo1l7AbEwwEO try this discovery tool
    if you can't still locate your device try checking User Manual on page 7 - Category 1.5

    While we didn't use the file at the link you provided, we attempted using the Java version of the tool from the official download and we were able to detect the device. It turns out that it's actually a v4 instead of a v3, but the device was able to be discovered and configured once again to use DHCP. It's currently getting a firmware upgrade right now. Thanks, Strelizia.
  • StreliziaStrelizia
    WNKSU said:

    Strelizia said:

    https://drive.google.com/open?id=1RpvIlDlctjGTON6PuUw7oo1l7AbEwwEO try this discovery tool
    if you can't still locate your device try checking User Manual on page 7 - Category 1.5

    While we didn't use the file at the link you provided, we attempted using the Java version of the tool from the official download and we were able to detect the device. It turns out that it's actually a v4 instead of a v3, but the device was able to be discovered and configured once again to use DHCP. It's currently getting a firmware upgrade right now. Thanks, Strelizia.
    Glad I could help, you're welcome
Sign In or Register to comment.