Announcement

Collapse
No announcement yet.

Did not get an expected response within timeout period from 0001 - Portal 2.8.2

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Did not get an expected response within timeout period from 0001 - Portal 2.8.2

    When I start Portal and try to connect, I am getting the following message:

    2017-04-03 15:05:48 A SNAP USB Device was Discovered
    2017-04-03 15:05:48 A SNAP USB Device was Discovered
    2017-04-03 15:05:55 USB0: Found
    2017-04-03 15:05:57 Connection opened to USB0
    2017-04-03 15:05:57 Did not get an expected response within timeout period from 0001
    2017-04-03 15:05:59 SNAP communication timeout
    2017-04-03 15:06:01 Unable to Send Broadcast Requesting 'Device Status'
    2017-04-03 15:06:01 SNAP communication timeout

    And, this of course, means that I am unable to access my Synapse network. The SM220 device that is in the USB dongle does not show up in Portal. I saw some reference to resetting the device back to factory,m but the erase and program options in Portal do not see USB0.

    I have tried several reboots hard and soft as well as different USB ports including direct on machine and through a hub.

    Please advise

  • #2
    If you are referring to the USB adapter then you are correct Portal cannot reset that hardware. You will need access your device via a serial connection back to Portal. What module do you have?

    Comment


    • #3
      I am using an SM220 installed on the USB dongle. USB dongle says PCB P/N 500206-01A

      Comment


      • #4
        If you have a SM220 plugged into the USB adapter then you actually have a "RFxxx" device. Most likely a RF220UF1. The "RF" in the part number denotes a specific foot print and a plug in / socket type part.

        What you will need to do is remove the device from the USB adapter and place it in a proto board then make a serial connection from the proto board to your PC running Portal. Once you do this then you can erase any script on the device, reset the NV parameters, load new firmware, etc

        Comment


        • #5
          That did it. Thanks!

          Comment

          Working...
          X