I am trying to use the function „get_microseconds“ from the PLC Next Controller-library, but it returns this error when attempting to build:
E1002: [Arp.Iec.Commons]Arp.Iec.Commons.Chrono.GET_MICROSECONDS.__Process(System.Boolean) IL_0006 : emitting of cil code failed
image.png
I am using PLCnext Engineer version 2023.9
Hello!
Pay attention that FW of plc have to be 2023.6 too. For plc itself and for project template.
I figured it out.
The problem being I was using a 3152 controller which does not yet have the required 2023.6 firmware.
Swapping to a 2152 with 2023.6 solved the issue.
But WHY are you not releasing firmware to all controllers in the x152 series at the same time?
(edit: ninjaed by Oleksander)
This is just great 
WHY are you not releasing firmware to all controllers in the x152 series at the same time?I can assure you that if it was easy, then we would. The development and testing processes for each hardware platform (e.g. AXC F 2152 and AXC F 3152) take a long time to complete for every new FW version. With so many PLCnext Control devices now available, this is quite a big task. In some cases firmware versions are skipped - like version 2023.6 for the AXC F 3152 - and in almost all cases the release of a new FW version is staggered for different HW platforms.
If you want to discuss this, you can speak with the technical specialists in your local Phoenix Contact office, who can pass on your comments and suggestions to the Product Managers.
I understand the challenge, but also when you introduce new functions which are not available on all controllers due to firmware availability issues - it creates challenges for developers instead:
* Same code cannot run on a different (and stronger in this case) controller - making an upgrade impossible without rewriting the code.
* User Libraries (which utilize e.g. get_microseconds) shared between controllers are not compatible and code will simply not build - it is not possible to use logic to check which kind of controller you are using and skip the functions which are not available yet
Can you say something about when next firmware is available for 3152? We are up for type approval testing early next year and need to know if we need to create workarounds.