
adccommunitymod (AutomationDirect) asked a question.
Created Date: March 21,2010
Created By: davidd
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I'm using Lookout 4.5.1 inside a Windows XP virtual machine running in Virtual Box on Windows 7. The only problem I 've run into is related to the PLC communications link. I'm connecting to a DL 205. After being connected to the PLC for 15-30 minutes I seem to lose connectivity. Lookout alarms do not sound but the SP4 status bit stops flashing. I also see no updates on the HMI when data is changing in the PLC. Buttons in the Lookout HMI do continue to change connected coils, etc in the PLC, however. The method I 've found to correct the problem is to modify the DL object, configure the com link, and remove the check box next to "link enabled " and the immediately re-check it. I close the dialog windows and everything is back to normal. Has anyone seen anything like this before? I fear it may be a problem related to running Lookout inside the vBox virtual machine. I have also noticed that the network connection (bridged to the physical NIC) displays 'limited or no connectivity. ' If I try to use NAT the PLC link is not detected. Perhaps I need to setup the link manually to use it that way? DirectSOFT5 is running on this same XP VM with no problems the entire time. I do have two separate links setup so that Lookout and DirectSOFT are not sharing the same link. Thanks for any help, David
Created Date: March 21,2010
Created by: davidd
I'm using Lookout 4.5.1 inside a Windows XP virtual machine running in Virtual Box on Windows 7. The only problem I 've run into is related to the PLC communications link.
I'm connecting to a DL 205. After being connected to the PLC for 15-30 minutes I seem to lose connectivity. Lookout alarms do not sound but the SP4 status bit stops flashing. I also see no updates on the HMI when data is changing in the PLC. Buttons in the Lookout HMI do continue to change connected coils, etc in the PLC, however.
The method I 've found to correct the problem is to modify the DL object, configure the com link, and remove the check box next to "link enabled " and the immediately re-check it. I close the dialog windows and everything is back to normal.
Has anyone seen anything like this before?
I fear it may be a problem related to running Lookout inside the vBox virtual machine. I have also noticed that the network connection (bridged to the physical NIC) displays 'limited or no connectivity. ' If I try to use NAT the PLC link is not detected. Perhaps I need to setup the link manually to use it that way?
DirectSOFT5 is running on this same XP VM with no problems the entire time. I do have two separate links setup so that Lookout and DirectSOFT are not sharing the same link.
Thanks for any help,
David