Notices
Page 24 of 27 « First 142223 24 2526 Last »
Reply
Thread Tools
tz1's Avatar
tz1 is offline tz1
2009-05-06 , 20:30
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#231
First, you need to set a path to save the KML files or set the save interval for KML files to zero. Also you need to use the BTScan to find and set the GPS (it should be paired and ready to connect when the scan is started). You need to run the configure if only to say OK in order to set various things internally to a known state.

I have a 0.31g version that fixes some of these things. I'm still working out a few things so it won't be up for a few days.

Second, it might take some time to link the BT gps.

Third, use the application, statusbar, or taskbar icon to start gpsd. You can start it from the command line but there may be other side-effects.
 
joy_fun_man is offline joy_fun_man
2009-05-06 , 22:33
Posts: 22 | Thanked: 0 times | Joined on Nov 2007
#232
Originally Posted by tz1 View Post
First, you need to set a path to save the KML files or set the save interval for KML files to zero. Also you need to use the BTScan to find and set the GPS (it should be paired and ready to connect when the scan is started). You need to run the configure if only to say OK in order to set various things internally to a known state.
I haved already done these steps but the same things that i described occurs !
I follow your growning creature since the first release 0.30-pre1beta.
I've start the app in xterm only to obtain more debug info.
If you want i can post the strace result with the option that you prefer.

Second, it might take some time to link the BT gps.

Third, use the application, statusbar, or taskbar icon to start gpsd. You can start it from the command line but there may be other side-effects.
If i start without before:
rfcomm0 connect BT__gps_address
but only with use of the application, statusbar, or taskbar icon the red circle status never disappear and the process never see the sats.
Otherwise if before i use:
rfcomm0 connect BT__gps_address
when i starts the app with use of the application, statusbar, or taskbar icon, the red state change immediatly to the correct green circle status and the sats yellow-green-red symbols appears.
I've also correctly verified (loading in google earth) the data of any stored .kmz files.
In few words, with this method, i succesfully connect or MMapper set to /dev/rfcomm0 or minigpsd (but only one at a time)

I have a 0.31g version that fixes some of these things. I'm still working out a few things so it won't be up for a few days.
I'm waiting for new variants

If i can try it, post the link where to download this release.

Thanks mate for your interest
 
tz1's Avatar
tz1 is offline tz1
2009-05-07 , 00:59
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#233
In the bluetooth scan status screen (config, then btscan button), is the address the same next to the setGPS button as the correct address for the BT GPS?

Also do a FULL "ps" (before worrying about the strace). There is btconnect.sh which parameters has to match (normally /dev/rfcomm0 and the address for the GPS) and it should do l2ping to find the gps, then an rfcomm to connect to it.
 
joy_fun_man is offline joy_fun_man
2009-05-10 , 16:43
Posts: 22 | Thanked: 0 times | Joined on Nov 2007
#234
Originally Posted by tz1 View Post
In the bluetooth scan status screen (config, then btscan button), is the address the same next to the setGPS button as the correct address for the BT GPS?
Yes, the GPS BT Addr and Current GPS Saved (in configure panel) are setted correctly to my gps BT address; (OBD BT and V1 BT all zero)

Originally Posted by tz1 View Post
Also do a FULL "ps" (before worrying about the strace). There is btconnect.sh which parameters has to match (normally /dev/rfcomm0 and the address for the GPS) and it should do l2ping to find the gps, then an rfcomm to connect to it.
When i start minigpsd i see gps connected but always red circle state:
~ $ ps | grep bt

1148 root 2948 SW< /usr/bin/btcond -l
...
~ $ ps | grep rf

292 root SW< [krfcommd]

1339 user 1452 SW< rfcomm connect 0 00:xx:xx:xx:xx:xx (<-my gps BT address)
BUT ONLY if i perform before in xterm:
rfcomm connect 00:xx:xx:xx:xx:xx (<-my gps BT address)

Connected /dev/rfcomm0 to 00:xx:xx:xx:xx:xx (<-my gps BT address) on channel 1

Press CTRL-C for hangup
and then start minigpsd i see the green circle with the sats dots and btconnect.sh:
~ $ ps | grep bt

