Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x0VFTPDL004918 for ; Thu, 31 Jan 2019 16:29:32 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gpEBQ-0003d2-Ch for rs_out_1@blacksheep.org; Thu, 31 Jan 2019 15:23:16 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gpEBN-0003ct-BZ for rsgb_lf_group@blacksheep.org; Thu, 31 Jan 2019 15:23:13 +0000 Received: from mout02.posteo.de ([185.67.36.66]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gpEBL-0005EI-Df for rsgb_lf_group@blacksheep.org; Thu, 31 Jan 2019 15:23:12 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 601352400E5 for ; Thu, 31 Jan 2019 16:23:10 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1548948190; bh=Z+DU8tVnaeAI2HChyhAy5WcFISS2M2hzofkKp6nT8EA=; h=Date:From:To:Subject:From; b=DR6EnqsXp3SkqHPwd+iDKkdSta7+QOCDnEqPh8GmKrlp8L0OnhY3pfGgOTkDfSOFH 4emqDeamXKktC/DNWKSMVw9fi2CWFlvMsCRFCwutRiQ5kmR3x4zu2Oig/yULDvfhvc mLsNIXrc6V0/V3+O5nLHgggCVB/YyGoZZ+FvpVUzztQOVMiDPPYpc35fhafVsEz0Ft mSivzihiPi4+niObM/Nmyq331jQATPbJJv5a+RaPwJ8/055AzEvCvhwCC0+xibu9JK G4VOCQA4HJLV+hBdM9OmCHDC7wZdXFuQB4u7EkJ1VB+Tn8i4uOcFUnSsismalk1ZtG M85dboXLZ508g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 43r3s84dzWz9rxp for ; Thu, 31 Jan 2019 16:23:08 +0100 (CET) Message-ID: <5C5312CF.7010000@posteo.de> Date: Thu, 31 Jan 2019 16:22:55 +0100 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <1UTCZw4Jzr.F7dZYpniNns@optiplex980-pc> <5C52F3F6.5080906@posteo.de> In-Reply-To: <5C52F3F6.5080906@posteo.de> X-Spam-Score: -2.3 (--) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello dear GPS experts, I'm still struggling with my NEO-7M and vlfrx-tools. Instead of the standard ucenter software i use my Raspi and vlfrx-tools to configure the module. Using the vtubx tool, i can configure the time pulse as expected, for example *vtubx -P 1e-1 -S /dev/ttyAMA0* leads to a blinking LED with 100 ms on-time. So the communication works fine. However,with *vtubx -F 10 -S /dev/ttyAMA0* or *vtubx -F 1,10e1 -vv -S /dev/ttyAMA0* the LED gets and stays dark, i.e. no frequency output. Now i tried to use the old u-center software and there i can configure the TP output as expected to a frequency of say 20 Hz and there the LED is indeed blinking. Does someone have tried to use vtubx and have some experience? What am i doing wrong? 73, Stefan --------------070209040001020904060101 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello dear GPS experts,

I'm still struggling with my NEO-7M and vlfrx-tools. Instead of the standard ucenter software i use my Raspi and vlfrx-tools to configure the module. Using the vtubx tool, i can configure the time pulse as expected, for example
vtubx -P 1e-1 -S /dev/ttyAMA0
leads to a blinking LED with 100 ms on-time. So the communication works fine.
However,with
vtubx -F 10 -S /dev/ttyAMA0 or vtubx -F 1,10e1 -vv -S /dev/ttyAMA0
the LED gets and stays dark, i.e. no frequency output.

Now i tried to use the old u-center software and there i can configure the TP output as expected to a frequency of say 20 Hz and there the LED is indeed blinking.

Does someone have tried to use vtubx and have some experience? What am i doing wrong?

73, Stefan


--------------070209040001020904060101--