We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Comparing wizconfig.py with their main_gui.py counterpart on WIZnet-S2E-Tool-GUI repo, the following vars seem off:
wizconfig.py
main_gui.py
WIZnet-S2E-Tool:
SOCK_CLOSE_STATE = 21 SOCK_OPENTRY_STATE = 22 SOCK_OPEN_STATE = 23 SOCK_CONNECTTRY_STATE = 24 SOCK_CONNECT_STATE = 25
WIZnet-S2E-Tool-GUI:
SOCK_CLOSE_STATE = 1 SOCK_OPENTRY_STATE = 2 SOCK_OPEN_STATE = 3 SOCK_CONNECTTRY_STATE = 4 SOCK_CONNECT_STATE = 5
If you use the values of WIZnet-S2E-Tool-GUI on the WIZnet-S2E-Tool, TCP unicast seems to work.
The text was updated successfully, but these errors were encountered:
@fvarandas Thank you for leaving the issue. I'll check the function and update.
Sorry, something went wrong.
Update issue #11
709e1d2
Update README
@fvarandas The issue is fixed. Thanks again 👍
No branches or pull requests
Comparing
wizconfig.py
with theirmain_gui.py
counterpart on WIZnet-S2E-Tool-GUI repo, the following vars seem off:WIZnet-S2E-Tool:
WIZnet-S2E-Tool-GUI:
If you use the values of WIZnet-S2E-Tool-GUI on the WIZnet-S2E-Tool, TCP unicast seems to work.
The text was updated successfully, but these errors were encountered: