I have been in touch with a customer that installed our first generation SMU over 2.5 years ago. Read the email threads and see for yourself what steps constitute a typical diagnostic and troubleshooting procedure for a simple RS-485 network with multiple sensors. I will have a final comment at the end of this post, but this case history actually speaks for itself. Procedures outlined in this post generally apply to both SiloPatrol and Flexar with very minor exceptions, the most significant being that the Flexar guided wave radar line does not have a built in network termination resistor on the RS-485 module which changes one of the outlined procedures, unless the installer added one during installation. These threads have been slightly edited for clarity and condensation of text.
Greg
CUSTOMER SUPPORT INQUIRY:
"Greg,
Our SiloTrack Server has been running great for 2.5 years, and then suddenly, Com errors appeared on all 4 SMU's.
I went up on top of the silos and verified that the SMU's have power, and that I can run them in Manual mode, using the push buttons on the SMU circuit board, and it all works just fine.
Then I purchased a new RS 485 Serial Card, set the jumpers just like the old card, and installed it into the SiloTrack Server -- but it won't see the SMU's on the network.
I suspected wiring at one point, so I disconnected all devices except for 1 of the SMU's and the SiloTrack Server Computer, and even this did not work to re-establish communications.
My next step will be to get 100-foot of new wire, and wire the Server to one of the SMU's directly, bypassing the old wiring. But I am doubtful that even this will work, because I suspect that something may be wrong with all 4 silo SMU's.
My questions:
1.Is there a way that I can test communications on each SMU individually, to verify that their COMS are working independently of the SiloTrack Server, and network ?
2.Is there a way that I can test the RS-485 board from SeaLevel to verify it is working?
Thanks,
Valued Customer"
TECH SUPPORT RESPONSE
"Dear Valued Customer,
The fact that you are getting a COM error indicates to me that the PC is seeing the RS-485 card as a valid com port. This does not mean, however, that it is indeed fully functional but the likelihood is very high.
Usually when someone gives me a similar report as you have, it is a simple matter that someone killed the power circuit breakers to the SMU's. If not, cycle the power to the SMU's and you will effectively reset the sensors without climbing.
The next thing I would do is power off all of the SMU sensors and remove the DB9 connector for the RS-485 bus from the PC. With an ohm meter, measure the resistance between pins 1 and 2. If your termination switches are correctly set, you should see around 100 ohms. If you measure a very high resistance or infinity, either no termination resistor is on or you have an open circuit on your communication line. If you measure a low resistance, you likely have a short somewhere or have too many termination resistors enabled.
Now, on the PC side, go to Control Panel, Device Manager, Hardware and check the PCI card entry for errors. Verify that the virtual com ports assigned to the RS-485 adapter are indeed the same as you have configured in SiloTrack under CONFIG, Networks of the Task bar. If you restore the jumper settings to the Sealevel factory default, you can run the WinSSD diagnostic on both serial ports. Sealevel factory settings have the card running in RS-232 mode. The instructions for this test are contained on the Sealevel Installation CD. First, a loop-back connector must be constructed by obtaining a DB9F connector and shunting (jumper) pins (1 & 4) and (2 & 3). The BERT test contained on the Sealevel CD verifies two way communications. Since you have tried two separate RS-485 cards, if the test does not work, I would un-install the sealevel software, power off the PC, remove the Sealevel Adapter card from the PC, power up the PC, reinstall the Sealevel drivers, power down, re-install the sealevel card in a different PCI slot (Don't forget to return the jumpers to RS-485 if the test passes), and repeat the test.
The last test I would do before pulling new wire would be to remove one electronic module and the power connector from one of the sensors. Construct a new short cable with a DB-9F connector with the wires connected to pins 1 & 2. Do not connect the shield to pin 5. Secure a line cord with plug to the power connector. Connect the DB9 to one of the serial RS-485 ports and apply AC power to the module taking care not to allow any shorts or allow yourself to touch the modure anywhere while the module is powered so you do not get shocked. Prior to applying AC power, be certain that the address switch on the module is a valid setting for one of the silo icons configured for that particular port. If the ICON on the PC screen says READY, you indeed have a wiring problem. If this does not happen, send us the Module for evaluation.
Keep me advised of your findings.
Thanks,
Greg DeRudder,
Technical Sales Support Manager"
FURTHER CUSTOMER COMMENTS REGARDING PROBLEM:
"Greg,
Long story short -- a "Cold Solder Joint" was found in the DB9 cable going into the SeaLevel 7201 RS-485 card.
When IT came out to swap the monitor, they must have tugged on the SiloTrack 3-wire cable, and loosened one of the soldered wires.
We re-soldered it, and now the network is communicating with the SMU's.
Thanks for the help,
Valued Customer"
TECH SUPPORT COMMENTS:
"Final Comments
Depending upon the quality and type of solder you use, connecting your communications cable to the DB9F connector can range from “A piece of cake” to a “Pain in the @$$.” A good clean tin-lead Sn63 solder with a sufficient quantity of resin flux will leave a very smooth and very shiny solder joint that is easy to inspect. Solder that is not pure (the really cheap stuff) will harden as it cools below the melting point sometimes leaving a dull pitted looking appearance. (see photo) After stripping the insulation to the correct length, I prefer to tin my RS-485 wires before inserting them into the DB9F for final soldering. This step greatly reduces the risk of having a poorly soldered joint and it is well worth the effort. If you typically apply additional flux to your joints (I’ll leave this alone at this point, but the quotation “I did not inhale” does come to mind), you should also have the appropriate solvent to remove and residual flux residue. This results in a much higher quality of soldered joint that is easily inspected.Also, watch the temperature of your soldering iron. You don't want it to get too hot or you will have other issues to deal with. Your iron should be just hot enough to allow a smooth yet gentle reflow of the solder between the two pieces being joined. If the solder and flux "spits" at you, it is probably too hot.
What about RoHS you ask? We will try to cover that subject in a future post once compliant solders and effective fluxes become more readily available and are more commonly used."