EMX and Airlink GL 6110 modem

Hi!

We are currently trying to get an AirlinkGL6110 modem
(product description: [url]http://www.sierrawireless.com/productsandservices/AirLink/Programmable%20and%20Simple%20Modems/GL_Series/GL6100_GL6110.aspx[/url])
(technical specification and user guide: [url]http://www.sierrawireless.com/Sierra%20Wireless/Support/Downloads/AirLink/Programmable_Gateways/~/media/Support_Downloads/AirPrime/Hardware_specifications_and_user_guides/AirLink_GL61x0_Product_Technical_Specification_and_User_Guide-Rev004.ashx[/url] :cry: )
to get to work with your EMX devboard and PPP.Connect(“ourusername”, “ourpassword”) always fails.

The modem is connected using the COM2 port with a RS323 cable. The SerialPort uses hardware handshaking and as far as we can tell, that does not seem to cause the problem. (We checked that with a logic analyzer)
Sending commands to the modem works just fine. We also achieved to connect to the GPRS network:

AT+IFC?
+IFC: 2,2
OK
AT
OK
AT+CGMI
WAVECOM WIRELESS CPU
OK
AT+CGMM
MULTIBAND 900E 1800
OK
AT+CCID
+CCID: “8943050810202738161”
OK
ATV1
OK
ATH
OK
ATZ
OK
ATE
OK
AT+CSQ
+CSQ: 8,0
OK
AT+CGREG=1
OK
+CGREG: 0
AT+CGATT=1
OK
+CGREG: 2
+CGREG: 1
AT+CGATT?
+CGATT: 1
OK
AT+CGREG?
+CGREG: 1,1
OK
AT
ad: 1 - current message: ‘OK’
OK
AT+CGDCONT=1,“IP”,“web.one.at”
OK
ATD99**1#
CONNECT 115200

Our problem now is, that the PPP.Connect(string username, string passwort) call always fails with the status
PPP.ConnectionStatus.Connection_Faild

Just a note: We make heavy use of your sample code of the PPP class in the GHI Framework so that should be fine too.
We also tried the very same with our old Siemens MC35i modems and that worked like a charm.
We also tried changing the cable, power adapter, sim card, and used another Airlink GL6110 to exclude a hardware fault.
We even tried using the USB version of the GL6110 and had the very same issue.

That makes us think that there might be a problem with your internal PPP stack. Are you currently working and/or planning to release an updated version of your stack?

Any advise on what we could do/try next would be apprechiated! :cry: