Strick pointers check

otrotabi · ‎2022-07-19

I forgot to correctly set some of the input types (CL00/01/02/03/04) in a TM171 so I implemented the SmartBaseGetAiType available in the SmartBios library.

AiCfg_usiType := SmartBaseGetAiType(0); works fine in a real target but hangs the simulator. I have seen a "simulate" variable being used in one of the TDVA projects, is that the suggested solution or there´s a better one ?

I also found out of misreading the instructions, that if I do set the "Strict pointers check" checkbox to TRUE I get this error in the CompCntrl_onOff function block which is part of the standard Application/Refrigeration library. That sound a little weird not knowing what this checkbox actually does. Can anyone comment on this ?

This is what I get:

COMPCNTRL_ONOFF(322) - error G0101: ADDRESS => Type mismatch in assignment
COMPCNTRL_ONOFF(331) - error G0101: ADDRESS => Type mismatch in assignment
COMPCNTRL_ONOFF(341) - error G0101: ADDRESS => Type mismatch in assignment
COMPCNTRL_ONOFF(342) - error G0101: ADDRESS => Type mismatch in assignment

0 warnings, 4 errors.

FedericoM · ‎2022-07-19

Hi,

SmartBios library can't be simulated because it is internally using pointers to memory addresses which are not simulated.

The easiest workaround is a variable/constant which allows to skip these functions when the application is executed on a simulator target.

"Strict pointers check" enabled increases the check done by the compiler which will raise an error if you play with pointers/variables of different types. I normally keep this disabled because sometimes it is necessary/useful to do it.

By the way, in this specific case, the compiler is raising a wrong error, it will be fixed in the next ESME HVAC release

See Answer In Context

Bastian_Schmitz · ‎2022-07-19

If you enable this feature you must check the compability of data types by the use of pointers.

Normally this feature should be deactived in default.

FedericoM · ‎2022-07-19

Hi,

SmartBios library can't be simulated because it is internally using pointers to memory addresses which are not simulated.

The easiest workaround is a variable/constant which allows to skip these functions when the application is executed on a simulator target.

"Strict pointers check" enabled increases the check done by the compiler which will raise an error if you play with pointers/variables of different types. I normally keep this disabled because sometimes it is necessary/useful to do it.

By the way, in this specific case, the compiler is raising a wrong error, it will be fixed in the next ESME HVAC release

otrotabi · ‎2022-07-20

Thank you both for your comments. I found the error quite strange because it is a well proven function block and the hours/starts counter work fine.