Joe Tauser

Define "Selector". If you're talking about something like an HOA switch, I've put a graphic by pointer object on the screen and placed small invisible boxes with touch properties right at the corners of the graphic. Then get a picture out of the Unitronics library of the selector in each of the positions. When you touch one of the corners or the center of the graphic, the PLC logic writes a number to an MI corresponding to "Hand", "OFF", or "AUTO". You can then use equal blocks looking at the MI to set coils in your program. No, I'm not going to post an example, yet. If this is something you want to do I want you to try to make it. Then post your code (.vlp file). Also dig into the example projects under the Help menu. There's a lot of good stuff in there. Joe T.

You have to have a copy of the PLC program (the .vlp file) with the data table in it. Do you have this? Joe T.

You're supposed to call SB 80 last (in a separate net) after you've loaded SI 80 .. 84. If you're variable isn't changing fast your code will work fine, it's just kind of backwards. Joe T.

Yes. If you want to post both .vlp files after you've changed them we can be of more help. Joe T.

Please clarify this. The screens you show are from Info mode, which you need a password to get into. It is used to view and change the raw memory of the PLC. If your workers were screwing around here you have a problem we can't fix. Typically the application has input on the various screens, which are designed for the data the programmer wanted changed. Where exactly were your workers changing data? Joe T.

Do you have the plc program? It will be a file with a .vlp extension. Joe T.

You've already mentioned that you set the jumpers - they are correct. Verify you have +24V on terminals VA and 0V on the other side of the module. As a sanity check, put a jumper wire between T+ and T- on channels 0 and 1. This should give you ambient temperature in tenths of a degree. Let us know. Joe T.

The V130 has four sockets. Socket 1 defaults to port 20256, which is what the app uses. You can initialize the other three to TCP slave connections, but each has to have a unique port number. This means four things can communicate with it over Ethernet simultaneously but each thing needs to use a different port. The only Vision that has more is the V700, which has eight. UniStream does not have this limitation. Joe T.

@Nancygogogo - rather than post pictures when you have a question, it is more helpful if you actually post the link of where you found the information. Then we can look at exactly what you are looking at. RS232-CB1 seems to be what the rest of the world is calling this cable. I've always called it a -CS25, because that's what's on the little RJ-12 to DB9 adapter. To use the words "telephone style" cable is incorrect, because a telephone cable does not cross the conductors between the RJ12 plugs like this cable does. This cable is included with every M90 and Vision controller. They don't include them with the Samba and the Jazz as those products are aimed at OEMs and they do everything they can to cut cost. I have a large box of them that has accumulated from panels we've built. So I guess I'll have to get with the global program and change the part number on my price sheet. Joe T.

I don't see any thermocouple wires connected to the analog inputs in that picture. Did you remove them? Joe T.

You've hit the Jazz Wall. I've done it a handful of times with my customers. Unfortunately the Jazz logic can not just be pasted into Visilogic. Most of the system bits are the same, but it does depend on what they are. You're just going to have to have a copy of U90 open on one computer or screen and a copy of Visilogic open on another, and enter each rung. You'll be able to improve many of the Jazz rungs as you go to Vision. Have fun. Joe T.

The -RC1 comes out of the box set to ID 1, but the DIP switch settings in the Unitronics documentation are confusing as it's not clear which is up or down - black or white. The switches themselves are actually white, but the drawing shows them as black: So ID #2 is switch 2 up. Or it could be this. If the bus is powered and the switches are right, CANbus works. Joe T.

The AD cable is totally different than the Unitronics cable. AD converts serial to TTL, while Unitronics uses standard RS-232. Sambas don't come with a cable. It's one of the things removed in the Vision->Samba downsizing. You need an MJ10-22-CS35 USB to serial converter if you don't have a serial port and an MJ10-22-CS25 serial programming cable. Joe T.

Yes, that should work. Make sure you use a Positive Transitional to call it. Joe T.

With CANbus working correctly, you should be able to program the EX-RC1 through the V570. I'm assuming you have your com settings like this when you try to connect to the EX-RC1 via the V570: With the PC port set to whatever COM port your USB cable is using. No. That doesn't work. Joe T.

You realize the EX-RC1 is another PLC, correct? You have to download The EX-RC1.vlp program to it using a serial cable. Joe T.

+1 to what Flex says. If I may elaborate- If you stop calling a subroutine everything in it stays the way it was in the last call. So coils get left on, timers don't reset, etc. You have to be very careful cleaning up after yourself if you use conditional subroutines. This is why my State Machine example uses a common pointer (MI 0) with Equal blocks and has all the logic in one subroutine. If you need more space for a given step you can set a coil that is only true while the pointer is equal to a given value (like MB 0 in the first net). With the pointer method, only a small amount of a larger subroutine will solve at any given time. The rest won't because the Equal blocks won't let them. For the next level of State Machine programming, I also usually put all my output coils in their own subroutine which is called all the time. Then I can put them in order and use the internal coils I set in the sequence subroutine to control them. If an output needs to be on for more than one step, just add additional contacts in parallel- This makes control and troubleshooting much easier. It puts me in charge of the program, not the other way around. I'm not guessing what other logic may exist that I may not of thought of and now I have to make a mish-mash of logical ANDs and ORs to get the output to work right. I call this method "bit-banging". And it's a nightmare to figure out someone else's bit-banger. It's like trying to dance to jazz music. If you post your program we can have a look. Joe T.

