WM 5.0, RS232, OpenNETCF and HP rx1950

[Markus Humm]

Hello,

we've some app. which uses the RS232 port via OpenNETCF components and
it works fine on most WM2003.

Today I got the first WM 5.0 device into my hands, a HP rx1950, and the
app. didn't work that fine! Serial communications didn't go correctly.
We found a way now around it, but it's a workaround rather than a
correct solution.

If one opened the com port only one time (set it ip first then do a
..open) it didn't work, but if you changed that to:

1. set ip up (baurate etc.)
2. open it (.open)
3. close it (.close)
4. dispose it (.dispose)
5. set ip up again (same as 1., code copied)
6. open it again (as in 2.)

then all works! Why? What's wrong here?

Greetings from a puzzled

Markus

 

[Joseph Byrns]

I don't know what is wrong here, but can you not use the built in Serial
Comms that comes with CFV2.0, now that it is available?

 

[Markus Humm]

I don't know what is wrong here, but can you not use the built in Serial
Comms that comes with CFV2.0, now that it is available?

I don't want to. This would imply that every WM2003 user had to install
CF 2.0 JUST FOR RS232 IO, where .NETCFSDF up until now was enough!
And: I wouldn't be sure that I wouldn't run into this problem with CF
2.0 as well!

Greetings

Markus