Messages

1

Support Questions / Re: INI file for basic labels

« on: September 03, 2021, 02:06:00 PM »

Eggcellent, sir!!
Working as intended.
Thank you for the very prompt assistance.

2

Support Questions / Re: INI file for basic labels

« on: September 02, 2021, 07:30:23 PM »

thanks for the quick reponse.
Color me stoopid.
I don't see those properties in the property tree.
can you give me a clue where to find my problem..

3

Support Questions / Re: INI file for basic labels

« on: September 02, 2021, 03:15:03 PM »

I would like to0 implement t INI file use in the basic label.
Using AdvancedHMIv399yBeta38
Followed the instructions in this topic and got several build errors: (below)
Fhis topic is over a year old. I assume versionitis?
Is there a way to use AMHI latest version and use Ini files with the basic label?
Thanks for any assistance.

Severity   Code   Description   Project   File   Line   Suppression State
Error   BC30269   'Public Sub BeginInit()' has multiple definitions with identical signatures.   AdvancedHMIControls   C:\AHMI_Test\AdvancedHMIControls\Controls\BasicLabel.vb   947   Active
Error   BC30269   'Public Sub EndInit()' has multiple definitions with identical signatures.   AdvancedHMIControls   C:\AHMI_Test\AdvancedHMIControls\Controls\BasicLabel.vb   951   Active
Error   BC30583   'ISupportInitialize.BeginInit' cannot be implemented more than once.   AdvancedHMIControls   C:\AHMI_Test\AdvancedHMIControls\Controls\BasicLabel.vb   979   Active
Error   BC30583   'ISupportInitialize.EndInit' cannot be implemented more than once.   AdvancedHMIControls   C:\AHMI_Test\AdvancedHMIControls\Controls\BasicLabel.vb   983   Active
Error   BC2017   could not find library 'C:\AHMI_Test\AdvancedHMIControls\bin\Debug\AdvancedHMIControls.dll'   AdvancedHMI   C:\AHMI_Test\AdvancedHMI\vbc   1   Active
Error   CS0006   Metadata file 'C:\AHMI_Test\AdvancedHMIControls\bin\Debug\AdvancedHMIControls.dll' could not be found   AdvancedHMIcs   C:\AHMI_Test\AdvancedHMICS\CSC   1   Active

4

Support Questions / Re: CLX driver intermittently does not update

« on: August 18, 2021, 03:31:55 PM »

The first suggestion was going to be my last ditch effort. I split the screens and that worked - for awhile. problem recurs less intermittently than before.

I already use the code to stop comms when a screen is not visible.

I assume that it is a bandwidth issue?
This is not a high response rate requirement. Throttling the throughput would be acceptable - if I knew how...

if a driver reports a ComError, it appears to stop. no more updates and the ComError count does not increment past 1.
restarting / resetting the driver would be acceptable also - if such a feature is available.

I recall reading somewhere that DataSubscriber gives better throughout than a conglomeration of BasicLabels. Is that correct?

thank you for the response.

5

Support Questions / Re: CLX driver intermittently does not update

« on: August 17, 2021, 06:55:05 PM »

Godra, your suggestion worked.
for my education:
it appears that reducing poll rate has no effect. what is the failure mode for this problem?
is there a means to reduce the communication demand or to stagger timing between drivers?
is there a way to measure the comms load?
or reset a faulted driver during runtime?

thank you for the assistance.
r
GF

6

Support Questions / CLX driver intermittently does not update

« on: August 13, 2021, 04:36:54 PM »

I am building a diagnostic application - displaying status of many PLC tags from 5 PLCs.
Using AdvancedHMI 399yBeta38
All but one PLC driver use a route path (to drill through the backplane to get to other subnets)
So far, I have about 25 screens. all are working. but ...
recently, one screen started to misbehave.
this screen has 4 different drivers to 4 different PLCs. 3 are routed as described above. There are about 80 basiclabels on this screen.
when this screen is opened, the tags of 1 or (usually) more than 1 driver do not update. If I close and reopen the screen, one or more different drivers will not update. At least one driver will not update no matter how many times I close and reopen the screen. A ComError event is raised on the drivers that do not update.
All other screens appear to work reliably. all other screens have fewer than 4 CLX drivers.

Any clues as to the problem?
Is it possible to reset / restart a driver at runtime?
How to workaround the problem?

BTW: cannot say enough good things about the AdvancedHMI package.