Messages

1

Support Questions / Re: Issue on implementation of AdvancedHMI

« on: September 29, 2020, 07:31:34 AM »

That is what I plan to use in the end. 
I used the timer just as a quick test to confirm the I can access the register 'L' values and I am getting values from all the addresses.
It's just odd that I can't read the 'L' register values using just the BasicLabel properties.
All the other controls are working as expected. I'll just trigger my read off another value change event and see how that goes.
Thanks.

2

Support Questions / Re: Issue on implementation of AdvancedHMI

« on: September 28, 2020, 04:57:59 PM »

Yeah.
I did do that and the label was getting the correct value.

I am using a timer to query the addresses and write to a WinForm label and I am getting correct values.
Is there anything to look out for besides assigning the BasicLabel control a valid address?

Thanks for the quick response.

3

Support Questions / Issue on implementation of AdvancedHMI

« on: September 28, 2020, 01:39:59 PM »

Good day!
I am encountering an issue that I believe is not being caused by AdvancedHMI,
but rather my method of implementing it. If possible is there a recommendation to
a solution to the issue I am having. Any insight to a solution is much appreciated.
Let me know if there is any more information I can provide.
Thanks.

I am compiling my solutiion with .NET Framework 4.7.2
Visual Studio Professional version 16.7.3
AdvancedHMI Assembly Version 3.9.9.24

I have a solution that connects to an AllenBradley MicroLogix 1400 using
the EthernetIPforSLCMicroCom driver. I have the PollRateOverride set to 100 ms.

There are several AdvancedHMI controls I am using in the solution,
MomentaryButtons, PilotLights, DigitalPanelMeter and several BasicLabel controls.
The buttons and DigitalPanelMeters all work as expected.

The problem I am running into is the BasicLabel is not updating values from L registers
from the PLC. If I change the address to a valid N register address, it reads the value.
If I try to step through this source, after a minute, the program exits to Visual Studio
and states the application has entered break mode.

I created a program with a fresh copy of AdvancedHMI, added the PLC driver and a BasicLabel
and the BasicLabel reads the L value properly.

The error in debug is:
 
Managed Debugging Assistant 'ContextSwitchDeadlock'
  Message=Managed Debugging Assistant 'ContextSwitchDeadlock' :
  'The CLR has been unable to transition from COM context 0x1577c60 to COM context 0x1577ba8 for 60 seconds.
  The thread that owns the destination context/apartment is most likely either doing a non pumping wait or
  processing a very long running operation without pumping Windows messages. This situation generally has a
  negative performance impact and may even lead to the application becoming non responsive or memory usage
  accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads
  should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during
  long running operations.'

4

Support Questions / Re: Selecting drivers / controls for project

« on: February 14, 2018, 02:23:53 PM »

Ok, following pal's suggestion I was able to get 3.99 to work. I will proceed with this version and hopefully stop spamming the thread. Thanks, but I'm sure you haven't heard the last of me.

If it helps , I am using AHMI v 3.99r with 2010 sp1 . As Godra said ,  non - appearing drivers was a problem suspected to be in studio . Putting any driver from the toolbox onto your form and then building has always populated the rest of the drivers into the toolbox for me . You can then insert the driver you want and delete the 1st .
Archie , for me I still have not figured out how to deploy a small enough version of VB offline . The target machine has no internet connection , nor will it for security reasons .
Paul

5

Support Questions / Re: Selecting drivers / controls for project

« on: February 14, 2018, 02:07:21 PM »

Version 3.2.1.0.
I was able to get this version connected quickly and talking to the PLC.
I will try a more recent version working now that I have some of the kinks worked out.

Your above suggestion worked, thank you!
Is there a way to remove the extra driver that remained?

I am trying version 3.8.4.
The EthernetIPforPLCSLCCom1 driver is asking for a Port Number that the 3.2 version didn't require. Is this the correct driver to talk to an Allen-Bradley Micrologix 1400? I tried both 44818 and 2222 with no luck.

6

Support Questions / Re: Selecting drivers / controls for project

« on: February 14, 2018, 01:29:56 PM »

Well, not so fast.

I have added all my classes and forms to the AdvancedHMI project.
I add the EthernetIPforSLCMicroComm driver and as expected a control is added EthernetIPforSLCMicroComm1 to my form  and I configure the IP property to what I need. All good, compiles, no errors.

When I add the DigitalPanelMeter, another EthernetIPforSLCMicroComm control is added to my form.

