Lookout 6.2 displays BCD/hex formated data (152) from AutomationDirect 250-1 as a decimal(338).

[dalewh]

How can I configure Lookout to display the BCD/hex formated number(152)?

[JW_Tech]

As an example, if you have a Lookout Pot called Pot1, and you want it to read/write a BCD value into/out of  250-1 register V5000, then Pot1's Remote position source should be DL1.VBCD5000 (not DL1.V5000)

Hope this helps,

G

[dalewh]

JW,

Thanks for your response to my question. I tried your suggestion with following results:

The OPC Client will not allow the use of the "Data Type" VBCD except for Timer/Counter values. Most of the data within the DL1.250-1 that I read/write from Lookout is located in V1400 and above. And the OPC Client requires that the address be V____ and the data type Word.

Am I looking at this correctly?

[JW_Tech]

I'll warn you up front I have never used OPC (I still use Serial) but I gotta think building the Lookout objects are the same...

We both use the D-250-1 See two images attached.

Here's the code I used to duplicate your symptoms.  

Pot1 = new Pot (0, 100, 1, yes, 0, "DL1.Rm_1_Humidity_Setpoint");

DL1           = new DL205 ("DL250", "1", 8, 4, 5, 500, "COM1", 9600, "odd", 0, 
                8, , "Upper port (k)")
                 alias ("Rm_1_Humidity_Setpoint","VBCD5000","n",,,,,,,,,,1);
DL1.PollRate  = 0:01;

Make two expressions: DL1.Rm_1_Hum_SP     and      DL1.VBCD5000

When I set Pot1 at 152, both expressions read 152

Change the data member in the second expression to DL1.V5000 and the reading changes to 338

G

[dalewh]

Yes, I should have mentioned that when I use a serial link(in other applications) I DO NOT have an issue with the data format. However, in this case my only access is via E-Com and the internet via the OPC Client.

[JW_Tech]

Then I'm all out. Sorry.

G

[dalewh]

Thanks for your time, very good of you!

[Mike@Forshock]

Try to import the number as HEX, AD PLCS treat BCD and HEX almost the same.

Mike

[jbesselm]

You indicated that your only access is via E-com and the internet via the OPC Client. Where is the OPC server? In my experience communicating with Koyo via the ECOM module you set the data type BCD in the OPC Server tag definition.

[dalewh]

You are correct the tag location is in the OPC server. I referred to the client in error. We cannot get the OPC server tag configuration to allow a word format in BCD, except for timer/counter values.

If we can not get the OPC to handle this conversion, is there a possibility of a math formula in Lookout performing this task? If so, where could we find such a formula?

Thanks for your interest and help!