> Hi. I have written a program using Free Pascal / Lazarus which uses
> Synaser to communicate with a ham radio via a serial port at
> 4800/8/N/2. It is running under Windows XP SP2. When the radio is
> connected via a regular serial port it works fine. When connected
> using a USB to serial adapte
Hi. I have written a program using Free Pascal / Lazarus which uses Synaser
to communicate with a ham radio via a serial port at 4800/8/N/2. It is
running under Windows XP SP2. When the radio is connected via a regular
serial port it works fine. When connected using a USB to serial adapter
(Prolifi
Mark Rogers wrote:
> I'm not ready to take the blame yet, much easier to blame the drivers :-)
>
OK, time for me to put my hand up...
I had a lot of problems.
Partly because I was not properly terminating my comms thread while
testing the code and that was often leaving the port tied up.
Par
Jon wrote:
> Ah yes, the good old PEBKAC issue
> (http://en.wikipedia.org/wiki/Pebcak). Get's me every time ;-)
I'm not ready to take the blame yet, much easier to blame the drivers :-)
I mostly use Linux now, so I forget that you can often fix problems in
Windows with a reboot!
> Seriously tho
>
> There was definitely something odd going on
> but it seems to have passed now.
>
Ah yes, the good old PEBKAC issue (http://en.wikipedia.org/wiki/Pebcak). Get's
me every time ;-)
Seriously though, to check the port names, examine the registry branch:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\
In addition to what I just wrote in reply to Lukas' email:
Jon wrote:
> Are you sure that the port is not in use? PortMon is always my first
> troubleshooting tool.
>
If I shut down my software and used the software supplied by the
hardware manufacturer (ie the software to talk to the thing
Lukas Gebauer wrote:
> No, here are no reason for this. I am using Synaser with USB emulated
> serials, I am using it for RS-895 too.
>
I thought it should be OK, it's nothing particularly unusual.
> What exactly is failing? Connect method or Config method?
>
I can't remember now, because
I have used SynaSer successfully with USB serial ports on Windows 95 upwards.
No fancy coding, I just followed the basic example.
> At the moment I can connect to the real COM1 ok but any
> attempts to connect to COM5 are failing (using SysInternals
> portmon, it recognises that COM5 exists but w
> Is there any reason why SynaSer would see the port any differently than
> Windows? Any suggestions as to what I can try to find the port?
No, here are no reason for this. I am using Synaser with USB emulated
serials, I am using it for RS-895 too.
What exactly is failing? Connect method or Conf
I have a Windows application that needs to work with USB serial ports,
which will likely appear as COM5 upwards.
At the moment I can connect to the real COM1 ok but any attempts to
connect to COM5 are failing (using SysInternals portmon, it recognises
that COM5 exists but when I monitor it ther
10 matches
Mail list logo
