IPaq 1945 Irda write error

[SNR]

Hi,

I have developed an application using raw IR serial capabilities to transfer
data using the Irda port on my IPaq 1910. Works great. Same code base on
an IPaq 1945 fails on Write attempts giving the error 1359. I have scoured
the Internet and newsgroups and have seen lots of people who have had
similar problems, but no one has posted a solution.

Several posts have recommended using the EscapeCommFunction and SETIR, but
this does not work in my case. At least one site said this specifically
does not work on IPaqs. I also saw one comment saying that raw IR is not
supported on the 1945, but have found nothing to substantiate this.

Any suggestions would be appreciated.

Scott

 

[Peter Foot [MVP]]

Does the default Object Exchange server have control of the port?

Uncheck the setting Settings > Connections > Beam > Receive all incoming
beams.

Peter

 

[SNR]

Peter,

It is unchecked.

This IPaq is equipped with Bluetooth, can there be any conflict?

Scott

 

[Peter Foot [MVP]]

Bluetooth shouldn't cause any issues opening the IR port. Do you have any
other background utilities running?

Peter

 

[SNR]

Peter,

None other than Active Sync.

Some more information as of yesterday. The comments in the newsgroups keep
saying that the port listed in the registry is the one that must be used for
Raw IR, and that port was set to 2. However I could never open this port,
only port 3 which is what works on my 1910. The registry on my 1910 says 2
as well BTW. Anyway I found a comment that indicated that port 2 exists, it
is just held open by IRSIR and that this could be short circuited by toying
with the registry. Well it can, but my registry is a little goofed up now.

Under LOCAL_MACHINE/Comm/Irsir is a Linkage to Irsir1. Comm/Irda has the
same linkage to Irsir1. Under Irsir/Linkage, I edited the Bind value to
point at a non-existent place by making it "xxxIsir1". Since then the
registry has been pretty flaky and I can only view the contents of Irda and
Irsir1 sometimes. Sometimes they show as blank. I'd be interested in any
comments about why that is and how I might fix it. Anyway, I can now open
COM2:, however it makes no difference, I still cannot communicate.

So I am presuming, because it works on the 1910, this is really not the path
to take, but instead that the routing
through COM2 is handled by the Irda driver when I open COM3. The trick is
perhaps to tell the connection I desire a raw IR session rather than IRCOMM.
This is all guesswork of course. Just a hunch that this Irda driver has a
problem and may not support raw IR, or that there is a trick to it that I
don't know.

Any thoughts would be appreciated.

Scott