InSphere Logo

HomeTerraFlex - Mobile

Discussions and feedback specific to TerraFlex Mobile

Problem with GNSS functionality Messages in this topic - RSS

CJK
Posts: 10

6/15/2015
I keep getting the same error that reads the following
"TerraFlex has detected a problem relating to the installation of its GNSS
functionality.
TerraFlex will now close, please check the installation and reinstall if necessary."

I am running TerraFlex on a Mobile Demand T1600 with windows 8 operating system.
0 link
CJK
Posts: 10

6/15/2015
Also my tablet has a u-blox 7 GPS/GNSS Location Sensor
0 link
CJK
Posts: 10

6/15/2015
Here is what it says in the log file...

[2015-06-15 14:38:50Z] No connection could be made because the target machine actively refused it 127.0.0.1:504
[2015-06-15 14:38:50Z] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at GNSSServerProxy.Connection.Connect(IPAddress serverAddress, Int32 serverPort, Int32& errorCode)
[2015-06-15 14:38:51Z] No connection could be made because the target machine actively refused it 127.0.0.1:504
[2015-06-15 14:38:51Z] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at GNSSServerProxy.Connection.Connect(IPAddress serverAddress, Int32 serverPort, Int32& errorCode)
[2015-06-15 14:38:52Z] No connection could be made because the target machine actively refused it 127.0.0.1:504
[2015-06-15 14:38:52Z] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at GNSSServerProxy.Connection.Connect(IPAddress serverAddress, Int32 serverPort, Int32& errorCode)
[2015-06-15 14:38:53Z] No connection could be made because the target machine actively refused it 127.0.0.1:504
[2015-06-15 14:38:53Z] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at GNSSServerProxy.Connection.Connect(IPAddress serverAddress, Int32 serverPort, Int32& errorCode)
[2015-06-15 14:38:54Z] No connection could be made because the target machine actively refused it 127.0.0.1:504
[2015-06-15 14:38:54Z] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at GNSSServerProxy.Connection.Connect(IPAddress serverAddress, Int32 serverPort, Int32& errorCode)
0 link
Tom H
Administrator
Posts: 510

9/4/2015
Hi CJK

Although we support full Windows, we only explicitly support and recommend the Yuma 2 and Motion tablets as these are part of our test program and listed on our Technical specification > system requirements on the Terraflex web page.

The problem comes not from the Windows7/8 OS but from the inbuilt GPS /Camera sensors and the API's used to access these.
If they differ from our test devices then this can sometimes result in unpredicatble behviour like you are seeing.

We do offer the R1 or Pro 6 series GNSS receivers as an external option for tablets without GNSS capability or those just wanting to take advantage of professional grade Trimble GNSS equipment.

There's a good forum topic here: Supported Windows Desktop Devices which discussed this in more detail and even got some user contribution on tested windows platforms you may find useful.
If you want us to look into this in more detail then follow steps #2 & #3 from the forum topic Need Support? Here's what you should do and provide the dealer with as much information as you can. they will help resolve or escalate this via the correct channels


-
edited by Tom H on 9/4/2015
0 link
murphybeck
Posts: 1

7/15/2020
This exception message says you're trying to connect to the same host ( 127.0.0.1 ), while you're stating that your server is running on a different host. This 127.0.0.1 represents a 'loopback' . It allows the computer to communicate with itself via network protocol .

Dns.GetHostEntry(IPAddress.Loopback).HostName returns the host name of your machine. When you pass a host name to TcpClient , it will resolve it to one or more IP addresses using Dns.GetHostAddresses(hostName) . This includes the public and local IP addresses of your machine (e.g. 192.168.12.10), but not 127.0.0.1 (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.
0 link