Hate doing this: Two little problems...

**guino** · 04-16-2005, 11:04 PM

Hi Zorro & guys.. I've been playing around with my new phone today along with Phoco (1.4 Registered - Thanks Zorro) ... I'm trying to get it to a fully working condition so I can improve/fix some of RR's issues with Phoco.

I have two little problems:

1-I can get all phonebooks, and call lists, make calls and get battery/signal statuses no problem.. I only have a problem when trying to receive a phone call: The phone rings and imediately says "you have 1 missed call". I thought this was a phone setting so I looked and looked and found nothing. Then I tried it with Phoco Closed and the phone call came in perfectly (ringing normally). So I figured the connection to the computer could be the issue, so I went into hyperterminal and opened the port manually and called in again: I could see the 'RING's comming in and, when I entered "ATA", it answered the phone correctly, meaning there's nothing wrong with having the computer connected while the phone call comes in (by connected I mean the BT connection to provide the serial port only).. After looking at settings, manuals, forums and such, I could not find wrong with it except this excerpt from the log file:

----------------------------------------------------------------------------
16.04.2005 22:37:08 Error in LoadPhonebook: PhoneCtl.PB.xml
System.ArgumentException: DataSet can be associated with at most one XmlDataDocument. Cannot associate the DataSet with the current XmlDataDocument because the DataSet is already associated with another XmlDataDocument.
at System.Xml.XmlDataDocument.Init(DataSet ds)
at System.Xml.XmlDataDocument..ctor(DataSet dataset)
at PhoneCtl.NET.frmMain.LoadPhonebook(Int32 pi_iPBIndex)
----------------------------------------------------------------------------

The Above is what Phoco logs exactly at the time the phone is supposed to ring. I ran a Port Logger and found that immediately after the phone rings Phoco is:
-writing the above to log then
-closing and re-opening the serial port then
-sending the ATZ command (which is proably what hangs up the phone at such time).

I did searches on the error message above and found nothing of help.. I have a SE T637 and I downloaded the Setup for Phoco today (4-16). Also, after so many tries, I even updated it with the binaries to check for any differences -- stil same issue. The Phone book file is in the right place, it is not currupted and it has what seems to be the correctly formatted XML data of my contacts. I'm only writing because I ran out of options.

Also, not so important:

2-Some of the Serial Ports listed in Phoco (the ones I need) are messed up in Phoco's list (and only there). Ports like COM10 show as COM10c and COM11 show like COM11c -- and it seems to prevent phoco from using them. Other ports like COM6 show as COM62 or COM9 show like COM92.. I have been able to manage around this by switching my Regional Settings to German Format and removing/re-adding the serial port I needed and it then displays it correctly (COM12 right now). Since I was going to write already, I thought I'd mention and take a screen shot of it. I must re-inforce the fact that this happens only in Phoco. I have tested with hyperterminal and other terminal applications and they work fine with the serial ports setup (no wrong names).

Sorry for the long post (I just hate not giving enough details), Thanks in advance.. any clue is certainly appreciated.

**zorro** · 04-17-2005, 02:41 AM

Ok, can you please mail me the logfile from this session and your Config?

The error message is a bit strange but it shouldn't cause PhoCo to re-initialize. Also, it's not supposed to load any phonebooks at runtime unless you click one of the phonebook buttons.
Usually this (re-init) happens only when a timeout occurs (which you'll see in the log as well). You're right about the ATZ, it's cutting off any connection. To aviod this, you may set UseReset to False in your config.

The second issue is very strange. I'm reading the COM ports from the registry (HKLM\Hardware\Devicemap\Serialcomm). You may have a look there to check whether it's messed up there. I had this once with the MS Bluetooth drivers which appended a non-readable character to the name. Didn't find the reason yet.

**CdRsKuLL** · 04-17-2005, 03:45 AM

ok.. shoot me if you want..

I use this code to scan the com ports to find out which ones are there

Code:

Public Function ComPortExists(ByVal ComPort As Integer) _
   As Boolean

    Dim udtComConfig As COMMCONFIG
    Dim lUDTSize As Long
    Dim lRet As Long
    
    lUDTSize = LenB(udtComConfig)
    lRet = GetDefaultCommConfig("COM" + Trim(Str(ComPort)) + _
        Chr(0), udtComConfig, lUDTSize)
    ComPortExists = lRet <> 0
End Function

and use it to list in a combo box like

Code:

For n = 1 To 30
ports = ComPortExists(n)
If ports Then Combo2.AddItem n
Next n

may not help.. but thought I would post it anyway :-)

CdR

**zorro** · 04-17-2005, 03:57 AM

Yap... works as well.

Only thing to mention here is: You get more and more software generating strange virtualport COM ports (such as COM1001).

May I shoot you anyway?

**CdRsKuLL** · 04-17-2005, 04:04 AM

please do.. I went out last night.. first time in months. GOD my head hurts !

**zorro** · 04-17-2005, 04:05 AM

Guino, one thing I might figured out with RR and PhoCo:

If you start PhoneCtl.NET.exe, you should wait at least 5 seconds until you proceed (you may do other initialization in the meantime). Then, check for a TCP connection to PhoCo. If you get that connection, you have to wait for the "Init stage=2" event/message before you send messages to PhoCo.
If you send anything before PhoCo is in stage 2 of the init sequence, it may cause some wierd side effects.

**zorro** · 04-17-2005, 04:12 AM

Originally Posted by CdRsKuLL

please do.. I went out last night.. first time in months. GOD my head hurts !

Ouch... this is the price you have to pay for getting older

**guino** · 04-17-2005, 05:07 AM

Thanks guys... here's my registry: (I'll pm the log -- it has phonebook lists in it). Also, I did click on the values and they have no weird character behind them -- but they are UNICODE if that is of concern..

**guino** · 04-17-2005, 05:50 AM

Ok, sorry to bother you guys with this.. there was something wrong with my WIDCOMM .. I don't think it installed right the first time.. I re-installed it and it works fine now -- except that I can only connect to 1 one serial port (because they're both mapped to COM13).. I'll look into how I can "fix" this... Thanks for the help anyway.. sorry for the trouble.. it's weird how mostly everything worked except one little thing..

**zorro** · 04-17-2005, 05:55 AM

I suppose you mean in the BT-Neighborhood you see "Serial Port 1" & "Serial Port 2" for your T637 but in the properties you see the assigned COM port is COM13 on both, right?

This is no bug, this is by design of Widcomm.
You have to go to the "Extended Config" and add a new COM Port (on the "Client Services" tab), then assign the new COM port to the second serial port.