F64 Datatype

[Keithang]

Hi,

We are busy working with Codesys and importing data into PLUS+1. However time base for TOF, TON, TP is giving us issues. When compiling, the driver requires a F64 data Type. How can we introduce F64, or is there a work around for this?

[Keithang]

Doing a Simple Code to see if I Export from Codesys v3 into GUIDE, how to make minimal changes. Comiles, with the following error:

*** ERROR 446 *** [PLUS1_IDE] PLC Code Compilation Failure {Convert PLCopenXML -> CCP}

[Nilla]

Hi Keithang!

Question
1. Could you explain a little bit more what you mean here?
2. Is it possible for you to post the entire content of the Error tab here on the forum or maybe send it in to plus+1helpdesk@danfoss.com together with your appliation in a .P1P-format for us to take a closer look at?

Best regards
Nilla
PLUS+1 Helpdesk

[FStelzer]

Hello Keithang,

It is not possible to deal with F64 datatypes in GUIDE.

Here is a comparison between datatypes in Codesys and GUIDE:

SINT - signed short integer (1 byte) --> possible, S8
INT - signed integer (2 byte) --> possible, S16
DINT - signed double integer (4 byte) --> possible, S32
LINT - signed long integer (8 byte) --> not possible, S64
USINT - Unsigned short integer (1 byte) --> possible, U8
UINT - Unsigned integer (2 byte) --> possible, U16
UDINT - Unsigned double integer (4 byte) --> possible, U32
ULINT - Unsigned long integer (8 byte) --> not possible, U64

Is it possible to retype the variable of the time for your delay to a U8, U16 or U32 (USINT, UINT or UDINT) value ?

In structured text you do that with e.g. USINT_TO_UDINT(Variable); --> Change the datatype from U8 to U16

Regards,
FStelzer