#9 Serial output is not sent to the physical port

[Martin R.]

Hi,

I'm opening a ticket because the serial output signal is not sent to the serial port. Instead, a text file is created and the output content is written in that file. I'm joining a screenshot showing the issue, a screenshot showing the different parameters that were used in the application and a screenshot showing the configuration values. For my case, since I use the serial port COM6, the filename containing the output content is COM6.

The version of the application where this issue occurs is gpsfeed+_win64.exe (modified 2019-07-01) available in this link : https://sourceforge.net/projects/gpsfeed/files/.

The environment where the issue occurs is Windows 7 - 64 bit with the serial port COM6.

Thank you,

Martin.

[dzach]

Hi Martin
Please have a look at the Open Discussion section and specifically at this discussion, regarding similar issues. The usual cause for this problem is: the desired port (in your case COM6), as set, does not appear to gpsfeed+ as a writable serial stream, and ends up been written to as a file instead. In such a case, you will have to find out which serial ports on your machine are actually functioning as such (and are available for writing), and how to refer to them properly.

[Martin R.]

Hi dzach,

I've just looked at the specific discussion with a similar issue and i found the solution to make it work,

For some reason, in the previous versions of the application, putting 'COM6:' in the serial port field worked to output the content to the physical port. However, with the latest version of the application, it does not work anymore, you have to remove the colon. Thus, putting 'COM6' instead of 'COM6:' in the serial port field makes it work like a charm.

You can consider the issue as auto-resolved. :)

Thanks!

Martin.

[dzach]

I'm glad it worked. The version for Windows was packed using Wine on Linux, an emulator, so this could be the reason for the change in port names.