Autor Thema: GPS-Daten in FHEM einlesen - gelöst  (Gelesen 10275 mal)

Offline morph

  • Full Member
  • ***
  • Beiträge: 220
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #60 am: 30 Mai 2018, 10:17:38 »
Ok, also für mich selbst als Marker, äh ich mein natürlich für alle anderen mit einem Pi3 oder Zero (einem mit Bluetooth und WLAN on Board).

1. Image installieren, Updates etc durchführen.
2. In der /boot/cmdline.txt alles was mit console und serial und AMA0 oder was auch immer entfernen
console=ttyAMA0,115200
kgdboc=ttyAMA0,115200
serial0,115200
console=ttyS0,115200
3. in der /etc/inittab alles bis auf vt100 auskommentieren, falls dort etwas drin ist.
4.
sudo systemctl stop serial-getty@ttyS0.service
sudo systemctl disable serial-getty@ttyS0.service
5. Via sudo nano /boot/config.txt dort die Zeile ergänzen, ganz unten am besten
enable_uart=1
6. reboot und gpsd + Zubehör installieren
sudo apt-get install gpsd gpsd-clients
sudo apt-get install libnet-gpsd3-perl
FALSCH: [s]sudo cpan force install GPSD::Parse[/s]
sudo cpan -i install GPSD::Parse
7. Danach noch folgendes und es läuft:
sudo killall gpsd
sudo rm /var/run/gpsd.sock
sudo systemctl stop gpsd.socket
sudo systemctl disable gpsd.socket
sudo gpsd /dev/ttyS0 -G -n -F /var/run/gpsd.sock
8. cgps und fertig...

Es kann so einfach sein....
« Letzte Änderung: 30 Mai 2018, 12:05:53 von morph »

Offline morph

  • Full Member
  • ***
  • Beiträge: 220
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #61 am: 30 Mai 2018, 10:18:33 »
Läuft denn gpsd überhaupt?

sudo service gpsd status

Ja, der lief. Ich denke, es liegt/lag an Punkt 7 Zeile 2

Nur scheitert es jetzt mittlerweile wie beim Kollegen vorher beim Laden des Moduls.


nach einem reload 49_GPSD.pm
Can't locate GPSD/Parse.pm in @INC (you may need to install the GPSD::Parse module) (@INC contains: . /etc/perl /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5 /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base ./FHEM) at ./FHEM/49_GPSD.pm line 24.
BEGIN failed--compilation aborted at ./FHEM/49_GPSD.pm line 24.

Denn auch die Installation des Teils CPAN ist am Ende fehlerhaft

pi@SchantallPi:/opt/fhem $ sudo cpan force install GPSD::Parse
Loading internal null logger. Install Log::Log4perl for logging messages
Reading '/root/.cpan/Metadata'
  Database was generated on Wed, 30 May 2018 05:54:08 GMT
Warning: Cannot install force, don't know what it is.
Try the command

    i /force/

to find objects with matching identifiers.
install is up to date (0.01).
Running install for module 'GPSD::Parse'
Checksum for /root/.cpan/sources/authors/id/S/ST/STEVEB/GPSD-Parse-1.02.tar.gz ok
'YAML' not installed, will not store persistent state
Configuring S/ST/STEVEB/GPSD-Parse-1.02.tar.gz with Makefile.PL
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for GPSD::Parse
Writing MYMETA.yml and MYMETA.json
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/perl Makefile.PL INSTALLDIRS=site -- OK
Running make for S/ST/STEVEB/GPSD-Parse-1.02.tar.gz
cp lib/GPSD/Parse.pm blib/lib/GPSD/Parse.pm
Manifying 1 pod document
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/make -- OK
Running make test
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00-load.t ................ 1/? In socket mode...
t/00-load.t ................ ok
t/05-poll.t ................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/05-poll.t ................ 1/?

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 5.

