Messages

1

Support Questions / DF1Comm bug in 3.7.0

« on: October 10, 2014, 03:12:14 PM »

I used successfully AdvancedHMI v3.6.0 for a project last year with DF1Comm and a SLC 500.

I started a new project this year with DF1Comm and a SLC 500 so I updated to the latest AdvancedHMI version which was 3.7.0. There are problems with this version. I tested with Visual Studio express 2012. Using AdvancedHMI v3.7.0, Visual Studio often crashes when editing my application code. It also crashes to an error somewhere in the AdvancedHMI code when closing the application.

I did some quick tests on previous version of AdvancedHMI available on sourceforge. Versions 3.6.1, 3.6.3 and 3.6.9 seem to work correctly and do not crash Visual Studio or in the driver code. I reverted to 3.6.9 for my projects and it seems to work fine so far.

2

Support Questions / Re: 3.52 Bugs

« on: August 16, 2013, 09:56:58 AM »

Thank you, it works.

3

Feature Request / Property description

« on: August 15, 2013, 11:12:34 AM »

It's not a feature but more of an improvement to help the programmers. When you get the time, please add descriptions to the properties of the controls and drivers. That way you get a description of the property at the bottom of the property window.

Code: [Select]

<Description("Property text")> _

4

Support Questions / Re: 3.52 Bugs

« on: August 15, 2013, 11:01:59 AM »

I'm still getting the exception on version 3.54.

5

Support Questions / Re: Problem when starting with loss of DF1 connection

« on: August 15, 2013, 10:50:01 AM »

I tested both 3.40 and 3.54. I used one DF1Comm and two BasicLabel to two different addresses. With the cable connected, the form appears after two seconds. With the cable unconnected, the forms takes 20 seconds to appear (roughly 10 seconds/control on the form).

I tested on one computer with a RS232/USB converter and another computer with a serial port. Same result.

6

Support Questions / Re: 3.52 Bugs

« on: August 14, 2013, 03:13:28 PM »

Archie, here's a bit more information. The exception 'System.IndexOutOfRangeException' happens when "Responses(TNS And 255).Values.Count" is equal to zero at the end of the Read function. It happens most often when Read is called many times in a row rapidly.

7

Support Questions / Re: 3.52 Bugs

« on: August 14, 2013, 12:36:06 PM »

I confirm the same problem with DF1Comm and a SLC 500.

In version 3.40, the following line always succeeds :

Code: [Select]

Button1.Text = DF1Comm1.ReadAny("F8:0", 1)(0)
In version 3.53, the following line fails most of the time and sometimes succeeds:

Code: [Select]

Button1.Text = DF1Comm1.Read("F8:0", 1)(0)
when it fails, the error is :

An unhandled exception of type 'System.IndexOutOfRangeException' occurred in AdvancedHMI.exe

Additional information: Index was outside the bounds of the array.

8

Support Questions / Problem when starting with loss of DF1 connection

« on: August 14, 2013, 11:13:17 AM »

I'm using version 3.52 with a SLC 500 connected with a DF1 connection with a RS232 cable connected to a RS232 to USB cable. It works fine when the cable is connected. When the cable is not connected on the PLC end, the HMI start time is long and the form is slow to react to user input. The startup time increases with the number of controls on the form. With about fourty controls, it takes about two minutes for the form to appear on screen.

It looks like most of the startup time is spent inside line 340 of DF1Comm.vb (inside the dll) :

Code: [Select]

result = DLL(MyDLLInstance).SendData(CommandPacke, MyNode, TargetNode)
When that line executes with one control on the form, the following output appears in the ouput window of the debugger :

Code: [Select]

The thread '<No Name>' (0x3d4) has exited with code 0 (0x0).
The thread '<No Name>' (0x1e48) has exited with code 0 (0x0).
The thread '<No Name>' (0x129c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1458) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d1c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1da4) has exited with code 0 (0x0).
The thread '<No Name>' (0x1510) has exited with code 0 (0x0).
The thread '<No Name>' (0x1648) has exited with code 0 (0x0).
The thread '<No Name>' (0xac8) has exited with code 0 (0x0).
The thread '<No Name>' (0x1f04) has exited with code 0 (0x0).
The thread '<No Name>' (0x1da0) has exited with code 0 (0x0).
The thread '<No Name>' (0x818) has exited with code 0 (0x0).
The thread '<No Name>' (0x1eac) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d20) has exited with code 0 (0x0).
The thread '<No Name>' (0x1d38) has exited with code 0 (0x0).
The thread '<No Name>' (0x1aec) has exited with code 0 (0x0).
The thread '<No Name>' (0x1824) has exited with code 0 (0x0).
The thread '<No Name>' (0x494) has exited with code 0 (0x0).
The thread '<No Name>' (0x1b7c) has exited with code 0 (0x0).
The thread '<No Name>' (0x1640) has exited with code 0 (0x0).
After that, the following line appears in the output window of the debugger :

Code: [Select]

A first chance exception of type 'MfgControl.AdvancedHMI.Drivers.Common.PLCDriverException' occurred in AdvancedHMIDrivers.dll
Those lines repeat every 10 seconds. If there are many controls on the form, this seems to cause a slowdown of the application.

9

Support Questions / keypad failure if decimal separator of regional settings is comma

« on: August 14, 2013, 09:49:01 AM »

I'm using version 3.52. I'm from Canada, we use the comma "," as the decimal separator. When using the keypad on a BasicLabel to enter floating point numbers, it fails in the KeypadPopUp_ButtonClick function if the decimal separator of the regional settings is comma because the keypad inserts a dot in the string.

Below is my quick fix. You could find a better solution and include it in the next version. After "If KeypadPopUp.Value <> "" Then", add  :

Code: [Select]

Dim DecimalSeparator As Char = System.Globalization.CultureInfo.CurrentCulture.NumberFormat.NumberDecimalSeparator()
If StrComp(DecimalSeparator, ",") = 0 Then
  KeypadPopUp.Value = Replace(KeypadPopUp.Value, ".", ",")
End If