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 x0NBxPis017525 for ; Wed, 23 Jan 2019 12:59:33 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gmH5o-0007TN-6E for rs_out_1@blacksheep.org; Wed, 23 Jan 2019 11:53:16 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gmH5n-0007TE-GN for rsgb_lf_group@blacksheep.org; Wed, 23 Jan 2019 11:53:15 +0000 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gmH5l-00046h-VK for rsgb_lf_group@blacksheep.org; Wed, 23 Jan 2019 11:53:14 +0000 Received: by mail-wm1-x32d.google.com with SMTP id f188so1647143wmf.5 for ; Wed, 23 Jan 2019 03:53:13 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:message-id:to:subject:in-reply-to:references :mime-version:content-transfer-encoding; bh=FJUvTx/yPFUjsWu7Chnuo5425Qew2fRvrvRapg4OnR4=; b=H+DrqZmPR/am4TwthxA+KgujYprhJpGogv7nl31ff21coWYFHspHsWJsAbTrGNByMx NBPskFhRxNI8rpJv4fO671d4PpzkRG6Z0Z9F7hbKf+3yszLQK2BJhj8+YohvTPRj1euI fFRxrzTcf/2eazj3UD3Y84Eeugcklvaxndhw4Bt5exemETcXP43kwVhPWWQDMs1eDSTN z4B6QGSETmWT3pVdwcRoCefbCxM1A+soFA+r4Ns9DuXTc0ORMY2u16i98g5xt9OMplFd ofBmjIa5SPr3VUKq9qLslgAZP5xgZtQpO1ws0NUEe3bLAhMuaqBctyo9A3AsVtpllicB FiwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=FJUvTx/yPFUjsWu7Chnuo5425Qew2fRvrvRapg4OnR4=; b=fzieiCLIpZD1YQEe6+U7vWII6Bx9qCRqi3zxuisoo8ORpSU85RdteSUCuVsSo/yKBU qm1ValTnSLHpXb356cSP61SJUvY/eCQPGpphHZi3kODB4VbDXB4y77nYbjSM29yclaN3 bzBatZ38kJjW97+9Fmm6p3H6Qs1d7a4jvCTMmlqVsL8ZtjSZH6fc+Fb+/9Gc1qQNE/no 8j3oo+9g/bAddI5rh3Z8UhaGqrF5K6jYk/qLn7axPcCDfZKh9DAqfKyV0FyY1TpX2VSN LalqgzN1356T+QFA0zSoVnxa2HU/01DizSbAPeAgW7/T9CiVqVDs4591VT7nnEgtsKdB /Apw== X-Gm-Message-State: AJcUukfBsvrLd7O4frSiZfVlJimR+josjop3vtVg8wSbqV3+q0GJnjXs RWFqTGCzExaeN/Z3xTjfSh67QoaO X-Google-Smtp-Source: ALg8bN7Fu+m4xyoXo3oMKxU324MWNkRGRADplDMExDUlZRO9SHq30Pn6alg+H+bTtlALC0LVQmQL2A== X-Received: by 2002:a7b:cb18:: with SMTP id u24mr2340591wmj.138.1548244392540; Wed, 23 Jan 2019 03:53:12 -0800 (PST) Received: from OfficeWin7.lan (82-70-254-222.dsl.in-addr.zen.co.uk. [82.70.254.222]) by smtp.gmail.com with ESMTPSA id t66sm20703190wme.15.2019.01.23.03.53.11 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 23 Jan 2019 03:53:11 -0800 (PST) Date: Wed, 23 Jan 2019 11:53:10 +0000 From: Chris Wilson X-Priority: 3 (Normal) Message-ID: <3310676628.20190123115310@gmail.com> To: Riccardo Zoli In-Reply-To: References: <1762043626.20190104174530@gmail.com> <9410247640.20190104185544@gmail.com> <1624085399.20190106110624@gmail.com> <1288743451.20190107142430@gmail.com> <5C336344.7010308@posteo.de> <1854885531.20190107171609@gmail.com> <78801854.20190122210433@gmail.com> MIME-Version: 1.0 X-Spam-Score: 0.0 (/) 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 @@CONTACT_ADDRESS@@ for details. Content preview: Hello Riccardo, Thanks, a good point I will be sure to bear in mind! I have further info so will copy paste what i posted to the "Time Nuts" forum in case it helps anyone else. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:32d listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dead.fets[at]gmail.com) 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 7ab87d4d3ea1d9dcb73a78e83fe4d608 Subject: Re: LF: Ublox 8 question Content-Type: text/plain; charset=utf-8 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id x0NBxPis017525 Hello Riccardo, Thanks, a good point I will be sure to bear in mind! I have further info so will copy paste what i posted to the "Time Nuts" forum in case it helps anyone else. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Ublox M8T is now fixed! For future reference this is what was wrong. CSG Shop ship various versions of this GPS module on a generic board, as far as I can tell, and reading between the lines. Some versions need this jumper across two of the three normally bare solder pads. Mine seems to have "escaped" with a Neo_M8T but the jumper soldered in place needed for NEO_M8L and NEO-M8U modules. Upon removing it the device now outputs under control of the current release of U-Centre software on TP0 and TP2. If anyone wants a photo of how the pads should be for the M8T I can take one and link here. But basically the M8T module should have NO jumpers across the three pads on the reverse side of the board...A learning experience I could have done without, but at least I have learnt something and it can now be cased up :) Thanks to all for help here and by direct e-mail. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Tuesday, January 22, 2019, 9:55:18 PM, you wrote: > Hi Chris, > I'm glad you fix it, thank you for the info. I'm curious, Chris: what the blob was shorting? > If you're planning on using 2nd timepulse, remember to decouple > TP2/SAFEBOOT pin with an adequate capacitor, without charge the > output in DC to GND (for example, directly with a resistive voltage > divider), otherwise the module (at power on) starts in safeboot mode and remains inoperative. > All the best > 73 de Riccardo IW4DXW -- Best regards, Chris mailto:dead.fets@gmail.com