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
-
- 2 replies
- 1.1k views
-
- 6 replies
- 2.1k views
-
- 2 replies
- 2.4k views
-
- 15 replies
- 1.8k views
-
- 3 replies
- 818 views
-
- 4 replies
- 1.7k views
-
- 1 reply
- 1.5k views
-
- 2 replies
- 1.1k views
-
- 3 replies
- 1.2k views
-
- 1 reply
- 925 views
-
- 1 reply
- 1.2k views
-
- 1 reply
- 1.1k views
-
- 1 reply
- 656 views
-
- 4 replies
- 2k views
-
- 1 reply
- 1.3k views
-
- 11 replies
- 3k views
-
- 4 replies
- 2.9k views
-
- 5 replies
- 3.7k views
-
- 2 replies
- 1.1k views
-
- 2 replies
- 2.2k views
-
- 5 replies
- 1.9k views
-
- 3 replies
- 1.6k views
-
- 2 replies
- 568 views
-
- 3 replies
- 1.5k views
-
- 3 replies
- 3.3k views
-
Member Statistics
8,510
Total Members1,206
Most Online
-
Topics
-
-
Who's Online (See full list)
-
Posts
-
Do you mean that since you replaced CPU you don't have CPU errors anymore? Or do you mean that every time it occurs, you replace the CPU and reboot and then it works, but fails again a few weeks later with the replacement CPU? After CPU error occurs, rebooting again with same CPU works? If the issue happens always with same CPU, it can be because of a loose connection between CPU and panel. If it happens with different CPUs, please contact support so they'll guide you how to extract logs and send to us when it happens again. Hope this helps, Rivka -
I would be increasing your timeout in the ComInit to a few seconds, and also match your D10 to that amount. D10 & D2 are not shown here, but shift timeouts upwards and no retries to see if things work. If that then works, decrease your timeouts appropriately so that things are stable. Many people here do no retries at all, on the grounds that if it doesn't work, check it again in the next few lots of reads. However, I still wonder at your methods of testing. You may actually be using the 232 system, instead of the 485 pins on 1 & 6. Kratmel's ask is relevant...screenshots? Also, try changing your network ID to a number higher than 1 that isn't a number elsewhere in your network. -
Here! I am using COM1 for Modbus, and COM2 is unused at the moment (no serial port card) but I've initialized it. So, I connect a RJ11 (6P6C) cable to a SUB-D9 adapter and then to a USB-to-Serial adapter and to PC. This works because Vision serial ports enable RS-232 signals even if port is initialized in software as RS-485. On the PC I use these two software to test out the Modbus: 1. Modbus Slave by Witte Software 2. pyModSlave - free They both work fine, and I've been able to simulate Modbus traffic over COM2 and TCP/IP, with my PC acting as a slave device. -
Hi; As a note : Take all Grounds to 1 Point( localized area) as Kratmel illustrates. Do not Daisy Chain them. The noise just gets amplified as each ground is added ( more resistance) to the daisy chain, and can find a new less resistive route route( maybe thru the device) along its way. A single point ground will greatly reduce the chances of these electrons going back thru devices. They want to get "home " the easy way, less resistance the better. Milli Ohms do add up -- to trouble. DanT -
I am going to necro this thread being I am starting to have this issue. Currently using 1.33.210 and 1.33.273. In six months had 6 cpu errors in various places. All we been doing is sending a replacement cpu and then it works. So what could be causing this issue?
-
-
Blog Entries
-
