ThingWorx ATrack AX-7, Руководство по установке

Страница: 11 / 12

ATrack AX-7 Protocol Adapter SDK Setup Guide
Copyright © 2015 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved.
9
Troubleshooting
Problem Solution(s)
1 Protocol Adapter is reporting
this debug message:
[ClientHandler: 1299411443]
Client has been idle, sending
websocket ping... This is a normal communication when the Protocol Adapter
is receiving no data from the ATrack device.
1. Verify that config.json is configured with the correct
Thingworx application key and it is set to receive
messages on the desired host port and IP address.
2. Check the configuration and reset the device by sending
the configuration AT$ commands mentioned earlier in
this guide. Wait for the device to reboot after changing
the server connection information. Make sure that the
GPRS server hostname is set to the “public” IP address of
the Computer/AWS server running the protocol adapter
SDK.
3. Disable the firewall setting for TCP port 5000 (or the port
you are using for your connection, as defined in
config.json ). This is the socket port the Protocol Adapter
SDK will listen on for incoming ATrack AX7 messages.
4. Ensure that the ATrack AX7 device has GSM signal (check
the status LED on the front).
5.
Check the AT$TRAC command once again by sending
“AT$TRAC=?” on the terminal via Serial connection. If you
do not get 1,10,,,,,2 as the response, then send the
AT$TRAC command again to set it. Ensure that the device
is disabled for acknowledgment and the periodic report
time is set to 10 seconds.
2 The ConnectionServer.java
cannot connect to the
ThingWorx platform. 1. Verify that the parameters in config.json are correct;
especially the Application Key, the server address, and
the connection port.
2. Verify that config.json is in the root directory of the
ATrack SDK.
3. Verify that no firewalls are blocking your connection to
the Platform.
4.
Verify that the port chosen for your application is not
closed on your server.