Program locks up if connection is interrupted

[opmal7]

I'm using a Micrologix 1100 PLC with a tablet running AdvancedHMI 3.98t.

One of the issues that I've run into is that when the tablet screen is locked, the connection to the PLC gets disconnected.  Then when the screen is unlocked, the program locks up, and doesn't appear to be communicating with the PLC anymore.  If I exit the program, and restart it, the program works fine.

I was wondering if there is any way to prevent this from happening.  Or, if there is a way to make a button to re-establish the connection with the PLC.  Then I could make a popup dialog box saying "Connection interrupted, Click OK to re-establish the connection" or something along those lines.  Thanks.

[Archie]

Try using 3.99w

[qsiguy]

I'm on 3.99x and if the IP isn't correct when you start the HMI it locks up before I have a chance to update the IP from my on screen textbox.  Trying to figure out how to prevent this.  Any help would be appreciated.

[Archie]

I'm on 3.99x and if the IP isn't correct when you start the HMI it locks up before I have a chance to update the IP from my on screen textbox.  Trying to figure out how to prevent this.  Any help would be appreciated.

Try it on V3.99y Beta that you can download from this forum.

[qsiguy]

Thanks, I'll give that a try!

I did build a work around but would like it not to freeze up if it looses comms.

[qsiguy]

Try it on V3.99y Beta that you can download from this forum.

How do I migrate my project to 3.99y or does running the "AdvancedHMIv35.sln" file from 3.99y update my PC so when opening the project from the old folder opens with "y"?

I did try this from another thread and I get a bunch of "...not a member of..." errors

"As long as you don't cross over the 3.5 version update:

1) Open the newest version in Visual Studio
2) Right Click AdvancedHMI in Solution Explorer
3) Select Add->Existing Item
4) Browse to and select your .vb files (forms) from your previous project"

I added my MainForm.vb which is my only page. Is there something else I need to import using the Add function?

Thanks.

[qsiguy]

Anyone?  I'm sure I am missing some minor detail or I've over simplified adding just the MainForm.vb file.  It can't be that difficult to move my project from 'x' to 'y'.

One error I did notice was for an image file I had on my MainForm so that was easy to import manually. Since it didn't migrate the graphic over, there must be more to do to bring the project over than import the one .vb file?

[Archie]

Anyone?  I'm sure I am missing some minor detail or I've over simplified adding just the MainForm.vb file.  It can't be that difficult to move my project from 'x' to 'y'.

One error I did notice was for an image file I had on my MainForm so that was easy to import manually. Since it didn't migrate the graphic over, there must be more to do to bring the project over than import the one .vb file?

Can you post more details of at least one of the errors?

[qsiguy]

A screenshot seemed the easiest way to share what I'm seeing.

[Archie]

Open MainForm.designer.vb and do a Search and Replace for ".LightColors" to ".LightColorOption"

[qsiguy]

That seems to have cleared up quite a few.  Here's what is left.

Thanks for the assistance!

[Archie]

VisibleControlEnum -> VisibleControlOptions
ForeColoeAltername -> ForeColorAlternate

HighLightColor* and HighlightKey* -> delete each line completely. Those properties no longer exist.

[qsiguy]

Thank you very much, would have never figured that out on my own.  Some things are broken now as I was using those obsolete things but I think I can work with this.

Really appreciate it.

Shane

[qsiguy]

Unfortunately it still locks up if the Modbus TCP comm fails.

[qsiguy]

I have a couple "MessageByDisplayValue" functions that broke after that.  When I try to open the "Collection" to repair the messages Visual Studio shuts off and restarts.

Update:
I just copied the old ones from 399x and pasted them to 399y and it seems to have worked.