Advanced Search

no retro fits on these i was just saying the memory for program storage is what ever the base model came with at the time. sadly the people i work for don't spend the extra money to upgrade that part of the machine when they buy them.

they guys were old school who have retired or moved on and they hand coded everything in the past so bloated cam programs were never an issue before because of this. the one mori is nothing fancy at all but when i first came out of trade school back in 1991 they had that machine at it's still there so it's 35 years old plus

Yes, the ODrive (Pro) has extensive options for configuration; PID tuning; torque, velocity, position, and trajectory control modes, etc.

Some initial PID tuning was already done, and the intention is to run it in position control mode, driven by step/dir from Mesa + LinuxCNC.

In my original post in this thread, I linked a forum thread in which an ODrive development engineer didn't see an issue connecting an incremental encoder to both ODrive and Mesa + LinuxCNC. In response to concerns about signal levels or ground loops, his response was that "The [ODrive] Pro has common-mode filtered encoder inputs, so it should be able to withstand some AC-mode ground differential. But you can actually make it fully isolated – if you desolder [a couple of components], it’ll isolate the the A/B/Z and Hall encoder inputs". 

So there are a few possible approaches and I'm trying to understand what makes the most sense:

* Encoder feedback to ODrive with LinuxCNC + Mesa in open loop (simplest but accuracy concerns?)
* Encoder feedback directly to both ODrive and LinuxCNC + Mesa (potential signal/ground loop issues, maybe worth a shot anyway)
* Two separate encoders for independent feedback to ODrive and Mesa + LinuxCNC (added cost in funds and space on machine)

 

7i76EU in Portugal
eusurplus.com/index.php?route=product/pr..._62_71&product_id=50
OR
7i96S with 7i84
eusurplus.com/index.php?route=product/pr...t_id=104&search=7i84
eusurplus.com/index.php?route=product/product&product_id=159
Prices are without tax

7i96S in Germany
www.welectron.com/Mesa-Electronics-7i96S...-Ethernet-Controller
Prices are with tax

if all you want is to call a subroutine just drop in a subcall button name it and define the file for it to call and it will. that is the beauty of qtpyvcp is all the hard work is already baked in, just choose your widgets according to your use case.

ok, s im not certain what your implying regarding memory? are you wanting to retrofit the machines?

Note that the 7I76E/7I76ED have been replaced by the 7I76EU

They are also specified here as UINT32. And you say float (Ethercat REAL type).
This doesn't match.
Make the datatype REAL for this variable, read it as a float in the processor and as float-ieee in hal (gous into a float type hal variable)

as you can see, in the twincat ENC1RPM and ENC2RPM is REAL,
I also checked the XML files, they are REAL too,
But output of ethercat xml command, it seems like UINT32, I dont know why,


By the way, I am planning to sell the boards via ebay, and the Turkish local market via n11.com
there is 3. board, it can control 4x RC servo motor, actually it has 4x  isolated PWM output,

Dear All,

For my project I'm looking for a Mesa 7I76E card.
Anyone has such card in perfect working condition for sale?

Thanks in advance,

Frans

I depends on the ODrive performance and tuning, It there a tuning program for the drive?
 

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