1 is a number, only TRUE and FALSE are allowed to be assigned to a BIT.
An invalid pointer (either because it is 0 or points outside the memory reserved to the program) is being dereferenced. Track down pointers or interfaces that you have in code and check them - you should also be wary of mixing online change and pointers.
Did you deactivate the debug console via Daemon->HMD subdevice? See the attached picture. Otherwise the port is already seized by the Linux system. You'll need to reboot the display via ignition (not via power supply) for this setting to take effect.
Anyway a better way for what you want to achieve is executing the task with 32 ms (or submultiple like 16, 8, 4 ms...) execution time and increment the counter every 1 (2, 4, 8...) cycles without timers. You'll get the best behaviour your platform can provide.
First - what's the task cycle time? Timers cannot have better resolution than that. E.g. if your task cycle time is 20 ms, the following happens (every bullet is a cycle - the first is the global clock): 1) t#000ms - IN = TRUE - ET = t#0ms - Q = FALSE 2) t#020ms - IN = TRUE - ET = t#20ms - Q = FALSE 3) t#040ms - IN = TRUE - ET = t#40ms - Q = TRUE 4) t#060ms - IN = FALSE - ET = t#0ms - Q = FALSE 5) t#080ms - IN = TRUE - ET = t#0ms - Q = FALSE 6) t#100ms - IN = TRUE - ET = t#20ms - Q = FALSE 7) t#120ms...
There is no way to make ETrigTo variables xExecute/xDone/xError/xBusy alongside ClientRequest own ones (see attached picture). One can have them only by calling the block as CBML.ETrigTo but then specific ones are lost. In CFC, on the other hand, they all show up fine. Furthermore, IClientRequest interface seems to be hidden.
It's probably done in the hardware. You should ask the manufacturer, typically the peripherals that do that stuff already have both the high/low time and the period information.
Quoting the documentation at https://content.helpme-codesys.com/en/CODESYS%20Visualization/_visu_dlg_project_settings.html You can also configure a visualization element with a property in those properties where you select an IEC variable. Then CODESYS creates **additional code** for the property handling when a visualization is compiled. So I guess that not using properties, thus not generating additional code that's executed every time the element is rendered, should be faster than using them....