Jump to content


UniStream & UniLogic Beta
  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Damian

  1. You've got a positive transitional (functionally the same as AB ONS instruction) in the first network

    Hi Joe,

    A transition contact is executed only based on the state of the memory location referenced by that contact.

    The ONS in AB instead executes based on the RLO condition of the entire branch preceding the ONS intruction.

    They can often be used to achieve the same result, but they really are fundamentally different.

    Actually would be a good wish list item for NG. An ONS type instruction. I also wish AB would add the P and N contacts as well.

    Don't want to be nit-picky but I have seen this trip up many in the past that have had to transition between PLCs that do it one way and those that do it the other.


    Also in support of what joe mentions in line item #4, it is a good idea to have your screen calls triggered by transition contacts. Otherwise you run the risk of having strange phenoma happen such as re-invoking the same screen consecutively. It might be helpful to have a separate subroutine (maybe name it "HMI") that is a collection of all your screen calls in one spot.

    There are definitely a lot of other issues as well. I would recommend breaking this up into smaller chunks and get each of those chunks working properly on their own before trying to tie it all together.


  2. Assuming your valve is normally closed (Output ON = Valve Open)

    If your switches are normally open (input is ON when full) then put three normally closed contacts of your inputs in parallel with your valve output. The pump will remain on until all three of them are open.

    If your switches are normally closed (input is OFF when full) then put three normally open contacts of your inputs in parallel with your valve output.

    This is the most crude method, however it would be wise to implement a timer in here as well to make sure you give the system some hysteresis.

  3. First thing is to definitely make certain you have the most recent OS in the V350. There was a bug in the DF1 block that caused abnormal behavior depending on what data and addresses were used.

    Second thing is a warning that the document you are referencing does have a few errors. It is definitely useful, but there are some inaccuracies. Unfortunately, I failed to properly take note of these back when I was doing this myself so I am a bit rusty on those details.

    There were also some address ranges that quite simply could not be accessed for whatever reason I was never able to figure out. If I get time I'll give it a try again a bit later.

    Good Luck

  4. Create a new "scanner" and have it point to the block of ML's you wish to access.

    For the data address, use 28672. Set length to however many ML's you want, and then select Holding registers.

    It is common that using a function call to the holding registers implies the 40001 offset, so you likely just need to give the sub-offset. Otherwise there is no point in selecting "holding registers" since the 40001 and up range is the holding registers by definition.

    Now when you create your variable, that offset will be in reference to the block your scanner is reading.

  5. I have verified everything you mentioned. The PID status is 12. When I try using the FB auto-tune, PID status is 1, but again CV never changes.

    I have posted the program along with the output from the PID server log that I used to try auto tuning.

    Thank You

    I think the answer to your problem may be simply that you have tied the PID config block directly to the rail and are executing a re-config every scan.

    Use and SB2 contact between the config block and the rail and let us know how you make out.

  6. Andrey,

    It does not work because you changed DW 1, and logic say that if you want to compare MI 1 to Zero if DW 1 is Zero - it is not Zero already.

    Attached is other example which works in accordance to your logic rules.

    I agree that the series connection isn't working because DW1 gets modified while the network is being processed.

    I completely DISAGREE that it should be evaluating the ladder like this.

    Each instruction in a rung should only be executed ONCE.

    This means that once the comparator is evaluated, it should retain the state of that decision until the rung has been completely finished executing.

    What is really happening is the rung is going back and re-evaluating the comparator for subsequent conditions.

    Looking at the STL generated for the rung, you can see that Visilogic is not properly translating the ladder as written.

    It is clearly evaluating the first comparator instruction TWICE.

    It should not be.

    This is not in line with any other translator that I have ever seen. It is completely unintutitive, and breaks from the "left to right" execution convention that everyone expects.

  7. I have a V570 with a V200-19-ET1 board connected. I configured the IP address and can PING the controller and get a response. I configured the IP Address in the Connections->Favorites menu, setup the TCP/IP Project settings. If I go to the Connections --> Communications & OS menu and select the TCP/IP connection type I cannot get comms to work. Any Ideas what I'm missing?

    You need to know the "name" of the unit and what port you are using.

    If your sockets parameters remain default, your port number can be 20256

    As far as the name of the unit, you need to use a NAME function block in your program and assign one yourself.

    Another option is that the default name will be the serial # of the unit. You can view this entering "info mode"

  8. Based on your original diagram, as a result of the miswiring is it very plausible your sensor outputs were damaged. Pay close attention to Simons & WalkerOKs diagram, as it shows that for an NPN sensor you need to bring +24v to the input commons.

    Also, keep in mind the real difference between and NPN and PNP sensor. A common misconception is that with NPN you get 0v for ON and +V for OFF, and for PNP you get +24V for ON and 0V for off. In reality, for a PNP sensor you get +V for ON and "Open Connection" for OFF. By the same token for an NPN sensor you get 0V for ON and "Open Connection" for OFF. In this fashion, you need to be careful how you measure the output of an NPN sensor in order to truly understand its state. You will get different readings based on whether your sensors signal wire is unhooked or is still connected to the input. This is because the input device is normally either "pulling up" or "pulling down" the voltage across internal resistors. In short, the sensor provides the ON voltage state, and the input provides the OFF voltage state.

    Just to make certain you have your inputs "pulled up" correctly, touch 0V to a spare input and verify that you see the state of that input change.

  9. Is there a way to add a couple of more displays than 60 such as display only a relevant screen set at one time switch off the other irrelevant sets at that time so that the number of displays which are active are only 60 displays at one time?

    Depending on what exactly it is you are doing, you might be able to use indirect addressing and cut way down on the number of screens.

    But like Joe says, if you have that much going on why not jump to the V120? The capability and software are vastly better.

  10. ----------------------------------------------

    Thanks for your help D, I made the sensor and solenoid wire changes as you pointed out and I reattached the wire schematic for your review.

    The sensors now show they are at a closed or open state ~4 or 20 volts. The weird thing is when a target is sensed the LED lights up but no change in voltage, the voltage starts at 4 VDC and does not jump to 20 VDC.

    Secondly, the solenoids still do not turn on when I change their state by toggling the output while in the debugging mode. Yet when I check continuity from the V+ to the solenoid output, the volt meter rings off each time I change the output state. So that tells me the PLC relay switch is making, but there still must be a short to solenoid. (I don't get it).

    The logic I attached before was to fill a tank based on two levels sensors low and high level. The low level sensor will turn on valve A & B and fill the tank until the high level sensor is true.

    Any other pointers here would be greatly appreciated.

    I was unable to open the new document

  11. Welcome to the form!

    Nice job on providing most of the details on your project.

    First quick tip, save your word document as a .DOC instead of a .DOCX. There are many out there that do not use the newest version of word yet and will be unable to view your file.


    "Is there a concern having two separate power supplies?"

    No concern, it is actually better to do it this way. It will help isolate the kickback from your inductive loads from wroking its way into the controller.

    In addition, you should use snubbers on your solenoid coils to help prolong the life of your PLC outputs.

    You may also consider fusing the outputs, or at least the power feed to the outputs so that a bad ciol or short doesn't blow your output/outputs.


    "Why does the PLC logic remain at 1 when the sensor state changes when sensing a target?"

    Your wiring diagram does not make sense. It shows all of your input tied "ON" all the time. It shows all of your prox swtiches shorted.

    The browns and blacks shoudl not be tied together. Each black wire should come back to a separate input. Each Blue wire should go to 24V common. Each brown wire should go to +24VDC.


    "During debugging mode, the Output logic value is "1" when the solenoid is in use. I cannot switch the state to 0 using the reset button in the PLC software"

    "Why doesn’t the solenoid engage when I manually change the state of the solenoid in the logic?"

    Because your program logic is overwriting it.

    You are using "output energize" instuctions. They are updated every scan based on the true or false condition of the logic preceeding it..


    "When I toggle the state of the unused solenoid, I can hear the relay inside the PLC make a click sound confirming that the internal relay is functioning"

    "Is this directly related to a wiring problem with the input and output wiring?"

    Your wiring diagram does not indicate you are providing power to your relay outputs.


    You should provide a description of what you are actually trying to do with your application. It is difficult to comment on your ladder program without the context of knowing what it is supposed to be controlling.


  12. Hi Damian,

    I had an experience last week that has some bearing on your situation. It was time to validate a couple of Omron-based machines as part of our pre-relocation inventory. I tried to get online with my linux/xp combo running CX-One, and failed completely. None of the comm drivers would work, serial or usb.

    I researched this ad nauseum, and found I was not the first to experience this problem, specifically with CX-One. Apparently Omron was late to the game supporting Win7, and alot of guys tried to VM XP to support their equipment. Omron provided no support for this at all, completely silent in fact. Some guys theorized you had to have Omron's drivers installed in the host, but I'm running Trio and PcanOpen both without any special setup, so unless Omron purposefully set it up that way, I couldn't imagine it.

    I tried every configuration I could think of, including making a separate XP service pack 2 VM and hacking the VM config file to simulate a 32-bit version. Still no love from Omron.

    In the midst of all of this, Omron began supporting Win7, with a laundry list of caveats, but I finally switched my host OS to Win7 and got CX-One operational. $#$#&&^ the %$^% off, because I had to lose linux to do it, but I also have to support this equipment, so there it is. I hate Omron.

    Long story short (I know, too late), the part you should know is that when I moved my usual VM from Linux to Win7, it went off without a hitch. Had to reassign the virtual CD-Rom manually, and reinstalled VMware tools as a precaution, but otherwise, smooth as silk - the main reason I went to a VM scheme in the first place.

    Of course, I use VMware Player (free). I've heard good things about the XP client in Win7 Pro, but I'm old enough to remember "Dos Mode" under Win98, and I find myself thinking about the compatability issues people had back then too, running what was essentially a stripped-down DOS VM. Microsoft is doing a better job these days, but virtualization is not their key revenue stream, so I have my doubts about it. And I seriously doubt you could move the instance you are running to another host OS in any way, shape or form.

    Best of luck,


    Hi TM,

    The only reason Mircosoft packaged the XP VM in Win 7 was to attenuate peoples fears of backwards compatibilites. So far the only glitches I have not been able to overcome are getting Rockwells activation server to work properly in the VM (I am told it want's to see a client/server setup with the host, but that defeats part of the point of having the VM in the first place), and issues with Rockwells drive server and recognizing the thrid octet of the IP address properly. I look forward to giving VMWare a try, largely because the backup routine for the XP machine in Win7 is not what I would call convenient.

    Thanks for all the info. Sorry to hear you had to lose the Linux.


  13. Hi Damian

    I'm running on Windows 7 64bit and had a few crashes with VisiLogic 9.3. Haven't had any trouble with VisiLogic 9.3.1 though, and no slow downs on any version. What anti virus are you using?

    Thanks for the feedback.

    My system is a Dell Precision M6500 with core i7 & 8GB ram, Windows 7 Ultimate 64bit

    Also have a SSD, not sure if it is relevant but if it was I wouldn't expect different behavior within the VM.

    I am running Kaspersky Internet Security It was the first place I looked when the problem occured. Turning it off had no effect.

    The slowness is sporadic, but once it shows up it never just clears up.

    It is most noticeable when doing communications related activities, and doing File Save/Open types of things.

    It also happens often when selecting different subroutines or HMI screens, or inside the HW configuration.

    If I am just building ladder, I rarely see it when I am actually drawing the logic. Only occasionally when I highlight a new network it will go to sleep for a spell.

  • Create New...