| Versions |
 |
|
| Author |
Topic  |
|
mdeweerd
798 Posts |
Posted - 09 janv. 2009 : 19:51:29
|
Hi Chris
I made some trials and when I set 2500 followed by a 'Store Settings', I consistently 'restore' 2500 ms.
Can you activate debug and look for the setting string (first one) and response string (second one). PMTK300 and PMTK500 introduce the 'packets':
PMTK300,2500,0,0,0.0,0.0 PMTK500,2500,0,0,0.0,0.0, |
 |
|
|
cdgmol
Netherlands
85 Posts |
Posted - 10 janv. 2009 : 15:18:23
|
Mario, it's a mystery what was wrong 2 days ago, but after activating debug the Fix value after restore is always OK now (and after deactivating debug too)!!
Note. Finding that PMTK strings was a mystery too for a while. In DebugConsole.txt in ...\SuperWaba\BT747 I did not see anything like that (only a few lines with e.g. Availability of 2skipped). The problem was that a user should know that the debug info is written to that file at exit of BT747 and that this file is deleted (refreshed) when starting again.
A feature request: can you let the store and restore button flash (green) when they are pressed? When using a touchscreen device it's very convenient to see some confirmation when pressing a button. |
Chris |
 |
|
|
1drey
Russia
62 Posts |
|
|
mdeweerd
798 Posts |
Posted - 11 janv. 2009 : 23:04:24
|
| Web start works fine for me - maybe there has been a transient connection problem? |
 |
|
|
1drey
Russia
62 Posts |
Posted - 13 janv. 2009 : 10:02:49
|
Starts okay now.
Question. I get COM port numbers >40 while BT747 allows selection of nubers <16 How to resolve this contradiction? I am sure it was answered before, but I can't find the answer :) |
Edited by - 1drey on 13 janv. 2009 10:38:47 |
 |
|
|
mdeweerd
798 Posts |
Posted - 13 janv. 2009 : 10:33:08
|
3 methods: - in the Desktop GUI: just type the port name in the pull down box, - you can populate that pull down menu by doing 'Find serial ports' in the file menu; - you can force the port name on the command line as you can find in the startup scripts |
 |
|
|
cdgmol
Netherlands
85 Posts |
Posted - 17 janv. 2009 : 14:56:02
|
I've now an E-ten Glofiish DX900 Smartphone and I'm afraid that it is a tough job to realize USING BT747 with my Q1000P. Installing SuperWaba and BT747 (BT747.PocketPC_ARM.CAB) was easy and starting BT747 is OK. But connecting BT747 with the Q1000P is perhaps a severe problem. I think or expect that it is device or system (WM6.1 or software) related, but nevertheless I post it here. Note. Don't worry about the SuperWaba warning about the newer OS, it works (however, not fully "tested" yet). But WM users should worry about or be aware of, that a single tap ("click" on touch screen) at a file in Explorer, starts executing that file (e.g. cab) without asking. Note. When I run the BT747 CAB on the iPAQ (with WM5), there is after the question about replacing "SuperWaba BT747", the possibility to select the location (Device, Storage Card or 'iPAQ File Store'). On the DX900 (with WM6.1), there's no location selection (but that's no problem at all).
On my iPAQ rx5935 with WM5 there is a "Bluetooth Manager" where I can (and have to) double tap on the iBT-GPS icon to establish a connection. Then I start BT747 and after clicking at 'Connect Port Nbr' it works (when 5 is selected). But on my DX900 I did not find (so far?) a possibility to manually activate the BT connection (before starting BT747). I don't know if that BT manager is HP or 3rd party software or that it is part of WM5 and is left out or changed in WM6.1 (the usual "blessings" of Microsoft !). And there was a (5 dots) signal strength indicator too. Another difference is assigning a COM port. On the rx5935 there is nothing like that to select or configure in the BT part (AFAIK), but now I can (and should?) assign such a port. However, only port number 0 is accepted and using that in BT747 don't work. But, on my Smartphone the program 'GPS Viewer' has used the Q1000P when the internal GPS did not work properly. So, maybe BT747 is involved too in this problem (is currently not able to activate/open a BT connection). Any suggestion will be welcome. |
Chris |
 |
|
|
1drey
Russia
62 Posts |
Posted - 17 janv. 2009 : 16:37:32
|
Problems with downloading data from Holux-M241 over bluetooth.
Never manage to dowload it with the sinle try. The progress bar freezes at some poin and the program stops to respond. Have to shut it down with the help of tack manager.
Tested on various OS (Windows XP, Windows 7), 3 different PC's
Can it be a fault of logger? |
 |
|
|
mdeweerd
798 Posts |
Posted - 17 janv. 2009 : 16:44:53
|
Supposing that you are using the latest versio, you'll need to activate the 'GPS Connection debug' and send me the transcript + GPSRawDebug.txt to get an idea. It is pretty strange though that the program stops responding. |
 |
|
|
1drey
Russia
62 Posts |
|
|
mdeweerd
798 Posts |
Posted - 17 janv. 2009 : 18:30:43
|
Hi I had a look. The device stops reponding after a re-emitted request to get log data. Actually it takes slightly more than 3.7 seconds to get the last data from the device while the timeout is set to 3.5 seconds. My first approach is to increase the default time out to 4 seconds and later possibly to take link activity better into account. |
 |
|
|
cdgmol
Netherlands
85 Posts |
Posted - 18 janv. 2009 : 13:22:26
|
I still can't connect my Q1000P with BT747 on the DX900. But with 'GPS Tuner' (a program like Navio) I can use now the Q1000P as an external GPS receiver. I found the main reason of the BT problem in a HTC Touch topic. The GSM must be on to make the Bluetooth connection possible!! And that was indeed true, in case of this dual SIM Smartphone even both "Phones" must be on. A very bad situation, but battery life is long enough to download logs from the GPS.  But unfortunately, I still don't realize a BT connection between BT747 and the Q1000P. And using COM0 is not the problem as it works with GPS Tuner. It seems that GPS Tuner is doing something that BT747 should perhaps has to do too.
Mario, do you have any idea about this? It would be very nice if it could be solved within a few days (due to my upcoming holidays). |
Chris |
 |
|
|
mdeweerd
798 Posts |
Posted - 18 janv. 2009 : 15:34:09
|
Hi Chris
An alternative is that you try to get it working with the J2ME version - try the one in the development section. Port 0 is a bit special and it is really up to Superwaba basically, but I'll have a look if I can find anything in my code that puts a limit on this.
[edit:] You can also activate the debug log (not the connection debug, just the basic one) and see if you can find the text "opening 0 @115200". I am rebuilding now to add an extra message just after that with the text result of the attempt to open the link. |
Edited by - mdeweerd on 18 janv. 2009 15:46:31 |
 |
|
|
1drey
Russia
62 Posts |
|
|
mdeweerd
798 Posts |
Posted - 18 janv. 2009 : 16:01:08
|
| The update for a bit of extra debug information is in 1.67.12. |
 |
|
Topic  |
|
|
|
| This page was generated in 2,16 seconds. |
 |
|