Topics

1

Feature Request / BasicLabel Blink

« on: March 18, 2019, 11:53:13 AM »

I have three suggestions for the basic label.

1. It would be nice if the label "Blinked" between the highlighted color and the normal color by setting a blink rate.  If the "Blink" rate was set to 0 then blinking would be disabled.

2. Have the "ValueToSubtractFrom" property be a value that can be read from the PLC.  This would allow you to display a time remaining (Timer.PRE - Timer.ACC).  You would also need to have the "ValueScaleFactor" affect the "ValueToSubtractFrom".

3. Add Auto/Manual and Enabled/Disabled to the Boolean text choices.

2

Support Questions / BasicLabel Keypad Show Value

« on: August 24, 2016, 12:22:03 PM »

I am using the BasicLabel to allow the operator to change timer values.  The scale factor is set to .001 in order to display the timer value in seconds.  If I set the property "KeypadShowCurrentValue" to true, the value that is read from the PLC and displayed on the keypad is not scaled.

For example: If the timer is set for 10 seconds the value displayed on the keypad will be 10000.  Changing it to 10 and saving the result works correctly; the value saved back to the PLC is 10000.

I am currently looking at version 3.99n but I checked an older version (3.99d) and it does the same thing.

3

Open Discussion / EthernetIPforCLXCom1.ComError

« on: August 22, 2016, 09:56:06 AM »

When EthernetIPforCLXCom1.ComError is triggered does EthernetIPforCLXCom1.ConnectionEstablished trigger when communication is reestablished?

4

Open Discussion / Trailing space in PLC address

« on: August 16, 2016, 04:21:30 PM »

I discovered a problem, created by the developer, which is caused an invalid tag error.

During the process of building the HMI screens, I was copying the tag names from an old system and pasting them into the new.  Some of the tags ended up with a trailing space.  This caused a failure to read tag error.  I did a quick fix by modifying the controls I was using (modified control's properties by adding X = Value.Trim).  This was faster than going through each screen control and looking for and removing the trailing space.

It would be a nice addition if this fix was added to future releases to prevent development error caused by unawareness.

5

Support Questions / MessageDisplayByValue Returned Value

« on: June 30, 2016, 01:25:26 PM »

This maybe by design but is was unexpected.
If you read the returned value (MessageDisplayByValue.Value) from ValueChanged event, the value that is returned is the value you are changing from (old value).

If you read the returned value from TextChanged event, the value that is returned is the value you are changing to (new value).

6

Feature Request / BasicLabel Highlight forecolor

« on: June 20, 2016, 09:36:43 AM »

In future releases to would be nice if a Highlight forecolor property were included.  Also, it would be nice if the Highlighting worked for boolean values also.

7

Support Questions / MultiStateSelector V3.99j

« on: June 17, 2016, 03:09:23 PM »

The MultiStateSelector control has a bug.
When you click on the "States" property to add to the collection the control displays an error "Parameter not valid".

8

Feature Request / GraphicIndicator image rotation

« on: June 08, 2016, 01:24:54 PM »

The ability to rotate the 3 images during development.  It would help in development time and overall size of the compiled project because you would not need to have multiple versions on the same image at different angles (depending on the need).

For example:
I created a image of a valve.  In some places I need the valve to be shown vertically and in other places it need to be shown horizontally (depending on the flow and physical space on the Form).  Currently I need to have a minimum of 4 images (2 for each rotation to show status On/Off).

9

Feature Request / Motor Control

« on: June 08, 2016, 12:43:40 PM »

I would helpful if a second color (Red) was added to the motor control be used to indicate a fault.  This would eliminate the need to add a separate BasicLabel control.

10

Open Discussion / Microsoft.VisualBasic reference

« on: June 07, 2016, 10:25:01 AM »

Since you are only using the Microsoft.VisualBasic reference in 2 controls (BasicLabel and ChartBySampling) it would be nice if you replace MsgBox and Now so that this reference is not needed in future releases.

11

Feature Request / MinimumHoldTime

« on: May 19, 2016, 08:56:53 AM »

Your BasicButton has a MinimumHoldTime property.  This feature would be nice to have on the MomentaryButton as well.

12

Support Questions / Pilot Light Control

« on: May 18, 2016, 03:33:21 PM »

I have placed a pilot light control on a Form and set the PLCAddressValue property.  If the PLCAddressValue is True and the pilot light is clicked then the pilot light shows the LightColorOff even though the PLC address is still true.  It remains the off color until the Form is closed and reloaded or the PLC address changes from True to False to True.  If I have multiple lights with the same PLC address, the only one affected is the one clicked.

Using version 399f

13

Open Discussion / AdvancedHMI Logo

« on: May 17, 2016, 04:58:19 PM »

The logo on the main screen sent with the application is made for a dark background.  I would like to place the logo on the main screen of my project (give credit where credit is due) but my screen is not dark.  Do you have a preference as to the color of the word "Advanced"?  Currently it is white.

14

Feature Request / GraphicIndicator Text Color

« on: May 12, 2016, 11:01:08 AM »

Is there a way to change the GraphicIndicator's text color?  If the graphic is dark you cannot see the black text.

15

Support Questions / BasicLabel ValueChanged event problem

« on: May 10, 2016, 10:55:25 AM »

The ValueChanged event is triggering constantly event though the BasicLabel value has not changed.  The PollRate seems to have no effect.
The TextChanged event is working properly and only triggers when the value has changed.