[V570-57-T20B-J Modbus Slave to US5-B10-T24 Master]

2 hours ago, Flex727 said:

In rung 2 you are continuously calling the MODBUS Configuration FB. You need to replace SB 142 with SB 2.

I have tried this fix, and it gives me status 2 on the unistream PLC, that doesnt seem to fix my communication issue.

However i have noticed that a couple of times i have tried communicating the IP address is completely wrong as below.

The screenshot below is of that with the initial vision program i attached and not the fix you suggested

[V570-57-T20B-J Modbus Slave to US5-B10-T24 Master]

I have now tested this with a V700-T20BJ with no avail of communication between a vision slave and a unistream master, so I don't know what has happened since I last did this type of communication, but I cannot get it to work at all.

 

I have also tried unistream to unistream which is working seemlessly

[V570-57-T20B-J Modbus Slave to US5-B10-T24 Master]

Hello,

 

I am familiar with Modbus and have used it before from a vision slave PLC to a Unistream Master PLC.

However, i now seem to be encountering issues when trying to communicate from one to the other.

The Slave PLC is a V570-57-T20B-J with an V200-18-E1B Module and an Ethernet card added in being a V200-19-ET2.

The Master PLC is a US5-B10-T24.

Is there a special way I need to set up the ethernet card added into the Vision PLC as I have copied program logic used previously on already in built ethernet PLCs to get an Modbus communication error showing on the Unistream PLC, Status 3 on the Unilogic software, meaning there is communication but the commands arent set up correctly.

And I cannot seem to figure out what is wrong with the Visilogic program.

 

As seen in the attachments I have the code for visilogic with MI0 Flow Test value linked to the screen to be able to manually change the number to see it on the unilogic program.

On the Unilogic program I am reading address 0.

All IP addresses and ID numbers etc all are aligned as they should be.

Any advice would be greatly appriciated.

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

18 hours ago, kratmel said:

Researching unique things is one of my favorite activities. Especially interesting to explore modbas with developer features...in Chinese.

I visited the website of the this sensor developers. And I even saw a video on YouTube where someone programs such a sensor using some program. However, I did not find links to the programs themselves.

Based on the problems with configuration setup described by the author, it is easier for him to buy another communication module for Unistream and connect his sensors separately to separate communication ports.

I did think of this, obviously a much easier solution and guaranteed sucess, however the supply from unitronics on parts is obscene at the moment so getting hold of another one of these for however many projects we would use 2 instead of 1 might be a great issue. Hence the reason for trying to work out if i can reprogram it.

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

On 9/23/2022 at 4:12 PM, kratmel said:

Two tips:

1. Try to check (read) what info you write to sensor before power-off.

2. Try to not disconnect green wire before power off...

 

I think that after starting the sensor, it has communication settings in RAM memory. If the green wire is connected, the standard setting from ROM  is recorded there. If green wire is not connected, the setting is loaded from another EEPROM memory.

Actually you write something to EEPROM memory. So this information cannot be used by the sensor immediately - it must be turned off and it will download it after restarting.

That is, it is important to follow the correct wire connect -disconnect sequence which is not specified in the manual...

What I am trying first from the MODBUS Register list is trying to read the values of Baud Rate and Modbus address, as from the table it shows this should be 1 and 3 respectively, however currently reading these addresses I am getting 0. So I feel if I understand the issue as to why i am not able to see these values on the HMI screen I can then work on setting the parity bit with the steps you've already suggested. Each Tag on the unilogic program below for the 3 addresses shown are UINT16.

Any help again would be greatly appreciated.

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

12 minutes ago, kratmel said:

Yes!

This has not worked, unless i am doing it incorrectly

I have the red wire/ green wire connected to +24V and black wire connected to 0V

The Yellow and white are connected to the RS485 COM module on the back of the unistream

I power on the plug socket to power the PLC and sensor

I write the parity bit to 1 in the program via a button on the HMI.

I disconnect the green wire - (and see values on the screen which I shouldn't if I've changed the parity of the sensor)

