DanW

MrPLC Member
  • Content count

    289
  • Joined

  • Last visited

Community Reputation

12 Good

1 Follower

About DanW

  • Rank
    instrument guy

Contact Methods

  • Website URL http://
  • ICQ 0

Profile Information

  • Gender Male
  • Location Midwest, USA
  • Country United States

Recent Profile Visitors

4397 profile views
  1. Help with PLC communication basics

    PLC’s basically run ’real-time’ and do not routinely store data unless specifically programmed to do so.   ’HMI software’ (several flavors listed in the post above this one) takes on the task of communicating with the PLC to get data from or to write data to the PLC. As someone noted, some PLC comm ports are for programming, others for data transfer; depends on app specifics.    It takes a ’driver’ to talk to a specific brand/model PLC.   OPC server (Windows software) are like a gateway; one side has a driver that talks to the  PLC, the other side exchanges the data from the PLC with an OPC client.   OPC clients are built into most HMI software packages nowadays.  The latest iteration of OPC, OPC UA, is friendly on the server-client side, listing PLC configured tags in the client, but the driver side still requires ’building a tag database’ for many devices.   I think the proposed task is incredibly ambitious.  I find the prospect of connecting to a variety of installed controllers daunting, to say the least.   It’s my opinion that the world of IIoT is largely an illusion with its implementations requiring significant programming effort. Best of luck in the endeavor.        
  2. Banner DXM 700 or other Model

    I have configured dozens of DX80 gateways over the years, mostly mapping AI’s to AO’s, DI’s to DO’s.  It was straight forward with the software. Then came the DXM100.   I bought one to try and after a day’s effort at trying to get the DXM onboard AO to ’follow’ the node radio AI, I gave up.   The factory, which used to have superb support, blew me off.  The DXM100 was supposed to offer cellular communications and my guess is that Banner packed a whole bunch of programming features into it that the DX80’s did not have, especially in light of their marketing push into the agriculture markets (irrigation, soil moisture).  In that move, they made a gateway that won’t handle a 4-20.   Good for them. I didn’t bother to compare the DXM100 vs the DXM700 and I couldn’t find an on-line comparison chart.   Out of curiosity, why does yourclient want a particular brand/model wireless gateway?
  3. FX5U Modbus communication

    Historically and generally, a spec for the maximum number of units on an RS-485 network is based on the RS-485 chip in the device, and the frequently followed by the disclaimer (as in embedded graphic in the first post above) like "the number of slaves varies depending on communication equipment type". There have been advances in the 3+ decades that RS=485 has been around, and there are 485 chips that can support 64 devices, but the entire network has to be those chips. The Modbus RTU protocol limit for addressable slaves is 247 slaves. 
  4. FX5U Modbus communication

    A couple comments about Modbus in general. 1.  Consider how often the master can communicate with each slave.  The query/reply time period for multiple slaves adds up.   If one slave is “down” then the master waits for that slave’s reply until the master “times out”.  Consider a relatively workable means of de-selecting slave(s) in the master’s polling list should a slave be out-of-service. 2.  Pushing the maximum number of nodes on a single network/bus frequently leads to communications issues where a simple work-around is to use an RS-485 isolator repeater half way down the bus so the 485 drivers do not have to drive all the loads, only half the total loads.  
  5. Rules for the Forum

    As a non-admin, but long time forum participant on multiple industrial controls fora, my observation is that attempts to produce better interaction by establishing ’rules’ is not going to go anywhere. The fact that many OP’s never return-post beyond their initial post is universal. The fact that most OP’s do not clearly articulate their problem and leave out critical information is universal. The fact that some people desperately ’want’ something that is not commercially available is universal.   The fact that there is continued belief in one-size-fits-all ’secret PID terms’ that somehow just are not published but will be revealed in a forum thread is and will be universal. The fact that about 70% of my replies come straight out of a publicly available (downloadable from the web) manual or spec sheet will not inhibit those who will not research their own topic themselves. Just like the saying, ”there are 10 kinds of people, those understand binary and those who don’t”, there are those who understand troubleshooting and those who don’t.   I fail to understand those who stay in a vocational field where the ability to troubleshoot is ubiquitous, but hey, it’s their problem. Make up all the rules you want to, but just like I don’t bother to read EULA’s, they won’t bother to read or pay attention to new rules. my 2 cents
  6. ProfiBus Noise

    Try this article by a SMAR engineer http://www.smar.com/en/technical-article/tips-for-trouble-shooting-on-the-profibus-dp Other technical articles not specific to Profibus on that site, too Or this one: https://procentec.com/about/news/2016/a-short-guide-to-addressing-emc-on-profibus/
  7. Analog Wiring NO NO

    OK.  I thought the distinction your were making was signal type (analog vs digital), not connector type (screw terminal vs terminal block).   Even so, given the number of times I've found the problem to be a whisker (that errant single strand) that makes it way out from under the screw terminal and touches where it shouldn't, I'd take a ferrule over bare stranded wire even if a fork is the correct and proper solution.   Have you encountered maintenance/performance-over-time issues with ferrules under screw terminals?n   Loosening?
  8. Analog Wiring NO NO

    I have the panel shop use twisted pair from the short run from field terminal blocks to the AI cards.  You can see the blk/clear pair below coming up from the top of the field terminal blocks. I haven't a clue why analog signals rate fork terminals and discretes rate ferrules.  What's the logic for that?
  9. Universal Analog Input Card

    It is not just a marketing term, there is a true functional difference between a dedicated function analog input card (4-20mA only) and a universal input card. An analog input card that takes a direct RTD or thermocouple input in addition to 0-10Vdc and 4-20mA has a lot of functionality that an analog input card that a 4-20mA-only card does not have.
  10. Honeywell HC900

      1.  Did the HMI ever communicate successfully with the CPU, or is this a commissioning/start-up problem? 2.  What HMI instruction faults the HC900 CPU? 3.  Which version firmware is the HC900 CPU running? 4.  Which hardware comm is for CPU/HMI comm?  Ethernet or RS-485? 5.  Is the HMI the Modbus Master, HC the Modbus slave? 6.  Are the CPU’s genuine Honeywell, or the fake, knock-off made in India models?
  11. Swimming Pool PLC

    If the pump doesn't pump water or the heater doesn't turn on and heat, then you need to determine whether the pump or heater is faulty or whether the control circuit that tells the pump to run or the heater to turn on can be the reason those things do not turn on and do what they're supposed to.  
  12. What performance factor is so critical that you'll travel 1/3 way around the world to find an alternative to what you're using now?  What does your current vendor suggest for upgraded performance? In answer to your question, I'm unaware of any standard of comparison.  But I can understand why - so much of PLC's performance is related to how it is programmed.  
  13. Rosemount Radar Level Transmitters

    > only when filling the water chamber. Is the radar positioned so it shoots through partially through the fill stream? Does the fill splash onto the antenna? Does the fill create turbulence like waves or agitation ?  Is the algorithm one designed for turbulence (which does not reflect the beam energy straight back up) ?
  14. Rosemount Radar Level Transmitters

    Water has a high dielectric so it should be a no-brainer application for radar, but non-contact radar is complex so the fault could be any of a dozens of reasons.    Diagnosis, remediation and root cause analysis require data.   Data for top mount, non-contact radar level includes stuff like - as complete a description of the fault/failure that can be compiled - accurate dimensional sketch or drawing or annotated photos of the installation with respect to geometry (slopes and angles) of the tank ceiling, nozzle, walls, interior structures and its fill/empty ports, radar mounting (angular aimers, flange/screw thread), antenna purge - written narrative on the process: temperature, pressure, atmosphere, mixing/agitation, -when, where and how it fills and empties, condition of the interior of the tank (steam?  dust?  rats?) - written record of the device model number, technology, beam angle, blanking zone distance for that device, range and accuracy - device's spec sheet and operating manual - written record of the existing setup (parameters, as found) - written report of device diagnostic log - screen shots of the echo profile at various levels - maintenance history - written notes on periodic inspections of the process side of the instrument - condition of the antenna for water, dust or material deposits - recorded trend charts of the level at a fairly high sample rate so that you can analyze the frequency, duration and time of the faults, to analyze whether the faults are event-related. A skilled (factory) technician with field experience for that manufacturer might be able to identify some probably causes and provide some remediation.  
  15. Fuel tank level automatic report

    see this thread covering the aspects of serial printing, then one adds the wireless on top.  It's a project. http://forums.mrplc.com/index.php?/topic/18102-slc-503-to-print-tickets/