Comm32 Logo
Home Button  Buy Button 

Topic:   Not a "drop-in" substitute for MSComm

By: GerryPosted on: Jul 20 2017 at 12:58:31 AM
I'm trying your SComm because we're having problems with Windows 10 and MScomm, but I just replaced MSComm for SComm, and some routines don't work. I'm using the trial version.

At the beginning, right after opening the port, I send some commands to read the instrument info, but it doesn't receive the info. If I put a breakpoint, and debug, it works, so I'm not sure if it's a problem with timing, because when it's run uninterrupted (no break point) it doesn't work and the only difference is that I break the programming in every call.

Also, I noticed that when I use binary communication (not ascii) some things don't work with my program. What are the differences while using 'InputMode = comInputModeBinary' vs MSComm?

By: GuestPosted on: Jul 20 2017 at 01:21:09 PM
Inputmodebinary should be the same. It just reads bytes out of the receive buffer.
Inputmodetext comes in as a string of characters.
Inputmodebinary comes in as an array of bytes.

SComm32 is not MSComm32. If it was identical then one may as well just keep using MSComm32.

But it should be a drop in replacement unless your code somehow relies on timing within MSComm.

Look at the .OverlappedIO property in SComm32. Disabling that may make it work better with your application.

Reply - add a comment to this topic.

You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.

Topic:- Not a "drop-in" substitute for MSComm

Enter the numbers.

Your name here is optional