I then download a new program to the PLC with the changed parity bit of the COM module

I then turn off the power and reconnect.

 

what is it I am doing wrong? I am very confused as to why it is not changing

Thanks again for your help

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

4 minutes ago, kratmel said:

From manual wiring

SET, V+ (power) when boot module into the "setting mode". Not connected
or connected with the GND when boot into "mode of operation".
Module configuration parameters such as Modbus address, baud rate,
parity, communication protocol is composed of module inside the EEPROM
(power down storage device stores). The specific configuration sometimes
forget these parameters that cannot communicate with the module. In order
to prevent this problem, the module has a special mode called "mode".
When the module is based on the "mode" electric start, the module
communicates with the following parameters:
Fixed Modbus address 0
Communication configuration is 9600, N, 8,1 (9600bps, no parity bit, 8 data
bits, a stop bit)

That is if you connect green wire - sensor settings after power on  is not from EEPROM but from standard (i select it via bold)  internal settings....

You must use this setting for connect to sensor - then change EEPROM setting to needed value - than disconnect green wire - power off-on  and connect to sensor via new EEPROM programmed settings.

 

Communication protocol for Modbus-RTU
Configuration parameters in EEPROM will not because the module into the
"mode" and "will change, when the module is in communication with in the
EEPROM configuration parameter is still running mode".

Hi thanks for the reply,

I really struggle with the wording of the manual as posted.

So I need to:

1) power on the sensor with the green wire connected

2) Write the parity bit to 1 from unilogic to the sensor

3) disconnect the green wire

4) Power off then on sensor

5) Connect the sensor to unistream again by changing the parity bit on unilogic to match the sensor

 

Is this correct?

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

 

On 9/22/2022 at 12:25 PM, Ausman said:

The pdf you supplied shows that the parity can be changed in the sensor.  Bottom of page 8. 

It would be possible to do UniLogic programming to change the parity, you would simply need to add some code to do a write to the sensor instead of a read.  Once the change is done, you would then change Unilogic to whatever parity you decided to use for both sensors and perhaps the code could sit in readiness for next use, or be deleted.

To me, your easiest way of doing this is to connect to the sensor by using a RS 485 port on your PC.  The parity register can then be easily accessed with a variety of modbus tools freely available online and changed to what you want.  No Unilogic programming needed at all.

cheers, Aus

I have already tried changing this through Unilogic program, with the wording on page 5, i am unsure what to do with the wiring? Do I need to use the green one? I have tried using this on the program, however when i have green connected I see no values on the screen from the sensor, but when it is not connected, I see values but then don't know if the sensor is in its setting mode.

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

3 hours ago, Ausman said:

The pdf you supplied shows that the parity can be changed in the sensor.  Bottom of page 8. 

It would be possible to do UniLogic programming to change the parity, you would simply need to add some code to do a write to the sensor instead of a read.  Once the change is done, you would then change Unilogic to whatever parity you decided to use for both sensors and perhaps the code could sit in readiness for next use, or be deleted.

To me, your easiest way of doing this is to connect to the sensor by using a RS 485 port on your PC.  The parity register can then be easily accessed with a variety of modbus tools freely available online and changed to what you want.  No Unilogic programming needed at all.

cheers, Aus

Thanks for the reply, do you have any links to online software you have used?

[Changing sensor parity through MODBUS RTU on a US5-B10-RA28]

I have a US5-B10-RA28 with a UAC-CX-01RS4 card fitted onto the back.

I have 2 sensors needing to be wired to fit the PLC Program, however the 2 sensors have a different default parity value, meaning they don't work together and only work when I set the 01RS4 card in unilogic program to either Parity = None for one sensor and Parity = Even for the other sensor. This however is not suitable for my application as I constantly have to redownload the project to the PLC changing the parity value for the module to get one sensor running.

 

So my question/ help needed is how can I change the Parity value of the sensor below, and is there a way of doing this through unilogic?

 

Thanks

Soil Moisture & Temperature Sensor User Manual-S-Soil MT-02.pdf

[SM35-J-RA22 Factory Boot Error]

