Joe Tauser

Make sure you have "Run as Administrator" checked under the Advanced properties of the shortcut. It doesn't matter if your user level is already administrator - you have to double-bang it. Joe T.

When you downloaded the program did you choose "Download All & Burn" from the Download menu? Joe T.

I'm guessing V0 is a type - 0V is supposed to be connected to the negative of the supply. V1 must be connected to the power supply + to power the internal relay coils. This does not supply power to the contacts - you must provide that yourself externally. A test light will light on the PNP output O10p because power comes from within the module. Joe T.

It's in Logic->Shift - both left and right. Open the Help and enter "Shift" in the search box on the Index tab. Joe T.

Getting a window off a monitor that is no longer connected- Try "Alt-Space" then "M" (Windows Move command) and use your arrow keys to drag it back. Joe T.

The HSO's frequency stability is not specified. +/- 5 Hz may be the best it can do. Did you verify this with an oscilloscope? Go back and closely examine the specs on the V350 high speed input - the 3 V you mention for a logical 1 is for the NPN input and the voltage must be below that. You'll have to get the input above 20.4 V to get the logical 0 or the PLC will never see it. I would suggest the following level shifter- Power it with 24V instead of 12V and run the output to the PLC input. You may have to fiddle with the 1K value to get the transistor to switch with your 2V signal. Joe T.

John - good question. As soon as I figure out how to unlock my UniStream after trying to update the Beta BIN files I'll connect to an RC1 and give it a whirl. The Creators have been partying all month so it's taken a couple of weeks to get my O/S problem addressed- http://punktorah.org/jewish-holidays-2013-2014/?gclid=CLO3ze2h77kCFcxAMgodxncA3g They've been working really hard on the UniStream. I think they deserve a little break. jahauser - no conversion utility exists at this time. That was one of my first questions. I feel your pain. Joe T.

The PWM "frequency' value for an HSO output on the PLC and the PWM function block are different. I know this is confusing. Check the Help on configuring an HSO output - Search tab->HSO->Configuring a High-Speed Output. On a dedicated HSO, the frequency MI is the actual frequency. For a 1 kHz signal enter 1000 into the MI value. For a PWM block, the Cycle Time is in units of 2.5 ms. The best you can do with a PWM block is 400 Hz. I'm assuming you have a 6V power supply connected through a 2.2K pull-up resistor to the NPN HSO output of the PLC to get your desired signal level. Don't forget to connect the 6V power supply common to the PLC's power supply common. Joe T.

How are you going to get the data into the PLC? Ethernet or serially? Start looking at the Help on the Protocol block and the String functions. Joe T.

If you look carefully at the PWM Scan configuration, you'll see that Cycle Time is in 2.5 ms units, so it's not really frequency. 1/0.0025 = 400 Hz; to get 100 Hz use a value of 4 for the cycle time (4 x 0.0025 ms = 0.01 ms per cycle = 100 Hz). Joe T.

Have you looked at Help ->Index tab->ASCII String ? Joe T.

You can configure your PID block to output 0-1000 (0-100.0%) and run that into a PWM block. A heating application doesn't need the speed of a true high speed output - you can map the output bit to any DC output if you set the PWM frequency to 100 Hz and it will work fine. I would also think about if your application really needs PID on all heating loops. If your heaters are "matched" to your process and you don't need super-tight control, On-Off control might work just fine and be a lot simpler. Joe T.

You are correct about the conversion direction, Flex. There's no handy tool to downgrade from color to monochrome. That's just crazy talk. It's not a frequently used utility, but in my role as a distributor I've had this request before when customers have wanted to go from a V130 to a V350. This conversion is no where near as painless as the V280->V570 because of the significant difference in resolution. I ran the V280 conversion on one of my old programs before I answered the post just to make sure it did indeed work on the standard instruction models. Joe T.

Unistream IO modules can't be used with a Vision PLC at this time. Joe T.

Yes - you'll have to set up CANbus I/O drops with EX-RC1 modules to use existing modules. Unistream local I/O modules are a new format and attach to the back of the unit. Joe T.

It's in Visilogic- Open your V280 program and use the menu Project->Convert Project to Color. The conversion program will tell you changes you have to deal with, such as Hide Vars function blocks. As Flex727 points out, you'll have to make buttons to emulate the function keys. The screens will come through in a mostly usable format, but you'll want to go through them all and take advantage the additional screen functionality. Joe T.

