SysmacUser

You can home Axis1 in the way you wish. You can home Axis 2 in the way you wish Homming basically means to provide a 'reference' or 'origin' to the system. Some applications MUST have a home, other applications... don't really need to know where you are before you start moving... Anyway, you can do i.e. the following: Axis 1,  do the home according to external home input or whatever, and Axis 2, you can use the "Zero position preset" Homing method, that basically will do the following:   -Set the Homed Bit to TRUE   -Set Actual Position Feedback to 0 + an Offset if you define an offset   Hope it helps :)

Just one tip: Sysmac Controllers already have RAND  FB to generate pseudo-random numbers. Once you have th random number, should not be difficult for you to generate small FB to populate with 1 and 0 your array

There are applications in the high tech semiconductor market that require fast motion control. On the other hand there are machines that require to synchronize more than 100 axis. NX7 is a super-gifted PLC, and can do both at same time since it's four core Processor can handle 2 motion cores in parallel.

Omron Releases a new entry level NJ Sysmac CPU. This new controller targets application up to 0 or 2 EtherCAT Axis. http://www.omron.com/media/press/2015/04/i0401.html

Omron releases new 'SUPER-PLC' http://www.omron.com/media/press/2015/04/i0401.html

Maybe is interesting to remark another possibility, and it is to use Servo PDO's. In the past the MCE (Motion Control Engine) of NJ Sysmac was exclusive owner of Servo PDO mapping. Recent firmwares allow to map unused PDO's for Read/Write. PDOs (Process Data) are refreshed each EtherCAT cycle like the rest of NX Sysmac I/Os, so no need of SDO (Service Traffic). In the EtherCAT menu, sellect the G5 slave and press the button "Edit PDO Map Settings" there you can choose an Editable PDO mapping for Outputs, then you can add PDO's in your case Object 0x60FE01 (Physical Outputs). Then will be possible to assign a variable in the I/O map even if the Servodrive is declared as an MCE Axis. Notice that this possibility of mappign PDO's is not possible for all objects, since some PDO's are still exclusivelly owned by MCE.

I agree eith you in most of the topics. Please consider NA is very new device, so will for sure improve. Regarding online edits, which cpu firmware are you using? I see very difficult to be faster than cxp online edit, cj series is interpreted code, NJ is compiled studio online edit modifies sorce, builds the compiled and transfers both. Why compiled code? It is necessary i.e. To speedup plc code. NJ is 8 to 10 times faster than the fastest CJ2H

Online edit in a PC simulator as you have experienced is less fluent than in real NJ hardware. Simulator runs on top of Windows, whereas NJ is a realtime system... As you suggested... Stopping the simulator may help...

Regarding internal forcing, is not first time I see this request, let's see if this can be achieved in a reasonable way in future. Regarding coping data beween bitstring and numerical datatypes required to use union datatype as defined in IEC-61131-3

Thanks I think you have to discuss with Beckhoff and Omron in order to improve situation. ESI file is part of product, therefore only product manufacturer is allowed to modify the xml file

Sorry for the situation I am sure that both OMRON and Beckhoff will fix the situation, soon. Can I get the ESI xml file?

Yes, when NJ system is used. If Orher PLCs are used then Network configurator is required

Studio 1.10 already supports new NA HMI. So... You can start playing with the NA (in simulation mode) rightnow and... Judge by yourself ;)

V 1.10 of studio is faster ( when firmware 1.09 is used in NJ ). For onlinedit And includes (amongst others...) 2 New Major Funcions: -integration of NA HMI -EtferNet/IP network datalinks configurarion

CJ is very oriented to Ladder In NJ Ladder and ST are at same level, I assume you are taking advantage of InLineST function?... ST language has a very nice instruction ... CASE that is ideal for implementing STATE MACHINES... Please, check all the possibilities of CASE instruction... , and if you are Ladder fan... I suggest you to combine The CASE with InlineST instead of making 100% ST prog Additional tip... You can use ENUMERATION datatype in your CASE starement to define fhe state... So will make your prog easy to understand