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,913 topics in this forum
-
- 7 replies
- 1.1k views
-
- 3 replies
- 600 views
-
- 4 replies
- 544 views
-
- 0 replies
- 311 views
-
- 5 replies
- 880 views
-
- 4 replies
- 1.2k views
-
- 2 replies
- 653 views
-
- 3 replies
- 2.7k views
-
- 16 replies
- 1.5k views
-
- 3 replies
- 832 views
-
- 15 replies
- 1.4k views
-
- 3 replies
- 2.8k views
-
- 2 replies
- 776 views
-
- 3 replies
- 914 views
-
- 12 replies
- 1.2k views
-
- 1 reply
- 1.2k views
-
- 6 replies
- 1k views
-
- 5 replies
- 599 views
-
- 2 replies
- 570 views
-
- 2 replies
- 501 views
-
- 0 replies
- 825 views
-
- 6 replies
- 529 views
-
- 1 reply
- 381 views
-
- 4 replies
- 667 views
-
- 0 replies
- 281 views
-
Member Statistics
8,752
Total Members1,206
Most Online
-
Topics
-
-
Who's Online (See full list)
-
Posts
-
Personally I wouldn't use this subnet for anything of interest on my networks. Here's why. 169.254.0.0/16 (169.254.0.0 – 169.254.255.255) These addresses are “link local,” which means packets with these addresses are sent out to the network, but should never be forwarded to other parts of the network. You’ll often see addresses from this range if a device is unable to get an address using DHCP. Then it simply takes an address from this range and uses it to try to at least communicate locally. Any local device that can't get to the DHCP could, simply by chance, get assigned in this subnet and that could be what you're pinging. -
I know it depends on how you are connecting, but is all of this correct and not missing needed info? -
OK on doing it as admin. I don't think it's a W10 issue, it might be an A/V issue. You could try turning your A/V off to see if it changes things, but I think your best course of action is to contact support direct. https://support.unitronics.com/index.php Please remember that we are volunteers here, Support is Unitronics staff, and they often resolve issues by doing a remote connection session with you. If the issue gets solved please advise the cause and fix. cheers, Aus
-
PLC Version, UniLogic Version, is this PLC new or it used to have an older firmware version and then it was updated? Did it used to work but now it doesn't? (If it so, why did it stop communicating). Did you give the PLC the IP: 169.254.100.1? (Is it by a project that was downloaded to it, or by configuring the IP in the UniApps?) -
By h1rik_fryd · Posted
Hello guys, Im having trouble connecting to my PLC via Ethernet. When I ping my PLC IP address (169.254.1.100) in cmd I get replys every time, but when I try to connect to the PLC in Unilogic, this IP doesnt work. I have my computer IP set to 169.254.1.121, subnet to 255.255.255.0. The IP in the PLC panel is set to 169.254.1.100, subnet is 255.255.255.0. The IP in the PLC CPU is set to 169.254.1.99, subnet is 255.255.255.0. Could the reason for the problem be differences in software maybe? Or is it something else Im missing?
-
-
Blog Entries
-