1150 root 2948 SW< /usr/bin/btcond -l

1654 user 1884 SW< sh /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx (<-my gps BT address)

1657 user 1892 SW grep bt

~ $ ps | grep rf

292 root SW< [krfcommd]

1547 user 1588 SW rfcomm connect 00:xx:xx:xx:xx:xx (<-my gps BT address)

1874 user 1892 RW grep rf
I have only the SUDSER package with a psw setted for the root rights, i don't know if it's necessary anything else.

And what 'bout the rfcomm.conf and hcid.conf in /etc.

Maybe i have to modify anithing in these files

Thanks in advance
 
tz1's Avatar
tz1 is offline tz1
2009-05-10 , 17:22
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#235
It doesn't help me one bit seeing a highly edited output of ps. If I wanted selected bits I would have asked for them (you can go "ps >/media/mmc1/x.log" to save the output. Also make sure kml interval is set to zero or that the directory points to something which exists.

I still have no idea what is happening.

You also can try doing

sh -x /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx &

And watch what is happening and where it is hanging up.

Are you starting minigpsd from the application/applets?

DO NOT start any GPS in any other way, not the map, not the location manager. Make sure all GPS activity is off before you do StartGPSD from the applet.
 
joy_fun_man is offline joy_fun_man
2009-05-10 , 19:17
Posts: 22 | Thanked: 0 times | Joined on Nov 2007
#236
Originally Posted by tz1 View Post
It doesn't help me one bit seeing a highly edited output of ps. If I wanted selected bits I would have asked for them (you can go "ps >/media/mmc1/x.log" to save the output. Also make sure kml interval is set to zero or that the directory points to something which exists.

I still have no idea what is happening.

Are you starting minigpsd from the application/applets?

