Mori Seiki SL1H Oak Board Build

[cncsnw]

You are getting a differential error because the encoder isn't even hooked up.

That is what a differential error means: there is apparently no line driver on the other end of the cable, holding the differential pairs at opposite voltage levels.

Setting the error-defeat parameters to 3 defeats encoder errors on axes 1 and 2. Add a further 32 to defeat errors on axis #6 as well (i.e. set the parameters to 35).

Or, if your objective is to blindly defeat all errors, and all messages, of either type, on any encoder ever, and forget about it, then set all four parameters to 65535.

[Wolfenstien]

You are getting a differential error because the encoder isn't even hooked up.

That is what a differential error means: there is apparently no line driver on the other end of the cable, holding the differential pairs at opposite voltage levels.

Setting the error-defeat parameters to 3 defeats encoder errors on axes 1 and 2. Add a further 32 to defeat errors on axis #6 as well (i.e. set the parameters to 35).

Or, if your objective is to blindly defeat all errors, and all messages, of either type, on any encoder ever, and forget about it, then set all four parameters to 65535.

\I never configured anything to use the spindle encoder. Is that a default parameter that was part of the original install because I installed the lathe version? I'd be interested in turning it off so I can focus on just the motors and vices versa.

Its certainly not my intent to blindly ignore all the error messages I'm getting. I'm just out of my depth and not sure if I have multiple issues or just one.

Talking to a friend about it and he asked if the errors I'm getting from the drive have anything to do with the feedback loop being closed in the drive and not in the oak board? I wonder if I have parameter 256 in the wrong mode. I currently have it in precision mode. Which is probably wrong. I think it should be in velocity mode.

I'll try changing parameter 256 to velocity mode tonight and see if that clears anything up.

The spindle encoder error could be because I made the end on that cable and its quite possible I screwed it up. I'll review that as well.

[Wolfenstien]

Update:

1) Spindle encoder errors were caused by encoder being wired wrong. (My fault) All better now
2) Just got on Teamviewer with DMM and they were very helpful. Drives were setup correctly. The only think we changed was parameter 256 back into precision mode. (3).

Everything seems to be working ok now. Note I was in precision mode originally but changed to velocity mode with not improvement a couple days ago. DMM did not specify which mode to be in.

I'm wondering if the spindle encoder was faulting which would estop the machine which was killing power to the drives which in turn was creating the encoder errors (Note with DMM your not reading the encoder signal the encoder is read by the drive and the drive generates a simulated signal to feed to the oak board.) If you kill power to the drive you kill the encoder signal to the oak board. To remedy that dmm suggested that I wire the control voltage outside my relay for drive. (I.e. the power for the motors will get cut, but the control voltage will stay hot even when estop is pressed.) The only issue they mentioned would be that if you ever got a drive fault (overload etc) you would need to power cycle the drive which would mean that in my case I need to add another relay or more likely cycle the power to the whole machine. Probably just power cycle the machine.

One thing that is still creating an error. If I go into MDI and run the following code: X100 Z100 F11 G1 and am in inches per revolution I thought I would be able to spin the spindle by hand and have the servos follow. The servos just sit there (because the spindle isn't moving) and when I manually rotate the spindle it immediately creates a servo position error. Is this an invalid move in MDI? Does the spindle need to be spinning at a constant rpm?

I'll try running code in inter con next.

Thank you,
Joel

[cncsnw]

X100 Z100 F11 G1

That is a pretty aggressive feedrate (11 inches per turn of the spindle). You might try something more realistic, like F0.010.

Also make sure you are turning the spindle forward, and that your Parameter 34 value has the correct sign (positive or negative, depending on which way the encoder counts when the spindle turns forward).

[Wolfenstien]

Bahahaha.

Oh that's funny. 11 inches per revolution. (Typical mill guy mistake)

Yep works fine at .01 per rev. Sigh.

Thanks!

[Wolfenstien]

Making some more progress.

I do still get an Quadrature error when moving in -Z direction. (Not in +Z) which is odd, but I haven't used it much so may be issues both directions and I just haven't tested enough yet.

Got my lead screws resolution narrowed down pretty close. Waiting for an MPG to do anything else with the axises. (Just been using Mdi for now)

I've switched to working on the VFD. Had some trouble getting the motor to sound right. It is the original yaskawa spindle motor (Motor specs attached) Note it has at least two V/HZ ratios depending on rpm range. I've think I've got it figured out and motor is running and sounds better now and runs up to 6000 rpm. Even in sensorless vector mode I don't have much torque at low speeds. (As in I can stop the motor with my bare hands when its at 5 HZ) I don't have a brake resisitor on it yet so have to be careful with slowing down for now. Seems to run fine in local mode on the keypad, but I've not been able to control it with oak yet. Oak is sending out the correct voltage but vfd isn't responding which tells me I've got it wired wrong, or I'm not in the right mode to received control from the oak board. Not sure.

If someone has a step by step on a yaskawa v1000 drive I'd be interested in what you did you gain control of the vfd. (Tech manual for the drive attached) Mine is the 7.5 KW drive.

Not sure if it makes any difference, but I also don't get any faults when I error the drive in local mode. (Might just be because I'm in local mode)

Input 10 in the oak board is green which is about the only thing the oak install manual seemed to indicate was needed.

Thanks again,

[martyscncgarage]

Glad you are making progress.
Good DMM jumped in to point you in the right direction.
Keep us posted on your progress.

Here is DMM's latest video in case you have not seen it as of yet:

https://youtu.be/YC04zuUjEK8

[Wolfenstien]

Just recieved my wireless mpg minutes ago.

Can't seem to get it working. Can someone suggest what to do next.

1) usb mpg plug in unlock for oak installed.
2)parameter 218 set to 3
3) parameter 348 set to 15
4) parameter 350 set to 100
5) cnc12 restarted. (Have restarted just software as well as whole pc).
6) turn on mpg
7) place mpg in x or z axis and rotate habdwheel while set in either 1x 10x 100x feed, or spin.

No change to dro and no axis movement. Do I need to be in a particular mode. (Note I do not have virtual control panel setup. Do I need to do something for the contorl to allow mpg input? Alt-w (mpg enable) doesn't appear to do anything different.

Worth noting that moving the machine around in mdi does update the dro on the mpg so it is communicating.


Thank you

[Wolfenstien]

Just grabbed a widescreen TV from the house (16:9) and changed parameter 219 to 1. Vcp shows up now but is not responsive. Same as mpg.

I think the reason the mpg isn't working is mpg enable isn't engaged on the vcp. Do I need to upload vcp plc.

If it makes a difference I'm using the basic plc program for the oak.

Should I be using the vcp mpg beta plc program?

If so do i just make a copy of my current file install the new plc and then backup to the saved file?

[martyscncgarage]

Did you buy the software license to use the wireless MPG with OAK? Are you using CNC12 for OAK?


Oak USB MPG Software Requirements

Oak requires:
CNC12 v4.12+ with USB MPG software add-on part #14688 $139