Question about ppp connection


6 posts
by sanchomuzax » Tue Apr 30, 2013 7:20 am
I would like to connect my Rasberry Pi "B" with old HP iPAQ H3970 Pocket PC 2003 device. I want to build a link between the two devices using PPP to get a PDA with an Internet access.
Image
The PDA shows on the USB port:
Code: Select all
$ lsusb
...
Bus 001 Device 012: ID 03f0:1016 Hewlett-Packard Jornada 548 / iPAQ HW6515 Pocket PC
...

It seems on the serial port also:
Code: Select all
$ lsmod | grep usb
usbserial              32890  1 ipaq

I have used this script to build the connection beetween the two devices (with /dev/ttyUSB0 setting, and with 198.168.0.2:192.168.0.55 IPs):
http://math.bme.hu/~lackac/ipaq/linux-ipaq/files/PocketPC

Result of the running of the script:
Code: Select all
$ sudo /usr/sbin/pppd call PocketPC
' OK 'AT' OK 'AT' OK 'AT' OK 'AT' OK 'AT' OK 'AT' OK 'AT' OK 'AT' OK 'ATDT' CONNECT finished (pid 22897), status = 0x3
Connect script failed

More information about the operations of the 1.1 section:
http://math.bme.hu/~lackac/ipaq/linux-ipaq/Linux-iPAQ-HOWTO-1.1.html

Any idea? :geek:
Posts: 13
Joined: Tue Apr 09, 2013 9:36 pm
by topguy » Tue Apr 30, 2013 7:28 am
I would start with confirming that you actually have a working link to the iPaq.

"minicom" is a commanline terminal that you can use to talk with modems and other serialports.

If you have proper connection you should be able to do the same sequence as the "chat" script in PocketPC.

You write ATZ, iPaq answer with OK etc. etc..
User avatar
Posts: 696
Joined: Tue Oct 09, 2012 11:46 am
Location: Trondheim, Norway
by sanchomuzax » Tue Apr 30, 2013 7:52 am
Thank you for the tip. I will try it!

I don't recognize this app, but I guess that should be install:
Code: Select all
sudo apt-get install minicom

It's okay.
I think that this should be run:
Code: Select all
minicom -b 115200 -o -D /dev/ttyUSB0

How can I use this app? How can I type the commands.

(Now, I 'm not at home, and I can't start the connection on the PDA side.)
Posts: 13
Joined: Tue Apr 09, 2013 9:36 pm
by obcd » Tue Apr 30, 2013 8:01 am
To my knowledge, it's the other way around
The Compaq sees the linux as a modem and will send the AT commands to it.
The linux should answer with OK which is the normal AT command set answer.
The ATDT coming from the Compaq initiates a dial up. If such succeeds, the modem answers with
CONNECT or CONNECT 1200 (the last number being the connection speed)
From that moment, it should stop sending AT commands as the modem link is now becoming transparant.
At that moment, something is happening that the script doesn't like as it terminates with an error. I haven't looked any deeper into it to figure out what exactly.
Depending upon the version of windows mobile on your Ipaq, the way things are done can differ a little.
If I remember well, some devices had an upgrade path from windows mobile 2002 to windows mobile 2003.
Posts: 890
Joined: Sun Jul 29, 2012 9:06 pm
by topguy » Tue Apr 30, 2013 8:06 am
obcd wrote:To my knowledge, it's the other way around
The Compaq sees the linux as a modem and will send the AT commands to it.
The linux should answer with OK which is the normal AT command set answer.


You are correct, that makes more sense.

He should still be able to verify if his iPAQ actually sends those commands with minicom.
User avatar
Posts: 696
Joined: Tue Oct 09, 2012 11:46 am
Location: Trondheim, Norway
by sanchomuzax » Tue Apr 30, 2013 10:03 am
obcd wrote:Depending upon the version of windows mobile on your Ipaq, the way things are done can differ a little.
If I remember well, some devices had an upgrade path from windows mobile 2002 to windows mobile 2003.

Yes, I updated it from Pocket PC 2002 to Pocket PC 2003 version. (No Widdows Mobile, only Pocket PC...)
Posts: 13
Joined: Tue Apr 09, 2013 9:36 pm