Messages

1

Support Questions / Web Viewing

« on: August 18, 2016, 04:31:51 PM »

Has anyone successfully setup an Advanced HMI application for web viewing? Is this even possible? Perhaps with MVC?

2

Support Questions / Re: 399a Missing Components from AdvancedHMI

« on: October 29, 2015, 09:07:01 AM »

Yes I do

3

Support Questions / Re: 399a Missing Components from AdvancedHMI

« on: October 28, 2015, 04:41:01 PM »

Still no dice

4

Support Questions / Re: 399a Missing Components from AdvancedHMI

« on: October 28, 2015, 04:29:35 PM »

I did as suggested. Same results.

5

Support Questions / 399a Missing Components from AdvancedHMI

« on: October 28, 2015, 10:18:07 AM »

I have a project that I had built in version 398s, but I was having some issues with too many items being written at once that were addressed in 399a. Everything was working last week, but today when I open the project in VS2013 to make some additional changes, most of my forms are no longer able to be opened in design mode. I am getting the following message:

Missing Components from AdvancedHMI. C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\
Instances of this error (1) 
 
1.   Hide Call Stack
 
at MfgControl.AdvancedHMI.Drivers.CIP..ctor()
at MfgControl.AdvancedHMI.Drivers.CIPforPCCC..ctor()
at AdvancedHMIDrivers.EthernetIPforSLCMicroCom.CreateDLLInstance() in C:\Office_Stuff\AdvancedHMI\PrebuiltStartPackage\AdvancedHMIDrivers\AllenBradley\EthernetIPforSLCMicroCom.vb:line 103
at AdvancedHMIDrivers.EthernetIPforSLCMicroCom.set_IPAddress(String value) in C:\Office_Stuff\AdvancedHMI\PrebuiltStartPackage\AdvancedHMIDrivers\AllenBradley\EthernetIPforSLCMicroCom.vb:line 196
at MfgControl.AdvancedHMI.frmControls.InitializeComponent() in C:\Office_Stuff\ALR_Cutter\PB_AllRubberCutter_2_0\AdvancedHMI\frmControls.Designer.vb:line 235
at MfgControl.AdvancedHMI.frmControls..ctor() 

In my project there are 6 forms, 2 of which open without any errors and 4 give this same error. The forms that are giving the errors all are built to inherit one of the working forms. The reason for this is the main PLC I am connecting to has a very limited number of connections that it will accept, so to reduce the number of connections that are being made as well as keep it from lagging as it tries to make a new connection while it changes forms, I have my PLC Connection (ModbusTCP for a TrioPLC) made on one form that has the majority of the controls that need to be on the other forms and then the other forms just inherit that form so only the one connection is being made. There is also a second PLC connection (EthernetIPforSLCMicroCom for a MicroLogix PLC) on this same form. This appeared to work fine in 398s (although the second connection in 399 had to be recreated as it was EthernetIPforPLCSLCMicroCom in the the previous version) and like I said, this worked fine in 399a originally as it worked the last time I had the project opened. Now I am getting these errors.

I tried adding the
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\" into my project reference paths, but this did not help.

Something just doesn't seem to be right with the inheriting forms, but I have no idea why it would just stop.

Thoughts?

Thanks,
Jeremiah

6

Support Questions / Re: Modbus TCP - Send Que Full

« on: September 25, 2015, 04:47:21 PM »

That did the trick...mostly. I loaded 5 sets of recipes and the 3rd recipe gave the error. 20% failure is much better than 100%. I may be able to limp by until the new version with the fix is available.

7

Support Questions / Re: Modbus TCP - Send Que Full

« on: September 25, 2015, 02:08:59 PM »

Thanks Archie. I'll give that a shot.

8

Support Questions / Modbus TCP - Send Que Full

« on: September 25, 2015, 01:20:42 PM »

I have an application that is replacing an old Wonderware application. There are about 45 recipe parameters I have to send to the PLC which currently works in the Legacy application. The new AdvancedHMI application must be writing too fast as now when I try to write the recipe parameters down, I am getting the "Send que full, may have lost connection or data request too fast" error. I have changed the PollRateOverride on the PLC Driver to 500 and then again to 1000, but the results were the same. I have added a System.Threading.Thread.Sleep(50) after every 10 recipes I write, and I still get the error. My assembly version is 3.9.8.18

Is there something else I might be able to try? I am really at a loss.

Thanks,
Jeremiah

9

Support Questions / Re: Modbus TCP - Check for Connectivity on Launch

« on: August 07, 2015, 03:24:32 PM »

Perfect! Thanks Archie!

10

Support Questions / Re: Modbus TCP - Check for Connectivity on Launch

« on: August 07, 2015, 02:38:08 PM »

I'll give that a shot. Is there not a way to just check for connectivity? There may be many reasons why it couldn't read, but what I'm looking for specifically is to check for connectivity before it tries to read.

11

Support Questions / Re: Modbus TCP - Check for Connectivity on Launch

« on: August 07, 2015, 02:03:11 PM »

Ok, I stand corrected. I thought it was the visual controls that were throwing the exception, but that is not the case. I have a couple of timers in my code that are running and they are reading from the PLC. So, I guess a better question to ask is "What do I need to add to my code to check if the connection is there before it tries to read and errors out?

12

Support Questions / Re: Modbus TCP - Check for Connectivity on Launch

« on: August 07, 2015, 11:46:02 AM »

The visual controls

13

Support Questions / Modbus TCP - Check for Connectivity on Launch

« on: August 07, 2015, 10:22:28 AM »

I have an application that is connecting via Modbus TCP. If the PLC is not on the network, which happens frequently, the application throws an exception as it can't read from the PLC. I'm looking for a way to check for connectivity before it loads everything else so that I can send them a message and close the application gracefully rather than the standard exception message.

14

Support Questions / Re: Modbus TCP - No Response from PLC(21)

« on: July 12, 2015, 10:52:28 PM »

This is now working! I don't have a reason as to why aside from the fact that I rebooted my computer. Thank you all for your time as you have been very helpful and I can't express my gratitude enough.

15

Support Questions / Re: Modbus TCP - No Response from PLC(21)

« on: July 12, 2015, 10:46:10 AM »

The machine touchscreen also communicates to the PLC, but that is it. The PLC can accept 2 connections at once so this shouldn't be an issue as it still leaves a connection for this project.