AdvancedHMI Software
General Category => Support Questions => Topic started by: pal on September 04, 2015, 03:57:44 PM
-
Hi Archie ,
Just downloaded V3.99 and went to release notes to see what has changed , but nothing about the new version . Could you put the notes in a post please ?
Paul
-
In AdvancedHMI\ReleaseNotes399.txt you will find the changes at the top of the file:
V3.99
FormChangeButton did not fire click event
BasicDataLogger2 - Added PauseLogging
EthernetIP (CIP) - Fixed a problem with the ForwardCloseRequest packet
MessageDisplayByBit - Added PLCElementBitWidth and PLCNumberOfElemts
MesssageDisplayByBit - fixed several problems
OmronFINS - fixed some problem with bit subscriptions
ChartByArray - Added RefreshAllPoints for an array with fixed number of points
MessageDisplayByBit - Added ValueBitMask property
ChartByxxx - Added YAxisMin and YAxisMax properties
GraphicIndicator - Added support for BackgroundImage
Modbus - Added support for U3xxx addresses (unsigned)
EthernetIPforSLC/Micro/PLC5 - Split the PLC5 driver into its own
-
The version I,ve just downloaded had release notes 3.98t , so thank you for your very quick reply AND adding the notes to your reply .
Paul
-
tried to add purchased controls and get these errors
-
The AB drivers have been renamed. If you click each error, then edit the EthernetIPforPLCSLCMicroCom and change it to EthernetIPforSLCMicroCom
-
I just tried to add my existing 398t project into 399 & got hundreds of errors about the PLCSLC, so I decided to not upgrade that project (my pet project I am using to control a 2 rack SLC5/05 & 2) SLC5/03's for home automation control & Christmas lights - mostly as a test to see what I & AdvancedHMI are capable of).
-
I just tried to add my existing 398t project into 399 & got hundreds of errors about the PLCSLC
The version number change from the 3.98 series to 3.99 indicates there are some changes that can break an existing application. One of those changes is the name change of the AB drivers.
If you do a Search & Replace of the entire solution for EthernetIPforPLCSLCMicroCom to EthernetIPforSLCMicroCom, it will probably fix most of the errors if not all.
-
Archie,
;
Thanks, I got all the PLCSLC driver errors taken care of, now however I keep getting 4 errors saying:
'PLCaddressVisibilty'is not a member of 'AdvancedHMIControls.PilotLight3Color' & I don't have a bit address in the entries.
Should I remark out these lines, or how would I add the member?
-
I keep getting 4 errors saying:
'PLCaddressVisibilty'is not a member of 'AdvancedHMIControls.PilotLight3Color' & I don't have a bit address in the entries.
Should I remark out these lines, or how would I add the member?
Those change to PLCAddressVisible
-
For the driver name, it should also work if they rename the driver back to EthernetIPforPLCSLCMicroCom.
It's just a name.
-
The version number change from the 3.98 series to 3.99 indicates there are some changes that can break an existing application.
Right after I redo a whole hmi from scratch in 3.98t : (