chantecler

  Searching the internet I found these four: Sisteme Helmholz 700-884-MPI21 NETLink® PRO Compact IBHsoftec IBH Link S7++ MPI / PROFIBUS / PPI - Ethernet CommDTM for FDT hilscher NL 50-MPI S7-200/300/400 Ethernet programming connector DeltaLogic ACCON NetLink Pro Compact MPI-Profibus-PPI to Ethernet Gateway BUT at the end my client decided to buy an original costly Siemens 6ES7972-0CB20-0XA0 which is a PC USB adaptor And I did the job   Note: There are some Chinese versions of this adaptor that can be found on ebay at one tenth of the price, if you have the time to wait for its delivery.    

Hi, I decided to restore the PVP6 to its factory default state, after that I upgraded it to V9.0 again, configured it, downloaded my app again and everything is working fine. Problem solved, mystery unsolved. Bye  

Hi all, Recently I upgraded a PVP6 from version 7.0 to version 9.0 since I needed it to communicate with a 5069 CompactLogix Controller (L320ERM V30). I am still developing my app in FTView 7.0 because this is the latest version I have. By the way, now they communicate but not fully. The PVP6 accesses variables like Loca:1:I.Pt00.Data but opposite to the PV5500 it does not access variables like Loca:1:I.Pt00.@Description Now the weird part: The last time I downloaded an app to the PVP6 it stopped communicating. Then I examined the PVP6 and it was showing the desktop and no app was running. I managed to get into the terminal configuration and found that the device’s name and IP address had changed. I introduced the name and address back, checked that the desktop access was set to Disallow, downloaded my application again and now the application runs, the PVP6 communicates but it still shows the desktop. I hided the task bar but every time I reset the terminal it still shows the desktop prior to run the app. I haven’t put much effort on this yet but ideas will be appreciated. Thank you, Bye    

  I faced a situation kind of related to this topic. I am working on a project replacing the control and servos of a punching press (the project is getting to the installation phase only waiting for some items to arrive). The original idea was to replace only the controller, but the servos communicate with the controller via CANbus network with CANopen protocol. I couldn't find a way to control the servos with my CompactLogix controller cause AB as far as I know does not support CANopen so I ended up replacing the servos too. CANopen is widely used. I wish AB supported it. I suppose the situation is similar to Profibus's 

Hi guys, Is there any way to preserve the current value of a variable present in the PLC when I download a program with RSLogix 500?. I mean that I want to download a modified program without overwrite some data. In this particular case I am doing some improvements to a program and when I download it I do not want the machine production counter to be modified. Thank you  

Thank you Ken

Two screen shots of your short program Bye

Hello mr Attached a copy of an excel spreadsheet contaning links to many cad drawings form the RAISE library (hope this is legal) I downloaded a couple PLC-5 drawings and worked well You can also download and install eCADWorks form the Rockwell site Bye Drawings.zip

Hi Armadillo852, I visited the CCU link. Very nice story and very interesting character (this Chantecleer) I borrowed the name from a movie I watched with my children years ago called Rock-a-Doodle I think the movie was based upon an Edmond Rostand’s play called Chantecler Edmond Rostand is better known for his Cyrano de Bergerac Bye  

You're probably reaching your vfd's current limit or the motor speed is too low. I suggest to check the current and also consider using a reducer gearbox or pulleys.

Hi colleagues This may sound crazy but don't forget to check for mechanical disturbances like wind, vibration coming from the floor, etc. Check if the weighing device has any kind of damper. Check if your load cell is well fitted and doesn't move To determine if your noise source is electrical, check grounding, check module inputs isolation, check noise coming from your power supply. The last can be checked with a voltage tester in mV AC. Good luck  

Is the belt a motorized belt? Does it stop moving when there is a real jam or continues sliding under the boxes? Maybe you can monitor the belt's speed to help you decide when you have a real jam. Another idea (in case you must create a gap): Every next belt should move faster than its predecessor.  

Could somebody let me know how to copy the input data from a 5069-IB16 to an integer within a single instruction like a “MOV” or a “COP” (in ladder diagram please).   I can do it bit by bit like this:   Local:6:I.Pt00.Data ---[]-------------{}---DI_01.0                   (DI_01 is an INT) Local:6:I.Pt01.Data ---[]-------------{}---DI_01.1 Local:6:I.Pt02.Data ---[]-------------{}---DI_01.2 . . . Local:6:I.Pt15.Data ---[]-------------{}---DI_01.15   But this is not efficient   Thank you, very much

You don't set the value of the Motor Offset. If you do the Commutation Test or know the commutation offset and it is different from the Motor Offset determined by the system then use Controller Offset, introduce your offset value and this is what the drive is going to use. Bye