DO NOT start any GPS in any other way, not the map, not the location manager. Make sure all GPS activity is off before you do StartGPSD from the applet.
Starting minigpsd from the applet with New KML Every 0 these are the processes:
PID Uid VSZ Stat Command
1 root 1468 SW init [2]
2 root SWN [ksoftirqd/0]
3 root SW [watchdog/0]
4 root SW< [events/0]
5 root SW< [khelper]
6 root SW< [kthread]
14 root SW< [dvfs/0]
66 root SW< [kblockd/0]
67 root SW< [kseriod]
79 root SW< [OMAP McSPI/0]
86 root SW< [ksuspend_usbd]
89 root SW< [khubd]
113 root SW [pdflush]
114 root SW [pdflush]
115 root SW< [kswapd0]
116 root SW< [aio/0]
119 root SW< [mipid_esd]
238 root SW [mtdblockd]
280 root SW< [kondemand/0]
281 root SW< [kmmcd]
292 root SW< [krfcommd]
303 root SW< [mmcqd]
310 root SW< [mmcqd]
339 root 1108 SW< dsme -d -l syslog -v 4 -p /usr/lib/dsme/libstartup.so
347 root 804 SW /usr/bin/bme_RX-34
349 root 564 SW /usr/sbin/kicker
396 root SW< [cx3110x]
416 root SWN [jffs2_gcd_mtd4]
445 root 1580 SW< /sbin/udevd --daemon
737 messagebus 2312 SW< /usr/bin/dbus-daemon --system
746 haldaemon 3988 SW /usr/sbin/hald
747 root 2824 SW hald-runner
751 root 2980 SW /usr/lib/hal/hald-addon-bme
753 root 2984 SW /usr/lib/hal/hald-addon-cpufreq
754 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
755 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
756 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
757 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
758 root 2972 SW hald-addon-input: Listening on /dev/input/event2 /dev
759 root 2468 SW /usr/lib/hal/hald-addon-mmc
760 root 2468 SW /usr/lib/hal/hald-addon-mmc
774 root 3788 SW< /sbin/mce --force-syslog
776 messagebus 3356 SW /usr/lib/gconf2/gconfd-2
780 root 11132 SW< /usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolis
807 user 1312 SW< /usr/sbin/temp-reaper
810 user 2044 SW< /usr/bin/dbus-daemon --session
814 user 7148 SW< /usr/lib/sapwood/sapwood-server
818 user 9080 SW< /usr/bin/matchbox-window-manager -theme default -use_
826 root SW< [dsp/0]
829 root SW< [dsp/0]
832 root 2956 SW /usr/sbin/dsp_dld -p --disable-restart -c /lib/dsp/ds
892 root 4832 SW /usr/sbin/multimediad
897 root 2168 SW< /usr/bin/esd
946 root SW< [file-storage-ga]
950 haldaemon 2540 SW hald-addon-usb-cable: listening on /sys/devices/plat
958 root 7896 SW< /usr/sbin/ke-recv
976 user 21296 SW< /usr/bin/maemo-launcher --daemon --booster gtk --quie
1007 user 1448 SW< /usr/bin/hildon-input-method
1008 user 31944 SW< /usr/bin/hildon-input-method
1011 user 3944 SW< /usr/bin/clipboard-manager
1053 user 1448 SW< /usr/bin/hildon-desktop
1054 user 54240 SW< /usr/bin/hildon-desktop
1114 nobody 1808 SW< /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z
1137 root 3428 SW /usr/sbin/sshd
1140 root 2588 SW< /usr/sbin/hcid -n -x -s
1143 root 2508 SW< /usr/lib/bluetooth/bluetoothd-service-audio
1146 root 2444 SW< /usr/lib/bluetooth/bluetoothd-service-input
1150 root 2948 SW< /usr/bin/btcond -l
1155 root 3604 SW< /usr/sbin/wlancond
1161 root 4148 SW< /usr/sbin/icd2 -l0
1179 user 1448 SW< /usr/bin/osso-connectivity-ui-conndlgs
1180 user 23008 SW< /usr/bin/osso-connectivity-ui-conndlgs
1196 user 7448 SW< /usr/bin/osso-media-server
1208 systemui 17012 SW< /usr/bin/systemui
1216 user 3208 SW< /usr/bin/obexsrv -l
1236 user 5260 SW /usr/bin/alarmd
1254 root 5112 SW< /usr/sbin/hulda
1255 root 3060 SW< /usr/sbin/hulda
1275 user 16476 SW /usr/bin/mediaplayer-engine
1281 user 16408 SWN /usr/bin/metalayer-crawler -F
1297 user 40120 SW /usr/sbin/browserd -d -i microb
1308 user 67324 SW /usr/sbin/browserd -s 1308 -i microb
1317 user 1448 SW /usr/bin/osso-xterm
1318 user 35348 SW /usr/bin/osso-xterm
1319 user 1960 SW -sh
1322 user 7920 SW /usr/libexec/gnome-vfs-daemon
1326 user 1448 SW /usr/bin/osso_notes
1327 user 31592 SW /usr/bin/osso_notes
1329 user 3100 SW< /usr/bin/minigpsd
1333 user 1452 SW< rfcomm connect 0 00:xx:xx:xx:xx:xx
1336 user 1988 RW ps


You also can try doing

sh -x /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx &

And watch what is happening and where it is hanging up.
~ $ sh -x /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx &

+ sudo /usr/bin/l2ping -t 1 -c 1 00:xx:xx:xx:xx:xx

~ $ + exec rfcomm connect 0 00:xx:xx:xx:xx:xx

Can't connect RFCOMM socket: Operation now in progress

~ $
When i do the command after few moments the Bluetooth symbol become blue and the gps bt is connected, after ~1 minute the Bluetooth symbol become white and the phrase
Can't connect RFCOMM socket: Operation now in progress
appears.
Last edited by joy_fun_man; 2009-05-10 at 19:19.
 
tz1's Avatar
tz1 is offline tz1
2009-05-10 , 20:14
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#237
Thank you. The ps output is unexpected.

Which version are you using? The current one is 0.31f.

Only a very old version of minigpsd would start rfcomm by itself.

The current version launches btconnect.sh.

Try removing (manually remove /usr/bin/minigpsd if needed) and reinstalling the latest from maemo extras.
 
joy_fun_man is offline joy_fun_man
2009-05-11 , 07:48
Posts: 22 | Thanked: 0 times | Joined on Nov 2007
#238
Originally Posted by tz1 View Post
Thank you. The ps output is unexpected.

