Joe Tauser

According to the Help- "This parameter is intended for future feature support. It has no influence on the Trend graph." So ignore it. Joe T.

Translated- Hi good day I have a problem with a PLC V280 with adjustment module V200-18-E3XB. this is the case: -I have configured the analog inputs of the TC module, with the bridges 3-4-5 for AN0 in B. -HW configuration is for TC J, no filter, ° F, MI 103 -I have a type J TC connected to the analogue input AN0, which is tested on another ABB PLC -program a screen with a shape Variable: numeric, to display the Variable MI 103 The problem is that I get on the screen the value 32767 and I do not get the real value of the temperature. Your jumpers are correct. If you're getting 32767 you don't have it wired right. Did you run 24V power up to the module? A common mistake is to not to run power to V2 and 0V. It's not real obvious in the instruction sheet that you have to do this. Post your code so we can check the configuration. Joe T. P.S. - looks like Aus already answered this. One post per customer!

Look at the Help on the 1.25 ms interrupt routine. If the input is on the main PLC board you can insert an immediate input into the interrupt routine and count the number of times the interrupt runs while the input is high. You'll have to scale it, as the interrupt runs 800 times per second. This is by far the fastest way to measure input ON time if you don't have an encoder. Post your code and I can put one in for you. Joe T.

Unitronics does not have a +/- 10V input module. Probably has to do with the fact that none of our analog I/O is isolated. Joe T.

You'll need to become familiar with the Protocol block using a Stream variable type. You'll also need a barcode reader with RS232 output. Connect it to COM 2 of the V350 and point the Protocol block at it. Post your code if you need some help. Joe T.

Thanks for loading and checking it on a live system, Dustin. Your settling timer on the scaling routine is a good solution. This would have also helped to indicate to the operator that the real problem was ALL the tanks were empty. The point of my code was to demonstrate a method. Joe T.

There is no way all the outputs could come on in Automatic mode unless all the tanks are low, in which case it will continually cycle through them. I did not put in a pause state as this program was written to show another way of doing things. I didn't have a system to test it on, so it's most probable that something was overlooked. My code almost always has a mistake the first time I load it. Did you troubleshoot what I did? Joe T.

First of all, only put one logical operation per network. When you put several separate rungs in one network, it may not compile the way you think it will. Creating a new network guarantees separation of operations. It is also very helpful in troubleshooting to keep your functionality together. For example, the timers controlling the fan were spread across several networks. I grouped them together and wrote simpler timer pair logic in the Outputs subroutine. Timers reset themselves when power is removed. You don't need separate logic to reset them. I put together a state machine that steps through the tanks in order in automatic mode. I also moved the scaling and the alarms to their own subroutine. You'll notice that the Main routine is now very small. I put all the functions of the system into their own subroutine. I hate the phrase "best practices", but this way really does make it easier to understand what's going on. Let me know if it works the way you want it to. "Likes" are always appreciated. Joe T.

I don't know if this will work, but try a complete uninstall of U90 similar to the Visilogic procedure: 1. Backup your projects 2. Uninstall U90 3. Delete directory C:\Program Files (x86)\Unitronics\Unitronics U90 Ladder 4. Delete directory C:\Program Files (x86)\Common Files\Unitronics 5. Reboot 6. Install U90 Let us know if this works. Joe T.

Virtual COM ports are very finicky. I've tried several and the only one that works reliably is a USB converter with the Prolific PL2303 chipset. It has to do with when the driver finally gets the operating system's attention - we didn't have to deal with this back in the day when serial ports were on the motherboard and had their own interrupt. Try Flex727's suggestion - if that doesn't work you're going to have to get a regular USB to serial converter. With wires. Sorry. I've had much better luck with wireless Ethernet bridges, but that does require putting an Ethernet port in the PLC. Joe T.

Make your own hour accumulator. I've attached a program that includes a decimal (6 minute increments) and will display up to 9,999,999.9 hours. Should be enough. Joe T. Jazz Hour meter.U90

You've built a bit-banger to make a conditional sequencer. There is a better way. It's also much clearer to put the outputs in their own subroutine and handle automatic and manual control separately. Can you post your actual PLC program? I could hack on it for you. Joe T.

