Thanks for your support Dear Kauquappe and Duris,

1.  Yes, I did not put termination resistor so i put it but found same problem.
2. I checked the function code in "y_Fcode" parameter i.e. 2 . so it was confirmed that function code is correct as per slave parameter specification.
3. Kindly find the attachment for modbus slave specification and please guide if any changes are required.
4. Now i dont have the RS485 to 232 converter with me. once it will be available i can also share the snap shot.

Hello,

pls again confirm (I've asked this in first post), your Slaves has same communication settings (speed, stop bits,...)? Because if not, this is problem. I expect you're using one comm board CB and if your Slaves have different comm settings you need then make some reconfiguration of port settings due your required Slave data.

Update: sry, can you tell us for which reason you want converter to RS-232? Your Slaves are RS-485 fitted, can you confirm?

Thanks for your support!!

1. I have checked in Modscan there is no err. find attachments

2. I discussed about RS 485 to USB coverter. 

till now i could not find the problem.

Thanks and regards,

Prasanna

Hello,

attachment? Pls zip all pictures that can show your situation, simply I can't remember after some time all...

Update: or your problem is solved? Sry for possible missunderstanding...

thanks for your response dear Duris...

Problem was not solved . 

please find attachments

Hello,

have made quick look and see one important difference - you need use 2 stop bits in comm settings, hope I good understand this because you've post this as required from manufacturer. In your settings you have only one stop bit (in Modscan??). If this is problem, that error STATUS simply point to this, also what we discussed already as not correct comm settings.

Update: also important info about parity bit set is missing...

Dear Duris,

                     Thanks for your support !!!

                     1. Stop bits: I have verified it and i checked by putting it 1 or 2, same problem found.

                      2. Pairity: I have been observed that modscan is recieving data if parity is either odd or even. so i kept the pairity as 1 or 2 and checked.

Regards,

Prasanna

Hello,

yes, but check again all settings in real Slave device, this is important. Hope you've checked this.

Update: can you pls give info about exact type (order number/name) of that problematic real Slave device? Hope it doesn't use other type of Modbus protocol...

Was the issue solved?

Possible to share the outcome/result?