Hoobs

MrPLC Member
  • Content count

    31
  • Joined

  • Last visited

Posts posted by Hoobs


  1. In doing a bunch of socket programming on the NJ501-1300, I have found what appears to possibly be an error/omission in all the manuals related to this controller.  There is an instruction mentioned in numerous places, the "SktSetOption" instruction, but nowhere am I able to find details on it.  What options can be manipulated?  How is that done?  Is there status information returned?  While it is mentioned in several places, it is *not* in the NJ Instruction Reference manual, unless there has been a recent update to this manual that I have been unable to track down.

    Does anybody know where the usage details for this instruction may be found?

    Thanks!
    --Al


  2. Wow...  really?  Man, this is important, IMHO.  I really like just about all of what OMRON creates, I have for years, but this PLC not having even simple embedded  debugging capabilities really puts the NJ series (and others) at a disadvantage up against some of the competitors.  On-board single stepping and breakpoints are critical to the development of large systems with a lot going on.  If I had known this I probably would have specified a competitive PLC instead of the NJ501.  But, I'm here now.

    OK, I guess I need to figure out if I can build some of my own simple debugging primitives in ST.  I hope you guys consider adding on-board debugging capabilities, soon!  If you do, or if you already are, I would be happy to be a focused and communicative beta tester for you on that functionality.

    Best Regards,
    Al

     


  3. I'm fairly new to Sysmac Studio, and the NJ series, but have done a lot of automation work for years.

    It appears there are four ways to write/run code in the NJs, but there is only monitoring/debugging support for three of them:

    • Ladder logic running on PLC: connection highlighting and variable watch/modify
    • Ladder logic running in simulator: all the simulator single-step and other debugging tools
    • ST running on simulator: all the simulator single-step and other debugging tools
    • ST running on PLC: no way to debug or single-step?

    Is my understanding here correct?  I am just starting a large project that I was intending to do largely in ST, but if I can't single-step execution on the PLC, set breakpoints, etc., that's not going to work out very well for me and I guess I would have no choice at that point but to revert to ladder logic.

    Thanks!

    --Al


  4. I've been through all the documentation I can on CX-Programmer, and for the life of me I can't find out what a small symbol means that has recently appeared on some of my instructions. It looks sort of like a capital 'T', I've attached a small screen capture that shows it. What is this thing? Thanks! -Hoobs WhatIsThis.bmp