Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - monteran

Pages: [1]
1
Hi again Archie,

I was mistaken in my announcement last time - in between our messages I had nullified the IP address of the PLC to test the interface and I forgot to set it back to the proper IP before saying that 3.99w had fixed the issue.

I just applied this patched DLL to my release build and it seems to solve the problem! Thank you for your help. I'll be sure to include this with the program as I hand off the project over the next few days.

2
Thanks Archie. I'll try applying the patch and testing the system over the next few days before I hand it off to the next user. I've been writing up my documentation and checking the program here and there throughout the day - the 3.99w update has prevented it from stalling so far with the PLC disconnected. Haven't had a chance to run it in the lab yet but I'll try to give you an update before the end of the week.

Thanks so much for your help. This software has been a real lifesaver for a computer science focused guy like me.

3
No, I was using whichever version was around in December last year.

I downloaded a copy of 3.99w. I'll try migrating and see if that helps with the issue. Just a little nervous of the problems that might cause since I'm a few days away from a deadline on this project. But that's life, I guess.

Ok, at a quick glance the issue seems to be resolved with this migration. I still get a bit of hang when switching to those tabs initially, but it looks like its about 2 seconds which I would probably expect with the default EthernetCLX properties here.

I'll try running it through some tests when I get in with the device later today. Thanks for the suggestion!

4
Hi Archie, thanks for your attention.

When I pause during debugging it rests within the SubscribeToComDriver() function, specifically on line 146 - Dim NotificiationID As Integer ....

In your reproduction attempt you mentioned have you put some of the basic labels on a second tab? Specifically not the default tab on application launch? This is where I am seeing the issue. Tabs 1,5,6, and 7 of my application are fine, but the three in the middle with labels are the ones that lock up.



I just tried disabling the subscriptions from the EthernetIPforCLXCom1 object and there is no issue there at that point. But of course that will be a problem when the PLC is connected.

5
Hi all,

After some more testing I think I found the set of conditions that has been causing a freezing problem with my AdvancedHMI project.

I have an interface made up of regular visual basic tab controls. When I start the project with no PLC connected everything is fine, a label on the left outside of the tab control says no PLC is connected, etc. I can click on tabs that do not have basic labels on them and they also work just fine. However, the moment I click on a tab that has basic labels it appears as if they try to fetch their update text from the PLC. From then on the program is frozen.

This is a bit of a problem for me because our program is intended to be used for other tasks besides simply controlling the PLC. Any advice on how to bypass this issue would be appreciated!

6
Support Questions / Re: Freezing when run without a PLC connected
« on: April 10, 2017, 09:09:55 PM »
Thank you bachpi. That works well for the few places that I have implemented so far.

Is there a way that I can use a DataSubscriber to monitor the change of a tag without it triggering on the initial startup of the program? I have a "test finished" flag that I set and I want to do some Excel generation after that flag is set, but it will call my function even when I just happen to turn on the program to a PLC that already has the flag high.

I guess I can just use a "last state" and "current state" variable or something.

7
Support Questions / Freezing when run without a PLC connected
« on: April 06, 2017, 04:03:16 PM »
I have an AdvancedHMI solution I am working with that has been a great help for me and my workflow the past few months. I am wrapping up a project and trying to iron out a few little hindrances before I call it a day and hand off the project to the next guy.

Specifically, one issue I have had is that when I debug the software on a PC that is not connected to the our AB CompactLogix PLC via Ethernet, after a few seconds the application will freeze and need to be restarted. No exceptions or anything seem to be called, and currently all of our code that reads from the PLC is handled in functions tied to buttons. Without touching any of those buttons, the various AdvancedHMI labels will show their typical errors and then the program stalls.

One detail I would like to clean up to figure out how to ensure that the program remains responsive when the PLC is not detected. In the worse case I can try and put up a error box to the user that allows them to know what the issue is. Both would be fine solutions, I suppose. I'm now in the "cleanup" phase where I'm adding in the necessary exception handling and other important usability items.

Any tips or tricks from the community would be appreciated. I certainly couldn't have gotten this system working without this forum.

Pages: [1]