Posts Tagged troubleshooting
When their Remote View option is turned on, Trendview paperless recorders display recorder screens in Internet Explorer as shown here:
Getting a printout was not as easy as using file > print, because the technology uses Active-X components in Windows, so the result is a blank screen; something to do with Active X and printing.
Recently, we’ve run into a few radar level applications that had some startup challenges, mostly because the person installing the transmitter didn’t consider how radar wave transmission would affect the level transmitter’s performance.
One trick to any installation is to reduce the number of obstructions encountered by the transmitter. But you have to take into consideration that radar waves don’t transmit in a concentric circle around the transmitter. And this can create a problem of its own.
One of the strengths of Honeywell’s X-series paperless recorders is password security. You can configure it to keep operators from making configuration changes, and it’s a necessary part of being able to view a recorder’s data using a web browser.
One of the weaknesses of Honeywell’s X-series paperless recorders is password security. And by that, I don’t mean it’s bad. I just mean it can cause problems if a user fails to enter their username and password right, and ends up locked out of the recorder.
So I’m guessing if you searched for the backdoor password, you’re in that situation. You’re locked out of your recorder and can’t figure out how to get back in.
First, I apologize for luring you into reading this. There is NO backdoor password for an X-series recorder. But don’t give up hope: There is an answer.
(What’s a back door? Watch and learn.)
Hopefully, there’s a user at your location with administrator level access, who can reset a locked-out user. But if that’s not the case, what do you do when everyone is locked out of an X-series recorder?
Sometimes I get lazy and don’t follow my own rules. (Rule #1: Test EVERYTHING!) That one oversight cost me three hours when I could have solved a problem in three minutes. Maybe you can learn from my mistake.
The goof happened at a customer site last week. He had a Siemens MultiRanger 100 ultrasonic level transceiver, and was trying to connect to it via Modbus using Siemens SIMATIC PDM software on his Windows XP laptop PC.
Early on, the Lesman salesman who worked with this customer had connected to the MultiRanger from his laptop using PDM, but only one upload worked successfully. The rest failed. The salesman had lent the customer his “known good” serial cable that he’d used for the successful upload.
Siemens tech support had offered the customer several “Try This/Try That” suggestions, but came to the conclusion that a software program on the customers’ laptop had locked up the laptop’s internal serial port so PDM couldn’t access it. The customer’s IT guy ran a port scan program, but could find on application or service running on COM1. Plus, they’d used the serial port successfully for other connections.
I couldn’t do anything more for the customer over the phone, so I grabbed my serial comms toolkit and headed to the site myself.