Vision & Samba PLC + HMI Controllers & VisiLogic Software
Welcome to the Vision and Samba series forum
Talk about issues related to the Vision and Samba PLC + HMI series and to VisiLogic software
3,896 topics in this forum
-
- 9 replies
- 1.4k views
-
- 5 replies
- 2.4k views
-
- 3 replies
- 2.1k views
-
- 8 replies
- 2.2k views
-
- 2 replies
- 1.9k views
-
- 1 reply
- 990 views
-
- 2 replies
- 1.3k views
-
- 3 replies
- 2.6k views
-
- 1 reply
- 1.2k views
-
- 3 replies
- 1.3k views
-
- 11 replies
- 3.7k views
-
- 10 replies
- 4.8k views
-
- 4 replies
- 4.3k views
-
- 3 replies
- 1.6k views
-
- 5 replies
- 2.5k views
-
- 5 replies
- 1.3k views
-
- 2 replies
- 1.2k views
-
- 3 replies
- 1.7k views
-
- 3 replies
- 1.2k views
-
- 17 replies
- 3k views
-
- 1 reply
- 927 views
-
- 4 replies
- 1.3k views
-
- 6 replies
- 1.5k views
-
- 3 replies
- 1.7k views
-
- 3 replies
- 1.7k views
-
Member Statistics
8,502
Total Members1,206
Most Online
-
Topics
-
-
Who's Online (See full list)
-
Posts
-
First of all, I think you probably know that working with visilogic over port1 disables port1 from working over other protocols. Even when using the USB port, we must remember that it is still a busy port1 (but through the USB - COM adapter in the PLC). The second point - for communications with the outside world, it is necessary to take into account the galvanic separation of the port and the common grounding of the devices. A high potential between two devices connected to the rs485 network can destroy the receiver-transmitter of the signal, which is not galvanically isolated. Therefore, I practice to always use the isolated version of the rs485 port card for communication with external devices. P/S. As a hardware check, you can compare the RS485 outputs pin of the connection of the working and non-working ports relative to the common point (GND for RS232) using the tester. -
Few days ago I had this happen to me a second time: Vision RS-485 doesn't seem to work on COM1 port. First time it was a V570. I connected COM1 port to a VFD using RS-485 pins 1 and 6 on 6P6C connector. Speed was 9600 bps. The communication didn't work. It started working when I connected it to COM2 port. Second time it was a V700. I connected COM1 port to several transmitters using Modbus RTU. Speed was 9600 bps. Nothing worked. The problem was not in the software, because I connected COM1 port using RS-232 to my PC with a Modbus slave simulator, and Modbus comms worked perfectly fine over RS-232. So definitely it's something in the port hardware or in the OS of Visions. I've checked the DIP switches, and tried both termination on and off. Total cable length doesn't exceed 1 meter. I've tried with external 120 ohm termination resistors on and off. Double checked port initialization, nothing. Nothing made RS-485 work on COM1 port. COM2 add-on port work fine with RS-485. What could I be doing wrong? Has anyone else had a similar problem? What could be the workaround? Maybe the 9600bps is too high speed? -
Great, thanks for this! Should be pinned.
-
For me, layers introduce another variable to need to keep track of when editing Also, I would now want to name all elements in the title section to keep the layer section organized I keep all my elements titles at default (button 6 / fixed text 14 / binary image variable 4 / etc.) I can see the benefit of using layers depending on the page being created, I mean it would keep all elements better organized Most of my HMI pages don't have enough overlapping images to justify setting layers vs. send to back / bring to front I may try using layers going forward at some point for a screen with lots of overlapping elements -
By curtharrington1 · Posted
you could make your own block and then call it whenever you need: FUN_isArryBit.ulle
-
-
Blog Entries
-
