[V 570 and kepserver]

Do you have some entries in SI 103 - SI 106?

[Problems reading voltage level on analog inputs A0 and A1]

It might be helpful if you mentioned what hardware you were using and how you configured it in the software and how you wired it.

[Communication between usp-156-x10 and sm 35-j-ra22 via ethernet ip]

Take a look at this and see if it helps you:

 

[UID Sortie TOR]

For convenience I'm including a translation to English below:

Quote

 

I have a problem I want the click on an image to activate my digital output.

I am using a SET BIT on my alias of my digital output but it does not work.

 

 

[Unitronic V570 error de arranque de fabrica]

Moved to the correct forum.

Have you looked at this sticky at the top of this forum?

 

 

[Touchscreen scratches and scuffs]

46 minutes ago, Joe Tauser said:

I have a bit of experience removing scratches from headlights on my kids' cars. 

How about car windshields? You have a solution for that? I have a real problem with mine and don't want to replace the entire thing if I can avoid it.

[Barcode!]

On 3/13/2018 at 5:12 AM, Ausman said:

Hi,

1).  Vision reads bar.

2).  Vision executes bar entry routine.

3).  Vision proceeds to bar.

4).  Vision reads different codes.

5).  Vision interprets codes, runs decision-making subroutine.

6).  Vision waits for a while accepting results of decision-making sub.

7). Vision leaves bar sub.....somewhat unsteadily.

8). Vision attempts to run main program normally, but errors appear out of nowhere.

Hmm, I read something recently that might apply. Oh, yes, here it is:

[Conveyor Delay]

Moved to the correct forum.

[When multiple coils are connected in series....]

I don't know if @Damianis still around after all this time, but maybe tagging him will provide an alert that he is needed.

[RTU MODBUS RS485 - Decimal Adress]

I moved this thread to the correct forum.

 

For coils, the DECIMAL address should be the same as the MB number, with the proviso that Unitronics addressing starts at zero whereas the MODBUS standard (and Siemens iirc) starts addressing at one. Therefore when addressing from the Siemens Master, add 1 to the MB number to get the correct decimal addressing for the master.

[Display a list of strings]

Maybe this is implicit in Joe's answer, but why not simply have a series of text boxes, one under the other, and have logic unhide each in sequence as the button is pressed? Seems like that would be very simple to execute.

[V 570 and kepserver]

14 hours ago, Joe Tauser said:

Also, I'm not entirely sure what's under the hood in the way Unitronics handles being two Modbus IP slaves at the same time.  I'd give myself a way to turn on and off the slave functionality for each one:

I've done this multiple times and there is no issue. The Vision PLC handles this without the need to add logic. I've also done multiple MODBUS R.H.R commands in the same PLC cycle with no problems.

[How to make a summary of MI in Software Visilogic]

Moved to the correct forum.

There is a math function to add up to 8 MIs. You could do that 8 times to get your 61 MIs added together, or you could develop an algorithm using indirect addressing to add them over multiple PLC scans.

[Using MODBUS IP to get values from sensors through Visilogic to Raspberry Pi]

6 hours ago, petchpetals said:

My collegue told me that the level sensor is wired with input 9 and the temperature sensor is wired with input 10. Does that make sense ?

Yes, I don't have a V430 here in my office and it's been awhile since I used one so I didn't realize how they had it labeled. You are correct. I had forgotten that some of the smaller Unitronics PLCs with built-in I/O have some digital inputs that can be jumpered and wired as analog inputs. Yes, inputs 9 & 10 can be wired with a thermocouple (negative to 9 & positive to 10). That will be T/C 0 and will be assigned analog input 0 in VisiLogic. Inputs 7 & 8 can be wired for T/C 1, which will be assigned analog input 1. Analog inputs 2 & 3 can be wired to I6 & I5, respectively.

Sorry if I led you astray earlier - the V430 is a bit different in some respects than most other Unitronics I/O.

For the temp sensors, the MI assigned will hold the temperature reading to the tenth of a degree (i.e. 98.6 F will be 986 in the MI). For the analog inputs, the MI will hold the analog to digital conversion of the mA measurement to a resolution of 14-bits, so it will be a number between 0 & 16383 (3277 - 16383 for 4-20mA).

