-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A121 Client open timeout #157
Comments
I am seeing a similar issue. ET 7.13.2 Error I am seeing - Recv Timeout Detailed Error Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
It sounds like the firmware in your module is out of sync as it waits for a line break before it starts processing the commands sent from the client. Best Regards, |
@jbjornstedt I am using the firmware flashed using the Exploration tool. I get the latest binary by signing in into the account. Thank you |
@anupcherukuri You don't have the same issue as the OP. Best Regards, |
Thank you for response. Unfortunately I cannot use flow control in case of my device. |
@misisnik |
@anupcherukuri If not I urge you to file a ticket on our Customer Helpdesk if you need more assistance since this is not a problem with the Acconeer Exploration Tool application: https://support.acconeer.com/support/solutions |
Describe the bug
When freshly powered device, no problem with client open:
client = a121.Client.open(serial_port=args.serial_port, flow_control=False)
then normal operation of SparseIQ, starting the session, getting the data.....
after finish - program close
client.close()
Fresh Python script start and no power reset of the device. Client.open raise error:
acconeer.exptool._core.communication.links.buffered_link.LinkError: recv timeout
Possile to fix this by multiple connection (second time is possible to connect without problem)
Installed packages
Environment (please complete the following information):
Additional context
Haven't seen this behavior before update
Tested wiht SDK 1.2.0, 1.5.0 and 1.8.0
The text was updated successfully, but these errors were encountered: