Printable View
Does anyone have experience with drip feeding on a Meldas M50 control?
I set my machine to TAPE mode and hit cycle start, then i set my dnc program (DNC4U) to send.
it read about 10 block ok, than the machine stops.
it looks like a rts or xon xoff problem.
need some help, who has a parameter list what everything means.
btw, file transfer with in and output goes ok
Hi, I have the Meldas M500 control which should be very much the same.
If all comms are set up correctly, this is the procedure I use for DNC:
1) Get DNC program ready for DNC dripfeed
2) Set machine to "Tape"
3) Push "Monitor", then "Search"
4) Type the program number in the O( ) field
5) Change the DEV(0) field to DEV(1)
6) Tell my DNC program to begin dripfeed
7) Press "Input"
8) Cycle start
Can answer any other questions if this doesn't help.
I googled the M50 control and I think it is similar.
could you make a screenshot of your monitor with the dev parameters?
Let me know if you need pictures of the parameter lists inside the controller manual too.
Edit: sounds like the same sort of thing I got when I was trying to get mine working a few years ago. Make sure that the parameters you have for input & output are the same as the parameters for device 1 but with a much higher delay time.
What got me stuck was changing the DEV from 0 to 1 when searching for the program, and I just want to make sure this isnt getting you stuck too. I have skype if you want to go through it over the phone.
thnx will try this, it looks a bit different.
i will give it a try
here are my old settings, today i try to modify some of them.
http://img20.imageshack.us/img20/9255/08092011822.jpg
To bring up an old thread, has anyone had experience where they don't have the device field?
I know this sounds strange, but it is the only thing that works on my M50...
Host PC: 7, Even, 2, 4800
Control: 8, None, 2, 4800
I thought I was nuts untill I saw others use these settings.
Drip feeding on the M50 is unfortunately not as good as running it from the memory, it dwells every once in a while and is not as fast. I am still amazed at how fast the M50 executes code and how smooth it is.
I was afraid of sounding stupid, because I've been reading about needing 200 line lookup for high speed machining, and I loaded in some trachoidal milling and the control didn't seem to flinch, it just ran the damn thing perfectly.
Thanks for giving me a heads up, I'll try on Monday
Quote:
Originally Posted by avongil
Although the Mitsubishi interface is kinda crude, the speed of the entree level 1995 controller is excellent! I am glad its not all in my head...