Which version are you using? The current one is 0.31f.

Only a very old version of minigpsd would start rfcomm by itself.

The current version launches btconnect.sh.

Try removing (manually remove /usr/bin/minigpsd if needed) and reinstalling the latest from maemo extras.
I have the last public version 0.31f.

Few days ago i have just tried to deinstall and reinstall the app by apps manager utility, but nothing changed.

On my n800 the current version launches btconnect.sh ONLY if before i manually do rfcomm connect my_gps_bt_address.
Last edited by joy_fun_man; 2009-05-11 at 07:50.
 
svs57 is offline svs57
2009-05-12 , 09:33
Posts: 207 | Thanked: 31 times | Joined on Apr 2008
#239
N810 DIABLO_5.2008.43-7
minigpsd 0.31f
minigps doesn't running but Minigpsd SB in status bar menu show
"Stop GPSD" insteat of "Start GPSD"
If I start minigpsd from console and tap "Stop GPSD" in status bar then minigpsd stop. But menu in status bar is the same: "Stop GPSD"
 
joy_fun_man is offline joy_fun_man
2009-05-16 , 10:51
Posts: 22 | Thanked: 0 times | Joined on Nov 2007
#240
Originally Posted by tz1 View Post
Thank you. The ps output is unexpected.

Which version are you using? The current one is 0.31f.

Only a very old version of minigpsd would start rfcomm by itself.

The current version launches btconnect.sh.

Try removing (manually remove /usr/bin/minigpsd if needed) and reinstalling the latest from maemo extras.
Originally Posted by tz1 View Post
It doesn't help me one bit seeing a highly edited output of ps. If I wanted selected bits I would have asked for them (you can go "ps >/media/mmc1/x.log" to save the output. Also make sure kml interval is set to zero or that the directory points to something which exists.

I still have no idea what is happening.

Are you starting minigpsd from the application/applets?

DO NOT start any GPS in any other way, not the map, not the location manager. Make sure all GPS activity is off before you do StartGPSD from the applet.
In order to resolve these unexpected errors I HAVE ENTIRELY REFLASHED MY N800 WITH THE LATEST DIABLO 5.2008.43-7 FIRMWARE and after installed MINIGPSD as first application.

