i've reverse engineered many of the mitsubishi proprietary protocols a while ago... including sscnet, sscnet ii, iii, iii/h, mds-a/b/c1/d..
http://yurtaev.com
Type: Posts; User: dm17ry
i've reverse engineered many of the mitsubishi proprietary protocols a while ago... including sscnet, sscnet ii, iii, iii/h, mds-a/b/c1/d..
http://yurtaev.com
mitsubishi has been pretty generous in keeping debugging hooks in production hardware... servos, encoders you name it - most of them have a way to read the cpu address space. i have the mr-j2s-a...
i guess it's MDS-B-SPJ3-37. the only way to interface this drive is via a proprietary digital serial bus. there's no solution for mach3 exists, afaik
if you consider going the retrofit way - i have an interface card which can talk to mitsubishi MDS drives under LinuxCNC control. MPGs, threading, constant cutting speed etc. - all are perfectly...
i use a single 18650 li-ion cell cannibalized from a dead laptop battery for encoder backup :) it keeps 4 motors alive for about a year with the machine off most of the time. then recharge and good...
that's my point.. regardless of the programmed encoder id and what the nameplate says those encoders are physically the same and always report 1,048,576 counts per revolution (20 bit) and are all...
exactly, that's why i don't like parallel interfaces :) but 16 (or even 8) channel LA should be enough to get started. when it's clear what's going on in there, i would make an fpga board with a...
yeah, sorry CNC Viking. but in a nutshell, you need to get compatible encoders and your new drives should be functional again. or contact me at yurtaev at gmail dot com if you wanna try to convince...
MrMetric, i have a long history with mitsubishi servos... :) it started 12 years ago when i bought a few mr-j2s-b sscnet servo drives off ebay with the intention of reverse engineering the protocol...
i believe the difference between S, S1, S2 are additional mounting holes or something mechanical like that, if any at all. i don't have enough statistics to say it for sure. but for the drive they...
marketing probably? :) i don't have any mds-c1-v drive to confirm, but mds-b-v still support lower resolution quadrature OHE5K. OSA/OSE are serial interfaced, same protocol. not sure about early...
alarm 18 is the "initial encoder communication error".
i bet it's because the mds-c1-v does not support osa/ose253 encoders. neither do mds-b-v. i think the only other drive (apart from mds-a-svj)...
SGDB-xxxN are early Mechatrolink-I drives. the bus gets connected to the blue 8-pin honda connector at the top left. 1CN circled in red is for limit switches and the like.
the manual is available...