One of the great things about Honeywell Trendview X-Series paperless recorders is that they communication via Ethernet. It’s great, because you can get data from your recorder anywhere on your plant network. But, since they’re network devices, you now have to understand how to troubleshoot network failures, and not just fix “regular” recorder issues.
Trendview recorders frequently connect to a local area network (LAN), so the recorded data can be easily transferred to the historian database portion of the recorder’s Trendserver Pro software (TSP). TrendServer pro uses a standard Internet file transfer protocol (FTP) to grab data from the recorder. And in a lot of cases, a software scheduler is used to grab data on a periodic basis.
So, you’re cranking along, and the recorder’s talking perfectly to the server, and then one day you see one of the dreaded FTP failure messages.
So now, what do you do to diagnose and solve the problem?
Start with the most basic steps:
- Is the recorder powered on? A recorder that has no power will not respond.
- Cycle the power to the recorder. Power brown-outs can affect operations. Try a manual FTP operation after the power cycle.
- Is the recorder still connected to the network?
Check to make sure the cable is connected to both the recorder AND the router/switch. (If you’re not sure, unplug it and push it back in till you hear it click.)
- Is the PC where Honeywell Trendview software is installed still connected to the network? Is the Ethernet cable plugged in? Repeat procedure from step #2 to be certain.
- Does the recorder think it still has a good network connection? Check the Diagnostic message log. On your recorder’s screen, click Messages > Messages > Diagnostics.
- Is FTP still enabled on the recorder?
On your recorder’s screen, follow the path here: Edit Setup > Comms > Comms Services > FTP. You’re looking for a green checkbox in Enabled.
- Can the recorder be browsed from Internet Explorer?
First, double-check that web browsing is enabled on your recorder: Menu > Setup > Edit > Comms > Comms Services > Web
Next, open your browser and type in the IP address of your recorder. You should see a screen like this:
Successfully browsing the recorder proves that the hardware layer wiring is good from the PC to the recorder. If the recorder cannot be browsed there are likely network issues.
- Can the recorder return a successful ping from the PC?
On your PC’s Start menu, go to Run, type CMD, and hit [Enter]. Then, type the word ping and the IP address of your recorder. If it works, you’ll see something like this.
If it can’t connect, the four “Reply” lines will be replaced with “Request Timed Out”.
Note: The network must allow the ICMP service that allows a ping to function. Windows 2008 servers turn ICMP off by default. (You may need your IT team to verify.
- Is the recorder lost in the Bermuda Triangle of ghost DHCP IP addresses?
If the recorder was configured to get its IP address from a DHCP server, what happened to the DHCP server? Was it unplugged? Did it give the recorder a different address than the TrendServer Pro is expecting? My recommendation is to always put a recorder on a static IP address.
- Is more than one TrendServer Pro package trying to talk to a recorder? Only one TSP ‘package’ and its FTP client are allowed to talk to a Trendview recorder. The recorder is not a PC and does not have the ‘power’ of a PC. The recorder does not support FTP client requests from more than one Trendserver Pro application at a time. All sorts of things get screwed up when two or more TSP FTP clients query a given recorder.
- Are FTP ports 20 and 21 open on the network path between the Trendserver PC and the recorder? IT people sometimes close down FTP ports on managed switches. It has been a rule of thumb in network security to isolate the office side from the manufacturing side, but since the Stuxnet virus revealed the vulnerabilities of manufacturing devices to viruses a couple years ago, many IT departments have implemented much more restrictive network policies, which sometimes include turning off ports that a Trendview recorder uses. The IT actions do not always get communicated to the people who are affected. Check it out.
Still no joy?
If all of these steps fail, you’ll probably want to call Honeywell for technical support. See the side of your recorder for the Technical Assistance Center (TAC) phone number. Have your recorder’s model and serial number ready (printed on a paper label inside the front door).
And if you want further resources, check out the Honeywell X-Series recorder user manual’s Communcations section.
What am I forgetting? Did I miss any steps? What else have you tried that fixed a network failure between your recorder and the network?
#1 by Bruce on January 20, 2017 - 10:47 pm
You refer in #10 to TSP “packages”. Does “packages” mean multiple single licenses?
#2 by Horacio Cedillo on February 1, 2016 - 4:03 pm
First of all thanks for all the good info. However i am still having issues with networking TSP with my recorder. i already try all of the above tips and i am still getting FAIL TRYING TO REQUEST LCF FILES. my problem stated when Honeywell did the new software upgrade. Before that i was able to communicate back and forth no problem. My assumption is that it might be something in the network. Also does been on domain vs. LAN make a difference with importing data. Perhaps the upgraded software has more security options that i might need to enable. Any suggestion will be greatly appreciated it.
#3 by danstips on February 11, 2016 - 3:20 pm
Honeywell support is really the source for a resolution. However, if there is no GR series recorder involved (the recorders are X series recorders) then going back to X series V6 software is likely to get your FTP running again.