Hello Guest it is April 29, 2024, 12:53:59 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jofriedl

Pages: « 1 2 3 4 5 6 7 8
71
CS-Lab / Re: Matsuura MC500v retrofit with CSMIP/IP-A
« on: January 02, 2015, 12:05:01 AM »
Hood,

   That tool setter looks pretty impressive. Nice work! I like your brushed stainless switches. I just ordered a boatload of switches and a pair of joysticks from Automation Direct. The first machine i retrofitted I ran solely off the keyboard and mouse and I can tell you it gets old.

    I made it to the shop tonight and started gutting the machine. For some reason, on projects like these, I plan to precisely excise only the components and wiring I know I won't need, but I end up getting carried away. And tonight, I got carried away! There is little left of the original machine innards and wiring, Limit switches, encoder signals, transformers, power wiring, wiring to the drives and the drives themselves. The rest is piled on benches beside the machine.

    This brings me to tonight's question: Is it really worth it to salvage the original drives? If I were to upgrade to new drives like Advanced Motion Control Drives, what could I expect to pay? I would have called AMC myself today but being that today is a holiday I didn't even bother. I'm sure they were closed.

    Per the encoder wiring, I have attached a picture of the encoder ID plate on the outside of the motor. On the wiring diagram there are 9 connections and I'm assuming that two of them are the tachometer. Since it is a single ended encoder, D will be the common ground for each channel.  Connections labeled E and F I'm assuming are the power connections. Not sure about the other connections though.

Jonathon


72
CS-Lab / Re: Matsuura MC500v retrofit with CSMIP/IP-A
« on: December 31, 2014, 06:00:43 PM »
Thanks for clearing that up, Hood.

 I was looking at pages 2 and 4 of the manual. The servopak wiring looks fairly simple. But I was under the impression that most servo drive to servo connections included the encoder feedback. Is that not typically the case? From the look of the diagram on page 4, the encoders are not connected to the servo drive.  Once again though, reading electrical diagrams is not my forte.

Something else that caught my eye is that reverence input is rated from 4 to 50V. I suspect that the reference input is the analog voltage signal you referred to in your last response. If the servopaks truly require such a range, I'm thinking I might have to start looking for replacement drives. I remember reading another post in which you mentioned the brand AMC drives.

Another question; I know that CS labs sells an mpg module, but I'd like to use the original mpg in the yasnak control panel. I haven't done the research to know for sure, but I am almost certain that I can wire in the module through the discrete inputs on the ip-a. However, I also have a DL06 connected to mach3 via modbus tcp via ecom module and I'm wondering i there would be any advantage to running the mpg through the plc. Scott, AKA 'Poppabear' described the ecom module as blazing fast so I'm wondering what would be faster, digital inputs though the ip-a or inputs via the plc? This will also determine where the tool touch probe is wired.

Jonathon

73
CS-Lab / Re: Matsuura MC500v retrofit with CSMIP/IP-A
« on: December 31, 2014, 03:39:49 AM »
oops! I attached the wrong portion of the wiring diagram. Please see the attachment bellow for wiring of the servo motors. Thanks!

74
CS-Lab / Re: Matsuura MC500v retrofit with CSMIP/IP-A
« on: December 30, 2014, 11:15:33 PM »
Hood,
 You're just the guy I hoped would respond! I've read quite a few of your posts. Thanks for your response!
I haven't been able to find a manual for the cpcr mr 52, but I have found a cpcr mr 01C - 07c. ALso, Foothills Machinery out of Denver contacted me today to let me know they found electrical schematics for the mc500v. I'll be honest, I don't have the background to fully understand these wiring diagrams. There are a few things I can pick up, but I need to learn a bit more before I can figure out where to wire step and direction inputs and encoder outputs. In the attached image bellow, the wires are there and numbered, but not labeled in great detail. I'm assuming PC stands for pulse counter. As for T.G. stands for, not really sure. Also, the diagram depicts connections between the 3000g controller and X,Y and Z axis motors. I hope they mean X,Y and Z servopacks, because the controller will wire up to the servopacks alone. (step, dir and encoders).

 This retrofit i my first experience with servo controlled systems, so If I am missing something, feel free to mention it. Thanks!

75
CS-Lab / Matsuura MC500v retrofit with CSMIP/IP-A
« on: December 29, 2014, 11:53:50 AM »
Hello there guys,

      Just like the title says, I'm working on a Matsuura retrofit that I'm pretty excited about. The machine is a 1979 Mc500v. The motion controller is a CSMIP/ip-a and an Automation DL06 will be running the tool changer. At this point, I'm well on the way to having the PLC programmed. I also finished ironing out the M6 macro last night.

     I could definitely use your guys' help with the ethernet controller integration though. When I initially concocted the retrofit, I planned on using a digital encoder and swapping out the servos. However, after reading about Hood's success with the analog version, I took the leap and bought the IP-A in the hopes that I could simply wire it to my existing yaskawa drives.

     I contacted Yaskawa hoping to obtain electrical prints for my servopacks. After bouncing from one department to the next, I was finally told by a Tech that all schematics are proprietary (never mind that they have other servopac prints available for download on their website ). It was suggested that I contact matsuura and obtain electrical prints for the machine. While Matsuura USA is more than willing to share their prints, they have been unable to locate the schematics for my machine. So my first question is, does anyone out there in Mach land have schematics for Yaskawa CPCR- MR 052 NB servo drives?

     As a side note, the DL06 is a pretty cool device! I highly recommend them for anyone implementing a tool changer.

