-
Notifications
You must be signed in to change notification settings - Fork 951
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
Asynchronous RTU serial server not detecting port string #1697
Comments
Hmmm I am pretty sure we check that, but let me investigate. Apart from that your port string seems wrong, you need to point at the device driver. |
Please test with current dev and verify it works. You might be able to just apply the bug fix, but there are other changes and I have not controlled which depend on what. Please let us know if everything works, we are planning to release 3.4.1 within a week, and this patch with be part if confirmed. |
I have tried both variants. Unfortunately, both the dev branch and a manual bug fix where I only added the changes to transport.py is not runnable. Dev Branch
Bugfix in Transport.py
Working Version 3.3.2
|
thanks, this is another bug. |
This seems to be a windows problem, and I do not have a windows machine, so I cannot test it. We did change the serial_asyncio on dev, but neither the old nor the new have a "serve_forever", so I am a bit lost. I will play a bit more with PR #1701, but once I deem it is ready I hope you will be so kind and test it (wait until I say it is ready). |
Dev branch work now in my local setup, please give it a try. |
The new Dev Version is working on my Windows now, too. |
Versions
Pymodbus Specific
Description
With the new Version it is not possible to start a server, because the Port String is not detected and the default Value of 127.0.0.1 is used.
Code and Log
Code
Log
The text was updated successfully, but these errors were encountered: