Advanced Search

How much of an accuracy/performance impact would there be if running LinuxCNC + Mesa without encoder feedback, while having the encoder feedback to the ODrive motor controller?

I have not seen anything either.
Yesterday I cracked my the  monetisation target, First time getting enough views in a week to get paid. but I want to get there faster than 50 weeks!
I edit in kdenlive on Linux. Slowly getting the hang of it.

i have options for sim at work with different cam packages but one of the things i noticed right out of the gate once i started looking at the lathe controllers is lack of memory on the controllers since these lathes are maybe 15 years old with the exception one he new one that was just bought. the problem with cam if your trying to do something with live tooling without the Y axis the program size just gets way to big pretty fast. so macro programs seem like a good solution to keep the program sizes in check. Gibs cam might have something for macro's but i don't use it very much. i'm mostly interested in something to test lean programs with and maybe add some quick code for small run jobs for protype work we seem to get a good bit of that with the production work.

On an interesting note supposedly the YouTube I.D. thing started on 8-13-2025. I still haven't been asked to
verify my age even when I pull up video's with out being logged in on my Linux computer. So we will see if
it becomes a whole lot of nothing. I am still hoarding as many video's about stuff important to me as I can. 

to build what you see above once you have the machine files would take under an hour to be up an running natively. my suggestion would be to give it a try. it can be configured pretty flexibly for any functionality you might want to add. and instead of using hal you could simply trigger things like toolchange or part passing etc directly from the gcode with some simple commands. configuring vismach and hal for something like this while powerful, seems cumbersome and unnecessary in my opinion (that said, i'm not the hugest fan of working in hal, so im very biased on that front..lol). I would be trying to make this as gcode dependent as possible if your intentions are to use as a simulator for proving out programs.

if you are trying to make a configuration tester that would run off core signals and hal, that would be a different story. even so this could definitely be configured for that.

alternatively, for machines such as your talking about, if this is meant to be program proving sim and if you are programming with any decent commercial cam system they typically have excellent simulation built in with many more sanity checks that what you would likely have patience to build yourself in a stand alone sim. not trying to discourage you, its fun to have projects, just wanted to make sure you were aware of other existing options.

Lcvette wrote:

this has already been implemented in qtpyvcp and does not require vismach. the model can be setup to be shown and run in main vtk ui backplotter natively and respond to gcode and subroutines etc. and is quite easy to setup.

 

 

if i would have know this last week when i was about ready to smash the pc because it fought me so much i would have been all over this in a heart beat i probably should have posted something before i started this to see what other have done  

Sorry, please try again, Yes, I had limited to .AU Sorry about that,
middle of the night here,,,,

Über Debug kann man sich das im Fenster vorne ausgeben lassen. Z. B. #1234 = 12 + 32 ( debug, #1234 )
es gibt auch noch msg, und print, jenachdem ob es im terminal stehen soll oder vorne erscheinen soll

Is the a 7I96 or 7I96S?

If 7i96S you should be able to use the 7I96S analog output
connected to the VFDs +5V output, CM, and VIN1

VFD   7I96S
REF   SPINDLE+
VIN1   SPINOUT
CM      SPINDLE-

Then you would use 2 isolated outputs to drive the VFDs FWD and REV pins, something like:

V+  --> OUT0+
OUT0- --> FWD

V+  --> OUT1+
OUT1- --> REV
 

i have everything opening fine i just don't have the hal complexity for everything i want to have so it just a matter of building that out and using the qtpyvcp ui to wire it all together in the digital sense. this is basically a project that started out as me thinking it would happen quickly and then turned into a major project for me. now i got so much time in it i just have to keep going with it to see what happens i think i got past the really hard part so now i can start adding stuff to a bare bones setup test and if nothing crashed add some more stuff. i keep making progress with it it's just slow moving because i never did anything like this before. on the up side of the set backs i have not spent any money on real stuff lately so that ended up being a plus for me in that sense

Just enter a random made-up Australian address and you will get the option of "Standard delivery - Free"

this has already been implemented in qtpyvcp and does not require vismach. the model can be setup to be shown and run in main vtk ui backplotter natively and respond to gcode and subroutines etc. and is quite easy to setup.

 

some examples below of things already done. to setup once you have your stl/step file components, to do this follow the below steps:

step 1: add new folder to your machine config directory, name is "machine"

step 2: add your stl or step files to the "machine" folder

 

step 3: create a yaml file, can use the below example as a template, to set the base component and orient and configure each component relation in space, and assign an axis for motion.

 

step 4: add a setting in the ini file for [VTK] to activate simulation by loading the new yaml file on startup.

 


Have fun!

Chris

 

Hello Rod.
Thanks for the Info.
Too bad I can't buy it. I have no link account and with the standard checkout it says "No suitable delivery method could be found"
Is there any other option? Like PayPal or something else?
 

1. No, just ground them
2. See #1
3. Because the 7I52 (which supports RS-422/RS-485 Serial) and 7I52S use the same PCB
4. The FPGA source and HM2 driver support muxed encoders, so as long as the pinout file
    is correct, there's nothing else needed

This suggests to me that it may hang at the first G1 after the speed setting (M3 S10000)

• spindle.N.at-speed - (bit, in) Motion will pause until this pin is TRUE, under the following conditions:
  • before the first feed move after each spindle start or speed change;
  • before the start of every chain of spindle-synchronized moves;
  • and if in CSS mode, at every rapid to feed transition. This input can be used to ensure that the spindle is up to speed before starting a cut, or that a lathe spindle in CSS mode has slowed down after a large to small facing pass before starting the next pass at the large diameter. Many VFDs have an at speed output. Otherwise, it is easy to generate this signal with the HAL near component, by comparing requested and actual spindle speeds.
•