The SM35 has a buit-in RS232 port that will behave mostly like a V350. You didn't say whether you were doing serial or Ethernet communication. If Ethernet, you will have to add a card to the PLC. The front HMI has no programming ability whatsoever by design. You will need Visilogic and it is free (a great selling feature of Unitronics, BTW). I say mostly because the Samba SM35 is a hobbled version of the V350 with a lot fewer registers. I recommend you study up and compare the memory sizes of the V350 and the SM35: https://myzone-kza3sadj.netdna-ssl.com/wp-content/uploads/2015/12/SMXX-J-R20_TECH-SPEC_02-153.pdf https://myzone-kza3sadj.netdna-ssl.com/wp-content/uploads/2015/12/Vxxx_J_TR20_RH2_TECH-SPEC_01-15.pdf This may or may not come into play depending on which registers in the PLC your application needs to read. Joe T.

The Unitronics .NET library will talk to the V350 no matter what and it has more power. There's also a learning curve to deal with. If you use Modbus you will have to add a couple of networks to the V350's ladder program to make it a Modbus slave. This is a more generic protocol and you will be limited to reading/writing mostly MIs and MBs. But you will be able to use a simulator to test your end. Do you have control of the V350 program? I would hesitate to use the term "golden" until your program and the PLC are physically connected and you verify that the connections and data locations are correct. Unitronics starts counting at zero, while Modbus starts at one. This can be confusing. I would seriously consider getting a Samba of any flavor to practice on. They communicate the same way and cost less than a V350. Consider it part of your development cost. Joe T.

Assuming your application utilizes the Modbus protocol, here is a thread where I posted links to some online simulators- http://forum.unitronics.com/topic/3582-modbus-rtu-and-danfoss/ Otherwise, can you post more details of what you're trying to do? Joe T.

Post your code and/or be more specific with your question. Joe T.

I would be curious to see your program. I've never filled a Jazz, but I always use a Vision for an operation complex enough to require that much code. You can't argue with the compiler; it always wins. How did you arrive at the 2690 number? Project->Properties? If so, what are the values in the other memory allocations? Joe T.

You did not show that actual logic you are using to read the data table, which is probably where the problem is. Please upload your PLC program. Joe T.

The forum really isn't intended to provide complete finished solutions to people. That's how most of us make our living. That said, the forum is intended to help people arrive at their own solutions using Unitronics products. If you would provide details of the servo controller you are using, a wiring diagram, and upload a program that you have started we are happy to help you help yourself. Joe T.

JT- Don't mind us seppos and our funny tawkin'. Joe T.

Update - remember that the Vision series does not support email servers that require SSL or TSL, which is almost all of them now. So you'll have to come up with your own email server or work with a small ISP that will set up SMTP or ESMTP only. The big guys such as gmail, gmx, yahoo, et. al. won't work. Joe T.

The spec says the pump draws 0.35W at 24V. Without seeing one, I'm guessing these things are small. That translates to a 14 mA draw from the PLC output. The IO-TO16 has a 0.5A rating per point, which can handle this easily. Joe T.

I've been using UniLogic on two different Win 10 boxes and haven't had any issues. Yet. Granted, they're desktops, which tend to be more stable as the video memory is separate and does not share RAM with the OS. I always put a video card in, even if the motherboard has it on-board. That said, my old Dell has Win 7 32 bit and I've never had a problem. I have a sneaky feeling laptop manufacturers did not re-invent the driver wheel when Win 10 came out. You can see when you download a driver that they just lump them all together for Win 7 and above. Does this happen consistently or intermittently? This guy has some good suggestions- https://www.deskdecode.com/bad-pool-header/ Like any BSOD problem, it can be horribly elusive and can be caused by any one of several potential issues. My research kept pointing the drivers or to bad RAM. Are you connected via USB or Ethernet? Joe T.

I really don't think using relay outputs at 9 Hz is a good idea. This is a transistor output application. I think what you're seeing is the latency of the relay module response trying to keep up with the scan time of the PLC. The specification of the relay module is 10 ms response with a 100K cycle lifetime at maximum load (3 amps). You did not specify your actual load current. If your load is inductive (a solenoid) you have to take into account the flyback pulse which will add to the relay contact point degradation. You didn't say what your duty cycle is, so I'll guess it's 50%. The ON time of a 9 Hz signal at 50% is 55 ms, for a 111 ms total cycle. So if you're cycling relays at this rate and you go 100,000 cycles then you have 11,100 seconds before you hit the "rated" life. That's 185 minutes or about 3 hours. Usually relays go longer that their rated life because of less load, but that can go out the window if you're pushing solenoids, contactors, or even other relays. So let's say you get 1 million cycles. So now we're at 30 hours of operation be things start failing. I speak from experience and I'll bet that module doesn't last more than three months. I always use transistor outputs with those 6mm individual TB-style relays now. It adds cost, but when one fails it's an easy and cheap fix. Joe T.

Yes, this should not be a problem. The Vision Modbus Examples use the same code as the Samba. Joe T.