Crossbow

Sounds like something to ask your local Beckhoff distributor.

In the future, create a new post, do not piggyback on a post that is totally not related to your question. I am not familiar with that software, which model HMI is it?  Do you have the latest version of the HMI software?  Maybe it was written with a newer version than you are using and cannot uncompile it.  It might also be possible that the person who downloaded to the HMI prevented upload of their code.  As I said, without more information on what HMI and software versions, nobody will be able to provide much help.

Can you write logic in your function block to calculate the value and then use the value?  There's no way I know of to use a formula directly on an array index, but point the index at a variable and calculate that value...

You can contact any Siemens distributor for the software and cable.  They might also be the best place to ask for who locally may be able to come assist you, as most distributors have relationships with their best integrators.

In GX Works2?  That looks like a simple ladder program, he would need structured ladder would he not?

I would highly doubt they would release it to use on just any hardware.  By making the IPC, they also get to control the hardware and ensure full functionality like they would the actual PLC.  By opening it to all hardware, there are all kinds of risks regarding compatibility.  The Windows OS is entirely separated from the PLC OS, and you can actually reboot Windows without affecting the PLC.  It's not just a runtime executing in Windows.

Which CPU?  CPU22 and CPU23 are not complete part numbers, missing the controller family.  And you never said which software you have.  So we will have to guess?  If you want useful answers, you need to provide complete questions. But it doesn't matter.  Get online with the CPU and upload everything including device memory, then go offline, change the CPU type, get online with the new CPU and download everything.

When you make your own function blocks, everything used inside should be defined inside its local label list.  Never use global labels inside a FB, you should make an input pin and connect the global to that on the outside.  As for programs, local labels can be used in any way you wish that isn't required externally.  If it's required in more than one program, on a network, or an HMI, you should use a global label.  There's some good eLearning materials on the Mitsubishi US website that can help you learn programming basics.  And they regularly offer training classes on GX Works2 and GX Works3, if that would help.  I know labels are discussed in the in-person classes.

Does Device List do that?  It should show all addresses and if they were used input or output.  It's in the Find/Replace menu next to Cross Reference.

Cross reference should show you all of the places an address was used, including 32-bit and 64-bit usage.

ADD K1 D4 D4 can NEVER affect D5. Cross reference should show you all of the places an address was used, including 32-bit and 64-bit usage.

The reason you cannot draw that red line is because you are making a loop.  The EQ function is using the output of the CTU as an input, and then you try to use the EQ as an input to the same function block.  It won't allow you to draw that. Put the output of the EQ into a variable, and then use that variable as the input to the CTU.  It needs to process the EQ before it can process the CTU if it's input data...

Local labels are data specifically inside one program or FB, not accessible from outside.  Think of program local labels as work memory, that has no bearing on other programs. So for example, labels you make in program MAIN1 are not visible to program MAIN2, so creating duplicate names does not cause a problem.  Prevents you from having to remember which bits and words you used internally in each program to prevent duplication. Global labels are available to every program in the CPU.  That's why the I/O is created as global labels.  Global labels are also used for any data to display on an HMI or transmit over a network like EtherNet/IP. There's a lot of good videos out there explaining label based programming.

But your project is written FOR A SPECIFIC CONTROLLER...

This is a comment on a download file... If you need help, post in the Omron forum with details of your question.