hotwires

Members
  • Content count

    71
  • Joined

  • Last visited

  • Days Won

    6

hotwires last won the day on April 23

hotwires had the most liked content!

Community Reputation

13 Good

About hotwires

  • Rank
    Advanced Member
  • Birthday 03/29/1981

Profile Information

  • Gender
    Male
  • Interests
    land mobile radio, amateur radio, flying single engine aircraft

Recent Profile Visitors

764 profile views
  1. Carb, Here is a modified snippet from some working code I used to control the water level in a tank. It's the simplest form of an OUTPUT commanded by START and STOP setpoints. Might help to scale PSI to include tenths of PSI, if IF you had a 0-100 PSI transducer then linearize to 0- 1000. 1000 meaning 100.0 PSI. Then you can tweak your setpoints down to a tenth of a PSI. Happy composing. P.S. Obviously you would want to put an enable/disable contact in between the set/reset bit and the output coil. MB1 MB2 O0 AUTO bit S/R bit driven by compare blocks Control valve -----| |---------------------| |---------------------------------------------------( )-------------- HotwireS
  2. A hysteresis. I use start and stop setpoints for filling liquid levels in tanks (and alarms). open/close valve setpoints that are very close will result in chatter. PSI value reached could be the valve off setpoint and a value some PSI lower could be the fill valve open setpoint. Depends on how tight of a pressure value you are needing to maintain. If you have to keep a tight value at all times..... not sure.... a PID control? You generally don't want the valve open and close to trigger on the same setpoint. Heavy filtering on the pressure transducer integer would dampen the oscillation potential some. Just a burst of thoughts.
  3. R&D: Will the future bring a drag and drop email body element that inserts an ASCII string variable? I've found a work around for what I'm wanting to accomplish via binary text variable and lists of text variable. What I had in my was using store blocks in ladder to load an ASCII string with various messages then IF triggered email would convey the ASCII string message in body. Just a thought. Not sure if anyone else has looked for this as a feature. I guess I got the notion from email construct strategy I once used in Visilogic using Stores, Strings, and string to vector block (admittedly more complicated).
  4. Dear Community, Is it possible to have a bit trigger a message box? I have some ladder logic that determines if high and low user definable setpoints are equal to each other or inverse to each other. undesirable setpoint conditions make bit named SP> and SP= go true. Right now I have and indexed HMI text element that shows: legal entries, sp = illegal, sp> illegal, both illegal. I don't really want to trigger an alarm (though i could). The message box would be a nice way to signal operator of an illegal entry. I can't use legal entry ranges on numeric elements because legality is conditional to other setpoints. Thanks -dB
  5. I've been told USB on Unistream is a virtualized ethernet adaptor. I found that AVAST firewall was blocking USB connectivity but not ethernet when using my laptop on UniStream15.6. Turning third party firewall off allowed USB connection to work. This was on a laptop, Win 7 pro 64 bit. My discovery may not have any relevance to the issues being encountered o this thread but is an easy thing to try. I've also seen AVG FREE interfere with serial communucations to CAC card readers. Spent hours fidling with drivers to only find it's an AV problem.
  6. Mike, I've been told by UniTeam (Isreal) that a Unilogic release is coming soon with a (more) complete help section. You can always call tech support, that's what I did on my first Unistream project. It was a SCADA system with 4 RTU's; MODBUS was pivotal. Dan Logee at UniT east coast was able to answer/resolve all my questions/issues.
  7. Ausman's suggestion for using an interrupt for a precise 2.5 mS time base is an excellent idea. The whole thing was new to me. The Vision help section was well versed on the topic and answered my earlier question as to whether or not the subR required a ladder call. -hW Cara, The contraindication (let's not use the word bug) in visilogic is that in Ausman's "pumpexample2.vlp" the project optimizer shows a warning that a routine is not called in ladder. Fundamentally it's output is true, however inerrupts are an exception and do not require a ladder call. It appears the project optimizers code is not self aware of this. It's just evaluating subR's and their associated ladder calls. the program loads and functions fine. Thanks all for the clarification on what defines enhanced Vision hardware. -hW
  8. Program works in SM43. I'm NOT calling the interrupt subroutine. I'm just saying that the project optimizer is not "self aware" that "_interrupt" don't need to be called. No harm done. It could be a source of confision for someone who always runs the project optimizer and follow it's advice.
  9. It's doesn't prevent download, just states that the subroutine is not called, optimizer logic is not recognizing that the _interrupt is "self called". Program works. I added a comparator to zeroize stored count if 2.5mS counter exceeds 24,000 (less than 1 GPM). The update time and flow rate are directly proportional. cruises along nicely near 60 GPM. 2 GPM update time 30 sec, 1 GPM: 60 sec. that's the laws mathematics at work. Works better than counting pulses for a 60 sec interval for every sample. Thanks All
  10. correct, no comilper error. Just project optimizer. Hope to try it tonight live in the OPLC.
  11. Aus, Thank you for the .vlp, I'll try it in my "R&D" Samba 4.3" This may be a silly question: Does the subroutine: "_Interrupt 2.5 mS" have to be called in the main routine? Or does the _ make it run irregardless? The project optimizer flags it however after reading the help section it appears the name makes it run without a call. Looks like the theoretical resolution would be 0.15 GPM That will be more than sufficient! Is an SM43-J considered an enhanced Vision on NOT? Love the simplicity of your program!!! I'll be honest, my conceptual approach was a bit more complicated. Simple is good. Thanks, HW
  12. The pump runs 24/7. So demand bit wouldn't be a useful zero signaling bit. Zero flow would only occur during power failure (which could be detected) or: pump failure, pump sucking air, discharge side occlusion, flow meter failure, unauthorized valve closure between disharge side and meter input flange. I'm sure there are a few possible conditions I've missed. My approach for testing logic is to present every possible set of conditions and then observe results, then ask: Is this what I wanted to happened?
  13. i use ptc for totalizer counters. I'm new to the pulse to gpm conversion with (relatively) real time updates. I took the freq counter logical approach but quickly found anything less than a 60 sec sample wasn't gonna be accurate down to the gallon. I seen in one of the examples where they use an output on plc to simulate pulses. I'll have to try that out. don't think my analog function generator will go low enough, 1 Hz would be 60 gpm. i've got a plc on my bench to play with but not the meter. i'm pre planning this project, no trigger pull on it yet. anytime I learn something new it's not time wasted. all prior flow meters I've worked with have had a 4-20mA gpm scaled output and programmable pulse:gallon ratio (and pulse duration).
  14. thinking about how it will need to handle a zero flow condition. the count would just keep running depending on where the disc stops and in what state. that's where limit setpoints come in. not exactly simple, but as the saying goes: "if it was easy anyone could do it!"
  15. A Tektronix 422, how ever did you know! Very compact scope back in it's day. Still works great. Never used interrupts on a PLC, kudos for the inspiration! I'll have to go spend some time in a pumphouse to examine the flowmeter, I don't have it's twin on my office desk Just did a walk thru a few days ago to see what all client had to work with and wanted to see in an automation solution