- #Rslinx classic lite a signed driver is required serial
- #Rslinx classic lite a signed driver is required drivers
- #Rslinx classic lite a signed driver is required software
- #Rslinx classic lite a signed driver is required Offline
Perhaps the IP address the computer is using is being used by another device.
Do you see any flashing lights there when the cable is connected? The indicator you mentioned seeing on the hub is a good sign though. Some computers have an activity light right next to the ethernet connection. Have you tried another port on the hub? How about a different hub?
Have you tried a different cable? Do you have a cable tester? But for now, let's say it cannot be done. The advice others have mentioned on addressing ranges should be implemented. If that is not the case, and this equipment does connect to a plant network, then step back and get your IT/IS department in there to resolve this issue. If this is a stand-alone network that in no way connects to a plant/corporate metwork you should be ok. Forget everything else until you get PING to work.
#Rslinx classic lite a signed driver is required software
Ok then, so lets set aside the RA software for a moment as you have a network issue that has to be resolved. I have not pinged the panelview but i could try that. I get message timeouts when i try to ping the processor and i have not yet tried to turnoff the wifi. Always use addresses in the private IP ranges: .xx, 10.xx.xx.xx, 172.16.xx.xx thru 172.31.xx.xx If this is ever in any way connected to the Internet, you have a potential for a strange bug. Ken's observation that you are using a public IP address is troublesome. Especially when a good industrial 5 port 10/100 switch can be had for less than $100. And if any one Ethernet device is running at 10K bits, the whole network slows to a 10k rate. Hubs are bad news in a control network: they promiscuously broadcast everything to every device. Pardon me while I hop on my soapbox now :-)Īnd I hope nobody is planning on leaving a hub, much less a cheapo Linksys device, in a control network. And there is NEVER a reason to have a mask any wider that 255.255.255.0 in a control network. All those devices need to be in the same domain: all in 192.168.1.xx, for example (assuming the mask is 255.255.255.0). Keep in mind that a hub or unmanaged switch can only service one domain at a time: if you have some devices at 198.213.62.xx and others at, say, 192.168.1.xx your behavior will be crazy intermittent. What else is connected to the hub? At what IP addresses and masks? A HUB, rather than a switch, and a public IP address rather than a private IP address.
#Rslinx classic lite a signed driver is required serial
Do you have any other software on your machine that makes use of the computer serial port? Perhaps rebooting the PC, if you haven't done so recently, would free up your computer serial port. It looks like the reverse could be true here. Usually RSLinx is the culprit taking over your serial port so another package cannot use it. The serial port cannot be shared between multiple software packages like ethernet can. More concerning though, is that it is possible some other software on your computer may have taken over the serial port so RSLinx cannot access it. For the SLC it will read slc-cho/micro/panelview.
The device setting will set itself once you successfully complete the auto-configure.
#Rslinx classic lite a signed driver is required drivers
There are other drivers that can conflict, but not the ethernet one. Your ethernet driver won't conflict with the serial driver so it can run side by side. If set to ASCII, then we cannot use the serial port for communications.
#Rslinx classic lite a signed driver is required Offline
Your offline file tells us the port is setup so we should be able to talk to it, but Mickey brings up a really important setting. Until you get auto-configuration successful, and a RUNNING driver in your driver list, forget about RSLogix500, it won't communicate. I have noticed that some drivers can't be stopped, only deleted. If you can't stop this driver, then make sure you haven't got the RS-Who window open, and you are browsing this branch of the tree. If you don't auto-configure successfully, then there may be another RSLinx driver got hold of the COM port on your laptop. Once the driver is installed and running OK, it announces itself as AB_DF1-1 DH+ Sta.0 COM1 RUNNING in your configured drivers list. If you get Auto-configuration Successful response then all is well, and the driver should work with RSLogix500 - I've never seen it not work. The driver you need in RSLinx is called RS-232 DF1 Devices.Ĭonnect your cable to the SLC, and in RSLInx add a new RS-232 DF1 Devices Driver, don't do anything else except click on Auto-Configure. Channel 0 on the 5/04 is an RS-232 serial port.
0 kommentar(er)
