lostcontrol

MrPLC Member
  • Content count

    450
  • Joined

  • Last visited

Community Reputation

11 Good

About lostcontrol

  • Rank
    Sparky

Profile Information

  • Country New Zealand

Recent Profile Visitors

4645 profile views
  1. Sysmac Studio Failed to write variable in ST

    Try closing the section & re-opening.? Otherwise post a screenshot/your code so we can see.
  2. RXDU

     
  3. RXDU

    If you post your code, someone should be able to see where the issue might be
  4. Modbus frame sent to slave - strange size

     Can you send via multi-way & get a response?   my standard goto is to test with multi-way, both as a master & a slave for verification.
  5. Lost Data Memory and SCU Settings

    I’ve seen something similar once before. cant recall the CPU version, but all the module config settings had been cleared out. this rack had a SCU as well from memory
  6. NX1P2 to Indusoft communication

    The product is now InTouch Machine Edition, by Schneider/Aveva... The only results that cousin google has for indusoft-NJ/NX is to use Sysmac gateway or componet ( I think ) What is odd, is that FINS is FINS, so it should work. Only the Indusoft driver developer will be able to say why it is not working...   Update: Have now managed to get this working. There is a setting called 'Ignore non-fatal error' or similar, that defaults to No. Changing to yes enabled the basic FINS to work.
  7. NX1P2 to Indusoft communication

    Old post I know, but the Sysmac series of PLC's support FINS as well, so the OMETH driver should work but does not. I am currently trying to get this to work, but returns error code 64-UDP/IP Receive call returned error So, the question is: why is this, or what driver works with this series of PLC .?   I have an InTouch DASOMFINSEnet driver working to a NX1P2 with no issues, which is pretty much FINS  
  8. possibly, but also unlikely. One setup we have has only a single IOLink module..
  9. Interesting. The only difference I can see is that the GX variant has a higher frequency capability? Still no adjustments though..?
  10. At this stage, perhaps. What frequency will you be requiring to count at?  It is possible that you might not have the noise/interference we have experienced, but is a hard one to determine
  11. The NX-ECO can count 500 kHz yes, but it can’t do any filtering of any noise is present.
  12. Interesting, we are also experiencing similar issues that we have been unable to solve with the NX modules. i have a few thoughts, but nothijg concrete as yet.
  13. Compare not working

    I suspect there is another move further up in program, loading a #6 into H0. The way CX-P works when online, it shows the current value at end of the scan. Because you are comparing H0 to 6, the compare output is correct, then you are clearing it.   As Michael points out, the complet code will help to identify where the issue lies. But also, you don’t need the compare if you stick with the counter.
  14. I’ve never used it, not have no idea on what it even does. But, wouldn’t it be the implementation for the recovery, rather that a fault of the instruction itself.? Unless of course the manual says that it can deal with powe failure events.?
  15. Questions about CJ2M EIP

    I am not sure if PMCR is still about or lurks occasionally, maybe someone will know. It should be relatively easy to modify the code that communicates with the ML1400 to suit the K300...