#   Failed test '...and it contains TPV ok'
#   at t/05-poll.t line 40.
#                   '{"class":"POLL","time":"2018-05-30T08:44:26.397Z","active":0,"tpv":[],"gst":[],"sky":[]}'
#     doesn't match '(?^:TPV)'
# Looks like you failed 1 test of 11.
t/05-poll.t ................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/11 subtests
t/10-time.t ................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/10-time.t ................ 1/?
#   Failed test '...and is ok'
#   at t/10-time.t line 27.
#                   undef
#     doesn't match '(?^:^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$)'
# Looks like you failed 1 test of 2.
t/10-time.t ................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests
t/15-device.t ..............

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/15-device.t .............. 1/?
#   Failed test '...and is ok'
#   at t/15-device.t line 27.
#                   undef
#     doesn't match '(?^:^/dev/ttyS0$)'
# Looks like you failed 1 test of 2.
t/15-device.t .............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests
t/20-tpv.t .................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/20-tpv.t ................. 1/?
#   Failed test 'tpv() key count matches number of stats'
#   at t/20-tpv.t line 48.
#          got: '2'
#     expected: '17'

#   Failed test 'time stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'alt stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'climb stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'speed stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'track stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'device stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'mode stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epx stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epy stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epc stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'ept stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epv stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'eps stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'class stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'tag stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'lat is in proper format'
#   at t/20-tpv.t line 55.
#                   undef
#     doesn't match '(?^:^-?\d+\.\d{4,9}$)'

#   Failed test 'lon is in proper format'
#   at t/20-tpv.t line 55.
#                   undef
#     doesn't match '(?^:^-?\d+\.\d{4,9}$)'
# Looks like you failed 18 tests of 39.
t/20-tpv.t ................. Dubious, test returned 18 (wstat 4608, 0x1200)
Failed 18/39 subtests
t/25-satellites.t ..........

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/25-satellites.t .......... ok
t/30-sky.t .................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/30-sky.t ................. 1/?
#   Failed test 'keys match SKY entry count'
#   at t/30-sky.t line 40.
#          got: '1'
#     expected: '11'

#   Failed test 'SKY stat xdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat ydop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat pdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat tdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat vdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat gdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat hdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat class exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat tag exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat device exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'
t/30-sky.t ................. 14/?
#   Failed test 'SKY satellite entries are hrefs'
#   at t/30-sky.t line 47.
#          got: ''
#     expected: 'HASH'

#   Failed test 'each SKY sat entry has stats'
#   at t/30-sky.t line 48.
#          got: ''
#     expected: '1'
# Looks like you failed 13 tests of 16.
t/30-sky.t ................. Dubious, test returned 13 (wstat 3328, 0xd00)
Failed 13/16 subtests
t/35-unit_conversion.t ..... ok
t/40-metres_feet.t ......... ok
t/45-direction.t ........... ok
t/50-signed.t .............. ok
t/55-unsigned.t ............ ok
t/60-poll_signed_toggle.t .. ok
t/65-tpv_methods.t .........

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-hA7A_a/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/65-tpv_methods.t ......... ok
t/manifest.t ............... skipped: Author tests not required for installation
t/pod-coverage.t ........... skipped: Author tests not required for installation
t/pod.t .................... skipped: Author tests not required for installation

Test Summary Report
-------------------
t/05-poll.t              (Wstat: 256 Tests: 11 Failed: 1)
  Failed test:  9
  Non-zero exit status: 1
