#justinadkins

1 messages · Page 1 of 1 (latest)

violet troutBOT
signal tusk
#

Hello

#

Sounds like a Terminal issue. What SDK are you using?

#

Ah is this the Android SDK USB connection?

unkempt ginkgo
#

Android SDK USB, yes

signal tusk
#

Hmm are you trying to discover after already successfully connecting to the Reader?

#

When does that error occur exactly?

unkempt ginkgo
#

Looking through the log, we experienced an unexpected reader disconnect event, then began discovery to reconnect, then discovery gave us this error

signal tusk
#

Interesting

#

Can you share the serial number for the reader?

unkempt ginkgo
#

STRM26139015055

signal tusk
#

Thanks, and do you happen to have a timeframe that this happened?

unkempt ginkgo
#

19:09:10 UTC for the disconnection event,
19:09:42 UTC for the error I mentioned above

signal tusk
#

Thanks lookin!

#

Hrmmm weird. I see a USER_ERROR.USB_DISCOVERY_TIMED_OUT: Usb discovery timed out error at 19:09:12. But I don't see any disconnection event 🤔

#

Looking more, one sec

signal tusk
#

So I see another reader (STRM26138002468) hitting this same issue

#

Is that reader using the same PoS device?

#

Same cable?

#

Anything common between those two?

unkempt ginkgo
#

Looking

#

That reader is one of ours

signal tusk
#

Yeah so I'm not seeing any actual unexpected disconnect for these readers, but seems to be this USER_ERROR.USB_DISCOVERY_TIMED_OUT: Usb discovery timed out error is triggering you to try to reconnect, but then the reader is actually already connected. Maybe that error is coming through to your PoS as an unexpected disconnect.

#

Which could be a beta issue thing that we need to surface and get fixed. I'm not totally sure.

unkempt ginkgo
#

Got it, so the disconnection event may be happening accidentally?