AX58100
- COFHAL
- Offline
- Platinum Member
-
Less
More
- Posts: 362
- Thank you received: 43
23 Feb 2025 15:10 - 23 Feb 2025 15:14 #322367
by COFHAL
Replied by COFHAL on topic MAX VELOCITY STEP.
I did indeed modify JOINT_N_SCALE to match the drive configuration and the value in the INI file. and it works fine now. The axis moves exactly with the commanded value. Changing the BASE_PERIOD value to 10000 in the firmware also increases the speed without the joint tracking error occurring.
The only drawback is that if one modifies the STEP_SCALE parameter in the drive, the firmware would necessarily have to be recompiled. That is why it seems like a good idea to remove these parameters from the firmware so that they can be modified at any time.
The only drawback is that if one modifies the STEP_SCALE parameter in the drive, the firmware would necessarily have to be recompiled. That is why it seems like a good idea to remove these parameters from the firmware so that they can be modified at any time.
Attachments:
Last edit: 23 Feb 2025 15:14 by COFHAL.
Please Log in or Create an account to join the conversation.
- Hakan
- Offline
- Platinum Member
-
Less
More
- Posts: 651
- Thank you received: 213
23 Feb 2025 20:04 - 23 Feb 2025 20:06 #322394
by Hakan
Replied by Hakan on topic MAX VELOCITY STEP.
Attachments:
Last edit: 23 Feb 2025 20:06 by Hakan.
The following user(s) said Thank You: COFHAL
Please Log in or Create an account to join the conversation.
- SOLD
- Offline
- Premium Member
-
Less
More
- Posts: 116
- Thank you received: 12
01 Mar 2025 07:25 #322911
by SOLD
Replied by SOLD on topic AX58100
Attachments:
Please Log in or Create an account to join the conversation.
- Hakan
- Offline
- Platinum Member
-
Less
More
- Posts: 651
- Thank you received: 213
01 Mar 2025 12:41 #322919
by Hakan
Replied by Hakan on topic AX58100
Haven't been working on this particular board a lot since I don't use it myself. Been busy with a voltage reader for plasma and IO, for my plasma cutter and that works great.
If you continue to use the STM32F407 you should check that there are free timers available. Probable there are, but I used a lot of timers I remember.
Earlier in the thread there is an attachment with spindle control schematics, maybe you already had a look on that one.
My spindles are all controlled via Modbus/VFD and the 3V analog output was put there for good measure.
There could have been connectors for I2C and SPI to easily add on functionality controlled by the STM32. Maybe something you can think of.
If you continue to use the STM32F407 you should check that there are free timers available. Probable there are, but I used a lot of timers I remember.
Earlier in the thread there is an attachment with spindle control schematics, maybe you already had a look on that one.
My spindles are all controlled via Modbus/VFD and the 3V analog output was put there for good measure.
There could have been connectors for I2C and SPI to easily add on functionality controlled by the STM32. Maybe something you can think of.
The following user(s) said Thank You: SOLD
Please Log in or Create an account to join the conversation.
- COFHAL
- Offline
- Platinum Member
-
Less
More
- Posts: 362
- Thank you received: 43
30 Apr 2025 17:51 #327373
by COFHAL
Replied by COFHAL on topic MAX VELOCITY STEP.
I see that I've updated the information related to the AX5800 card. Now I have some questions:
I see that I created some enable pins. I assume they are to enable the output of each of the step generators. In the XML file for LINUXCNC, these pins appear as BIT, but I don't know how to configure them correctly in the EEPROM generator file. Bit variables don't appear there. In that same file it appears
<pdoEntry idx="6001" subIdx="01" bitLen="32" halPin="Frequency" halType="float-ieee"/>
</pdo>
<pdo idx="1a01">
<pdoEntry idx="6001" subIdx="01" bitLen="8" halPin="DI1" halType="u32"/>
<pdoEntry idx="6001" subIdx="02" bitLen="8" halPin="DI2" halType="u32"/>
<pdoEntry idx="6001" subIdx="03" bitLen="8" halPin="DI3" halType="u32"/>
<pdoEntry idx="6001" subIdx="04" bitLen="8" halPin="DI4" halType="u32"/>
It's not clear to me what function those DI pins have and how they are programmed in the EEPROM generator.
I see that I created some enable pins. I assume they are to enable the output of each of the step generators. In the XML file for LINUXCNC, these pins appear as BIT, but I don't know how to configure them correctly in the EEPROM generator file. Bit variables don't appear there. In that same file it appears
<pdoEntry idx="6001" subIdx="01" bitLen="32" halPin="Frequency" halType="float-ieee"/>
</pdo>
<pdo idx="1a01">
<pdoEntry idx="6001" subIdx="01" bitLen="8" halPin="DI1" halType="u32"/>
<pdoEntry idx="6001" subIdx="02" bitLen="8" halPin="DI2" halType="u32"/>
<pdoEntry idx="6001" subIdx="03" bitLen="8" halPin="DI3" halType="u32"/>
<pdoEntry idx="6001" subIdx="04" bitLen="8" halPin="DI4" halType="u32"/>
It's not clear to me what function those DI pins have and how they are programmed in the EEPROM generator.
Please Log in or Create an account to join the conversation.
- Hakan
- Offline
- Platinum Member
-
Less
More
- Posts: 651
- Thank you received: 213
01 May 2025 05:46 #327405
by Hakan
Replied by Hakan on topic MAX VELOCITY STEP.
I think there is something not quite right in the eeprom_generator with bits, so I use uint8 instead.
And then create a bit pin in linuxcnc with
<pdoEntry idx="600x" subIdx="01" bitLen="8" halPin="enable1" halType="bit"/>
Those DI pins are the input pins, for switches etc. I think the halType should be "bit" for them.
What do you do in the code with the enable information?
And then create a bit pin in linuxcnc with
<pdoEntry idx="600x" subIdx="01" bitLen="8" halPin="enable1" halType="bit"/>
Those DI pins are the input pins, for switches etc. I think the halType should be "bit" for them.
What do you do in the code with the enable information?
Please Log in or Create an account to join the conversation.
Time to create page: 0.153 seconds