Fwd: Moto V3Cm, E815m auto detection?

---------- Forwarded message ----------
From: Mark_Venture <[email protected]>
Date: Apr 11, 2007 9:23 AM
Subject: Re: Moto V3Cm, E815m auto detection?
To: [email protected]

> ...but the way I wrote it,
> I didn't make mention if it detected as V710 or V710m when the ID String
> Seem edit was un-done.    I wont have time until later today to undo the
> seem edits, and re-auto detect...

Just re-tested my V710...

With the *Seem* *04FF* set as default verizon string (*V710*)... using the
Detect phone option in BitPim 9.13 comes back with a pop up saying  "Found
V710M's V710 on COM16"   and when I click Send Data, the add column is
grayed out.
---(from hyperterm)-----------------------
OK
at+gmm
+GMM: Motorola CDMA v710 Phone
OK
at+gmi
+GMI: Motorola CE, Copyright 2000
OK
at+mode=2
OK
+MBAN: Copyright 2000-2004 Motorola, Inc.
at+cgmm
+CGMM: "CDMA800","CDMA1900","AMPS800","MODEL=V710"
OK
at +mode=0
OK
--------------------------

With the *Seem* *04FF* modified to reflect *V710M*... using the Detect phone
option in BitPim 9.13, the pop up says... "Found V710M's V710m on COM16"
and when I click Send Data, the add column is NOT grayed out.
--------(from hyperterm)----------------
OK
at+gmm
+GMM: Motorola CDMA v710 Phone
OK
at+gmi
+GMI: Motorola CE, Copyright 2000
OK
at +mode=2
OK
+MBAN: Copyright 2000-2004 Motorola, Inc.
at +cgmm
+CGMM: "CDMA800","CDMA1900","AMPS800","MODEL=V710M"
OK
at +mode=0
OK
---------------------------------------------------------

So yeah, in BitPim 9.13 auto detect does work on the V710/V710M... just not
on the E815m, V3Cm.  which is where the +CGMM command that Moto Phone Tools
uses to detect comes in handy.

Some info from Moto Phone Tools' Detect.inf (table of phones)...
----------------------------------------------
[Commands]
Manufacturer1=AT+GMI
Model1=AT+GMM
Wait=3000
Cmd=AT+MODE=2
Wait=3000
Manufacturer=AT+CGMI
Model=AT+CGMM
Mode=AT+MCMA?
Cmd=AT+MODE=0
Wait=500
-----------------------------------------------------
That commands section does match what is disaplyed on the screen while MPT
goes thru its process of detecting a phone.  (it shows command sent, and
result)

then each phone has a section in the detect.inf  ... which includes which
driver or command set used to communicate with the phone??, what appear to
be the return strings for the AT commands, how it shows in device manager,
is it bluetooth capable, and then the info about what on-screen graphic to
use....

here they are...
------------------------------------------------------

[V710m]
Driver=710mXUC
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V710m""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V710.jpg
ID_DEVICE=283

[V710]
Driver=710XUC
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V710""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V710.jpg
ID_DEVICE=210

[E815m]
Driver=815mXUC
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=E815m""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_E815.jpg
ID_DEVICE=495

[E815]
Driver=815XUC
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=E815""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_E815.jpg
ID_DEVICE=494

[V3cm]
Driver=v3cm
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V3cm""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V3.jpg
ID_DEVICE=1595

[V3c Rev2]
Driver=v3cr
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V3c Rev2""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT=1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V3.jpg
ID_DEVICE=1704

[V3c]
Driver=v3c
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V3c""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V3.jpg
ID_DEVICE=1313

[V3m]
Driver=v3cr
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V3m""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V3.jpg

[V3mm]
Driver=v3cm
Manufacturer=+CGMI: "Motorola CE, Copyright
Model=""MODEL=V3mm""
CapaNetwork=CDMA
PnPNames=Motorola USB Modem
BT= 1
DeviceFile=MotorolaGeneric_1.htm
PairingFile=MotorolaGeneric_2.htm
PicturePhone=Moto_V3.jpg

---------------------------------------------------------------------

notice how the V3MM and V3CM use the same driver for MPT..  On a side
note, With a Verizon V3M phone which has been seem edited to enable the
MultiMedia features (seem 2742/offset 6a/bit0), I can configure BitPim as a
V3CM make use of the GUI for adding pictures/ring tones, plus the phone
book... but I haven't tried the rest (calendar, SMS, etc).

Also, the V3C Rev2 id string is due to the calendar bug in the Verizon V3C
firmware... it was fixed with Verizon's 1.15.04 firmware, so they added the
REV2 to the ID string.  When MPT detects the ID string as V3C, the calendar
option of MPT is grayed out.  It must be a V3CM or a V3C Rev2 for the
calendar option to be present in MPT.

There are entries for the SPRINT V3M, as well as the CDMA Krzr K1m and K1MM
if you want them... but from what I understand, the the moto support in
BitPim doesn't work with the K1M/K1MM phones (when manually configuring the
phone selection), and I have no idea about the Sprint V3M.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
BitPim-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bitpim-devel