[Convert Timer to a Int or Real Value]

Both the Preset and Current values of a timer are UINT integers. Just use them directly as you wish or convert them into other types as you would any other integer. I think they are in units of milliseconds.

[Using MODBUS IP to get values from sensors through Visilogic to Raspberry Pi]

There are a number of example program that came with you VisiLogic installation. Take a look at those to see how to code your program for ethernet communications.

1) When you assign and IP address to the PLC, it needs to be on the same subnet as your Raspberry Pi. In other words, whatever the address is of the Raspberry Pi, the PLC needs to have the first 3 numbers the same. The last number can be anything between 0 & 255 as long as it's unique to the network it's on. Subnet Mask should be set to 255.255.255.0 and default gateway is only important if you are trying to communicate over the internet. Just set it for the same subnet with the last number 0 or 255.

2) Do you know how to set up your HW Configuration? That must be done in order for your PLC to collect data from the I/O. When assigning an MI to the analog input in the HW Config, it should be obvious which input you are assigning. The 4 rows are for analog inputs 0-3.

I'm not sure what you mean by inputs 9 & 10. You only have 4 analog inputs, which will be labeled something like AN0 - AN3. Perhaps you're confusing them with digital inputs?

Also, unless you are connecting your PLC through a hub, router, or switch, you may need to use a crossover ethernet cable.

[V 570 and kepserver]

2 hours ago, Seversean said:

moving stuff around and creating new rungs is all foreign to me, coming from Allen Bradley background. 

You didn't use Ladder Logic with Allen Bradley?

[V 570 and kepserver]

A couple of things:

1) Please do NOT place multiple logic threads in a single ladder rung. You did not break them up into separate rungs. The whole point of ladder rungs is to separate out the logic so there are no conflicts or confusion within a logic statement.

2) You don't really need anything in front of the SCAN_EX blocks. Just hang them directly on the left ladder rail. If you feel like something should be there, use SB 145 & SB 146 instead.

[V 570 and kepserver]

Yes that all looks correct assuming you have the SCAN_EX blocks addressed correctly. And yes, you are correct that the MODBUS Configuration block is just showing you the defaults.

There is no need to pack your ladder rungs so much. I like to tell people that Unitronics does not charge you by the rung. Break those logic pieces into separate rungs. What you have should work, but new users often get in trouble with overly complicated ladder rungs that don't compile the way you think they would. I would place each Socket Initialization, with its accompanying MODBUS Config into a separate rung (with SB 2 in front), and each SCAN_EX block into a separate rung.

[Software update in Unistream]

Yes, insert a memory stick into your computer running UniLogic, go to the PLC tab, click the Download down arrow, and select Export project to a USB Storage device.

[V 570 and kepserver]

Socket 2 defaults to Port 502. You have both Socket 0 and Socket 2 set to Port 502. Sometimes that works, but it is very bad practice to do that. Unitronics generally recommends that you Initialize all 4 sockets, even if don't plan to use them all so that you can be sure there are no conflicts.

[V 570 and kepserver]

Yes you need to initialize and configure each socket you're going to use for MODBUS IP. Pick any two sockets, though I would leave Socket 1 initialized to Port 20256 to use for a VisiLogic connection. I would keep Socket 2 at the default of Port 502 and initialize Socket 3 to Port 503, but it doesn't really matter - just don't initialize two sockets to the same port number, keeping in mind the default assignments.

You also need to configure each socket you're going to use for MODBUS IP with a MODBUS IP Configuration block. Don't duplicate addresses. The network ID isn't important with TCP, as I understand it, but you can assign them any way you want.

Then you will need two separate MODBUS IP SCAN_EX function blocks. Be sure the SCAN_EX block assignments match to the relevant MODBUS configuration names.

Set up one of the masters to communicate with port 502 and the other to port 503.

That's all there is to it.

[No sound came off when the program was active]

Also, do NOT place multiple logic threads in a single ladder rung.

[No sound came off when the program was active]

Yes, but what is the purpose of the Inverted Coils? As I said, Actions require SET coils.

[No sound came off when the program was active]

Coils (other than SET or RESET coils) can only be used in one single ladder rung. The value of the first coil will be overwritten by the second one.