ahbest

Use the ArySearch function.      Each Boolean in the array is compared to 1. If any bit in the array is 1 the output (FOUND) wil turn on.

You will need PNP output. 

We use this driver very often. You need the Festo Configuration Tool to program the settings in the drive. You can use this drive like a stepper motor, so a relative move on every pulse on an input (see attached scheme) or you can program fixed positions into the drive. A position is selected though the inputs. So on your (Omron) PLC you just use digital inputs and outputs.

It could be that one of the slices is broken and that this is causing the issue. Sometimes merging or applying the actual configuration doesn't work. Connect to the coupler via USB. You now first have to remove the actual configuration by doing a Clear All Memory action.  After this try again to make a new (actual) configuration. I even had it once that it said that the downloaded and actual configuration were identical, but still wouldn't run.     

My V1.24 is working OK. Only one weird thing. Every now and then, when I do an online edit, the monitor function of that section stops. All other open windows work fine. Just the one that was edited is grey. The edit itself is in the controller. Have to close the window of that section and reopen it. Then the monitor function works again.

You wrote you're using a brake cycle time of 10 ms. If you use an NJ controller your cycle time will be 1 ms. So also the timer functions will have a 1 ms accuracy. It means you calculate a percentage, but in reality it goes up and down by 10% (1ms is 10% of 10 ms). If you want to have it more accurate, you could for instance program it with a 0,1 ms interrrupt routine. With a counter that runs from 1 to 100 you will still have a 10 ms base time, but the output can be controlled with a 1% accuracy. At the init of the counter set on the output (immediate refresh). When the counter reaches the set percentage, turn off your output.  

For receiving the most simple solution is to stick to a fixed message length. You can see how many bytes are in the receive buffer. E.g. when your message length is 50 and the number of bytes received is 100, just treat it as 2 separate messages. So take all data from the receive buffer and split it into the number af messages calculated. For sending the easiest would be just using 2 ports. One for receiving and one for sending. If you can only use one port: also here stick to a fixed message length. Put all messages in a buffer. If the port is ready for sending, send the first message in the buffer.

The D9 error indicates that the PLC doesn't receive any data. Or the format is wrong. How did you set up your tag data list? Quite often the number of bytes (both input and output) need to be an even number. Had the same experience with Wago remote I/O. Always had to add an even number of IO blocks to keep the number of bytes in the tag list even. Otherwise it wouldn't work. Could be the same here.

From the main menu choose "Project" and then "Rebuild Controller" Solve all errors before you try to download.

From the menu choose  Controller and then Clear All Memory. You need to erase the whole configuration first before downloading the new configuration. Had a similar issue last week; this was the only solution.

First of all, the type number of the PLC you mention is not complete (or Omron is using different  type numbers in North America and Europe?). There are no expansion units for the CP1 PLC's that can handle encoders. So a second PLC would be an option. You can connect them through the serial ports or ethernet ports (option boards). But the encoder values exchange will be slow. So controlling the stepper drives should be programmed in each PLC separately. Another option would be remote I/O to hook up the encoders. But that will require more programming. The remote I/O can be connected to the PLC through any option board for serial or ethernet communication.