Search the Community

Showing results for tags 'pacdrive'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 4 results

  1. This is hard work! I've installed the CODESYS OPC Server V3 in the hope of using it to communicate with my Schneider PacDrive LMC. Apparently the PLC doesn't support OPC tag browsing so I need to export the symbols from the SoMachine Motion project file in a format that the OPC server can use. I've got the Symbol Configuration panel open and can see the symbol tree. What do I do next?
  2. Hi everybody I have a elau c400 controller trying to connect it to a mc-4 pacdrive. But I realized that the wd led on my c400 is on and it can be a fetal error. Anybody has this experience? Regards.
  3. In my application the LMC automation controller will be calculating date-based lot codes. I would like to synchronise the internal clock with a time server such as I can't find any info in the Schneider-Electric SoMachine help files or on the web. Does anyone know if this is possible?
  4. Schneider doesn't have the Sercos 3 interface out for the Altivar 32, and I'm going to use the Ethernet/IP interface until they do (not my choice). I found documentation on the CIP basic and CIP advanced control, and honestly, I will probably use one of those two, but I'm curious about the "Native" control, which seems sparsely documented. SoMachine Motion doesn't label any of the input/output words and it looks like you're supposed to custom select parameters that will be read/written using the drive's web server. Just wondering if anyone has an app note, bonus if it's explicitly for PacDrive3. Related, I'm a little fuzzy on explicit messaging with Ethernet/IP, but it seems that's what I'll need to do to setup the motor parameters and possibly to configure the "Native" control words. Any examples of that on PacDrive3 would be nice. I have a manual with the file name: ATV32_Modbus_TCP_EtherNet_IP_Manual_S1A28701_02.pdf that has been really helpful and may even answer all my questions, but it looses me in a few spots, such as how a parameter is addressed with explicit messaging.