Jonathon

76
Modbus / Re: AddressingTCP Modbus registers in VB
« on: December 26, 2014, 09:34:00 PM »
Well, I think I may have found a way around the problem. I had read that the registers can be called via VB through the command GetMasterInput(0-1023) where 0-1023 is the local address listed as Local(VAR) in the TCP modbus setup page. However, I couldn't seem to get that to work. Instead, I am using a brain to write the register values to a DRO and then reading from that DRO via the command GetUserDRO(###). So far this seems to be working. The only drawback is that you can't really access bit of word through a DRO/brain setup.

77
Modbus / Re: AddressingTCP Modbus registers in VB
« on: December 26, 2014, 01:48:41 AM »
I should also have mentioned, the only means of communication between the pc and plc is an ECOM module.

78
Modbus / AddressingTCP Modbus registers in VB
« on: December 25, 2014, 08:01:24 PM »
Hi,

    This is the first of what I'm sure will be many questions about how to get an Automation Direct DL06 to run the tool changer and spindle on a machine retrofit I'm working on.
The tool changer is a 16 station carousel run by what I presume is a stepper motor (the ID plate is worn off and Matsuura USA is still trying to source the wiring diagram for the machine) and 4 pneumatic solenoids. Originally I planned to use the m6 start macro written by the guys over at Machmotion. (see bellow) The macro is designed with the DL06 in mind and also comes with a ladder program which can be downloaded and written strait to the dl06. However, the addresses listed in the macro for current tool and max tool were all wrong. The octal address in the DL06 for max tool is V1206 while the modbus address translates to 646. I confirmed this address in the mach3 modbus test window. The addresses listed in the Macro don't match up at all. But, even when I changed the addresses in the macro to the appropriate addresses, I still can't seem to get the M6 macro to communicate with the DL06. My question is this, what is the protocol for accessing and writing to modbus tcp locations in VB? I'm talking both discrete input contact locations and reading complete word data like analog input or current tool value.

    Ive spent the last few days reading all I can about modbus tcp in mach3, watching all the relevant videos on the artsoft tutorial page and reading forum posts pertaining to using DL06s. After seeing what some of you guys are doing with them, I'm pretty excited to learn all I can about them.  I'm an oil field welder by trade, so most of these concepts are fairly foreign to me. Thanks for any and all help!

This is the m6 start macro

Dim Num As Integer
Dim Number As Integer


Sub Main


TimeOut = 20 '20 Seconds


''''Inputs'''''
Finished = 1600
CurTool = 1605
MaxTool = 1606    


''''Outputs''''
StartVal = 1500
ComTool = 1505


CurrentTool = GetUserDRO(CurTool)

MaxToolNum = GetUserDRO(MaxTool) ''From PLC
CommandedTool = GetSelectedTool()  ''Get selected tool


If CurrentTool = CommandedTool Then ''current tool equals commanded tool
SetCurrentTool( CommandedTool )
End
End If


If CommandedTool <> Current_Tool Then ''The current tool must be different than commanded tool


   If CommandedTool > MaxToolNum Or CommandedTool < 1 Then ''Make sure the tool number is correct
      r = MsgBox("Incorrect Tool Number.",1, "ERROR")
      End
   End If



   Code("G00 G53 X " & GetOEMDRO(1200) & "Y" & GetOEMDRO(1201) & "Z" & GetOEMDRO(1202)) ''Move to correct location
   While IsMoving
      Sleep 10
   Wend

   SetUserDRO(ComTool, CommandedTool)   ''Send Commanded Tool to the PLC
   SetUserDRO(StartVal, (GetUserDRO(StartVal) + 32768)) ''Turn on
   Sleep 500
   SetUserDRO(StartVal, (GetUserDRO(StartVal) - 32767)) ''Turn off
   While (GetUserDRO(Finished) And 32768)
   Sleep 100
   i = i + 1
   If i > (TimeOut*10) Then ''Time out in 20 seconds
      r = MsgBox("Tool Change is not Complete.",1, "Timeout Error")
      Sleep 100
      End
   End If
   Wend

   
   CurrentTool = GetUserDRO(CurTool)
   
   If CurrentTool = CommandedTool Then ''Does the current tool from the PLC match the commanded tool?
      SetCurrentTool( CommandedTool ) ''If so, update tool number
   Else
      r = MsgBox("Tool Change Failure.",1, "Error") ''Else somethine went wrong
   End If
 
 

 
End If ''Tool commanded position is different than current position

End Sub

 
      

Pages: « 1 2 3 4 5 6 7 8