Advanced Search

The space between 3 and 4 do not agree to say that it is possible to divide by 111I would like all 6 tools to work, the delta between 1,2,3 is 111mm, so there is a gap, so the same delta raster between 4,5,6 is also 111mm, so the distance between 3 and 4 is 317mm...I will post the script for the first 3 tools later...if I copy and put an additional [change position delta 2]' in the ini file with ``if<current_tool GT 3>`` it doesn't work

Did you try asking on cnczone.com and cncecke.de ?

You already have that with the 3 position switch.
If you want to use momentary switches for it, might need to add relays.

7i92TM + 7i77 is functionally the same as 7i97T, but with more IO so no need for 7i84.
The IDC26 connector can be used for other Mesa boards, like 7i85 or 7i85S or 7i74 etc, or a simple BOB can also be used and this will limit what pin can be used as input and output and limit the stepgen and/or encoder count rate, but still can be used for plenty things like switches, sensors, relays, etc.

Hello, I've bought my first VFD, a Vevor A2 8015 1.5kW model, for a 0.75kW, 1000rpm motor for my mini lathe. I've configured the most basic options and added an external potentiometer and a 3-position switch for forward and reverse.
I'd like to add two momentary switches, one for start and one for stop. Is that possible with my VFD? Can anyone help me with this?

I've attached the manual.

Is the gap a multiple of existing tool distances?
If yes, set it as tool (4 i think in your case) and just do not use tool 4 in post, and even if someone asks for tool 4 no damage should be done as the spindle does not go that low.

Here is how you assign the encoder value to the PDO variable
 

You decide yourself which SDOs and PDOs you need and want to have.
I propose to have zero SDOs to start with and only one PDO which is the hardware counter number.

 

You see at ther bottom in the figure, the save/restore button. Download all files, it will create a zip file with al you need.
Unpack those seven? files in lib/soes-esi and rebuild the code. Take the xml file to TwinCat and program the eeprom there.

You decide yourself which Vendor Id. Product code, etc etc you want to have.
Some sizes you should not change, it tells you in the mouse-over comment.

The config struct can look like this
 

And the loop()
 
A lot of clean-up  yes.

I can confirm that Innovance SV660N works by recompiling the IGH etherlab master stable-1.6 branch and installing on a fresh debian bookworm installation.
The configuration options I have used for the etherlab master are:
./configure --sysconfdir=/etc/ --disable-8139too --enable-userlib --enable-generic --disable-eoe

Thank you nanowhat.

-automata

Hello and thank you for your reply.
My encoder seems good and with the help of AI I modified the SPI to match my setup. I started from your E7000 version and made some cleaning of the main.cpp.
I went too fast and test in Twincat, I can see the device but its stuck in INIT mode yet. not surprising. I think the old eeprom is still there because in twincat, in the device I can see 8 inputs and 8 outputs, what I had on the original board.
I think I need to build the eeprom stuff correctly but I have absolutely no clue how to do it.

My github is up to date.
Do you have more information regading SDos and PDOs ? How to know what to write?

Thank you

HI Fdarling,
I actually tried to modify lcec to work with Yaskawa Sigma7 EtherCAT drive looking at the C program you have shared. I have had a little success.
I added a second domain (domain2) into lcec master but at the same time removed the write Pdos (status, actual_pos) from the lcec XML file. So the domain2 is empty pdos.
After doing this, I could enable the drive using drivecontrol regs. Although I cannot read anything from the drive (ofcourse).
Now the next step is to figure out how to add which domain to use information in the pdo configuration. I am going to try to make it backwards compatible.
I am open to all suggestions and any assistance on how to go about this task.
-automata

I am looking at the code now.
Encoder code from E3000 and E2000, are the only ones that have encoder input code.
I see that I treated it is a 16-bit counter even if TIM2 is a 32-bit counter.
I didn't research all registers, I found the encoder code here github.com/goktugh/EncoderStm32F4/
and was so happy when I found something that worked albeit 16-bit.
I think you need all files with encoder in the name

The initialization codeThere is code to handle an index pulse, you may remove that if it isn't relevant for you.
You get the current position from, it counts by itself. Just to read a register.
From that you can expand to velocity and possible other things, if that is interesting.

When you are confident that the encoder counter is rock solid it's time for spi and ethercat.
Settings are here github.com/MetalMusings/MyOwnEtherCATDev...uino-lan9252/spi.hpp The E7000 code is a good place to start for ethercat with LAN9252.
Verification of SPI is done by following the code to, from there to. SPI works when you successfully can read the test register, and the execution continues.

For the EEPROM, sdos and pdos and all that there is a utility in Utils/EEPROM_generator. Bring up a file manager view and double-click the index.html to open it in a browser. Here you enter SDOs and PDOs.  Save all and unzip all files into lib/soes-esi and it will be picked up be the code if you used the stanza I have. I think you can program the new eeprom with "ethercat sii_write eeprom.bin". I usually copied the esi file to Twincat and programmed it there, but lately I have used siitool with the -m flag, so siitool -m < xml-file > eeprom2.bin and the ethercat sii_write eeprom2.bin and that have work. 

Long post. Take it step by step. Make sure the encoder is rock solid. The ethercat part is pretty flexible once getting to know it.





 

Sorry links removed

now, I don't know how to set the delta y for the second toolbox 4-5-6, because it has a gap between 123 456

youtube.com/shorts/nZJZBoi4e4g

PCW wrote:

I don't take that negative a view of clone cards, if they get more LinuxCNC users,
that's basically a good thing. 

Hats off to PCW here. His tireless support to forum users and his client base is exemplary. He really has embraced the Open Source paradigm and I think his Mesa products are stronger because of it.