Advanced Search

Example:

 

OK then, that machine can not work, the motion of the X axis must be always in relation to the center of the part, here it is at what looks like 40-45 degrees.  

Hm, not sure what I'm missing here but slant bed lathes have been around for a long time. All that is required is:

- Z-axis must be parallel to the spindle axis
- X-axis must be perpendicular to the spindle axis
- cutting edge of the tool must move on a line that passes through the center of the spindle

The first two requirements are clearly fulfilled and I would certainly hope that the builder of the machine has made sure that the tool pointing 45° down will be the correct height to fulfill the third as well.

I replaced the thermal paste on the cpu and I am still getting this error at lower temperatures.
 
here is a ping test
 

  So my first obstacle doesn't even have to do with the machine, it has to do with my cad/cam program.
I had never needed to use more then 3 axis of movement before so it wasn't until today that I realized
fusion 360 won't allow synchronized turning without paying extra for the add-on. Keep it up Autodesk
I am really close to fully abandoning Windows and fusion 360 altogether. the Question now though
is do I just treat the models as 3D and add the 4th axis manually or can I repurpose the third axis as
a rotary axis? I guess there's always DevCAD.  More research is needed.
 

OK then, that machine can not work, the motion of the X axis must be always in relation to the center of the part, here it is at what looks like 40-45 degrees.
The carousel component is included with LinuxCNC, see:
linuxcnc.org/docs/stable/html/man/man9/carousel.9.html

Ok, so I have loaded the firmware (7i96s_5abobrcd) with MesaCT and I think I'm good there.  I created a basic XYZA config.

My plan is for 5 step/gen on the 7i96s and 1 step/gen and PWM servo on the BOB. 

Manually editing the *ini file to add the remaining axis seems straight forward.  Any tips??

The sim examples I've followed so far don't have any hardware specific details.  Does anyone have an example config with step/gen across two cards, one being a BOB?  How, or do I edit any of the HAL files to add the BOB.

 

PCW wrote:

If there is a choice, I  prefer sourcing outputs and sinking inputs

 

Good point on the need for less IOs than I initially feared. But since I am based on a small island in the Phillippines and the board(s) will take a decent while to get here, I thought the smart move would be to get a daughter card instead of having to order again later, just in case.

I'll go with your preference then as it easily trumps my zero experience. So, 7i96s + 7i84. 

Thanks for the help to you and Corn:)

thanks. I'll watch and see when it gets pushed to the master .deb
then give it a try.
it would be best if it could be consistent in all qtdragons.
and of course, included in the documentation.

If there is a choice, I  prefer sourcing outputs and sinking inputs

Also as I mentioned before, you likely need much fewer I/O
points than you think for enable or alarm as they can almost always
be combined.

tommylight wrote:

Sorry aber es geht schneller im English:
Are those two separate machines or is that a single machine in it's final state?
To run the tool changer you can use the included Carousel component, it support plenty of changer types.

It is a single machine.
Where can I find these prefabricated components?
When the whole configuration is completed, I would like to switch to the Probe_Basic_Lathe interface.
I am currently using AXIS for setup.

Way, wayyyyy to much.
Must be under 50$, otherwise PC and Mesa.
Sorry to repeat this, but humans should really wake up and stop buying 200$ SBC that can do nothing particularly well. Anything over 50$ is to much.

Sorry aber es geht schneller im English:
Are those two separate machines or is that a single machine in it's final state?
To run the tool changer you can use the included Carousel component, it support plenty of changer types.

No, i do not know if Delta A2 has deadband settings.

There is no "drive.x.scale" that i know of, so what scale are you talking about?
Either way, please do not assume stuff and set values at random, that is always painful and long winded resulting in frustration.
PncConf does a very good job of having reasonable default values.

tommylight wrote:

Cant do this anymore bye all wrote:

Why we don't go all the way and design a RISCV Linuxcnc SoC ?
That is a good idea, that would make everything Open Source.
That would also probably imply using a slim distro, or trimming Debian, a lot!

Cant do this anymore bye all wrote:

(actually I can't even afford to replace my old car that had to go to scrapyard). hahahahaha
Last year i sold my new-ish car and kept the now 20 year old one!
The new-ish one had so much electronic cr@p that the only thing i did while driving it was steering!
I like Manual gearbox, i like to drive, be in control... control freak

 

Rich sent me this link today,
git.beagleboard.org/beaglev-fire/beaglev-fire

Looks interesting has an on board FPGA, how much of that is left for use for the user would be interesting.
But it runs at about $230 odd Australian, $150 US. Would be a bit of a gamble and still would extra hardware to interface to the machine. And would it be any better than a 2nd hand PC and a 7i92T ?