The wierdest question about modems:40 chars

Try connecting two comps using newvbterm.exe of microsoft, or any other similar program using mscomm. Send exactly 41 or 42 characters.You'll find that exactly 40 characters get transmitted everytime.the last 1,2 chars get deleted from the output buffer.Any other similar numbers,anyone ? Or at least a way to solve the problem...?
sudeepnAsked:
Who is Participating?
 
mcoopConnect With a Mentor Commented:
In the case that sudeepn's comment is the 'solution', then I stand by my earler comment that there is in fact no 'fault' but rather that the user's receive buffer is simply not being handled in the right manner to catch the type of mixed length strings being sent.
0
 
Richie_SimonettiIT OperationsCommented:
interesting...
0
 
aaronkempfCommented:
id try sending some sort of VBCRLF character.

0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
sudeepnAuthor Commented:
Helllllp!!! Anybody!


I found that it sometimes happens with 9/10 chars as well. It sends 8 chars, deletes the last 1/2 chars.

Even VBCRLF sometimes doesnt work. I think the only way to solve the problem is to add random chars at the end. This way it works.
0
 
aaronkempfCommented:
i know of one person you can ask this-- but im sure that he'd make you buyg his backup software in order to get an answer.

www.ultrabac.com
0
 
aaronkempfCommented:
i know thats kindof a backwards answer-- but its the truth..
0
 
sudeepnAuthor Commented:
www.ultrabac.com has nothing to do with this.And this site is not an advertising space for those who dont know how to answer.
0
 
mcoopCommented:
I haven't tried your setup, but as I have had zero problems with MS-Comm when I use it properly... (and I have made a few mistakes !)

Perhaps you're simply not reading all the characters that are in the receive buffer.

There is no guarantee that a whole message will be delivered when the rx_commevent triggers.  You may have to buffer the input, and concatenate subsequent messages until your delimiter/terminator (e.g. CR/LF) is present... only then can you determine whether the whole message has been transferred (or not).

I only suggest this, as I see many people think that MS-Commm does everything - including read and interpret your data - but sadly this is not the case.

The reason many developers get away with this approach (most times) is that the messages are relatively short and bursty - so the RX buffer never overflows between Rx_comevents.

Good luck, I'd like to hear how this resolves.


0
 
sudeepnAuthor Commented:
I found the answer myself...in case anyone in the future gets into a similar problem. Send a few random characters every 1/1.5 seconds. This will ensure that all the data is received at the other end. Wierd answer.But it works, as the question itself is absurd.
0
 
sudeepnAuthor Commented:
"...then so be it."
0
 
sudeepnAuthor Commented:
"then so be it"
0
 
mcoopCommented:
Cheers & thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.