It works great for 1 port, but as soon as I add another (as described in the previously linked post), it fails with something like this:
Open("COM3", baud=19200, [..etc..]) - OK
then returns the command prompt to me. If I back down to just 1 port again, it works fine.
Has the syntax changed in the CVS version of hub4com?
I tried playing around with some different syntax to tie additional COM ports to the same TCP port, but all of my attempts are failing in different ways.
Thanks!
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was debugging myself last night and saw that isValid was returning False seemingly before it was even set to anything, but what threw me was that isValid was set to True if there was only one TCP port configured. Good to see the isValid just needed to be initialized!
Thanks for fixing it so quickly.
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using the syntax to create multiple COM ports from this post: https://sourceforge.net/forum/message.php?msg_id=7506826
Using the CVS hub4com, it fails to run.
It works great for 1 port, but as soon as I add another (as described in the previously linked post), it fails with something like this:
Open("COM3", baud=19200, [..etc..]) - OK
then returns the command prompt to me. If I back down to just 1 port again, it works fine.
Has the syntax changed in the CVS version of hub4com?
I tried playing around with some different syntax to tie additional COM ports to the same TCP port, but all of my attempts are failing in different ways.
Thanks!
Jeff
I hope it fixed in CVS.
CVS fixed it, thanks a lot!
I was debugging myself last night and saw that isValid was returning False seemingly before it was even set to anything, but what threw me was that isValid was set to True if there was only one TCP port configured. Good to see the isValid just needed to be initialized!
Thanks for fixing it so quickly.
Jeff