Advanced Search

@Hi Julian,

The display value for "dtg" abc, uvw is fixed. This was indeed a bug.

When moving in a blend segment, the "dtg" abc, uvw values are calculated slightly different.
This was not calculated correctly for the display value.

Then i tried max velocity overide : 20.0 and a max jerk of 20.000.
However i was not able to get the planner to run crazy.

Can you post video's with higher resolution or full screen. I cannot read the hal text in the video.
Your last video, maybe provide the file, and run values, so i can try to get same behaviour.

How do you update the code when github is updated?

living in Germany btw
Living in Holland, Next door.
 
Code is updated.
 

Thanks for the feedback
Yes =>  inductive sensor
Yes=> position sensor for the ram/cylinder
Yes=>Maybe using the values from that sensor to home or to check and retract the ram at LinuxCNC start

I am currently in the electronics lab, I will do some simulations and post them here for everyone to see. And when I go to the machine I will already have a theory to be applied. Thank you very much to everyone, I am available if anyone needs any more information about this machine or the process I am doing with the electronic boards from the manufacturer Mesa 7i77.

 

I will attach the technical data in case anyone needs to work with this type of machine.

 

 


Repeat accuracy ± 10 µm
Voltage output 0 ... 10 V

​​​​​​​note: I used google translate, sorry for any inconsistency

Hallo

ich habe einen Lichuan TLC57-E-36V-3
Vorerst nur den einen.
Mit der der *.ini und *.hal hab ich ihn mal zum laufen gebracht, nur eben die scalierung habe ich noch nicht einstellen können. Aber viel dank für eure hilfe!   

Iv got a pawn  

youtube.com/shorts/vlgv4FAAmmc?si=jZdAi8ldJxhEXNjL

Hi guys, I've tried a few things with these drivers, they work relatively well, but they are quite expensive and there are no new ones.

I was thinking of using an h-Bridge, could you recommend some, the motors have powers of 200W 48V 4.2A, thanks in advance, greetings

Tried this one, unfortunately same errors. 

I live near the winds and the fires in Pasadena, California, and after the sudden power failures (several trees made spectacular messes all over our neighborhood, so it was a sudden spike-outage: also fried my fridge) my CNC mini-computer has taken to randomly rebooting.

So I ordered a replacement mini computer, and repeated all my installation steps, except for a scratch re-make of pncconf.

Instead, I copied back all the config files, directories and symbolic links from the old computer (it still runs, just inconsistently).

But at the end of everything, I get this error report and I'm stuck.

I was able to get a version of QtDragon interface to run (as far as actually displaying on the screen, haven't run the machine yet) by going through the pncconf process...
... but I will have to make a lot of changes to get back where I was, so I was hoping to make that restore route work.

If anyone can take a peek at this error report and have an insight into what I've screwed up, it would save me a bunch of time.

If not, then time is what it will take ;-/

Thank you all!

Vector

As you'll only be able to run in simulation mode and you just want to get familar with Linuxcnc an arm install will be fine.

After doing a quick read I'd research the following:
Is Debian Bookworm able to be run. The kernel versions and X server versions seem to be limited.
Is the Kernel version that is on the Linuxcnc iso compatitable ?

Part of the hole processing smarts is in the qtpyvcp code base.  In the programe used by monokrom to parse out the incoming gcode file and adjust it if necessary.  I still want to come back to this and refine/improve it.  Just on a long list of other things in life to see to.

tommylight wrote:

This time you can blame it on me as if i recall correctly, Parallels is the software running on Apple hardware and makes it possible to run other operating systems in it, in short running virtual machines.
If that is correct, then all my answers are on point, it should run any ISO without making images on other hardware, that is the whole point of it.
Then again, it is Apple, so maybe only runs ARM stuff?
 

Both links I included explain in explicit detail why I need someone with an Intel Mac and Parallels to create a VM on that hardware for me load into my Apple Silicon Mac. It was, and still is, all that I need to try out x86 emulation in Parallels 20.2.

Changing the Z-axis accel only slightly affected the rapid distance, if at all.

The earlier tests were done with MAX_VEL = 4, and MAX_ACCEL = 175.

Dropping down to MAX_ACCEL = 2 resulted in approximately the same pre-synch rapid distance at all speeds.

Much less violent rapids, of course.