Menu
▾
▴
bitpim-devel
|
From: Roger B. <ro...@ro...> - 2004-03-03 10:42:13
|
I now have an Audiovox CDM 8900 thanks to RPI Wireless. However I cannot get it to talk. The modem side works fine. On the diagnostics connection, I can quite happily send any commands or traffic and it never returns a single byte of data. Is there some magic mojo or something else I am missing. I experienced this on two different Windows XP machines and a Linux. SW version T095VEDT20_0.189 HW version TX-95C_REV_02 RPI got it off eBay so there may be some unknown history behind it. Roger |
|
From: Chris F. <cf...@za...> - 2004-03-04 00:46:46
|
Roger Try using the com port that is assigned to the modem. At least that's what seems to work. ;) Chris... On Wed, 3 Mar 2004, Roger Binns wrote: > I now have an Audiovox CDM 8900 thanks to RPI Wireless. However I > cannot get it to talk. The modem side works fine. On the diagnostics > connection, I can quite happily send any commands or traffic and it > never returns a single byte of data. Is there some magic mojo or > something else I am missing. I experienced this on two different > Windows XP machines and a Linux. > > SW version T095VEDT20_0.189 > HW version TX-95C_REV_02 > > RPI got it off eBay so there may be some unknown history behind it. > > Roger > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel > |
|
From: Roger B. <ro...@ro...> - 2004-03-04 01:06:06
|
> Try using the com port that is assigned to the modem. At least that's what > seems to work. ;) Thanks for that. It was the one thing I didn't try :-) So it turns out that even though the circuit board is identical to the VX6000, the cable is identical, the drivers are identical (just different USB ids in the inf files), and it being a composite device (in exactly the same way), the crucial difference is that the VX6000 (and VX4400) use the seperate diagnostics port and the 8900 uses the modem port for both modem and diagnostics. There are occasions when a little knowledge is a dangerous thing :-) Roger |
|
From: Chris F. <cf...@za...> - 2004-03-04 00:53:56
|
Roger Sorry, I shouldn't have been so trite in my previous response. I'm a Telus customer and I've been playing with the CDM-8900 and BitPim since November. I have never had any success getting the handset to communicate over the diagnostic port. The com port that is assigned to the modem works quite well though, and so I haven't spent much time investigating why the diagnostic connection doesn't respond. Let me know if I can help out with the 8900. I have a limited amount of time to dedicate to it, but I'll try to do what I can. Chris... On Wed, 3 Mar 2004, Roger Binns wrote: > I now have an Audiovox CDM 8900 thanks to RPI Wireless. However I > cannot get it to talk. The modem side works fine. On the diagnostics > connection, I can quite happily send any commands or traffic and it > never returns a single byte of data. Is there some magic mojo or > something else I am missing. I experienced this on two different > Windows XP machines and a Linux. > > SW version T095VEDT20_0.189 > HW version TX-95C_REV_02 > > RPI got it off eBay so there may be some unknown history behind it. > > Roger > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel > |
|
From: Roger B. <ro...@ro...> - 2004-03-04 01:09:05
|
> Sorry, I shouldn't have been so trite in my previous response. You were not trite and were in fact spot on :-) > Let me know if I can help out with the 8900. I have a limited amount of > time to dedicate to it, but I'll try to do what I can. The main thing I need is pointers to research people have already done, and especially any sync protocols. There do appear to be various threads on Howard Forums, but they wonder all over the place. I do have the Curitel PC Sync app so I will have a look at that. Roger |
|
From: Chris F. <cf...@za...> - 2004-03-04 16:14:02
|
Comments inline - Chris... On Wed, 3 Mar 2004, Roger Binns wrote: > The main thing I need is pointers to research people have already > done, and especially any sync protocols. There do appear to be > various threads on Howard Forums, but they wonder all over the place. > I do have the Curitel PC Sync app so I will have a look at that. The only thing I can say about the PC Sync App is to caution you about writing any data back to the handset from it. It would appear that the phonebook data is -slightly- different on the TX-95C than the CDM-8900 and writing the data back without setting some of the fields results in the handset getting rebooting. At least this is the unfortunate experience of a number of users on HoFo. > > Roger |
|
From: Chris F. <cf...@za...> - 2004-03-04 16:46:50
|
> CDM-8900 and writing the data back without setting some of the fields > results in the handset getting rebooting. At least this is the unfortunate > experience of a number of users on HoFo. I mean to say getting -stuck- rebooting. My proof reading skills are diminishing it would seem. Chris... |
|
From: Chris F. <cf...@za...> - 2004-03-19 01:06:31
|
I wanted to share some information I just discovered. The reason you can't use the diagnostic port on the CDM-8900 is that it appears to be set to "UART MAIN" as a factory setting. I was playing around with ## commands today, and stumbled upon the "RunTime DevMap" menu that is accessable by issuing "##7678<END>" (##PORT). You can also control the DM Mode port speed by issuing "##2283<END>" (##BAUD). I changed the diag setting in the "RunTime DevMap" menu to "USB DIAG" and I can now successfully connect to the phone through the diagnostic port. The connections to the phone over the diagnostic port appear to happen with less negotiation as well. Of course it could just be my perception. Not sure if this helps anyone, but it seemed like an interesting tidbit of info. Chris... |
|
From: Roger B. <ro...@ro...> - 2004-03-22 09:12:31
|
> that is accessable by issuing "##7678<END>" (##PORT). You can also control That was fun to play with :-) From one of the Hofo threads, people claimed to be able to talk to the phone using the Curitel sync application. However that app doesn't work for me. (I downloaded the version for the PD-K500). From the portmon sniff, it puts the phone into DM mode, and then sends command zero, gets a result and puts up a dialog box in Korean. I assume it doesn't like the result which is firmware information. If anyone does have a working setup, I would appreciate some protocol traces. Grab the portmon application from sysinternals.com. Ensure Capture -> Ports includes all ports on the phone. Under Options, ensure show hex is turned on. Under edit, ensure Max Output Bytes is set to 4096. My goal is try and determine if there is an actual sync protocol for this phone, or if the "correct" way really is to read and write the files directly off the phone. Roger |
|
From: Calvin M. <mar...@ro...> - 2004-03-22 20:52:06
|
>>From one of the Hofo threads, people claimed to be able to talk to the phone >>using the Curitel sync application. However that app doesn't work for me. >>(I downloaded the version for the PD-K500). From the portmon sniff, it >>puts the phone into DM mode, and then sends command zero, gets a result >>and puts up a dialog box in Korean. I assume it doesn't like the result >>which is firmware information. The Curitel application that was used to communicate with the CDM8900 was the one for the TX95C found at the following link: http://www.curitel.com/english/download/pcsynch.asp I don't have a CDM8900 and can't grab the traces for you, but this app should at least communicate. Warning: Do not write to your phone using this application - apparently it corrupts your phone if you do (a slight difference in the phone book format). Best regards, Calvin |
|
From: Chris F. <cf...@za...> - 2004-03-22 21:14:38
|
I've created a trace, and will send it to Roger. I'd post it here, but it has a phonebook dump in it. ;) Chris... On Mon, 22 Mar 2004, Calvin Martini wrote: > The Curitel application that was used to communicate with the CDM8900 > was the one for the TX95C found at the following link: > > http://www.curitel.com/english/download/pcsynch.asp > > I don't have a CDM8900 and can't grab the traces for you, but this app > should at least communicate. Warning: Do not write to your phone using > this application - apparently it corrupts your phone if you do (a slight > difference in the phone book format). > > Best regards, > > Calvin |
|
From: Roger B. <ro...@ro...> - 2004-03-22 21:31:59
|
Chris Fraser wrote: > I've created a trace, and will send it to Roger. I'd post it here, but > it has a phonebook dump in it. ;) Thanks to Calvin, I got it up and working as well. Something that would be very useful for this phone is how the ringtone and wallpapers are done. My phone doesn't actually have a live line, and I don't want to pay to send/receive several in order to figure it out. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-22 21:59:44
|
> The Curitel application that was used to communicate with the CDM8900 > was the one for the TX95C found at the following link: Thanks. > Warning: Do not write to your phone using > this application - apparently it corrupts your phone if you do (a slight > difference in the phone book format). I will eventualy write, but be very careful. The phone is a loaner from RPI Wireless and I don't actually have it activated, but am still careful nonetheless. After looking at some traces, the news is that the phone has an explicit sync protocol for phonebook and calendar, and that it just does filesystem access for SMS. Roger |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X