The modem is connected to the PLC via port1 RS-232 and I have no problem getting the modem to dial and establish a connection, but not successful logon to the ISP. The sample program does not provide for a username, but that should not be an issue, once I am able to determine the protocol and log on successfully using a terminal program. The PC that can be connected to the PLC for programming has ability to dialup or DSL, but I would rather not have the PC and DSL powered up while on vacation.
I have a PLC that would like to login in to my ISP and send an E-mail if there is an alarm condition, like high water level of a sump pump. The PLC can be programmed and communicates via RS-232 to a dialup modem on a land line. With the PLC or a terminal software (Realterm) have no problem dialing, connecting and getting the ISP login message ending with "..User name:<sp>", but unable to get verified as a user, even though the username and password are correct. Long conversation with ISP (Windstream, used to be Alltel) India tech support didn't help, they know nothing of the login protocol and format.
Using a RS-232 Spy software (Free Serial Port Monitor) I am able to catch the Windows XP Dialer conversation which is able to logon successfully reliably. Several runs of logging on seems to indicated that the conversation is consistent with exactly the same strings of characters each time, ruling out noise. The following is the conversation after the "..User name:<sp>" and through my username and password being sent out. I have changed my username and password to protect the innocent. The password follows the 07h after the username (E-mail address).
|Port opened by process "svchost.exe" (PID: 1408)|
|*Request: 4/12/2008 10:04:27 AM.56364 (+0.2813 seconds)*|
| ||7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 7D 37 7D 22 ~?}#?!}!} } }7}"|
| ||7D 26 7D 20 7D 20 7D 20 7D 20 7D 25 7D 26 4F 6C }&} } } } }%}&Ol|
| ||5C C2 7D 27 7D 22 7D 28 7D 22 7D 2D 7D 23 7D 26 \?}'}"}(}"}-}#}&|
| ||78 7A 7E xz~ |
|*Answer: 4/12/2008 10:04:27 AM.75164 (+0.1875 seconds)*|
| ||7E FF 7D 23 C0 21 7D 21 F1 7D 20 7D 38 7D 22 7D ~?}#?!}!?} }8}"}|
| ||26 7D 20 7D 2A 7D 20 7D 20 7D 23 7D 24 C0 23 7D &} }*} } }#}$?#}|
| ||25 7D 26 3D 66 A9 2C 7D 27 7D 22 7D 28 7D 22 7F %}&=f?,}'}"}(}"|
| ||56 7E 7E FF 7D 23 C0 21 7D 24 7D 20 7D 20 7D 27 V~~?}#?!}$} } }'|
| ||7D 2D 7D 23 7D 26 AD 36 7E }-}#}&?6~ |
|*Request: 4/12/2008 10:04:27 AM.86064 (+0.0313 seconds)*|
| ||7E FF 7D 23 C0 21 7D 22 F1 7D 20 7D 38 7D 22 7D ~?}#?!}"?} }8}"}|
| ||26 7D 20 7D 2A 7D 20 7D 20 7D 23 7D 24 C0 23 7D &} }*} } }#}$?#}|
| ||25 7D 26 3D 66 A9 2C 7D 27 7D 22 7D 28 7D 22 B3 %}&=f?,}'}"}(}"?|
| ||BB 7E 7E FF 7D 23 C0 21 7D 21 7D 21 7D 20 7D 34 ?~~?}#?!}!}!} }4|
| ||7D 22 7D 26 7D 20 7D 20 7D 20 7D 20 7D 25 7D 26 }"}&} } } } }%}&|
| ||4F 6C 5C C2 7D 27 7D 22 7D 28 7D 22 7D 39 FC 7E Ol\?}'}"}(}"}9?~|
|*Answer: 4/12/2008 10:04:28 AM.06364 (+0.1563 seconds)*|
| ||7E FF 03 C0 21 02 01 00 14 02 06 00 00 00 00 05 ~?.?!...........|
| ||06 4F 6C 5C C2 07 02 08 02 F2 95 7E .Ol\?....?•~ |
|*Request: 4/12/2008 10:04:28 AM.12664 (+0.0313 seconds)*|
| ||7E C0 21 0C 02 00 12 4F 6C 5C C2 4D 53 52 41 53 ~?!....Ol\?MSRAS|
| ||56 35 2E 31 30 F1 17 7E 7E C0 21 0C 03 00 17 4F V5.10?.~~?!....O|
| ||6C 5C C2 4D 53 52 41 53 2D 30 2D 44 36 39 35 2D l\?MSRAS-0-D695-|
| ||4C 54 47 4F 7E 7E C0 23 01 01 00 1D 10 58 58 58 LTGO~~?#.....XXX|
| ||58 58 58 58 58 58 58 58 58 2E 58 58 58 07 58 58 XX@alltel.net.XX|
| ||58 58 58 58 58 01 12 7E XXXXX..~ |
|*Answer: 4/12/2008 10:04:28 AM.43864 (+0.2500 seconds)*|
| ||7E FF 03 C0 23 02 01 00 05 00 8B 3B 7E ~?.?#.....‹;~ -----------------------------
1:Can someone explain what's happening with the conversation between the request and sending the user name?
2: Looks like some kind of encryption or protocol like TCP/IP or? Sending what info?
3: I would rather not program the PLC for all this garbage, is there a work around?
|
