Advanced Search

Hi Hans,
the progress bar is a great idea to get a quick glance of how much is left!
Could be to only show elapsed time and predicted time (I did not get where this value comes from) instead of a progress number as you can already see how much the blue bar is filled.

I implemented a timer for the elapsed time myself to keep track of CAM-prediction vs. actual time as well as the spindle load which is super useful to get to know how hard you push your spindle. Not pretty but works^^

The G-Code Size I don't see much use for (if the program time is not there anymore), what I care about file size or lines of code? At least its hiding the currently used tool in the operating state. Imho more something for another layer like inside the file menu?

Agree with the different color of the spindle bar, it could be of the same color as the others. As the color is not representing any state by themself.

I run a machine with Gmocappy daily for work in my small startup. Has been great for the last 4 years

The python interface cannot use self.execute() that has to be done in the remap.

I have used self-execute command in my Python remap.
now I need to use it in my python interface ui
but it seems to be incorrect

Third times the charm? for 2.9 version:

Spindle running, but needs tuning. skimmed the table with it though. also got some new vises.

 

Good to hear.
Actually it’s made me realise I have to update my Mint boxes. So thanks to you.

fixed. yay. haha. it was in the wrong mode.

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?