Advanced Search

LCR wrote:

Also, what are people doing for gantry (dual servos on a single axis) systems? 

If I can get internal homing working, there is a setting in the drive for home offset so you would just adjust for squareness using it.

Hello JT, I hope to be able to respond promptly to your email. Why don't you use LinuxCNC?
Will I be able to see your machine online, running with your Ubuntu?
I think, LinuxCNC 32 Bits, isn't it more complete than your Ubuntu with LinuxCNC? I made a small mess of talk, because I wanted to use my 32-bit HP Mini, but it does not offer me a parallel port, and it is the one that distorts my image when booting LinuxCNC 32, it did boot Ubuntu correctly and hence my talk.
But I have forgotten the parallel port that the School's LinuxCNC 32-bit cpu offers me, which I have installed on the old 32-bit cpus, with 512 megabytes of ram, IDE mechanical disk, and I loved how fast they were, fluid, that I even installed games on them, to stimulate my students. So, if the 512 megabytes of ram work very well in your Ubuntu, in the 32-bit LinuxCNC, do they also work well? Or do you need more hardware? Thank you very much!... Congratulations!...
 

As the OP said, the missing piece in an Ethercat build is affordable encoder inputs for spindles. There are very few options outside of Beckhoff. I have some Beckhoff I/O but have not bought an encoder module.

There are a few I/O modules generally with 16 inputs and 16 outputs. There must be a cheap Ethercat chip they use. Examples from Deiwu and Rtelligent (I have both). Rtelligent includes some PWM outputs.

But lets face it, the main reason one goes with Ethercat is to use Ethercat servo and stepper drives so the Mesa cards with analog and step/dir interfaces are not particularly useful any more.

Using Ethercat drives reduces the need for I/O because most drives have some included I/O for home and limit switches and brakes etc. These can also be used for general I/O.

Whilst using hm2 over Ethercat should  improve network latency issues with Mesa cards due to the more efficient transport layer, adding the additional complexity of Ethercat just for this does not make sense to me.

Perhaps Mesa could look at an Ethercat 7i92 equivalent that supported some existing daughter cards to give I/O, encoder, counters for MPG and analog voltage by adding a THCAD2 with its Calibration data stored in Ethercat registers? Perhaps this card would include some  smart serial interfaces too?

Anyway, I'm gonna go back to fiddling with Ethercat internal homing now...  After a long hiatus, I got my homing lab working last night and homing commenced as it should. I just have to work out why it didn't respond to the homing switch when it came on...

vizavadsky wrote:

Thanks again! Now I can start LinuxCNC and motor start to make sound on start. Also Encoder shows position in DRO tab. Looks like I have communication with the servo motor now. When I trying to Jog or turn motor shaft I got Error: joint 0 following error. Same thing as  bananun described at the end of page one of this thread but his solution doesn't work for me. Now I'm not sure is this is Servo related error or I still need to do tweaking LinuxCNC settings. I seriously underestimate complexity of this project

 

Try to increase the ferror and min_ferror a lot, like 1000 for each, if that works then bring it down to a reasonable level

I would like to tune my drives a bit. What tuning have people tried? I'm not clear if the following command tunes the drives or re-sets everything. I'd rather not try at this point. I just let Linux do an update and had to re-install.

LC-E Series AC Servo Drive
5.2.1 Initialization parameters
Set P02-31 to 1 to initialize the drive parameters, and the drive needs to be restarted after the setting is completed.

Also, what are people doing for gantry (dual servos on a single axis) systems? 

Those drives will jump off that table is you get them started.

Now we are stealing this thread hehe
I bought most from aliexpress, and from a local dealer that carries a limited assortment.
Ax58100: vi.aliexpress.com/w/wholesale-ax58100.ht...0&sortType=price_asc
I hope that will give a list of several sellers, it does for me. Around 10 €/USD.

The crystal is a "passive crystal smd 25 mhz 3225", aliexpress have plenty dirt cheap
vi.aliexpress.com/w/wholesale-passive-cr...e=total_tranpro_desc
Any crystal with the "passive crystal smd 25 mhz 3225" spec will work.

The difference between the ferrite beads is laziness or something like that. They are the same.
I wrote out the full spec once, and not the other.
As for substitutes, any "ferrite bead 220 ohm 0603 1ln" will work.

 

Hello  5_Zylinder , hello everyone. I just bought a HURCO BMC 30 AP and I want to upgrade it to LinuxCNC. Could you please send me the documentation and the electrical diagram? Because I don't have any documentation, only the manual for the Yaskawa servo driver CACR-SR20BF12GE downloaded from the internet. I want to use the original servos and servo drivers and use mesa 5i25 and mesa 7i77 or 7i97. Is your machine working yet? If you could also give me your Ini and Hal file, it would be very helpful. Of course, I can appreciate it.
Thank you in advance.

sweet! let me know how it works for you!

if you are on the stable version it will not have the user_buttons feature yet if memory serves. that would be in the develop version for now only. you can leave it off and the pbsplash you can copy from the git directory if you would like that as the splash screen.

github.com/kcjengr/probe_basic/tree/main.../machine_setup_files

No, somehow I thought you had a 7I96S.

So is a 7I96 + 7I85 with one 7I96 stepgen (chan 4) replaced with PWM/DIR
and stepgen/encoder index on the 7I85 what you need?

amanker wrote:

Yes. I wanted to communicate via spi only. Since I also configured it in spi mode in daisy chain config in FluidNC. Remora communicate with LinuxCNC via spi. If possible I can send spi config data to tmc via some module in LinuxCNC. Or if you modded remora-spi source to suit tmc 5160
 

If you can make a direct SPI connection between the Raspberry Pi and the TMC drivers, then it should be very easy to adapt my code; all it does is sending the registers value to the drivers according to values you set via parameters until all the registers have been set, and then it reads the motor position. And another function sends velocity command. You'd just need to remove the write velocity part (or, simply said, not addf TMC5160.write) and not connect the position feedback pin. In theory you could still use the SPI line to get TMC status bit and be informed if one driver has an error.

I want to try to control the SPI device on the RPi without the use of BCM2835 library to avoid compatibility problems. Give me a week to try and I'll publish my code after that. I didn't even try to modify the spi-remora code, as this is way above my coding skills.

That was me, link is on page 1.

Glad you got it working.
I'm not really familiar with stepconf wizard but it may just simply have been overlooked when gmoccapy was added. Those wizards are very handy to get a simple working config but it's pretty much impossible to keep them up to date with the latest developments.
There usually needs to be some manual tweaking in the hal and ini files.

Thanks to "onceloved" problem is solved. My drive exposed EoE (ethernet over ethercat) and it was in conflict with CoE. I recompiled etherlab master with --disable-eoe option and the problem is gone.