There's more than one way to skin a cat. Use a Binary Text Variable for two colors or a List of Text Variable for more. You can put the same or different texts in the "Texts, Binary Variable" collection as well as change the text and background colors based on the value in the Link tag which is driven from the ladder logic. You can set the Actions to whatever you had the Button object do to a different (or the same) tag. Joe T.

Look at the System tags, specifically this UTF-32 string: System.CPU HW Version.Serial Number. Joe T.

I can't resist the temptation to chime in on this one. First, let us refer to my rant from last year on this very topic..... http://forum.unitronics.com/topic/4459-a-rant-about-the-cost-of-things/?do=findComment&comment=16304 @korenje - Judging from the location of the post you are talking about the UniStream platform. I agree with your position that they are expensive. They are, depending on what you need your controller to do. If you just need a PLC and a screen, the Samba is totally the way to go for less than half the price. A UniStream is two controllers - a Linux box running the panel with another CPU module dedicated to the logic. The IoT champions of the world have been screaming for computer-like behavior from a machine controller, and the Unistream does that by marrying a computer with a monitor to a controller. Don't compare our stuff to a cell phone. Those are manufactured by the millions and sold at WalMart. Joe T.

Baptiste - I took a look at V6 of your code. You're still calling the !Start-Up Display continuously in the first rung of the Main Routine, which will cause the display to flicker and won't let anything else work. Stop screwing around with subroutines and jumps until you have a better handle on how they work. You've created a train wreck here. It is good that you know how a Grafcet works. These are the basis for the State Machine programming style I am such a big fan of. You've made the classic beginner mistake of writing a whole program, downloading it, and then wondering why it doesn't work right. This is extremely true based on the questions you've asked in this post. This is not a fatal problem, but you are biting off way more than you can chew. There is no way you can learn to program a PLC without having one in front of you. In your current state of understanding you need to write a little code and then see how it works. Then write some more and continue. If you don't have a real PLC to practice with then you are just banging your head against the wall. Baby steps, Baptiste. We will help you along the way but we're not going to write your code for you. Unless you have a credit card and are willing to pay my $125/hr USD rate. Then I will. I have attached my State Machine example program, which uses a pointer and transitions to jump between functions. Remember that a PLC "runs" all the time and is nothing more than a collection of IF-THEN and logical AND and OR statements. If you study it well you will be able to write your Grafcet program. Joe T. State machine example.vlp

Understand the UniCAN is a broadcasting protocol. The broadcast is initiated by the UniCAN Send block. In your case, the RC1 will do the broadcasting and the UniStream will just sit there and listen. You'll need to upload your UniStream program for us to be of help, and I don't know if the upload limit will allow that. I looked at the UniStream example C:\Users\Joe\Downloads\Unitronics\UniLogic_Example_Projects\UniLogic Examples_V1.23 Rev 25\UniStream and EX-RC1\EX-RC1_IO The Check Alive pulse goes around every 0.5 seconds. I've had problems with the Unitronics Check Alive timer preset of 1.1 seconds, so I usually set it to 2.1 seconds. For starters, your RC1 program commented out the UniCAN Send block, and you've spread your MI address out. I'm assuming you've set the DIP switches so the RC1 is UniCAN ID #2. I grouped all the inputs registers together and entered them directly into the Send block. The problem may be in your IO tag definition in the UniStream. Here is how the example is defined- Notice that the tag names match what the example RC1.vlp program is sending. Did you do this? Joe T. WaterPumpMaybe JT.vlp

@EduMarg OK, now we're curious. What is the summary of the problem? Joe T.

As a more sane follow-up, this is why I shudder when someone starts shouting the praises of IoT. It is a huge Pandora's box of things that don't want to play together without a spending a massive amount of time getting all the little settings just right. Then Microsoft introduces a Windows upgrade that throws another wrench in the works, usually breaking stuff in the name of "enhanced security". This just happened today- Saks, Lord & Taylor Hit With Data Breach Millions of credit cards exposed by hackers; retailer says it has identified the problem I'm sure that they had a full-powered IT team in place already. With all the latest patches and upgrades. The Enigma was a simpler machine. Joe NOT IoT T.

In my day, we didn't have no fancy In-Ter-Nets! If we wanted to send a message we wrote it on a rock and threw it! That was if we could find a pencil! If not, we grabbed a hot piece of coal from the old Franklin stove and scribbled with that! Then there was this fancy new thing called Ra-Di-O! To make it work, we connected 14 car batteries to a magical box and strung a wire from the house to the barn! Did I mention the barn was two miles away?! And it was always snowing! So there we were, holding hot lumps of burning coal in our hands and throwing rocks at our neighbors all the while pulling a reel of antenna wire down the road in a blizzard just so we could listen to Little Orphan Annie! AND WE LIKED IT!!! Joe T.