viman

MrPLC Member
  • Content count

    45
  • Joined

  • Last visited

Everything posted by viman

  1. Sending data from CJ2M to CJ1M

    If your CPUs have RJ45, Omron FINS ethernet is the easiest choice. I usually wire multiple CP1L-E that talk to each other in a network like this. It doesn't work to the same extend with a regular CP1L with CP1W-CIF41 - this can only REPLY back data. It won't process any network commands in the program but can answer a call. Set up the IP address and the FINS node on the configuration page of each PLC - nothing else needed. CPU1 is 250.1 node 1, CPU2 is 250.2 node 2, and so forth. Drag the SendData function block from the CX-Programmer library and set the parameters. Network address should be local network (0 - default). Node address is the node of the CPU you want to send data to. Unit address is the type of device (0 for a PLC - default). Send/receive area ID is the type of memory you want to exchange (P_WR for Ws, P_CIO for I/Os, P_DM for Ds) Send/receive area number is the starting channel to write from/write to. Data size is the number of channels. This is all in the pdf you bring by hitting right click -> function block reference. You can use the opposite function, RecvData, to read from a PLC that can't send commands, like the aforementioned CP1L.
  2. Connecting to this controller

    There's a CNC machine with Siemens hardware raising an error. It says the SINUMERIK 810D cannot connect to the controller. It used to take ten minutes, then half an hour, now it's not working. The S7 is giving a SF alarm, I need to connect to it to see what's the cause, but I'm an Omron guy so I need some help in this. This is the S7. It's mounted to the right of a Siemens power supply, all good, tested. I have the MPI adapter that works with the S7-300 with native serial port, but obviously here it doesn't fit. I have no idea if just a getting a new cable for the adapter will work. I don't even know if one can connect to this. I'm getting a vibe this is a only coupler for the SINUMERIK to use remote IOs.
  3. Necroposting but I had the same problems with a DX200 and a NX controller. I posted this already in the Sysmac Studio request thread. The error Sysmac was giving me is the same as the OP, Tag Data Link Connection Failed. And like the OP, all the parameters both from the robot and plc looked correct. The solution for me was to use CX Network Configurator. I set up the same connection settings inside Network Configurator and it worked instantly, but still learned a thing or two that I'm going to post. I can vouch for them. The configuration instance in the robot CAN NOT be 0. The configuration size in the robot CAN NOT be 0. Input and output size in the robot DOES NOT HAVE to be equal. I read this somewhere but it's not true. You can mix types of variables in the plc as long as the total byte size is the same as in the robot. Mixing types of variables are not the source of the problem. I don't know why but the DX200 does not work if the configuration instance and byte are 0. And I think this is the root of the problem - in Sysmac Studio there's no setting for configuration so the plc must be getting 0 as value. Worth noting that in a YRC1000 I had to do exactly this to make it work. I had to set 0 as configuration instance and size in the YRC cause it was the only way to establish the connection, further cementing my belief that all these issues arise from the ethernet/ip parameters that are missing in Sysmac Studio. I'm aware there's a rather hidden menu where you can change more options (right click EDS file -> Edit). It's been discussed in this thread. But, still, setting all these parameters the same way as Network Configurator does not work. The same virtual configuration in NC works and in Sysmac doesn't. But I don't know if it's a bug of the current version. Lastly, here are my settings that are currently working.. DX200 INPUT SIZE: 8 BYTE OUTPUT SIZE: 2 BYTE CONFIGURATION SIZE: 1 WORD INPUT INSTANCE: 101 OUTPUT INSTANCE: 102 CONFIGURATION INSTANCE: 103 NX1P2 Create the variables and tags and the rest of the connection. Send to controller. Create a Network Configurator project with the same configuration as in Sysmac Studio Send to PLC and don't forget to reboot. It won't take the changes if you don't power it off.
  4. Encoder cards have bits to enable or reset the value, but they are not mapped by default. You have to map, if I don't remember wrong, the STATUS word inside the configuration of the module. Then you can either map that word to a variable or the individual bits you want as contacts/coils, and set the reset coil ON for a single cycle. I made this in the past, I'll look for the code and post it.
  5. Inflation - Cost Increases

    Here in Europe I'm seeing 7+ months for plcs, relays, inverters, even terminal blocks, along 4-10% raise. Insane. I have been expecting an Omron CJ CPU for more than a year and a half, and they told me things are getting worse actually.
  6. Greetings, I'm currently connected to a NT20S-ST128B display. I got the communications working, the NT software (4.87) recognizes the touchscreen, but I can't backup the data. I'm going to throw it away but I need a backup to recreate the program in a new HMI. It throws this screen, which is kinda self explanatory. I downloaded the software 'NT2S_Version1.3C' from mrplc but I can't install it. This dos tool it asks for.. is it available anywhere? Thanks
  7. That software is missing something. I downloaded the same version from myomron (account area) and all the menus that are missing are in this one. It has more files in the zip. I managed to backup the whole screen, I did as follows.. Own RS232 cable, with CPM/CQ pinout (M2-F2, M3-F3, M4-M5, M9-F5, F4-F6, F7-F8) Serial converter to USB (ftdi) NT Support Tools 2.23 from myomron, executed in virtual machine WinXP x86 Configure ftdi driver to port COM2 Bring the hidden configuration screen in the HMI (pressing two corners at the same time), selecting Transmit Mode F7 key menu in the NT software to backup
  8. Also make sure your RS232 cable is an actual serial port emulator. I always encountered issues until I got a FTDI cable
  9. connect encoder to nx1p2

    The variable in question is registered on the IO Map menu just like any other input/output. There you can see what data type the encoder value is using and assign a name to it. I suggest you enable the Controlword input (I think - need to check this) on the card's side parameters, since I have needed to reset and enable manually the encoder reading in every single application that used one.
  10. You can also copy paste FBs betwen different Sysmac Studio instances. 
  11. Lenze i950

    Check my thread about a Yaskawa ECAT servodrive, it took me a lot of time to figure out and you may get some guidance from it. It sounds like you are getting the same behavior from the motor as I did. Rule of thumb, get the trial of Twincat3 on your computer and connect the drive directly to it. Use your computer as ethercat master; you can still test the motor even if it tells you your network card isn't ethercat compatible. See if it works with it. From there I just started comparing the chunk of parameters of the servodrive written by Sysmac and Twincat, and found out which ones were being wrongly set by SS. That gave me a hint of what kind of PDO mappings I should modify.
  12. 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.
  13. 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
  14. 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
  15. 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/
  16. 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.
  17. EEPROM Error

    I'm understanding he's using an Omron servo drive.
  18. 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.
  19. 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.
  20. All of the ethercat servos I have installed are Omron. I have used many many brands in the past - over analog, pulse train, but not ethercat. I have one of the Yaskawa servopacks that can control two servos independently. The drive is all wired (POT, NOT, safety), autotuned, it's in RUN OK state, I have installed the ESI file, set up the axis, mapped the PDOs.. it's all working, but they do not move. I made a test program just with MC_POWER and MC_MOVEJOG/MC_MOVERELATIVE/MC_MOVEABSOLUTE along with the resetting of MC and EC and the servos do turn on, but ignore any movement command. They do not flare up with an error, and they give me their actual position, so the network is working. If I send the movement command the command position starts to differ, so the plc is/should be sending the command. I feel like there's something missing in the PDO mapping screen, but I didn't need to do all of this with Omron so I have no idea. I thought at first the servos needed huge units of movement and speed but the actual position value confirms this is not the case since it doesn't ever change.
  21. 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
  22. 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
  23. 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).
  24. 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.
  25. 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.