Search the Community

Showing results for tags 'altivar'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 6 results

  1. i am using a VSD Altivar71 and controlling it through serial MODBUS communication, the probllem is sometimes after stoping the motor the drives gives the "nst" fault which means according to the programming catalouge "freewheel stop" it doesn't do that all the time but it happens a lot and after uploading the code again to plc the problem is gone for a while before it happens again. i am sure that the fault is happening because if communication because when i controll the drive from hmi it never gives that fault, i checked the setting and tried different cables but it still gives "nst" and motor never moves, i found that in catalouge but i am not sure how to address the problem.
  2. i have a plc Modicon M340 , HMI hmigxu3512x and VSD Altivar 71, and i only allowed to use serial MODBUS port in plc, now the VSD is a slave and is controlled with plc as a master how can i add the HMI to this configuration?? i know that this model of HMI can be slave but then how it will give orders to PLC to start stop etc.. and if PLC is slave how it will control the VSD??
  3. I connected between Altivar 71 VSD drive and Modicon M340 PLC through MODBUS RTU RS485 and the communication is ok, now i want write  a command word using Write_var function to control the VSD but I find very confusing. first : it's written in cataloug that bits from 0 to 15 can be assigned to commands , is that done from HMI? i  can't find anywhere on HMI. second : in the function (both read and write) obj element can be int or bool bit but the EMIS element  in 'write_var' function (data going to VSD registers) only accepted if it's array of int not bool so i can't trigger the bits i want !! third : like the picture the VSD showing it's in NST mode and it says that it won't start until hex value of 6 written to command word but the catalogue says that only bit 0 is assigned(to forword command) and other 15 bits are free for user to assign and 6 in hex (0110) bit 1 and bit 2 still not assigned to any thing  !! i hope anyone could help 
  4. schneider somachine

    hello everyone,  Im new with schneider electic , ı m planing to work with Altivar 630 variable speed drivers and i want to control it with M241 plc in somachine . but when i want to configure in somachine i could not add the driver to my hardware. is there any document about it ? or does anybody control it like this ? 
  5. FX3U-ENET and Modbus

    Hi There i have heard from our local mitsubishi dealer, that there is a Fx3U-ENET module which also supports Modbus TCP. so i ordered one, because i am planning to do a Project using a atv71 FU and a Codesys PLC, so the plan is, that these 3 Devices are able to communicate together over Modbus. has anyone done something similar before? what do i need to setup in FX-Configurator EN, and how can i send modbus commands through that module. i am using GX-Works 2 and have a Structured project. any help would be appreciated. thank you jason
  6. 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.