adccommunitymod (AutomationDirect) asked a question.
Created Date: September 24,2013
Created By: TonyJ
**** 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.****
Was just about finished up with my application with a DL105 and C-More HMI and was just adding a feature to have the PLC switch the HMI to the 'main ' screen after a delay if one of my system setup screens was displayed for more than 10 seconds without the user interaction. Apparently I miswrote the logic incorrectly to change the screen as after the delay period expired, the PLC communications to the HMI stopped and I can no longer communicate with DirectSoft. Cycling power doesn't work either - is there a way internally to dump the memory of the DL105? I used the non-volatile registers for the HMI to PLC interface which is why just cycling power doesn't work. Thanks in advance.
Created Date: September 24,2013
Created by: Do-more PE
Please contact technical support.
Created Date: September 24,2013
Created by: TonyJ
Was just about finished up with my application with a DL105 and C-More HMI and was just adding a feature to have the PLC switch the HMI to the 'main ' screen after a delay if one of my system setup screens was displayed for more than 10 seconds without the user interaction. Apparently I miswrote the logic incorrectly to change the screen as after the delay period expired, the PLC communications to the HMI stopped and I can no longer communicate with DirectSoft. Cycling power doesn't work either - is there a way internally to dump the memory of the DL105? I used the non-volatile registers for the HMI to PLC interface which is why just cycling power doesn't work. Thanks in advance.