Cannot connect to M1 or C127

[JakeL]

Hi Guys,

Wanted to see if you could offer some things to try.

Recently took delivery of my car which has an M150, PDM15 and C127, set up by GSpeed down in Texas. Everything seems to be configured well by them, and they had no issues communicating with their laptop whilst finishing configuration and loading initial engine calibrations etc.

I cannot seem to get connected to any of the devices with my laptop, wondering if you can offer suggestions on what to try.

Thus far, I have not been able to see either of the M150 or the C127 when plugging in the ethernet cable.

M1 Tune and C127 dash manager are both installed. Ethernet port verified working on the laptop, and have tried two cables with similar results. IPv4 and IPv6 installed, normal windows networking. Laptop is ~2 year old Dell laptop, no antivirus installed, running recent Windows 10.

Below is an example log from the Motec "Discovery" service. First I plugged in to the m150 port, then tried the C127 port to see if the messages were any different.

Suggestions on what to try?

Thank you!

-Jake


Wed Mar 31 22:50:16 2021: Discovery Log Started (C:\Users\jlatham\AppData\Local\Temp\MoTeC.Discovery310321225016.log)
Wed Mar 31 22:50:16 2021: Joining mDNS multicast group on interface Loopback Pseudo-Interface 1.IPv6 with address ::1.
Wed Mar 31 22:50:16 2021: New relevant interface Loopback Pseudo-Interface 1.IPv6 for mDNS.
Wed Mar 31 22:50:16 2021: Joining mDNS multicast group on interface Loopback Pseudo-Interface 1.IPv4 with address 127.0.0.1.
Wed Mar 31 22:50:16 2021: New relevant interface Loopback Pseudo-Interface 1.IPv4 for mDNS.
Wed Mar 31 22:50:16 2021: Joining mDNS multicast group on interface Wi-Fi.IPv6 with address fe80::d05b:3386:39ec:68a9.
Wed Mar 31 22:50:16 2021: New relevant interface Wi-Fi.IPv6 for mDNS.
Wed Mar 31 22:50:16 2021: Joining mDNS multicast group on interface Wi-Fi.IPv4 with address 192.168.15.45.
Wed Mar 31 22:50:16 2021: New relevant interface Wi-Fi.IPv4 for mDNS.
Wed Mar 31 22:50:16 2021: Registering new address record for ::1 on Loopback Pseudo-Interface 1.*.
Wed Mar 31 22:50:16 2021: Registering new address record for 127.0.0.1 on Loopback Pseudo-Interface 1.IPv4.
Wed Mar 31 22:50:16 2021: Registering new address record for fe80::d05b:3386:39ec:68a9 on Wi-Fi.*.
Wed Mar 31 22:50:16 2021: Registering new address record for 192.168.15.45 on Wi-Fi.IPv4.
Wed Mar 31 22:50:16 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:17 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:17 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:21 2021: Joining mDNS multicast group on interface Ethernet.IPv6 with address fe80::1cc1:49dd:1722:5b3a.
Wed Mar 31 22:50:21 2021: New relevant interface Ethernet.IPv6 for mDNS.
Wed Mar 31 22:50:21 2021: Joining mDNS multicast group on interface Ethernet.IPv4 with address 169.254.91.58.
Wed Mar 31 22:50:22 2021: New relevant interface Ethernet.IPv4 for mDNS.
Wed Mar 31 22:50:22 2021: Registering new address record for fe80::1cc1:49dd:1722:5b3a on Ethernet.*.
Wed Mar 31 22:50:22 2021: Registering new address record for 169.254.91.58 on Ethernet.IPv4.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::1cc1:49dd:1722:5b3a ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN A 169.254.91.58 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received response from host fe80::1cc1:49dd:1722:5b3a with invalid TTL 1 on interface 'Ethernet.1'.
Wed Mar 31 22:50:23 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:23 2021: Received response from host fe80::1cc1:49dd:1722:5b3a with invalid TTL 1 on interface 'Ethernet.1'.
Wed Mar 31 22:50:23 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::d05b:3386:39ec:68a9 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN A 192.168.15.45 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::1cc1:49dd:1722:5b3a ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN A 169.254.91.58 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::d05b:3386:39ec:68a9 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:23 2021: Received record with bad TTL [JAKE2.local IN A 192.168.15.45 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received response from host fe80::1cc1:49dd:1722:5b3a with invalid TTL 1 on interface 'Ethernet.1'.
Wed Mar 31 22:50:25 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::1cc1:49dd:1722:5b3a ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN A 169.254.91.58 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::d05b:3386:39ec:68a9 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN A 192.168.15.45 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::1cc1:49dd:1722:5b3a ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN A 169.254.91.58 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received response from host fe80::1cc1:49dd:1722:5b3a with invalid TTL 1 on interface 'Ethernet.1'.
Wed Mar 31 22:50:25 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN AAAA fe80::d05b:3386:39ec:68a9 ; ttl=60]. Refreshing.
Wed Mar 31 22:50:25 2021: Received record with bad TTL [JAKE2.local IN A 192.168.15.45 ; ttl=60]. Refreshing.
Wed Mar 31 22:51:02 2021: Interface Ethernet.IPv6 no longer relevant for mDNS.
Wed Mar 31 22:51:02 2021: Leaving mDNS multicast group on interface Ethernet.IPv6 with address fe80::1cc1:49dd:1722:5b3a.
Wed Mar 31 22:51:02 2021: Interface Ethernet.IPv4 no longer relevant for mDNS.
Wed Mar 31 22:51:02 2021: Leaving mDNS multicast group on interface Ethernet.IPv4 with address 169.254.91.58.
Wed Mar 31 22:51:02 2021: Withdrawing address record for fe80::1cc1:49dd:1722:5b3a on Ethernet.
Wed Mar 31 22:51:02 2021: Withdrawing address record for 169.254.91.58 on Ethernet.
Wed Mar 31 22:51:02 2021: Received response from host fe80::d05b:3386:39ec:68a9 with invalid TTL 1 on interface 'Wi-Fi.1'.

[JakeL]

For what it's worth, was able to solve this by completely removing all Motec software and reinstalling from the web.

No idea why it worked...but it did

-J

[Stephen Dean]

Hi Jake,

There has been a Windows update recently that enables a mDNS function in Windows, this breaks the mDNS function that MoTeC Discovery uses so communication is lost with any device that uses MoTeC Discovery (any Ethernet comms) until the mDNS function is reenabled. This can usually be resolved by running the installer and selecting the Repair option. This will reinstall the mDNS function and re enable communications. We have not found any issues with other Windows functions from having the mDNS function provider changed.