Sources:

• Finder relays, general technical information (finder-relais.net)
• Relay contact materials – does it matter? – Finder (findernet.com)
• Relay Contact Materials – IBEX Resources
• How to choose relay as per relay contact material for variations of load. – Electrical Blog (eblogbd.com)

Real to Int

r2i_REAL_in (Data type: REAL):

The real number to convert.

r2i_Precision_in (Data Types: UINT8, UINT16, UINT32):

Number of decimal places to add to the fractional part.

r2i_INT_out (Data Types: INT8, INT16, INT32):

this is the integer part of r2i_REAL_in, no matter what the value of r2i_Precision_in is.

r2i_frac_out: (Data Types: INT8, INT16, INT32):

This is the fractional part of r2i_REAL_in, rounded to the specified number of decimal places, multiplied by 10^( r2i_Precision_in ).

There’s a special case when r2i_Precision_in is 0 (ie. round to the nearest integer): when the magnitude of th fractional part is less than 0.5, it will be 0, otherwise it will be 1 or -1, (the same sign as r2i_REAL_in). To get the correctly rounded number, you need to add r2i_frac_out to r2i_INT_out

The behaviour when the number is too big to fit into either of the integers seems to be inconsistent. If r2i_INT_out is an INT32, then it will 2 147 483 647 if r2i_REAL_in is bigger than that, or -2147483648 if r2i_REAL_in is smaller than that. INT16s and INT8s sometimes overflow instead. (i.e. 128 becomes -128 if r2i_INT_out is an INT8), but it doesn’t do this for all values). I’d avoid using this function in this situation if at all possible.

Examples:

Int to Real

i2r_INT_in (Data Types: INT8, INT16, INT32):

Integer part of value. Not actually necessary, because you can do everything without it.

i2r_FRAC_in (Data Types: INT8, INT16, INT32):

This is the only way to populate it the fractional part of the output, but it will also contribute to the fractional part.

i2r_DECPOS_in (Data Types: UINT8, UINT16, UINT32):

This controls how i2r_FRAC_in is intepreted. Values above 7 result in the fractional part being ignored.

i2r_REAL_out (Data type: REAL):

The Real output value. This is calculated as:
i2r_INT_in + i2r_FRAC_in / 10 ^ ( i2r_DECPOS_in )

Examples

Downloaded from https://cdn.automationdirect.com/static/specs/sinksource.pdf

USA Plug configurations – NEMA Plug & Receptacle chart

D = A + B x 10 ^ (-C)

Real to Int

A = XXXXXX.YYYYYY

C = XXXXXX

D = Round 0.YYYYYY to B decimal places, then multiply by 10 ^ B

At least I think this is what it’s supposed to do – it seems to have some issues:

• Rounding close to 0.5 can be somewhat unpredictable. e.g. A = 5.246, B = 1 will give D=3, not D=2 as it should.
• Note that the Integer part is always simply truncated – don’t expect this function to Round correctly – e.g. A = 12.99, B = 1 will give C=12 and D=10, instead of C=13, D=0 as you might expect!

And you’d stay curious if you tried to find the answer in the Allen Bradley Documentation, because it’s shit: It doesn’t even tell you how many characters there are on a each line. Incidentally, the answer is 16.

Entering the characters into strings is pretty easy – just type $ followed by the 2 digit Hex code. e.g. ‘Hello$21’ would appear as Hello!.

The first 32 are dramatically different to the ASCII standard, and well worth knowing about, but there are a few others different 5C,5E & 7F. Codes 80 to FF are less useful, but there are a few accented characters in there that might be of use, depending on which language you use.

I wrote a simple program to show every code across 4 pages – use the left and right buttons to switch between them. This was prepared with Connected Components Workbench 22.0.0 for a Micro810 with v7 firmware.

Characters 00 – 3F (0-63)

Loads of goodies in here, look!

Characters 40-7F

Most of these are pretty similar to standard ASCII, but with a few exceptions

Characters 80-BF

A couple of Asian characters, and some common accented letters

Characters C0-FF

A bunch of accented characters – these seem to be aligned to Unicode code points