Starting minigpsd from the applet with New KML Every 0 these are the processes:
PID Uid VSZ Stat Command
1 root 1468 SW init [2]
2 root SWN [ksoftirqd/0]
3 root SW [watchdog/0]
4 root SW< [events/0]
5 root SW< [khelper]
6 root SW< [kthread]
14 root SW< [dvfs/0]
66 root SW< [kblockd/0]
67 root SW< [kseriod]
79 root SW< [OMAP McSPI/0]
86 root SW< [ksuspend_usbd]
89 root SW< [khubd]
113 root SW [pdflush]
114 root SW [pdflush]
115 root SW< [kswapd0]
116 root SW< [aio/0]
119 root SW< [mipid_esd]
238 root SW [mtdblockd]
280 root SW< [kondemand/0]
281 root SW< [kmmcd]
292 root SW< [krfcommd]
303 root SW< [mmcqd]
310 root SW< [mmcqd]
339 root 1120 SW< dsme -d -l syslog -v 4 -p /usr/lib/dsme/libstartup.so
347 root 804 SW /usr/bin/bme_RX-34
349 root 564 SW /usr/sbin/kicker
396 root SW< [cx3110x]
416 root SWN [jffs2_gcd_mtd4]
448 root 1580 SW< /sbin/udevd --daemon
680 messagebus 2312 SW< /usr/bin/dbus-daemon --system
738 haldaemon 4012 SW /usr/sbin/hald
739 root 2828 SW hald-runner
758 root 2984 SW /usr/lib/hal/hald-addon-bme
760 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
761 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
762 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
764 root 2468 SW /usr/lib/hal/hald-addon-omap-gpio
765 root 2972 SW hald-addon-input: Listening on /dev/input/event2 /dev
766 root 2468 SW /usr/lib/hal/hald-addon-mmc
767 root 2468 SW /usr/lib/hal/hald-addon-mmc
769 root 2984 SW /usr/lib/hal/hald-addon-cpufreq
786 root 3788 SW< /sbin/mce --force-syslog
802 root 10924 SW< /usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolis
829 user 1444 SW< /usr/sbin/temp-reaper
836 user 7268 SW< /usr/lib/sapwood/sapwood-server
840 user 9008 SW< /usr/bin/matchbox-window-manager -theme default -use_
848 root SW< [dsp/0]
851 root SW< [dsp/0]
854 root 2956 SW /usr/sbin/dsp_dld -p --disable-restart -c /lib/dsp/ds
914 root 4836 SW /usr/sbin/multimediad
919 root 2524 SW< /usr/bin/esd
972 root SW< [file-storage-ga]
976 haldaemon 2540 SW hald-addon-usb-cable: listening on /sys/devices/plat
1042 nobody 1808 SW< /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z
1096 messagebus 3356 SW /usr/lib/gconf2/gconfd-2
1180 user 2052 SW< /usr/bin/dbus-daemon --session
1278 systemui 24560 SW< /usr/bin/systemui
1308 user 5268 SW /usr/bin/alarmd
1449 user 7448 SW< /usr/bin/osso-media-server
1534 user 16580 SWN /usr/bin/metalayer-crawler -F
1574 user 7980 SW /usr/libexec/gnome-vfs-daemon
3810 root 7892 SW< /usr/sbin/ke-recv
3827 user 21308 SW< /usr/bin/maemo-launcher --daemon --booster gtk --quie
3854 user 1452 SW< /usr/bin/hildon-input-method
3855 user 30020 SW< /usr/bin/hildon-input-method
3860 user 3944 SW< /usr/bin/clipboard-manager
3897 user 1452 SW< /usr/bin/hildon-desktop
3898 user 67436 SW< /usr/bin/hildon-desktop
3967 root 2596 SW< /usr/sbin/hcid -n -x -s
3972 root 2512 SW< /usr/lib/bluetooth/bluetoothd-service-audio
3973 root 2448 SW< /usr/lib/bluetooth/bluetoothd-service-input
3977 root 2952 SW< /usr/bin/btcond -l
3980 root 3608 SW< /usr/sbin/wlancond
3984 root 4152 SW< /usr/sbin/icd2 -l0
4002 user 1452 SW< /usr/bin/osso-connectivity-ui-conndlgs
4003 user 23020 SW< /usr/bin/osso-connectivity-ui-conndlgs
4009 user 3208 SW< /usr/bin/obexsrv -l
4024 root 5116 SW< /usr/sbin/hulda
4025 root 3064 SW< /usr/sbin/hulda
4045 user 16640 SW /usr/bin/mediaplayer-engine
4061 user 40168 SW /usr/sbin/browserd -d -i microb
4063 user 67356 SW /usr/sbin/browserd -s 4063 -i microb
4091 user 3100 SW< /usr/bin/minigpsd
4101 user 1452 SW /usr/bin/osso-xterm
4102 user 26436 SW /usr/bin/osso-xterm
4103 user 1960 SW -sh
4105 user 1452 SW< rfcomm connect 0 00:xx:xx:xx:xx:xx
4107 user 1988 RW ps


You also can try doing

sh -x /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx &

And watch what is happening and where it is hanging up.
~ $ sh -x /usr/bin/btconnect.sh 0 00:xx:xx:xx:xx:xx &

+ sudo /usr/bin/l2ping -t 1 -c 1 00:xx:xx:xx:xx:xx

~ $ + exec rfcomm connect 0 00:xx:xx:xx:xx:xx

Can't connect RFCOMM socket: Operation now in progress

~ $
When i do the command after few moments the Bluetooth symbol become blue and the gps bt is connected, after ~5 seconds the Bluetooth symbol become white and the phrase
Can't connect RFCOMM socket: Operation now in progress
appears.
 
Reply
Page 24 of 27 « First 142223 24 2526 Last »

Tags
gps, obd2

« Previous Thread | Next Thread »
Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:45.

Contact Us - Home - Archive - Top