Advanced Search

Why STEPGEN_MAXACCEL not allowed to be more than 1500?

Can you give some context as to why you think STEPGEN_MAXACCEL cannot be more than 1500?

well i hit my first snag already i picked up 2 air cylinders with the intention of picking a few more up if the plan works out. turns out they no longer have the cylinders i got before in stock now. so i had to come up with a plan B so i found some on AliExpress but have to wait. I guess the silver lining would be i now have a better match for this project now. i should be able to make things smaller as a result.

always something it seems

ohh, ich kann es mir ja in libreoffice anschauen, damit stimmt mein import sogar überein

also wer den cdr-import nutzen möchte sollte unter linux die 'libcdr-tools' installieren:

apt-get install libcdr-tools

oder unter win/mac mal schauen wo man das tool 'cdr2raw' herbekommt

Hi Studi,
erxtmal danke für die datei,
aber kannst du vielleicht noch ein bild posten wie die zeichnung aussehen sollte !?!?

denke mal das es so nicht ganz passt
 

BTW: schonmal vorab, ich denke nicht das ich das corel import zeugs unter windows zum laufen bekomme,

ich nutze dazu die 'libcdr-tools' mit dem programm 'cdr2raw' , keine ahnung ob es das für windows gibt



 

It work, thank you!

A few questions:
1 - no “pan” button, I think it was supposed to rotate the preview as when the right mouse button is pressed?  It was very good if yes, lacks such a possibility if only to use touchscreen.
2 - if I understood correctly in QT designer “DRO” buttons X, Y and Z should call separately the “calculator” window to be able to set coordinates manually? One more function I would like to have.
3 - coordinate selection button G54 combined with WCS? It would be good too, I get confused in them from time to time.

Can this all be enabled in 2.9 version or these features are only available in 2.10? 

 

Why STEPGEN_MAXACCEL not allowed to be more than 1500?

don't think it's directly due to the spi rate,
faster spi can certainly lower the value somewhat, but it's more to do with the set-up, as I send and receive in one step.
when i have more time i'll try to optimise the process, unfortunately i can't compare it with mesa because i don't have a mesa.

There is an easy solution to match the panel color to the theme. See the last comment here:

forum.linuxcnc.org/gmoccapy/45856-spindl...capy?start=40#313291

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.