Serial IrDa - still a problem

D

dion

Member
Licensed User
Bought a refurb iPaq H5550 and basic4ppc to check if it will be a workable solution - front end to configure a controller via InfraRed. These units are underground in the mines (3000m deep is not nice for a laptop).
The H5550 has Pocket PC 2003 Premium - and it works.
Now the customer needs a new PDA - bought a new iPAQ 2790b with Windows Mobile 5 - and it does not work!
Using .net2 and installed the latest sp2 on both handhelds.
Surely this seems odd??

Have checked IrDa Port - to beam from other PDA - slow, but works.

Tried basic terminal example - no go.

yet all work on H5550.:sign0085:
 
D

dion

Member
Licensed User
Did that earlier this year, when I e-mailed you with the problem.

Have also checked for bios/firmware = most current.
Tried original .net 2 compact framework = no luck
Note that serial fixes were in one of the sp's of the compact framework = back to latest sp2.

Have tried all comm devices = no luck.
Your registry utility does not identify the infrared port on this wm5 handheld.
Just putting the info that was in e-mails etc to avoid duplicate angles of attack:)

How do I go to HP and tell them it does not work, not keen to purchase another pocket pc to prove this - or maybe ms have changed the rules. In XP they have ditched the com port association for infrared.
 
D

dion

Member
Licensed User
@Erel
I have established the IrDa is com3 for now.
Now to work out what it is sending before the error message.
 
D

dion

Member
Licensed User
@Erel - more update.
It sends data, but all trash - loads of ????????????
Have checked baud etc
Initialized as follows:
Serial.CommPort = port
Serial.BitRate = 9600
Serial.DataBits = 8
Serial.StopBits = 1
Serial.Parity = "N"
Serial.PortOpen = true
port is assigned 3 initially and can be changed from the comport menu.

It is supposed to be Serial Text - where do I ensure that the mode is such?
 
D

dion

Member
Licensed User
Sending and receiving normal text - instructions and parameters eg "RT" & CR
Initialize it with serial.new1 in the open app sub, then the code provided above in the open port sub.
Basically the same as I did on the H5550.
Will try binary then.
 
D

dion

Member
Licensed User
Sounds dumb.
I have string eg "RT" - with serial.output2 I need buffer() of byte.
Would I then have to traverse the string and convert each character to byte, then serial.output2 = each_byte or the whole buffer??
 
taximania

taximania

Well-Known Member
Licensed User
Longtime User
dion said:
Sounds dumb.
I have string eg "RT" - with serial.output2 I need buffer() of byte.
Would I then have to traverse the string and convert each character to byte, then serial.output2 = each_byte or the whole buffer??
Click to expand...

Have you had a quick read of my pages about IrDA to a Pic microprocesser.
I had to send data byte by byte, it only ever read the 1st byte sent as a string.

IR - IRDA RS232 from microchip Pic to Pocket PC
 
D

dion

Member
Licensed User
taximania said:
Have you had a quick read of my pages about IrDA to a Pic microprocesser.
I had to send data byte by byte, it only ever read the 1st byte sent as a string.

IR - IRDA RS232 from microchip Pic to Pocket PC
Click to expand...

Yes, actually posted in the forum when the topic was still warm.
I recall you using the franson lib and a wrapper you wrote, right? Also the cheer in the forum when you got it working.

What beats me is that it works on the slightly older ppc with pocket 2003, but not on the new one with mobile 5. To verify if the irda actually works, I sent stuff from one pda to the other - worked, but appeared slow.

Either the new ppc has a suspect irda port - can only prove it if I lay my hands on another like it, or mobile 5 handles it different.
 
D

dion

Member
Licensed User
I know that one too well. Thank you Microsoft for nothing:(
Think I'll try Erel's suggestion first - not keen to spend more on this right now.
 
You must log in or register to reply here.
Top