Advanced Search

active high vs low no effect.
must be a setting in the drive but i dont see one.

Doh, Aciera, I think you were pointing me to the right place, and I just needed to kick myself with inane errors before realizing what I missed:

My old machine was installing from the buildbot2.highlab.com repository, and therefore getting a newer version (updated, as you said).

Once I fixed that step, the restored implementation is working (with some slight screen changes, but I can manage that).

Hooray, I'm better/good (for now) thank you.

Oh, A out works now. that was user error. the frequency shows on the drive.

BUT, no turn on. I have the - of the forward run output on the mesa connected to com on the drive. and the + connected to the Di. This is how it was on the delta drive.

Is this potentially backwards? When i read the IO they say 24v when off, and 0v when enabled. so "active low".
 

Thanks, that patch file was exactly what I needed for it to work properly - I had rebuilt it at the same time and it worked without issues.

Yes. can't post files atm, not on that machine, but they were not changed from the last time. the only change is connecting the wires to the new drive.

I do not *see* any errors.

Thank you Aciera,

I think so, if there's a better section of the forums. I very much appreciate it. I'm trying to go step-by-step through the working default .ini file generated by pncconf, but weirdly when I make innocuous changes, like adding a remark line, suddenly I'm getting errors when it shuts down.

Just when I think I figure out what kind of .ini change is causing an error screen on exit, then I can't reproduce it anymore ... at this point I'm just confused.

So more expert help would be great. Thank you!

So you have ~10V between TB2 pins 22 and 24?

Can you post your hal/ini files here?

So I've just wired up my new spindle, moves the wires over from the old drive to the new drive and.... nothing.

It seems that the mesa is not outputting any voltage with an M3 command. reads 0 between spindle minus and spindle out. It reads 10v between spindle plus and minus.

The wiring to the drive, and the drive params *seem* correct. the spindle of course works fine in control panel mode.

The DI1 and DI2 pins on the drive are set to fwd and reverse and have the minus on the mesa connected to common and the plus connected to the respective inputs and seem correct.

What have i screwed up here?

Can you explain how I can do this?
Many thanks

I have questions for you regarding how you used the m6start that you posted, i installed it for my cortini, it works but only if i call the tools in sequence...or is this how it works. Also if you have more pictures of your machine and what your doing with it , i would be very interested to see...many thanks

Hallo Meister, 
hab ein CDR angehängt. Mit CorelDRAW X5 erstellt.
Falls Du wieder erwarten was bestimmteres brauchst, lass es mich wissen.
Hoffe es klappt.
.txt hinter cdr entfernen........
Gruss Studi 

Hallo Leute,

seit dem letzten Update funktionieren meine Pfeiltasten nicht mehr um die Fräse zu bewegen.
Habt Ihr nen Tipp wo ich da nachschauen könnte?
Grundsätzlich lassen sich die Achsen über den Touchscreen (Probe Basic) problemlos bewegen, nur eben nicht über die Pfeiltasten.

Viele Grüße
Jens 

I have a cortini H105, runs under Mach3 as well as linux cnc, ihave installed the custom m6start that was posted for use with the rachet-pawl toolchanger (same 6 position turret)...it works well , ....but i am stumped as to why it only works when calling tools in squence for example tool 3 can only be propery seated on the lock after tool 2 has already been called... and so on so on.... if i call tools out at random the turret dosent lock down the tool at all...or is this how the code is suposed to work....many thanks

Oh, forget about the cpu load. Its to late. I forgot that I tested the axis cycle time.

Hi Grotius,

I made a small test nc file for better testing. This is a video with my 4 axis test machine capable of:

- 100m/min velocity
- 1 g acceleration
- 6.000 rpm A axis
- wild acceleration of the A axis

My current project will be capable of 30m/min, 0,5 g and the A axis will be a turning axis (of curse with way less acceleration). So in my opinion the test machine is not sooooo way of.

Video

I try different feed override values and as you can see I set the max jerk nearly to maximum (as if there is no scurve).
The behaviour of the A axis is still strange. And as you can see I am able to stop the tp. but it seems that the planer works on and only the axis gui si stoped. Nevertheless strange.

Please feel free to mention if I am testing to wild! I can live with boundaries so to say.

Last thing I just realised. 2.9.3 need a few percentage of my cpu (i5 4570T), maybe 3 to 10%. 2.10 with your scure tp needs over 40% while in idle and up to 50% while running the program.