Mori MV 35/40 retrofit
- clkeck1
- Offline
- Premium Member
- Posts: 108
- Thank you received: 2
Ive tried less I and no luck. I have the error under. 0002 everywhere in halscope and I get a following error with anything less than min ferror of .002 and ferror of .009. Its almost as if there is a scale of 10 somewhere that is being missed.
Any ideas?
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
- Posts: 23538
- Thank you received: 4854
Please Log in or Create an account to join the conversation.
- clkeck1
- Offline
- Premium Member
- Posts: 108
- Thank you received: 2
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
- Posts: 23538
- Thank you received: 4854
Pid.0.error
That should be scaled the same as the encoder position, and that is normally scaled to exact axis position.
If you halscope (or halmeter) axis.0.motor-pos-cmd then move the X axis by 1 unit, does the pin change by the same amount?
If so, then everything is scaled the same.
I would be tempted to try the 10x f-error and see how a test part works out.
Please Log in or Create an account to join the conversation.
- PCW
- Online
- Moderator
- Posts: 17883
- Thank you received: 4772
What are your PID max output and PWM scale numbers? (They should be the same)
what is you maximum rapid speed at 10V?
Please Log in or Create an account to join the conversation.
- clkeck1
- Offline
- Premium Member
- Posts: 108
- Thank you received: 2
Rapid at 10V was adjusted in halscope to 7.917 (475 ipm)
I've moved on to the control panel and discovered that using the servo thread of the 7i64 for the mpg is not acceptable. I guess ill have to run the wire back to the 7i48.
Speaking of threads does a base thread need to be defined for encoders when using the mesa components?
Please Log in or Create an account to join the conversation.
- PCW
- Online
- Moderator
- Posts: 17883
- Thank you received: 4772
The servo thread at 1 kHz is probably too slow to capture data from anything but a low resolution encoder, which is why the 7I64 fails. If the maximum MPG speed is close to ok, you might consider
Running the servo thread faster (say 2 or 3 KHz)
A base thread is not needed with the mesa encoders
Please Log in or Create an account to join the conversation.
- clkeck1
- Offline
- Premium Member
- Posts: 108
- Thank you received: 2
Ill experiment with a faster thread and see what happens
Please Log in or Create an account to join the conversation.
- clkeck1
- Offline
- Premium Member
- Posts: 108
- Thank you received: 2
I have a couple questions/suggestions
1. Is there a way to turn the flood coolant on/off while a program is running using the external inputs?
2. Is it possible to setup a tool touchoff button that records the current g59 z position as the z offset for the current tool in the spindle? Kind of like the current axis touchoffs.
Thank
Cory
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
- Posts: 23538
- Thank you received: 4854
Glad to hear it.Machine seems to be running well.
Yes, but you first need to decide what behaviour you want. Consider the 4 combinations of the G-code command and the external button, and decide which behaviour you want in all cases. (Actually, you might something even more complicated, where a change of state in the G-code is always followed, but a press on a momentary button toggles the state). You can then build up a structure of AND, OR, NOT, latch, edge-detect etc logic blocks in HAL to sit between the motion.coolant-flood EMC2 output and the pin which controls the physical relay.1. Is there a way to turn the flood coolant on/off while a program is running using the external inputs?
First decide what you want, and then we can try to figure out how to do it.
If you look at the bottom of the drop-down in the touch-off dialog, after the coordinate systems there is a "T" which means that the calcualted offset goes in the tool table. Is that what you want, or do you want something else?2. Is it possible to setup a tool touchoff button that records the current g59 z position as the z offset for the current tool in the spindle? Kind of like the current axis touchoffs.
You could create a PyVCP or GladeVCP button to call an MDI_COMMAND. I think you would want something like G10 L1 Z[#5383 - #5422]
Reading list:
www.linuxcnc.org/docview/html/hal_pyvcp.html
www.linuxcnc.org/docview/devel/html/gui/gladevcp.html
linuxcnc.org/docs/html/gui_halui.html#sub:MDI
www.linuxcnc.org/docs/2.5/html/common/ma..._id_sub_parameters_a
Due to a quirk in the forums you might have to click back into the address bar and press enter to get the links to work.
Please Log in or Create an account to join the conversation.