Advanced Search

My Maho was originally only 1,5m/min with the Phillips 432. I have it set to rapid at 2,5m/min, and it is fast enough to crash before I react.

Yeah, that behaviour threw me.

Thank you, I will try starting with slow accelerations, max velocities, and longer step timings until I find a safe limit for it. I'm 100% sure there are no electrical issues because when I first got the machine, it came with a standalone controller that could run programs, but I am unable to run the ancient software to load programs onto it. The jogging feature on the standalone controller worked perfectly and was able to move all axes easily

That is quite interesting behavior by the VFD. If you have a "single ended" output (say 0...10V -> 0...70Hz), you would think that with the wires reversed, it would go to minimum allowed frequency or just refuse to start.

Anyway, glad you got it working.

Thank you!

I have already tried a bigger LATCH numer but it would just miss the index. Currently I usind 1.

Mabey I just leave it like that.

And what speeds would you recommend to cap the machine? I currently use 4 m/min. Is it recommended to go higher?

That should work!

Do you need to assign the pktuart pins when you build the firmware?

If yes, the Mill with 7i92 has open connectors on the 7i85S TB1 TX6, TX7 SRX0, STX0 and all the odd I/O on the 7i75.

The Router with 7i92T supports a spindle, laser, and bunch of pins reserved for plasma.
P1 and P2 are both configured as G540 but P1 is actually connected to 7i75 card.
The pins I have unassigned are P1 gpio.029, .031, and 0.033.
The router is working fine and won't gain any functionality so an update is much lower priority. Really just a wiring cleanup so let's wait before putting new firmware in that.

I will try to get the  7i96d_7i85p_pktv3  installed today, otherwise it may be a week before I get back to it. 

Thanks!

Thanks. I fixed it. I think it was a combination of sometimes doing M3 without an Sxx first on start up, then pressing the button (which defaults to S200) and then trying S100 M3 in the MDI.
Turns out I got the Analog 0-10V and GND wires reversed when I rewired the VFD.

The weird thing was with those wire reversed, it would not start the spindle below S175, but would only run the VFD at the max frequency with any S speed above that. So switch on, type M3 nothing, push button (= S200 worked but always at 70 Hz),  then I had been typing S100 M3, and it would not start. 

Switched the polarity, and now it is all back to normal.

I'll upload the latest HAL and Ini to the first posts a bit later, as it is good to have a back up here.

Really a cool milestone to make the first parts. Congratulations.

On my Maho I have:
HOME_SEARCH_VEL = 0

HOME_LATCH_VEL = 10

HOME_FINAL_VEL =15

Try a HAL with just this header in it... this works on my set of Mesa cards. You will probably need to change the IP address.

loadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS
loadrt hostmot2
loadrt hm2_eth board_ip="10.10.10.10" config=" num_encoders=5 num_pwmgens=0 num_stepgens=0 sserial_port_0=0000000"
setp   hm2_7i92.0.watchdog.timeout_ns 5000000
loadrt pid names=pid.x,pid.z,pid.s
loadrt debounce cfg=3
loadrt matrix_kb config=8x8



addf hm2_7i92.0.read          servo-thread
addf motion-command-handler   servo-thread
addf motion-controller        servo-thread
addf pid.x.do-pid-calcs       servo-thread
addf pid.z.do-pid-calcs       servo-thread
addf pid.s.do-pid-calcs       servo-thread
addf hm2_7i92.0.write         servo-thread
setp hm2_7i92.0.dpll.01.timer-us -50
addf debounce.0               servo-thread
setp debounce.0.delay         5
addf matrix_kb.0              servo-thread

Hello! 
Finally the wiring for the EXE and Mesa that worked for me:
I also dont need a extern  12V supply.

Mesa name  /   EXE Pin and colour
1 QA0         /     9  braun
2 /QA0        /     14 grün
3 GND        /      3 grün-weis
4 QB0         /     1 grau
5 /QB0        /     4 rosa
6 +5V          /     2, 6, 10 grün/braun
7 IDX0        /     7 rot
8 /IDX0       /     15 schwarz

And finally the references work! I only can drive the joints very slowly to find the index. Is there a way to drive faster? The index is only 0.001mm wide. sometimes it wont pick up. 

I also milled the first pices! It works great!



I have already recived the 7i74 und the 7i84U´s for the extentions.
On the weekend i will hook up these so i can use the diffrent gear for the spindle. 

This should be close

 


Note that I had to reduce the number of sserial channels to 3 to fit
(the are also renumbered so channels 0,1,2 are on 7i85 channels 0,1,2)

Most info will still work. The problem is that there is not really consensus about what automatic toolbit offset en height settings must do.
I had mine working for a while. I switched to 3d printing and will pick up later this spring.

Are there any potential drawbacks of this? I've wondered why this wasn't the standard implementation - I figured it was for good reason, so never asked. I ended up dedicating a physical button to activate MDI mode instead, but it feels like a waste of a button...

Will this modification switch back to MDI mode after a python based probing cycle (successful or failed)? I find that's the most frequent time I need to switch back to MDI mode.

Hello,

attached are the requested outputs and I added PDOs and SDOs outputs as well.

When working with multiple m codes, i always use Queue Buster before each m-code.
eg.

M66 E0 L0
M169 P9

M66 E0 L0
M169 P6