From "motion-rm003_-en-p.pdf" "The Commutation Offset attribute is a value that specifies the commutation offset of the PM motor mounted feedback device in units of electrical degrees. This attribute specifies the offset from a commutation reference position defined by applying DC current into the A terminal and out of the shorted B and C terminals of the motor and allowing the rotor to move to its magnetic null position relative to the stator. On an absolute encoder or resolver, the offset is the difference from the device’s zero absolute position and the commutation reference position. On an incremental encoder or Hall sensor with UVW signals, the offset is the difference between the position corresponding to a transition of the commutation device’s W (S3) channel (with the U (S1) channel high and the V (S2) channel low) and the commutation reference position. The commutation offset is only applicable to the motor mounted Feedback 1 device. When the optional Commutation Alignment attribute is supported and set to Controller Offset or Database Offset, the drive shall apply the Commutation Offset value from the controller to determine the electrical angle of the motor. In this case, a valid Commutation Offset value must be entered by the user, read from the Motor Database, or determined by the Commutation Test. In the unusual case where the commutation offset is also stored in the motor, and differs significantly from Commutation Offset value from the controller, the drive shall transition to the Start Inhibited state. If the Commutation Alignment attribute is NOT set to Controller Offet or Database Offset, the Commutation Offset value from the controller is ignored by the drive and the drive must determine its internal commutation offset value by other means. Without a valid commutation offset, the drive shall be Start Inhibited." Bye

Hi, Not sure what your hardware is. Do you have the encoder and the drive in the same ethernet network? What is the encoder mechanically connected to? a motor, a shaft that the drive is moving or following? Please tell me more.  

Hi, In your project tree, right click the encoder and select "properties", select the Configuration Tab, check "Enable Scaling", introduce the resolution you want (for example: 3600) and click "OK" Ah! and read the User Manual (recommended) Hope this helps Bye  

Dear pc, This is a whole new topic. According to the knowledgebase subject referenced earlier, Rockwell says there isn't 3.001 AOP so you have to use 2.001 I haven't gone deep on the view designer thing but apparently 3.01 does not create apps for lower versions I must go now but will visit this later Thank you, bye  

Hi cyber-friends, I am working on a project using a CompactLogix 5380 model 5069-L320ERM and a PanelView 5500 model 2715-B10CD. I am developing the PAC app with Logix Designer V 30.00.00 and had to flash the PanelView to V3.001 to be able to download the app from View Designer 3.01 The problem is that the PAC and the HMI refuse to talk to each other and the PAC reports a device mismatch. The PAC allows me to select Panel mayor version 2 only I disabled keying but it didn't work According to knowledgebase subject 1028835 there isn't any V3.001 AOP but there shouldn't be a problem Any suggestion? please

Issue solved. Finally they get along together I was giving the HMI a wrong path to the controller. My fault.  

Thank you for your time pcmc, I really appreciate it. I tried deleting the PV from the tree but they still refuse to work together. I have always added the HMI to the tree in the past with no issues. In this case it is important since the machine is controlled from the HMI and I want the controller to go safe if the communication be lost. (I always prefer to use HMIs for configuration and error reporting, but in this case I have to use it to control the machine as well) This is the first time I utilize this hardware. My client wanted something future-proof and I am hoping I didn't do a bad choice.  

Screen shots attached

Yes, the PV is in the I/O Configuration tree under A1, Ethernet. By the way, I am using dual ip Ethernet mode. I am using port A1 for HMI and port A2 for motion control.

Hi, You just have to go to the Encoder Products Company website (http://encoder.com/) download the incremental shaft encoder model 725 datasheet and the Installation and wiring guide. If you do so and you decode your part number you’ll find (please check this) that you have an incremental quadrature open collector encoder with no Z channel. Connect: Terminal F to supply COM Terminal B to +24V Terminal A to PLC A input (I would use I00, the programmer has to tell you which one) Terminal B to PLC B input (I would use I01, the programmer has to tell you which one) Terminal G to ground Leave other terminals unconnected Now, if you look at the wiring guide you’ll find that you have to connect a 2.2K, 1/2W resistor form each input to +24V (my personal preference is to use 1W resistors for high ambient temperature and for long life) Bye

Hi Stan, The fuses are placed there to protect the contacts against a shorted solenoid. According to the module installation instructions the recommended fuse size is 3Amp, so my conclusion is that your 2Amp fuses are well sized and you have to focus on what is shorting your outputs. I would check: 1st. If the terminal base is appropriate for the working voltage (see: Installation Instructions) 2nd. If the working voltage is really 120V 3rd. If the solenoid working current is bellow 800mA which the contact capacity for inductive loads I would also consider: 1st. Installing a snubber circuit in parallel to every solenoid (not to the I/O contacts) 2nd. Interposing a higher capacity relay between the I/O contacts and the solenoids