This one is named "EthernetIPforSLCMicroComm" with a default IP that doesn't match my PLC IP address. And I can't change the IP address or delete the control unless I delete the DigitalPanelMeter and restart the solution.

Any thoughts as to why I can't add the DigitalPanelMeter without this extra EthernetIPforSLCMicroComm?

7

Support Questions / Re: Selecting drivers / controls for project

« on: February 14, 2018, 10:43:52 AM »

I was able to add my project and maintain all the controls in the toolbox.
I started with a fresh AdvancedHMIv3 solution.
Got everything working with this solution.
Added the references I needed for MyProject into AdvancedHMIv3 solution.
Added the classes, forms and resources from MyProject  into AdvancedHMIv3 solution.
Changed the startup form to the startup form in MyProject.
Added the driver to startup form -> recompiled.
All toolbox controls still available!

Thanks everyone for the help!

8

Support Questions / Re: Selecting drivers / controls for project

« on: February 14, 2018, 08:41:18 AM »

Just to confirm:
Listed in my References for MyProject I added into the AdvancedHMIv3 solution.
AdvancedHMI.exe
AdvancedHMIDrivers.dll
MfgControl.AdvancedHMI.Control.dll
MfgControl.AdvancedHMI.Drivers.dll

Is this listing correct? Is the AdvancedHMI.exe correct or should that be a dll?
I tried buidling the AdvancedHMIv3 solution prior to added MyProject.
I also tried adding it before building AdvancedHMIv3.

Under the Solution Set Startup Projects, should this be set as a Single startup project or Multiple startup projects?

My next step may be to import MyProject classes and forms one at time into the AdvancedHMIv3 and see if I can get that work.

If I open the MainForm.vb in the AdvancedHMI project, the toolbox lists the AHMI controls.
They are just not available when I open a form inside MyProject.

Thanks again for your assistance.

9

Support Questions / Re: Version 3.99 and VB 2010

« on: February 14, 2018, 08:10:47 AM »

Out of curiosity, why are you using VS2010 and not the latest version of 2017?

The software I am writing integrates with third party software deployments that have not been updated or tested with VB versions newer than 2010.

10

Support Questions / Re: Selecting drivers / controls for project

« on: February 13, 2018, 04:06:51 PM »

Very much appreciate the help.

I was able to Add my project to the AdvancedHMIv3 solution.
I added the EthernetIPforSLCMicroComm driver to my startup form.
Cleaned and Built the project - no errors.

The drivers show up in the toolbox.
When I go to Choose Items... I can see the list of AHMI controls, they are all checked. But, they aren't in the toolbox.
The references to add were the AdvancedHMIControls and AdvancedHMIDrivers Projects correct?
What can I do to get the controls into the toolbox?

11

Support Questions / Selecting drivers / controls for project

« on: February 13, 2018, 11:49:06 AM »

Is there a way to add to an existing project only selected drivers / controls?
For example, I only need EthernetIpforSLCMicroComm, DigitalPanelMeter, and SquareIlluminatedButton. I would like to add these to an already existing VB project that does not reference any AHMI components.

The entire AHMI source will of course be included on the system upon deployment.

12

Support Questions / Re: Version 3.99 and VB 2010

« on: February 13, 2018, 10:12:33 AM »

The version AHMI v3.8.4 came in without issue.
I will work with this version. Thanks for your help!

13

Support Questions / Re: Version 3.99 and VB 2010

« on: February 13, 2018, 09:45:30 AM »

I had not added drivers to the form yet. 

I added the OmronEthernetFINSCom1 driver to the form and the DigitalPanelMeter was able to be placed on the form without error. Thanks!
I tested several random controls and they were added to the form successfully.

How do I get the Allen-Bradley drivers to show up as choices in the Toolbox?

14

Support Questions / Version 3.99 and VB 2010

« on: February 13, 2018, 08:31:50 AM »

Good morning,
I downloaded and installed version 3.21 and was able to communicate with an Allen-Bradley Micrologx 1400.
I am using Visual Basic 2010 SP1 (I know, we need to upgrade) and .NET 4 Framework (Full).

I downloaded version 3.99 to try, opened the solution, built it without issue.
When I try to add the DigitalPanelMeter control to the form I receive this error:


Also, I am not seeing any of the Allen-Bradley com controls in the toolbox.
Is there anything I'm missing or should I go back to 3.21?
Thanks in advance for any suggestions.