t/10-time.t              (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/15-device.t            (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/20-tpv.t               (Wstat: 4608 Tests: 39 Failed: 18)
  Failed tests:  2-3, 6-21
  Non-zero exit status: 18
t/30-sky.t               (Wstat: 3328 Tests: 16 Failed: 13)
  Failed tests:  2, 4-13, 15-16
  Non-zero exit status: 13
Files=17, Tests=176, 19 wallclock secs ( 1.26 usr  0.25 sys + 15.12 cusr  0.96 csys = 17.59 CPU)
Result: FAIL
Failed 5/17 test programs. 34/176 subtests failed.
Makefile:832: die Regel für Ziel „test_dynamic“ scheiterte
make: *** [test_dynamic] Fehler 255
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
  reports STEVEB/GPSD-Parse-1.02.tar.gz

oder auch mit "-i"

pi@SchantallPi:~ $ sudo cpan -i install GPSD::Parse
Loading internal null logger. Install Log::Log4perl for logging messages
Reading '/root/.cpan/Metadata'
  Database was generated on Wed, 30 May 2018 05:54:08 GMT
install is up to date (0.01).
Running install for module 'GPSD::Parse'
Checksum for /root/.cpan/sources/authors/id/S/ST/STEVEB/GPSD-Parse-1.02.tar.gz ok
'YAML' not installed, will not store persistent state
Configuring S/ST/STEVEB/GPSD-Parse-1.02.tar.gz with Makefile.PL
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for GPSD::Parse
Writing MYMETA.yml and MYMETA.json
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/perl Makefile.PL INSTALLDIRS=site -- OK
Running make for S/ST/STEVEB/GPSD-Parse-1.02.tar.gz
cp lib/GPSD/Parse.pm blib/lib/GPSD/Parse.pm
Manifying 1 pod document
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/make -- OK
Running make test
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00-load.t ................ 1/? In socket mode...
t/00-load.t ................ ok
t/05-poll.t ................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/05-poll.t ................ 1/?

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 5.

#   Failed test '...and it contains TPV ok'
#   at t/05-poll.t line 40.
#                   '{"class":"POLL","time":"2018-05-30T08:53:20.183Z","active":0,"tpv":[],"gst":[],"sky":[]}'
#     doesn't match '(?^:TPV)'
# Looks like you failed 1 test of 11.
t/05-poll.t ................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/11 subtests
t/10-time.t ................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/10-time.t ................ 1/?
#   Failed test '...and is ok'
#   at t/10-time.t line 27.
#                   undef
#     doesn't match '(?^:^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$)'
# Looks like you failed 1 test of 2.
t/10-time.t ................ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests
t/15-device.t ..............

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/15-device.t .............. 1/?
#   Failed test '...and is ok'
#   at t/15-device.t line 27.
#                   undef
#     doesn't match '(?^:^/dev/ttyS0$)'
# Looks like you failed 1 test of 2.
t/15-device.t .............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests
t/20-tpv.t .................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/20-tpv.t ................. 1/?
#   Failed test 'tpv() key count matches number of stats'
#   at t/20-tpv.t line 48.
#          got: '2'
#     expected: '17'

#   Failed test 'time stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'alt stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'climb stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'speed stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'track stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'device stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'mode stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epx stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epy stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epc stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'ept stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'epv stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'eps stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'class stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'tag stat exists in return'
#   at t/20-tpv.t line 51.
#          got: ''
#     expected: '1'

#   Failed test 'lat is in proper format'
#   at t/20-tpv.t line 55.
#                   undef
#     doesn't match '(?^:^-?\d+\.\d{4,9}$)'

#   Failed test 'lon is in proper format'
#   at t/20-tpv.t line 55.
#                   undef
#     doesn't match '(?^:^-?\d+\.\d{4,9}$)'
# Looks like you failed 18 tests of 39.
t/20-tpv.t ................. Dubious, test returned 18 (wstat 4608, 0x1200)
Failed 18/39 subtests
t/25-satellites.t ..........

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/25-satellites.t .......... ok
t/30-sky.t .................

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/30-sky.t ................. 1/?
#   Failed test 'keys match SKY entry count'
#   at t/30-sky.t line 40.
#          got: '1'
#     expected: '11'
t/30-sky.t ................. 3/?
#   Failed test 'SKY stat xdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat ydop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat pdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat tdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat vdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat gdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat hdop exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat class exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat tag exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY stat device exists'
#   at t/30-sky.t line 43.
#          got: ''
#     expected: '1'

#   Failed test 'SKY satellite entries are hrefs'
#   at t/30-sky.t line 47.
#          got: ''
#     expected: 'HASH'

#   Failed test 'each SKY sat entry has stats'
#   at t/30-sky.t line 48.
#          got: ''
#     expected: '1'
# Looks like you failed 13 tests of 16.
t/30-sky.t ................. Dubious, test returned 13 (wstat 3328, 0xd00)
Failed 13/16 subtests
t/35-unit_conversion.t ..... ok
t/40-metres_feet.t ......... ok
t/45-direction.t ........... ok
t/50-signed.t .............. ok
t/55-unsigned.t ............ ok
t/60-poll_signed_toggle.t .. ok
t/65-tpv_methods.t .........

incomplete or empty dataset returned from GPS...

Use of uninitialized value $lat in pattern match (m//) at /root/.cpan/build/GPSD-Parse-1.02-JzvE1z/blib/lib/GPSD/Parse.pm line 185, <GEN0> line 4.
t/65-tpv_methods.t ......... ok
t/manifest.t ............... skipped: Author tests not required for installation
t/pod-coverage.t ........... skipped: Author tests not required for installation
t/pod.t .................... skipped: Author tests not required for installation

Test Summary Report
-------------------
t/05-poll.t              (Wstat: 256 Tests: 11 Failed: 1)
  Failed test:  9
  Non-zero exit status: 1
t/10-time.t              (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/15-device.t            (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
t/20-tpv.t               (Wstat: 4608 Tests: 39 Failed: 18)
  Failed tests:  2-3, 6-21
  Non-zero exit status: 18
t/30-sky.t               (Wstat: 3328 Tests: 16 Failed: 13)
  Failed tests:  2, 4-13, 15-16
  Non-zero exit status: 13
Files=17, Tests=176, 19 wallclock secs ( 1.38 usr  0.10 sys + 14.99 cusr  1.03 csys = 17.50 CPU)
Result: FAIL
Failed 5/17 test programs. 34/176 subtests failed.
Makefile:832: die Regel für Ziel „test_dynamic“ scheiterte
make: *** [test_dynamic] Fehler 255
  STEVEB/GPSD-Parse-1.02.tar.gz
  /usr/bin/make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
  reports STEVEB/GPSD-Parse-1.02.tar.gz
« Letzte Änderung: 30 Mai 2018, 10:54:37 von morph »

Offline Wernieman

  • Hero Member
  • *****
  • Beiträge: 5640
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #62 am: 30 Mai 2018, 11:25:01 »
Hast Du mal probiert, anstelle von CPAN mit apt-get (siehe ein paar Seiten vorher) zu installieren?

Bitte CPAN nur, wenn es die Libary NICHT in der Distri gibt ....
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

Offline morph

  • Full Member
  • ***
  • Beiträge: 220
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #63 am: 30 Mai 2018, 12:24:14 »
via apt-get install GPSD::Parse ?

Ich finde nichts weiter was du da meinen könntest.

Das obige geht nicht.

Das GPS Modul ab , das CPAN ausführen und wieder anlöten war das richtige... :-(
« Letzte Änderung: 30 Mai 2018, 12:53:39 von morph »

Offline morph

  • Full Member
  • ***
  • Beiträge: 220
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #64 am: 30 Mai 2018, 14:44:01 »
Und mit dem Track gings dann auch gleich weiter.

gpspipe -d  -l -r -o /home/pi/GPXLog/route.txt

erstellt eine Textdatei mit nmea Rohdaten

gpsbabel -i nmea -f /home/pi/GPXLog/route.txt -o kml -F /home/pi/GPXLog/track.kml


Erstellt dann direkt die passende kml Datei.

Das lasse ich mir dann ebenfalls, jenachdem was das für ne Größe ergibt, auf die Dropbox laden, und habe dann somit

- immer einen Aktuellen Google Link in der Dropbox
- immer eine Aktuellen GPX, mit dem ich dann was auch immer noch mit anstellen kann
- und die Route die das Wohnmobil zurückgelegt hat.

Offline Wernieman

  • Hero Member
  • *****
  • Beiträge: 5640
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #65 am: 31 Mai 2018, 09:06:46 »
WIe schon geschrieben: Habe es einige Seiten vorher geschrieben (Sorry, suche es für Dich nicht raus).

"GPSD::Parse" ist natürlich Perl und nicht apt-get Syntax. Da muß man raussuchen, wie die Libary richtig heißt ...

Edit:
Ausnahmsweise:

Mal Probiert:
apt-cache search GPSD
gosmore - Betrachter, Routenplaner und Such-Client für Openstreetmap.org
gpsbabel - Umwandlung von GPS-Dateien plus Transfer zum/vom GPS-Gerät
gpsd - Daemon für das Global Positioning System (GPS)
gpsd-clients - Globales Positionierungssystem - Clients
gpsd-dbg - Global Positioning System - debugging symbols
libgps-dev - Global Positioning System - development files
libgps22 - Global Positioning System - library
libqgpsmm-dev - Global Positioning System - Qt wrapper for libgps (development)
libqgpsmm22 - Global Positioning System - Qt wrapper for libgps
navit - Navigationssystem für Automobile mit Routenplaner
navit-data - Car navigation system with routing engine - data files
navit-graphics-gtk-drawing-area - Car navigation system with routing engine - GTK+ graphic plugin
navit-gui-gtk - Car navigation system with routing engine - GTK+ GUI
navit-gui-internal - Car navigation system with routing engine - internal GUI
python-gps - Global Positioning System - Python libraries
fso-gpsd - gpsd subset compatibility daemon for the freesmarpthone.org frameworkd
gypsy-daemon - A GPS Multiplexing Daemon
libnet-gpsd3-perl - Perl interface to the gpsd server daemon protocol version 3 (JSON)

Nach der Liste würde ich denken: libnet-gpsd3-perl
apt-get install libnet-gpsd3-perl
Gibt auch Suchmaschinen dafür im Netz, habe nur gerade keinen Link dafür zur Hand .....

Leider schreiben HowTows meistens den CPAN weg, der aber gerade für Anfängern wegen der Update-Problematik NICHT gewählt werden sollte .....
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

Offline morph

  • Full Member
  • ***
  • Beiträge: 220
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #66 am: 04 Juni 2018, 19:38:06 »
Ich danke dir für die mühen.

Aber das eigentliche Problem hab ich mit einem Ab und wieder An löten erledigt. Danke

Offline hanami

  • New Member
  • *
  • Beiträge: 20
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #67 am: 26 Januar 2019, 11:23:32 »
:o

Soooo einfach....

und Das mit dem GPX hab ich auch hinbekommen:

define Filelog_GPX FileLog ./log/Filelog_GPX-%Y-%m.log GPS:(gpx).*
Bekomme ich nun die, und nur die Zeilen:

2018-01-18_22:39:24 GPS gpx: <trkpt lat="48.41" lon="10.29"><time>2018-01-18T21:39:24.000Z</time></trkpt>
2018-01-18_22:39:54 GPS gpx: <trkpt lat="48.41" lon="10.2"><time>2018-01-18T21:39:54.000Z</time></trkpt>
2018-01-18_22:40:24 GPS gpx: <trkpt lat="48.41" lon="10.2"><time>2018-01-18T21:40:24.000Z</time></trkpt>
2018-01-18_22:40:54 GPS gpx: <trkpt lat="48.41" lon="10.2"><time>2018-01-18T21:40:54.000Z</time></trkpt>
2018-01-18_22:41:24 GPS gpx: <trkpt lat="48.41" lon="10.29"><time>2018-01-18T21:41:24.000Z</time></trkpt>
2018-01-18_22:41:55 GPS gpx: <trkpt lat="48.41" lon="10.29"><time>2018-01-18T21:41:54.000Z</time></trkpt>
2018-01-18_22:42:25 GPS gpx: <trkpt lat="" lon=""><time>2018-01-18T21:42:25.000Z</time></trkpt>
2018-01-18_22:42:55 GPS gpx: <trkpt lat="48.413" lon="10.29"><time>2018-01-18T21:42:55.000Z</time></trkpt>
2018-01-18_22:43:25 GPS gpx: <trkpt lat="48.411" lon="10.29"><time>2018-01-18T21:43:25.000Z</time></trkpt>
2018-01-18_22:44:01 GPS gpx: <trkpt lat="48.411" lon="10.29"><time>2018-01-18T21:44:01.000Z</time></trkpt>
2018-01-18_22:44:33 GPS gpx: <trkpt lat="48.411" lon="10.29"><time>2018-01-18T21:44:33.000Z</time></trkpt>

Okidoki.. Also soweit wie du :-)

Hallo Ihr nochmal,

ich habe es indes auch geschafft das Modul zum laufen zu bekommen und erhalte valide Daten in den Readings.
Was jedoch leider nicht so recht funktionieren will, ist das FileLog define Filelog_GPX FileLog ./log/Filelog_GPX-%Y-%U.log KastenGPS:(gpx).*DasLogFile wird leider nicht gefüllt.

Wenn ich jedoch beispielsweise das DOIF doif_gpx doif (["KastenGPS:lat"])((setreading KastenGPS gpx <trkpt lat="[KastenGPS:lat]" lon="[KastenGPS:lon]"><time>[KastenGPS:time_utc]</time></trkpt>))DOELSE
manuell über set doif_gpx cmd_1 auslöse wird einmalig ein Reading ins Logfile geschrieben, das war es dann aber auch.
attr. do always für das DOIF ist hinterlegt.


Vielleicht könnt Ihr mir nochmal mit eurem Wissen zur Seite stehen, dafür wär ich echt Dankbar :-)

Vielen Dank vorab.
beste Grüße Patrick

Offline UweUwe

  • Sr. Member
  • ****
  • Beiträge: 528
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #68 am: 28 Januar 2019, 07:18:38 »
Hallo,
ich hatte auch schon über einen Pi/FHEM im Wohnwagen nachgedacht. Wäre interessiert zu verstehen, welche Anwendungen ihr dort habt. Merci

Offline UweUwe

  • Sr. Member
  • ****
  • Beiträge: 528
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #69 am: 01 März 2019, 18:38:24 »
Hi, wollte nochmals nachfragen. Denke stark an einer GPS Anbindung für meinen Rasperry 3 nach.
Ich bin sicher, dass ich bei der Konfiguration etwas Unterstützung benötige. Ist da in den nächsten Tagen/Wochen jemand im Forum bereit und im Forum verfürgbar?  Welche GPS Modul soll man denn kaufen?


Offline StephanFHEM

  • Full Member
  • ***
  • Beiträge: 268
Antw:GPS-Daten in FHEM einlesen - gelöst
« Antwort #70 am: 04 September 2019, 18:51:37 »
ich hatte noch folgendes Problem: nach dem Reboot war die GPS-Verbindung bei mir immer wieder deaktiviert und ich musste sie manuell starten.
Hier die Lösung:

sudo nano /etc/default/gpsd
eingeben und folgende Daten in der Datei ändern/eintragen:

START_DAEMON="true"
GPSD_OPTIONS="-n"
DEVICES="/dev/ttyS0"
USBAUTO="false"
GPSD_SOCKET="/var/run/gpsd.sock"

danach ist GPS auch mit einem Reboot verfügbar

 

decade-submarginal