Advanced Search

Hi,

Would you take 400euro for it?

Regards,
Alex

I'm sorry I have no need for it. There is already enough stuff collecting dust on my shelfs.
I just thought you might get more response if it was clear that the cables were also included.

Hello,

no one interested in a 3 axis, 400W servo system for well under 1k euro?!

I am surprised

@Aciera if you are interested you can send me an email to flawapawacrew -at- hotmail.ch and we might find an arrangement. 

Cheers,

flawa



 

blazini36 wrote:

OK, so you're refuting what dm17ry said? Like I wouldn't do that, not with Yaskawas or Mitsus

Jumping the gun a bit Blazini, he explicitly mentions "not the pulse train ones":

dm17ry wrote:

i've been playing with several generations of mitsubishi/yaskawa position controlled servos. not actually a pulse train though, but sscnet/mechatrolink - but that shouldn't matter.

Apparently it does matter, but that would require much more testing and with a pool of devices.

Aciera wrote:

You have to ask yourself "why is no one else having the same issue running Linuxcnc and servos in closed loop". Maybe the issue is with DMM servos not being well built.
 
Actually, it's not uncommon to have delay issues when using drive generated feedback.
I had the same issue using  Mitsubishi MELSERVO J4 drives with step/dir.

There is a whole thread about that here:
forum.linuxcnc.org/10-advanced-configura...pain?start=30#193073

From that thread:

dm17ry wrote:

i've been playing with several generations of mitsubishi/yaskawa position controlled servos. not actually a pulse train though, but sscnet/mechatrolink - but that shouldn't matter.
so, they all exhibit similar behavior. there's no way to eliminate this time lag completely with tuning without introducing serious overshoots. but to counteract it, those protocols have a provision to latch the motor encoder counter at encoder z-index or some external signal wired directly to the drive. when that happens the drive raises a flag and controller can read back the latched position. kinda like linuxcnc's index-request...
 

Isn't dm17ry the guy who makes LinuxCNC controller cards for Yaskawa/Mitsubishi servos? He's also the guy with the infamous pick and place machine right? These guys are talking 5-10ms delay on the encoder outputs on much more expensive Mitsubishi servos so maybe we should lower our expectations a bit for DMMs

Hello Aciera,

yes, cables are included. They are several meters long.

Attached a photo of what I am selling (linear stage not included in the price, if you are interested let me know).

Here are some videos of it running:
youtube.com/shorts/I-b58vQV19A?feature=share


I noticed that the drive's (braking?) resistor is missing (see photo, in comparision with a MR-J4-222B I have). You might need to find a spare part. I was able to run the amp but I am not sure of the consequences of a missing resistor.

Let me know if you are interested. I am in the region of Lausanne.

Cheers,

Flawa

Do the drive and motors come with the motor and encoder cables?


Note that private messaging is not possible in this forum so you may want to keep an eye on any responses in this thread.

Hello all,

I have a 3 axis MR-J4W3-444B drive and three associated HG-KR43 (400W) servos that have been sitting in my basement for one year. 

I am willing to sell the lot for ~500 euros. I am located in Switzerland and would prefer to ship within europe.

To control these, you would need a control card from yurtaev.com/yssc3p.html, which allows you to control them through the proprietary SSCNET interface.

I have one of these cards which is running a MR-J4W3-222B and servos (200W) as well as a MR-J4-70B (750W) for the spindle and it is working like a charm.

If you are interested, PM me!

Cheers, flawa

dm17ry -

I put together LinuxCNC machine configurations that let me isolate and check individual Mitsu drives. MDS-C1-SPH-110 is fine by itself. Both MDS-A-V2-0505's throw #36 'NC transmission' errors on each drive, no matter what I adjust within the .PAR files - even setting them up with Mitsubishi standard parameter for the drive and motor settings. Maybe it is a matter of re-zeroing axes, even with absolute encoders that report back as OK?

We can take this to email if it's getting into the weeds. What is the best way to contact you?

Makes sense. Fix it one by one.
Thanks!

not 100% sure, but it may be provoked by other drives in alarm state..
i would start from the end of the chain. connect the card to the spindle drive's CN1A. MDS-CV i guess is hooked to the spindle. get it up and running without alarms.
then add one SVJ before it, get rid of the encoder alarm 20.
and so on..

dm17ry

Earlier on in the thread you mentioned issues with Mitsu #36 alarm codes with some of  drives when developing theYMDS2P board.  I'm having this problem with the 2 MDS-A-V2-0505 drives in my retrofit.  Motor and drives in the intro to my PAR file below:

; Howa 320H VCJ parameters
; originally MELDAS 520AM control
;
; 0: X    MDS-A-V2-0505    HA43NC-S
; 1: Y                    HA43NC-S
; 2: Z    MDS-A-V2-0505    HA43NCB-C
; 3: JC                    HA43NC-3
; 4: MG    MDS-A-SVJ-01    HA-FH13C-Y
; 5: TC    MDS-A-SVJ-03    HA-FH23C-Y
; 6: S    MDS-C1-SPH-110    SJ-N-11LZM
;    PS    MDS-A-CV-150
; Last Revision: 06/30/23 - CK

Screenshot after startup.  Servo period is 888888ns.  I added an 'err-count' readout to the right of 'phase' display.  
 

Any idea what's causing the alarms?