Parameters 156/157 | Time of up/down movement.

[MrMcRush 0]

Hi,

 

I think I found clear mistake in the manual of the FGR-223 module... see pictures below and please compare the max. possible values.

Picture no. 1 shows PDF version of the Fibaro manual , and picture no. 2, web version of the Fibaro manual.

Unfortunately, I don't have this module (only the original version FGR-222), so I can't confirm the correctness of these parameters myself, so maybe you can help me and provide me the proper values for both of these parameters (156/157)?

 

Picture no. 1

Please login or register to see this image.

/monthly_2023_01/image.png.0353801037e66386bb1ad70da82c7523.png" />

 

Picture no. 2

Thank you in advance 🙂.

Edited January 9, 2023 by MrMcRush

[Martin_N 146]

@MrMcRushI'm not a Fibaro developer, but 65535 will be correct.
It is an integer with a maximum length of 16 bits, in Hexa FFFF.
This is the answer to the next parameter "Parameter size 4 (Bytes)"
He cannot imagine an application where the shutter (motor) would run for 11 minutes, let alone 15 minutes in the case of 90,000.
But come on, it may have some use for a pump, conveyor, etc.

eM.

[Stycx 5]

1 hour ago, Martin_N said:

@MrMcRushI'm not a Fibaro developer, but 65535 will be correct.
It is an integer with a maximum length of 16 bits, in Hexa FFFF.
This is the answer to the next parameter "Parameter size 4 (Bytes)"
He cannot imagine an application where the shutter (motor) would run for 11 minutes, let alone 15 minutes in the case of 90,000.
But come on, it may have some use for a pump, conveyor, etc.

eM.

As @Martin_Nsaid, 65535 is correct.

I just paired an FGR-223 with a YubiiHome and there are these parameters shown

Please login or register to see this attachment.

[MrMcRush 0]

So the "parameter size" in the fibaro manual should be 2 bytes (16 bits) and not 4 bytes (32 bits)... am I right?

[Martin_N 146]

@MrMcRush

You reason correctly, but I have one big BUT.
It depends on how big the WORD BYTE is.
For a 4-bit converter, processor,...
It can be a 4 bit word. This gave rise to the term Nibble. It acquires the values 0000-1111, i.e. in hexadecimal 0-F.
4 bytes (Nibble) give the result FFFF, which is exactly 65535 in DEC.
Just to add... Nibble actually means "half byte".
So many theories as to why 65535