...I have a project...what hardware do I need?
Ask the Unitronics staff for recommendations regarding controller type, I/O configuration, and communication methods.
142 topics in this forum
-
- 1 reply
- 166 views
-
- 2 replies
- 652 views
-
- 2 replies
- 581 views
-
- 10 replies
- 2.9k views
-
- 1 reply
- 388 views
-
- 2 replies
- 1.2k views
-
- 3 replies
- 1.5k views
-
- 1 reply
- 499 views
-
- 1 reply
- 354 views
-
- 2 replies
- 995 views
-
- 8 replies
- 1.4k views
-
- 2 replies
- 863 views
-
- 1 reply
- 1k views
-
- 10 replies
- 1.8k views
-
- 5 replies
- 1.6k views
-
- 2 replies
- 795 views
-
- 1 reply
- 823 views
-
- 1 reply
- 722 views
-
- 8 replies
- 1k views
-
- 5 replies
- 1.2k views
-
- 5 replies
- 1.1k views
-
- 4 replies
- 1k views
-
- 1 reply
- 2.1k views
-
- 3 replies
- 987 views
-
- 2 replies
- 870 views
-
Member Statistics
8,980
Total Members1,206
Most Online
-
Topics
-
-
Who's Online (See full list)
-
Posts
-
Is it possible to use ucr router with m91 with the rs-232 port? I would like to remote access to my m91 with unicloud -
By Punt Systems · Posted
Hi Kratmel, Of course I have read that topic. The problem with the 'ModBus address access limitation' solution is, that it does not protect you against writing. If you make an operand readable, you can also write to it, and that is a risk. Best regards George -
-
By Punt Systems · Posted
Although it seems a common belief that you cannot block Modbus write due to the way it’s engineered in the Unitronics PLC's, there certainly is a way to achieve this. You have to look at SL11. where every Modbus command is processed. It looks like that the value in SL11 makes no sense at all, until you attach a “Vector fill” to it. Then each Modbus function becomes a specific value in MI 1240 (example). After that, it’s very easy to specifically allow or block a command (both 'read' and 'write') or an entire function. In this specific case you can read everything, but as soon as you give a write command, it must be 1 of the 8 values, otherwise the Modbus connection is stopped immediately, to prevent anyone from being able to continue. After that you can decide to display or send out a warning (or whatever) The only small downside to this solution is . . . . although it will be detected (for sure) . . . . . you could still make 1 'write command' mistake (If you hit the jackpot). This is tested with Modbus TCP/IP only, if you have Modbus RTU, you probably will need to edit a couple of things (I did not test that yet) There is a timer TD 153 (example) present, because of a timing issue, when switching from one Modbus function to another, to prevent unwanted blocking of the Modbus scan. But if you don’t allow any Modbus write command, a timer is not needed and MB 1703 (example) can do the job for you. Another tip: For anyone who wants to use a Samba with an ethernet card and still wants to have the option of Modbus RTU or any other situation with only Modus TCP/IP supported, you can use a simple module TCP2RTU from papouch.com. Example ladder with TCP2RTU: -
Hi Ausman, thank's a lot for taking time. I checked again, The dip switch of the last valve for the terminating resistor is set. What I do next is asking the supplier why signal cable is not drilled and shielded. It was included in the package..I would also like to measure the signal quality... Cheers Joachim
-
-
Blog Entries
-
