AdvancedHMI Software

General Category => Support Questions => Topic started by: betilly on December 18, 2018, 06:56:05 AM

Title: OmronEthernetFINSCom
Post by: betilly on December 18, 2018, 06:56:05 AM

Hi, i found with newest version 3.99y beta that OmronEthernetFINSCom driver , option TreatDataAsHex dont give right values in barlevel control.

Title: Re: OmronEthernetFINSCom
Post by: Archie on December 18, 2018, 07:25:46 AM

Can you give an example? Does a value of 16 in the PLC show as a 10 n the bar?

Title: Re: OmronEthernetFINSCom
Post by: betilly on December 18, 2018, 07:31:57 AM

Value in holding register D1 #10 is shown as 16, with 399x version it shows right .

Title: Re: OmronEthernetFINSCom
Post by: betilly on December 24, 2018, 04:31:28 PM

Anyone try and have same problem?

Title: Re: OmronEthernetFINSCom
Post by: Phrog30 on December 24, 2018, 06:35:20 PM

You mentioned barlevel, what about basic label? Try a basic label and report back.

Title: Re: OmronEthernetFINSCom
Post by: betilly on December 25, 2018, 05:45:24 AM

basic label is working ok because you have option in properties InterpretValueAsBCD.

Title: Re: OmronEthernetFINSCom
Post by: Phrog30 on December 25, 2018, 08:43:46 AM

Then it's not the driver. Your initial post makes it seem like it's the drivers fault.
So, open the basic label, copy the code for interpret BCD and paste that into the bar level.

Title: Re: OmronEthernetFINSCom
Post by: Archie on December 25, 2018, 08:56:30 AM

Is your objective to show the value in the Barlevel in Hex format?

Title: Re: OmronEthernetFINSCom
Post by: betilly on December 25, 2018, 10:50:17 AM

I didnt say that something is wrong with driver, just that in older versions just need to set parameter treatdataashex set to true and  got displayed numbers as i want ( in hex). In latest version dont. I compare both fins drivers and omron base, and saw that some code was commented in latest beta version, maybe thats the point....?

Title: Re: OmronEthernetFINSCom
Post by: Archie on December 25, 2018, 11:25:55 AM

The TreatAsHex property is being phased out because if it sends a hex value to a control that is expecting a numeric value, it will not be able to process it. The replacement for this is the modified addresses such as 000@B for a BCD address

Title: Re: OmronEthernetFINSCom
Post by: betilly on December 25, 2018, 12:18:44 PM

Thank you for explanation Archie.