Hello,

 

I have this SM35-J-RA22 PLC and it has this error appearing on it, it was working before it got sent off with a program to a customer and then when switching on for the first time their end, this screen occurred. I've tried having a look through Forums but can't seem to find anything on how to fix this issue on a Samba>

 

Can anyone help?

Thanks

[V350-J-RA22 Analog Inputs failing]

10 hours ago, sgull said:

Can you share the details of the two wire sensor you are using?

 

Sensors_CD7_PES7_OZ7_WP7_EN.pdf OZ7 Sensor 24-3-21.pdf

[V350-J-RA22 Analog Inputs failing]

12 minutes ago, kratmel said:

What you have encountered is a constant problem in PLCs with current input.

When connecting the sensor, the user can accidentally short-circuit the 4-20mA line with the +24V power line. It can also be during the operation of the sensor - for example, someone cut the cable. The consequences are like yours. For a load of 37 Ω +24 V creates an overcurrent of 0.6 A. This is a complete annihilation of the analog input.

Standard question - what to do?

I have two solutions for such cases:

1. An expensive solution is to use an external galvanically decoupled analog signal to analog 4-20mA to 4-20mA or 4-20mA to 0-10V converter.

2. A cheap solution is to buy a high-precision 500Ω resistor and connect it between the 0V ground and the analog input turned on in the 0-10V mode. We read values in the range of 2-10V - which corresponds to the range of 4-20mA for the sensor you need. In the event of a short circuit, you will see smoke from the resistor if its power is less than 2W. Usually, the analog input in the 0-10V mode from +24V does not suffer.

I also encountered 220VAC applied to the analog input - the consequences are even more terrible - the PLC usually breaks if the analog inputs are not isolated. And even if they are insulated - there is a lot of smoke!!!

Another case is when the wires to the analog inputs pass close to the frequency converter... The problems are also significant - sometimes it ends fatally.

 

P.S. Most recently, I had a case with a new module EX-D16A3-TO16 where user destroyed three current inputs in a row - because I said that in case of problems with one, there are two more spare and I made a software switch for redundancy - it did not help.

Thanks for the reply, we also tried this solution of a software switch to be able to utilise both inputs, however we have now gone through about 3 V350s with all the Analog inputs not working, we have bought a 

S1SL-1AI-1C

Signal conditioner

we have tested it wired up with a signal generator to the PLC but not yet to the complete system with the actual 2 wire sensor, but am unsure yet to if this is the right product/ will work?

 We have wired the PLC for the customer so I doubt the issue is them shorting the 4-20mA line with +24V, and for it to happen now to 5 analog inputs is baffling, so we shall try the signal conditioner we bought and see if that resolves the issue, if not, we will have to try your other solution!

Thanks again

[V350-J-RA22 Analog Inputs failing]

I have a job using a V350-J-RA22 and use one of the analog inputs from a 2 wire sensor, the sensor has a 24v wire powering it and then a wire to the PLC sending 4-20mA.

However a recurring issue is happening which we cannot fault find the reason why, where the analog inputs are blowing/ stop working.

Our only thought is to do with the datasheet as highlighted where it says max input rating 1.1V, and were sending into the PLC around 6V or so.

So if this is the issue how do I go about stopping this from happening in future/ why is it not seeming to be an issue when I've done a similar program with sensor on a unistream.

And if this is not the issue, what could be causing the analog inputs to stop working from the 2 wire sensor we have?

[CANBUS - CANopen - Posital Encoder set up]

Hello,

I am relatively new to Unilogic and completely new to CANBUS, and I have a project that requires 2 encoders a single turn and a multi turn encoder.

My struggle is with the software and how to generate the position values for the encoder onto the PLC, I have followed all the help guides etc and have uploaded the manufacturer EDS Files for the encoders, but I currently seem unable to get a reading onto the PLC HMI. And I cannot for the life of me figure out what I'm missing or have done wrong.

Can anyone help or have any tutorial videos for if I'm missing anything in the Ladder logic or in the CANopen set up.

Thanks