“connection at startup” is still TRUE. Change it to FALSE an re-initialize the modbus block. This is an init parameter and is only taken over, when the block is initiated.

Did you re-initialize the modbus block? In online IDB this internal parameter is still TRUE. Attach the new online-IDB as printed pdf.

Without the complete Online-IDB it is hard to find the reason. DONE and ERROR counter are 0, so no telegram is handled. 
What happens when you set ENQ_ENR = TRUE now via VAT? In STATUS there must be a change. 
Do you also use the connection ID = 1 for another communciation function? ID must be used only for this one modbus block, for no other block. Can you attach the wireshark-Trace of the telegram (query and response)?

Strange port numbers… Normally the modbus server has port number 502.  It it seems this is not a modbus telegram, I can't see the modbus header…
Please attach the parameter datablock. 
You can also copy the modbus block, the OB1, the online datablock and the parameter datablock into an additional project, zip and attach here. 

I need the information in the Online IDB of the modbus block and in the parameter DB. To make screenshots of all pages is to time intensiv, I think. So the idea is, that you copy the online blocks into another project to send me.
If you have time, you can also make many, many screenshots. ;-)

Almost… :-)
You parameterized the modbus block as a client (active partner), so you should make screenshots from “iMOD_CLI…”, not “iMOD_SERV”. It is sure, that the communciation partner is parameterized as a server?
And please a screenshot from online parameter db from adress 130.0 (ID1_send_buffer - 1 page) and from ID_recv_buffer. Then it is possible to see, if any byte is sent and received.

Check if TSEND is a part of your project and has the correct FB number. I don't see any action of TSEND. In properties of the modbus block you see, which FB numbers are called. These FB numbers must be used for TSEND, TRCV and so on. If you use another FB with the number of the TSEND block, which the modbus block calls, then it doesn't work.

FB numbers and symbols must be the same like in the modbus block property. When you change the names or the FB numbers, that you have to rewire the FBs in the modbus block. Have a look at the manual, there is a chapter for rewiring of the internal called blocks.

yes, both has to fit. In chapter in manual it is described too

The best way is, to copy all modbus blocks and T blocks from the example project into another temporary project, rewire as described in manual and than copy all of these new blocks into your project. So it is sure that you don't change the existing blocks, which you are using in other OBs or FBs.