Advanced Search

If A does not change, that sounds like there is a problem in the "A" encoder signal path
This might be:

1. Encoder connections wrong.

2. Bad 7I76 encoder input

3. Bad / loose DB25 cable

4 7I92 bad/damaged input

Also which pin does not change? A or B?

earlier post:

 When the X-axis moves, the yellow LED at A changes constantly between on and off, B remains on, Count changes between 0 and -1

latest post:

here “Count” only changes between 0 and -1, “B” flashes when I turn the encoder and “A” lights up constantly in the HAL show


 

 I connected normal input on IO 34 qnd 35, it works fine. But how should I tell the system the stepgen index for axis X is on the 36 and for the axis z on the 37 ?

You cannot, the index mapping is fixed by the firmware. That is, GPIO 34 is always the index for stepgen 00,
GPIO 35 is the index for stepgen 01 etc. You can, however map any stepgen to any axis.

So, ich habe mir mal einen normalen Drehencoder besorgt und den an die 7i76 angeschlossen. Dort wechselt "Count" nur zwischen 0 und -1, "B" blinkt wenn ich den Encoder drehe und "A" leuchtet konstant in der HAL Show. "Velocity" und "Raw Counts" tut sich gar nicht. Stecke ich nun um auf die 7i85 (Ausgang 02), dann funktioniert alles wie es soll, "RAW Counts" und "Counts" werden gezählt, ein Wechsel zwischen "A" und "B", also alles so wie es sein soll. Keine Ahnung, warum das so ist. Jetzt warte ich noch auf 2 GT2 Riemenräder und den Zahnriemen, dann kann ich das Ganze mit Motor testen, ob es dann mit dem Gewinde funktioniert.

Gruß
Olli

---

So, I got myself a normal rotary encoder and connected it to the 7i76. There “Count” only changes between 0 and -1, “B” flashes when I turn the encoder and “A” lights up constantly in the HAL show. “Velocity” and ‘Raw Counts’ do not change at all. If I now switch to the 7i85 (output 02), everything works as it should, “RAW Counts” and “Counts” are counted, a change between “A” and “B”, so everything is as it should be. No idea why this is the case. Now I'm waiting for 2 GT2 pulleys and the timing belt, then I can test the whole thing with the motor to see if it works with the thread.

Greetings
Olli

Mint 22 with LinuxCNC 2.10, sim works.

When I tried the Qt Touchy it would not start and gave this error as well as some strange noise out the speakers.
 

Running Debian 12

JT

listing said 4A max and said it was an upgraded version i have not picked up any power supplies yet. usually China ratings are exaggerated so i never go to the max. i think the motors are rated at 3 A. I will keep that in mind regardless. maybe i will get some sort of manual with them when they get here? I will have to wait and see. but if i smoke a $7 drive it won't hurt to bad

In a terminal, what does
xrandr
Return for available resolutions?

I have those drives, they are good, they have issues, and for sure will die at 42V!
Those use the TB67S109 chip (IIRC) that has the absolute max rating of 40V or 42V, and a working rating of 24V, i have them running at 27V without issues for years, but i would not go any further than 32V.
They have good microstepping, have some protections, and do not die like TB6600, also less sensitive to EMI than TB6600.
Also cheaper than TB6600.
Max current is 3.5A, should be plenty.

Fixed the 7i78 stepgens, download the deb again and reinstall.

JT

ER-Spannzangen sind genormt in der DIN 6499.
Für eine ER-Spannzange braucht du ein ER-Spannzangenfutter und eine ER-Spannmutter.
ER-Spannzangen gibt es in verschiedenen Baurößen. ER40 Spannzangen gibt es typischerweise von 3 mm bis 26 mm.
Die Spannzangen in Übergröße würde ich versuchen zu vermeiden.
Die Spannzange wird in die Spannmutter eingeschnappt. Erst dann wird des Werkzeug in die Spannmutter gesteckt. Somit wird sichergestellt, dass beim Lösen die Spannzange wieder aus dem Spannfutter gezogen wird. Die Spannmutter und die Spannzange sind ungefähr bündig.

Das von dir verlinkte Spannzangenfutter ist OZ und somit nicht passend für ER Spannzangen

I just received a new PCB that I designed based on an AXIS sample project. It is a CIA402 test board.
According to the AXIS manual, it uses an STM32H745, which has 2 cores, both H7 and H4, and is expensive. I saw that all the configuration examples only use the H4 core, so I designed another STM32H723 as an alternative. It has a single core, the H7. It costs almost the same as the F407, which is much cheaper than the H745.

When I finish building the PCB, I hope to compile the files successfully with the knowledge I have gained from Hakan.

Hakan wrote:

With the use of SOES github.com/OpenEtherCATsociety/SOES there is no difference for me as a programmer.
There is a tiny difference in how to reset the ESC chip, LAN9252 can be reset by writing over SPI, AX58100 need a pin to go low.
Ax58100 also has a pin for a led that indicates successful read of the eeprom. Pretty useless but has been nice diagnostics when starting up the board.
Other than that one can consider them identical.
I have seen someone state that the AX58100 is faster than the LAN9252. I can not see that, I haven't been in a situation where I can identify the ESC speed as a factor, on individual usec level.

If so, I will try LAN9252 on the next board.

The asix chips look nice on paper but then again if you pair it with a MCU, how much benefits are there, I don't know? I was just wondering if there are benefits from the programming side so that it would make sense to use that instead of the LAN9252. I have 0 experience with the asix chips so I would love to hear from people that have used both.

Although both maybe available on aliexpress, I would say the LAN9252 is far more obtainable than the asix chips. I typically try to scan something like octoparts for any "special" components I might use, at least if there is even a small chance I make something more than one. A quick look and just digikey and mouser stock these in the thousands. I lost my mind on the chip shortage so now days I try to find multiple sources for parts and if I'm lucky multiple alternatives.

I followed hackaday.io/project/181058-ethercat-serv...e/log/196311-ax58100 for years before the project switched to AX58100. There was a description between the two chips that I didn't quite understand until I found Kahan's project that switched to AX58100 and I followed suit.

@ pippin88  Yes, I started with this project to work with STMBL, but I was still a newbie with Ethercat, it was very confusing for me until I discovered Hakan's project that exposed kikad and explained it in detail on YouTube, with immediate response when I had problems via Github.

This is the AX58100 SPI to STM32F407VGT6 connection test board with Axis and IO expansion board.
I haven't made it into 1PCB yet due to the price constraints of PCB size exceeding 100X100mm.
I'm adding the DAC Op-amp circuit and waiting for the test. Encoder connection.