viman

MrPLC Member
  • Content count

    37
  • Joined

  • Last visited

Community Reputation

1 Neutral

About viman

  • Rank
    Sparky

Profile Information

  • Country Spain
  1. omron nt2s and ntxs-nt2st software

    I know. But he's going to need that virtual machine if he wants to use whatever software that display needs.
  2. Sysmac Studio IDE Very Slow

    Yes it is. Some days I get sick of it. It takes literal minutes to open a project, three minutes to detect a dropped connection, four seconds for each contact and relay you place in online editing mode. Removing a whole rung cause you didn't click in a specific part of all the white space, still the bug of selection rectangle not taking mouse client coordinates, variables taking forever to update in online, project compiling like every twenty seconds putting the element you are in out of focus. What about the awful performance of the simulator? CX-Programmer had all these things working better already
  3. omron nt2s and ntxs-nt2st software

    I had to set up a virtual machine with winXP to be able to get NTST working (older software). See my thread down this subforum, https://forums.mrplc.com/index.php?/topic/40250-nt-suport-tool-data-created-by-dos-tool/
  4. EEPROM Error

    Maybe the initialize feature needs the plc to be in PROGRAM mode. CX-Programmer behaved like this. If you are online in the plc, look for the PLAY/PROGRAM buttons next to the online/offline buttons. Click PROGRAM and try to initialize the drive. If it's not working create a new project, drag your drive from the toolbox in the ethercat category, go online and click Transfer to Controller (NOT compare). Like this Then click on the drive and open the parameter list, and from there click the Transfer All to Drive button.
  5. EEPROM Error

    I'm understanding he's using an Omron servo drive.
  6. EEPROM Error

    What's the reference of the drive? If it has buttons you can probably initialize setting a parameter. If not you are going to need a Omron NX/NJ to be able to transfer all the parameters from Sysmac to the drive. The parameters loaded by default when assigning the drive under the ethercat network should be the same as factory defaults.
  7. The paper in question is SIEPS80000219, chapter 13. End of the road anyway. With those parameters I can use jog, absolute and relative movements. I also tried linear interpolations and other sync movements and it seems to work. Looks like they all use the same mode of operation. Omron told me they know first hand that NX works with Yaskawa SGD7S via ethercat. Mine is a SGD7W but aside from controlling two motors instead of one all the parameters are identical, so I don't know what's going on.
  8. I will check the manuals but I haven't seen any SDOs so far. I did find however what the controlword and statusword mean in this drive. I'll locate the paper later and post it here. Time is running out so I'm just going to make the homing sequence myself. I just needed to confirm if the plc was able to set that mode of operation parameter correctly on its own, so it can command the servo later via MC_MoveX commands. It does, mapping just the following PDOs in the 2nd channel or whatever it is. Controlword Target position Modes of operation -------------- Status word Position actual value Modes of operation display Inputs Anything else than that makes the motors stop working. With this the plc can change the mode of operation from 0 to 8. I confirmed this by resetting that value manually on the drive, so it appears twincat isn't necessary. I can use the MC features I need except homing. These two motors have to work in sync at some point, but I guess (hope) that it falls back to the controller and works too
  9. Not really. You can't do anything with it other than mapping it to the axis, and since it's an output you can't assign it to a variable (unlike PDO inputs). I also discovered the MC functions don't work if I assign PDO objects to the 1st transmit/receive. I can only use the default 2nd, adding objects there if necessary, but that might be a requisite on Yaskawa's end
  10. I left work late trying to understand what's not working. I have compared the parameters doing everything in Sysmac and the key is the 'mode of operation' parameter. Twincat immediately sets it to 8, which per the manual means the drive works in cyclic position mode. Sysmac sets it to 0 (no operation) under some circumstances I still haven't figured out. I can edit it manually with the drive's own software and the servo magically starts moving, but it's not a solution if the plc randomly changes it. Aside from that, since the plc is not writing that parameter correctly, I still haven't been able to home the motors (requires changing mode of operation to 5).
  11. Thanks all for the responses. I got it working under the NX, but I can't yet say what's going on. I was following Yaskawa's quick guide for ethercat servos (AN.MTN.03) but yesterday it wasn't working so I thought about resetting the drive to factory defaults. After that I have done the same, connecting the drive directly to my computer (working as ethercat master, with no plc or coupler in between) and letting twincat 3 scan the network. It's working, but there's a catch. If I do anything else than adding the drive to the ethercat network in Sysmac Studio (pdo mappings, enabling some setting, whatever), the drive stops working under any condition. It doesn't work anymore in twincat either as long as I don't factory reset and let twincat configure the network again. Sysmac Studio must be sending some wrong parameters cause it breaks the drive. Reminds me of my past thread where the ethernet/ip wasn't working and it turned out to be Sysmac too.. If I have time I will extract the parameters that differ in the drive from twincat vs sysmac
  12. You are absolutely right. That's where I put the spotlight on this morning, since all it did was change from 0000 to 000F. The drive shows the actual command parameters (target velocity, target position) correctly as I send them from the plc, but I really doubt 000F is positive for movement. I once programmed pulse output manually in a NX and most bits of the controlword had to be activated. 000F looks like nothing. I may try to recreate that project but I counted with a lot of info that time. Unfortunately, and answering your question, there's nothing regarding what it means in this drive. I did ask Yaskawa for these details however. I'll get the controlword value sending the movements from twincat as the guide says, and see if it differs.
  13. Thanks, I'm already in contact with both. But I always end up coming to this forum  Yaskawa's response is that so far everything looks correct and it should be moving. I went back to factory defaults and followed their quick guide for ethercat servos using twincat, since I have used Beckhoff in the past. It exhibits the same behavior there as in Sysmac. I can't jog the motor but it shows the encoder response. I identified the issue with the 'soft servo on' though. It happens if I map the torque value PDO in Sysmac. I got rid of it, mapped the default PDOs, and works as it should now. Omron's investigating my project. I'm gonna try hooking their G5 servo to twincat. If it works there I can definitely rule out the plc.
  14. No, there's no errors. Neither from EC nor MC (from plc/drive side, all OK). The move instructions do not throw errors either and they do set the done signal. I can't home the servo at all since it doesn't move with MC_Home. There's something weird going on though.. MC_Power powers the servo but I can still move it with my hand. There's the internal relay activating inside the drive, but the servo doesn't have power whatsoever. Which is different from when I jog it from the yaskawa software - it sounds much louder, like they always sound like, and I can't move it manually (like it should be). I have connected a spare Omron ethercat servo I have and it works with the same code, so either there's something wrong in the PDO mappings/ESI file or the drive is faulty/not compatible.
  15. AFAIK it's not necessary as long as the motor can reach the target speed. But I did try all kinds of values for acc, dec and velocity. From single digits to millions. The motors don't move since the encoder is always showing the same value. It does change if I move the motor by hand.