SysmacUser

MrPLC Member
  • Content count

    27
  • Joined

  • Last visited

Posts posted by SysmacUser


  1. 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 :)


  2. 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.
    1 person likes this

  3. 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.

  4. 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

  5. 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
    1 person likes this

  6. In general my experience with simulator onlinedit is that it works fine (though a lot slower than with a real NJ) !! Which version of studio is causing problem? Studio 1.10 has big internal changes regarding onlinedit in a real NJ (it is a lot faster than previous studio even if huge number of lines are modified) Though I have nor experienced your problem ... I suggest you to update to 1.10 as mentioned... Online edit algorithm has been improved to work faster

  7. NJ troubleshooter screen is a very powerfull tool for Sysmac maintenance but assuming that you have not defined machine faults in NJ troubleshooter, I wonder if makes sense that machine operator always jumps to that window? In my experience I only access that screen when I push NJ troubleshooting button, so... Maintenance guy will access this window when he wants deeper info

  8. NJ troubleshooter screen is a very powerfull tool for Sysmac maintenance but assuming that you have not defined machine faults in NJ troubleshooter, I wonder if makes sense that machine operator always jumps to that window? In my experience I only access that screen when I push NJ troubleshooting button, so... Maintenance guy will access this window when he wants deeper info

  9. Wulfgar, sorry I am using phone so is difficult to answer all your points in deep, but some of your request are already possible in studio. Regarding "forcing I/O" most of PLCs in the market only allow IO table forcing as ... When forces are used ... Machine works in way different than programmer code... Forcing internal variables is cool for debugging but is a practice that I don't recommend
    1 person likes this

  10. Sorry for situation. EtherCAT interoperaibility can be tested in 2 ways: -Vendor self conformance test (vendor makes own test) -EtherCAT Organization Conformance test (ETG group makes the test) OMRON Sysmac NJ conforms to the 2nd kind (EtherCAT group did the test) you can check in www.ethercat.org) However and in particular for complex slave devices it can be the case that some functionality does not work properly, in this case you have several options: -Request support from Beckhoff -Request support from OMRON -Check if ETG (www.etherCAT.org) verified that combination In OMRON we have Tsunagi (connectivity in japanese) laboratories that check OMRON devices interoperatibility with 3rd party: EtherNet/ip , deciceNet, ..., and also EtherCAT. Purpose of Tsunagi is to avoid undesired situations like you are suffering. So OMRON performs own compatibility test when our controllers are used. My suggestion (since Sysmac is the master in your system) is that you contact your OMRON representative, they can check this combination or ask for further details to Tsunagi lab (there are several worldwide) Why 2 EtherCAT devices may not work or have trouble? - Could be issue in ESI file syntax - Could be specific or vendor function not supported - other... The nice of EtherCAT is that is really OPEN to many vendors, so you can choose your preffered provider for controllers, IO, servos, inverters,etc..., but on the otherside this freedom generates many possible combinations and sometimes we can have situations that require further test.

  11. I grew up with ZX Spectrum. MS-DOS was s'thing really modern to me. In the PLC world I started with AB's. PLC5 and still remember the transition to the IEC's Contrologix. Some ppl missed the memory adress programming, but solution is simple, create array of B. (Bool) of N (integer), of F (float) etc... i agree with you sometimes IEC uses complex aproach for simple problems. Then vendor speciffic addons make the difference: diffup,etc... SysmanNJ makes a lot of sense when you have servosystems or extensive information processing like databases, product trace, etc... Makes no sense to replace CJ2M with NJ InlineST is a good compromise for mixing ST in ladder programs.

  12. Hi, I clearly see some advantages using NJ Sysmac instead of NC*8: Integration, IEC-61131-3 based, processing speed, Embedded Ethernet/IP and EtherCAT, benefit of new technologies like NX I/O, etc... Regarding NC*8 series, it is an etherCAT Position Controller. So if you just care about Point to Point motion, this unit will do the job. However if you are considering to synchronize or CAM axis, or pure Torque Control, this is not a good option. Also from cost point of view, CJ2H is the high end of the CJ series. So maybe NJ fits in price. NJ is programmed according to PLCopen Standard Motion FB's NC*8 is programmed according to PLCopen Standard Motion FB's (optionally) or by direct memory operation (like traditional OMRON NC cards).

  13. There is strong trend in Europe to program using ST language. And NJ, as IEC-61131-3 system can be programmed seamless in ST and Ladder. My background is Ladder programming, but there are many situations where ST becomes best choice. Something particulary good in NJ is that Ladder and ST can be mixed in the same program in a very fluent and visual way, from my experience this is a very powerfull way of programming, and reduces engineering and maintenance time. The new NX Safety Network Controller (EtherCAT Safety) integrated in the Sysmac system closes the loop: Logic+Motion+Information+Safety in one single package, with EtherCAT and Ethernet/IP embedded..., so simple... In the past, I dedicated my time thinking "how to do it", now... I dedicate my time to "what I want to do", the... "how" is not a big issue anymore...

  14. Target for Sysmac Studio is to be the best tool for the NJ Sysmac Machine Controller. NJ Sysmac is not just a PLC. It is a Machine Controller: Including Logic, Motion, Information, Safety, Vision, HMI*, in same environment. CX-Programmer functionality is covered as one of the Sysmac Studio areas (with the natural improvements and changes due to the differnet nature of the controller (CJ series is memory based, NJ Sysmac is Symbolic IEC-61131-3). I can understand that first impression of CX-Programmer user in front of new Sysmac is to be overwhelmed, because of new areas and functionality native IEC-61131-3 based, but my experience is that after a short assimilation time, user apreciates the new features of the Studio environment, that drastically reduces the engineering time for the machine development, so will not go back to CX-Programmer... Best Regards *CX-Designer is provided in the package when NS Series HMI programming is required.