I think Simon went to the same school of hacking that I did. All his comments about interfacing with 8V sensors are true, but I don't usually recommend this approach on the forum because I don't know if the person asking the question knows how to use a soldering iron. If you build a circuit by twisting the wires together and wrapping them with electrical tape I will virtually smack you upside the head. If you are really comfortable with an iron, a voltmeter, and an oscilloscope you can do this, and it won't be that hard. An 8V power supply can be built relatively easily and as Simon described a cap and a resistor matched to the PWM frequency will make a nice little voltage producer. Then you can use a couple of ATC8 modules to read your data. The values on the picture below may or may not work; it's just something I found: Industrial sensors are not built to the vibration specification that OEM sensors are. As soon as you mentioned CAT and Cummins sensors I understood what you were trying to do and why. A comment on Simon's last post - an NPN sensor is also known as an "open collector" sensor. Google this to gain some understanding. If you tie the output of the sensor to +24V with a 2.2K pullup resistor you can generate the signal you need for the PLC by connecting the junction of the sensor output and the resistor to the PLC input. The signal will be inverted. If you use a DI16 module you can wire it to accept NPN inputs, in which case the pullup resistor is supplied for you. A "self-engergizing" mag sensor has two wires and is a coil wrapped around a magnet. You can tell by looking at it. It generates an AC signal of increasing frequency and voltage. The top end can be as high as 50Vpp - you'll need a separate conditioner if you want to connect this to a PLC - KEP makes one called the AMP1. You're probably better off using a DC proximity sensor. If you want to post an electrical design we can review it for you- I do have an electrical engineering degree and I'm not afraid to use it. Joe T.

It's not off the screen, is it? "FB's" is the last menu on the right. I tried making my window small and noticed that the menus on the right of the screen were no longer visible. Try grabbing the far left "handle" of the instruction toolbar and dragging it down to re-shape the toolbar. Joe T.

Post your exact wiring diagram. Joe T.

0V is the common of the DC power supply. The world referring to this as "earth" confuses me, so don't feel alone. I consider "earth" and "ground" to be the same thing, although in the US we always call it ground. Unless, of course, you ground your negative on the DC supply. Then it's earth Try really hard to find sensors that will accept 24VDC power, regardless of the output type. Interfacing 24V PLC inputs to a device that's powered by 8V is just going to cause problems. You're going to wind up building a circuit to do this. It would be helpful if you told us the exact model of sensor you want to use; otherwise we're just guessing at how to interface with it. Most models of Unitronics will accept two frequency inputs. If it turns out that all 13 of your sensors generate a frequency then you'll either have to build a circuit for each that converts the PWM to a voltage or go elsewhere and use a PLC that has HSC input modules. Either way, the 8VDC is going to be tricky. Joe T.

My take on the new platform so far..... UniStream/Unilogix is an awesome product for the power user. The first difference is the memory structure - gone are pre-defined tables of MBs, MIs, etc. It is tag based and you make whatever you want, how many you want. Each tag can be a single instance of any data type or an array of types. Types can be combined into structure variables that can then be used as an object and as many of those tags can be used. For example, you could define a type "oven" which contains an array of bits and an array of integers that would be everything you need for an oven - setpoint, PV, alarms, and so on. Then you if you have five ovens you can use to "oven" type to create five oven objects, with each parameter accessed like Oven1.setpoint. The need to wrap long rungs is also gone - if you get carried away you will have to zoom out to see your whole rung. For those of us used to the old ways, there is an option to have the software create a default set of tags with the same names as the current memory - MB0..MB8191, MI0..MI0..MI4095 and so on. We don't have to write our own communications handling anymore. Modbus and CANbus are set up in tables and the addresses you want to read and write are defined in the tables. The new O/S handles all the handshaking and timing. If you have communication in your application the need to write your logic using status bits and individual read and write blocks is gone. It's just flat out easy to set up communications. It has two Ethernet ports and a USB host port. I don't know what the upper limit on sockets is, but it's a lot more than four. I didn't do any heavy lifting on the screen, but I also didn't notice any lag on what I did. I have one of the early units and I'll try to answer what questions I can. You'll have to draw your own conclusions as to when to use it - my initial opinion is in a communication-heavy data application. Post them as new topics under this subforum for now. Joe T.

Look at Visilogic Help topic "Modbus Slave" and then "slave addressing" for the Slave Addresses of Enhanced Vision Controllers. It shows the "I" coils starting at address 6000h, so I2 would be 6002h. This translates to 24578 decimal. Try putting this address into the tag definition for prb and see what happens. Joe T.

Your last dialog box for tag "prb" - what is the address in the PLC you are trying to read? Joe T.

I did a little more digging on KepServer - Here's their Help on configuring it for Modbus TCP: http://www.kepware.com/Support_Center/SupportDocuments/Help/modbus_ethernet.pdf From the Unitronics side, read the Help on Modbus Slave Addressing - under the Search tab search for "Modbus" and choose topic 2 - "Slave Address Tables". Click on the link that says "Enhanced Vision Series" to show you what Modbus addresses correspond to which Unitronics addresses. Joe T.

1. Don't write the PLC program until you've defined your leak test. This is putting the cart before the horse. 2. The Dwyer sensors are two-wire devices - you can power them from the same 24V you're using to power the PLC. 3. What are you doing with a V120? Did you have it laying around or did you buy it recently for this project? This has a 10 bit A/D converter so your resolution will be limited to about 800 counts - do you need more resolution than 0.01 PSI for your test? 4. Just out of curiosity, where are you located? Do you have a distributor you can lean on? Joe T.