Messages

1

Support Questions / Re: Changing the Look of a Button

« on: March 04, 2024, 05:53:29 AM »

Thank you Archie that works very well.

2

Support Questions / Re: Changing the Look of a Button

« on: February 27, 2024, 06:32:16 AM »

Thanks Archie,

I am using the PLCAddressHighlightX and PLCAddressSelectTextAlternate to display reactions to the button press, these are basic Jog and Run buttons.

Is there an option/method to add a "Enable Forecolor" and "Enable Backcolor"?

Thanks

3

Support Questions / Changing the Look of a Button

« on: February 26, 2024, 08:02:15 AM »

Good Morning Everyone,

I have a working project that the operators are asking for a change.

I have several Basic Buttons that are Enabled and Disabled based on the machine condition.  The operators would like the Disabled state to be a different color as they are having trouble determining if the button is Disabled.

Is there some code I can add to the button to change the color when Disabled??

Thanks

4

Support Questions / Re: Adding Conditions

« on: February 23, 2024, 12:52:36 PM »

Thanks Archie,  I set it up like that and it works well.

5

Support Questions / Adding Conditions

« on: February 23, 2024, 10:13:47 AM »

Good Morning Everyone,

I have a program that works but I want to make the BasicButtons show and hide.
I can add PLC Addresses to the 'PLCAddressVisible' but cannot add multiple addresses.

is there a way to add additional 'PLCAddressVisible' addresses to the BasicButton code to accept multiple conditions??

I don't have PLC change permissions.

Thanks

6

Support Questions / Re: BasicLabel Overload

« on: June 07, 2022, 06:34:58 AM »

Out of curiosity, can you try to push it up to 100 BasicLabels with Beta 38?

Archie, bachphi,

I have migrated my app to Bet38, (only Minor Struggle, Operator Error ).
I tested the Basiclabel limit at 100 labels with no issue, I also tested it with more than 500 with no issues.

Edit/Update:
At 750 BasicLabels the communications is still trying but the update rate can not handle the changing data.

Thank you Gentlemen for your assistance,
Randy

7

Support Questions / Re: BasicLabel Overload

« on: June 02, 2022, 09:58:17 AM »

I can update to Beta 38, might take awhile to get it moved.

I will try to push it up to 100 BasicLabels and see if it strokes out.

8

Support Questions / Re: BasicLabel Overload

« on: June 02, 2022, 08:54:10 AM »

Archie,

Yes, I am using 3.99y Beta 34.

I switched the DisableMultiServiceRequest to True on all three drivers and now i can see all the data coming and going.

Thanks Archie

9

Support Questions / BasicLabel Overload

« on: June 02, 2022, 07:33:58 AM »

Good Morning Y'all,

I have an App that I've been working on that uses 59 BasicLabels to read and write data to three Allen Bradley PLC's.
I needed to add more BasicLabels to the app but adding one more causes all of them to loose connection to the PLC's.

Is there any way to increase the maximum limit of basiclabels per screen?

Thanks Randy 

10

Support Questions / Re: Error Migrating From Beta17 to Beta34

« on: December 02, 2019, 11:00:46 AM »

Thank you Sir

That fixed the problem perfectly.

Arv

11

Support Questions / Error Migrating From Beta17 to Beta34

« on: December 02, 2019, 10:29:27 AM »

Gentlemen,

I have an app that was built and functions using 3.99y Beta17, I have been trying to upgrade this app to 3.99y Beta34 but I have had minor errors to knock down.
This one however I can't seem to get past...
---------------------------
Microsoft Visual Studio
---------------------------
Code generation for property 'PLCAddressValue' failed.  Error was: '[A]MfgControl.AdvancedHMI.Drivers.PLCAddressItem cannot be cast to MfgControl.AdvancedHMI.Drivers.PLCAddressItem. Type A originates from 'MfgControl.AdvancedHMI.Drivers, Version=3.99.19.7, Culture=neutral, PublicKeyToken=null' in the context 'LoadNeither' at location 'C:\Users\rshepherd\AppData\Local\Microsoft\VisualStudio\15.0_8ccf801a\ProjectAssemblies\j5wj0pv401\MfgControl.AdvancedHMI.Drivers.dll'. Type B originates from 'MfgControl.AdvancedHMI.Drivers, Version=3.99.19.7, Culture=neutral, PublicKeyToken=null' in the context 'LoadNeither' at location 'C:\Users\rshepherd\AppData\Local\Microsoft\VisualStudio\15.0_8ccf801a\ProjectAssemblies\incer8y701\MfgControl.AdvancedHMI.Drivers.dll'.'

Anyone else having this issue?
Any help would be appreciated.

Thanks
Arvanoss

12

Support Questions / Re: Migrating to VS2019

« on: April 29, 2019, 09:06:33 AM »

Archie,

I did find that if I open a program that had an open screen it would fail.
If I close all of the screens then reopen them the problem was gone.

Thanks for all your help.

Thanks
Arv

13

Support Questions / Re: Migrating to VS2019

« on: April 25, 2019, 09:23:51 AM »

Archie,

The .Net Desktop Development is installed.

Not sure what happened but i'm sure I did something wrong.

Thanks
Arv

14

Support Questions / Re: Migrating to VS2019

« on: April 24, 2019, 10:46:02 AM »

Archie,

I think I did, how would I check and how do I install that option?

Thanks
Arv

15

Support Questions / Migrating to VS2019

« on: April 24, 2019, 09:30:52 AM »

To the Brain Trust...

I have installed Visual Studio 2019.
When I open one of Visual Studio 2017 programs and re-build the solution Every Connection and Every device has been wiped off the screen.  The only thing left in the MainForm.Designer.vb file is the Protected Overrides Sub Dispose(ByVal disposing As Boolean) subroutine and the Friend WithEvents data.

How do I Migrate my programs to VS2019 without losing all the screen components??

Thanks
Arv