do you use the Route_Serial_TCP_UDP script (https://sourceforge.net/projects/routeserialtcpudp/) or your own script?
Please tell me a little bit more about your configuration:
- how is the embedded device connected to your PC
- on which OS is ScriptCommunicator running
- how is ScriptCommunicator connected to the ethernet
- which version of ScriptCommunicator do you use
PS: I have removed the video because I have changed the GUI of ScriptCommunicator and had no time to create a new video.
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Stefan,
I think I configured my own script. Putting the images of the configration I had done.!
I am using a custom hardware (a microcontroller with an ethernet module) connected to the
PC using ethernet CAT5 cable.
I observed another related issue. After configuring the terminal and hitting the connect button
the system doesn't start receiving UDP packets until one sends out any random character to
initiate the receiving thread/function.
I don't know if I have understand you:
- ScriptCommunicator receives only UDP packets if you initially send a packet from ScriptCommunicator to your embedded device
- after a few minutes ScriptCommunicator receives no more packets until you send a packet from ScriptCommunicator to your embedded device
Is that correct?
Can you test this with the current version of ScriptCommunicator (3.28) please (I have changed a lot of things since your version (3.20))?
PS: I have uploaded a new video of ScriptCommunicator.
Thx for your patience.
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Iamfindingthesameproblemwiththeversion3.28aswell!Imageattached.1)YesyougotboththepointsIwastringtoconvey!!2)Ididn't realize the new version 3.28 is out I will try that!!3)Iunderstandandappreciatetheeffortyouhaveputinwritingandtestingthistool.Youcantakeasmuchtimetocorrectsthesmallbugsanditwouldbewrongonourparttoexpectyouwouldcorrectsmallbugsinshortnotice.Thanksagainforpromtlyreplytothemessagesandputtingthevideo.RegardsRohit
I have started 2 instances of ScriptCommunicator on Mac OS X, Linux and Windows 10 locally and started sending of UDP packets. All worked fine. I will see if I can connect to PC's directly at work (on monday) and check the UDP sockets.
Your port number is very low (maybe you collide with an other program). Can you test a port number > 10000 please?
Which operating system do you use?
Do you have the same problems if you start/connect two instances of ScriptCommunicator locally and sent UDP packets?
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Stefan,
I tried formatting my PC and reinstalling the OS, With the new install version 3.28 seems ok. I will test it further and get back to you in a days time. Apologies if this turns out to be a problem with corrupted OS files.
Regards
Rohit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stefan,
The normal versions are the one relased in the public domain on sourceforge not these zipped files. But I am still testing it should confirm my finding tomorrow when I go to office.
Regards
Rohit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stefan
I would like to confirm the problem was due to corrupted windows file rather than the software malfunctioning. Apologies for raising this issue.
Regards
Rohit K
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi,
Thanks for creating such a wonderful tool.
I am using this software to send/receive UDP packets
to an embedded system over ethernet.
Hi Rohit,
do you use the Route_Serial_TCP_UDP script (https://sourceforge.net/projects/routeserialtcpudp/) or your own script?
Please tell me a little bit more about your configuration:
- how is the embedded device connected to your PC
- on which OS is ScriptCommunicator running
- how is ScriptCommunicator connected to the ethernet
- which version of ScriptCommunicator do you use
PS: I have removed the video because I have changed the GUI of ScriptCommunicator and had no time to create a new video.
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-14
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Stefan,
I think I configured my own script. Putting the images of the configration I had done.!
I am using a custom hardware (a microcontroller with an ethernet module) connected to the
PC using ethernet CAT5 cable.
I observed another related issue. After configuring the terminal and hitting the connect button
the system doesn't start receiving UDP packets until one sends out any random character to
initiate the receiving thread/function.
Last edit: Anonymous 2016-01-15
Hi Rohit,
I don't know if I have understand you:
- ScriptCommunicator receives only UDP packets if you initially send a packet from ScriptCommunicator to your embedded device
- after a few minutes ScriptCommunicator receives no more packets until you send a packet from ScriptCommunicator to your embedded device
Is that correct?
Can you test this with the current version of ScriptCommunicator (3.28) please (I have changed a lot of things since your version (3.20))?
PS: I have uploaded a new video of ScriptCommunicator.
Thx for your patience.
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-15
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Stefan,
Last edit: Anonymous 2016-01-15
Hi Rohit,
I have started 2 instances of ScriptCommunicator on Mac OS X, Linux and Windows 10 locally and started sending of UDP packets. All worked fine. I will see if I can connect to PC's directly at work (on monday) and check the UDP sockets.
Your port number is very low (maybe you collide with an other program). Can you test a port number > 10000 please?
Which operating system do you use?
Do you have the same problems if you start/connect two instances of ScriptCommunicator locally and sent UDP packets?
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-16
Hi Rohit,
in the attachments are 2 test versions of the ScriptCommunicator executable. I would appreciate if you could test these to version.
Best regards,
Stefan
Last edit: Stefan Zieker 2016-01-17
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Stefan,
I will try them and get back to you.
Regards
Rohit
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Stefan,
I tried formatting my PC and reinstalling the OS, With the new install version 3.28 seems ok. I will test it further and get back to you in a days time. Apologies if this turns out to be a problem with corrupted OS files.
Regards
Rohit
Hi Rohit,
do you mean the 'normal' version or one of my test versions (from ScriptCommunicator_Tests.zip)?
Best regards,
Stefan
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Stefan,
The normal versions are the one relased in the public domain on sourceforge not these zipped files. But I am still testing it should confirm my finding tomorrow when I go to office.
Regards
Rohit
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Stefan
I would like to confirm the problem was due to corrupted windows file rather than the software malfunctioning. Apologies for raising this issue.
Regards
Rohit K
Hi Rohit,
no problem. If you see any other possible bug post again.
Best regards,
Stefan