1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • tommylight
  • tommylight's Avatar
23 Mar 2025 13:18
Replied by tommylight on topic Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Category: Configuration Tools

Attached is a config used for testing those drives exactly, with Mesa 5i25 or 6i25 so should be easy enough to edit to 7i95T, i think, i had no time to play with 7i95 as it went on to full daily duty soon after i got it.
-
I am glad you are very happy like a kid, it is a great feeling when you have things working as you like them, but do not expect MesaCT to make a working config after changing the basic functionality of the board, it can not account for all our requested features, but it does crate something you can edit easily, just replace stepgens with PWM's and mind the naming and order of lines.
While you're at it, here is that config driving a motor
  • Boogie
  • Boogie
23 Mar 2025 13:16
Replied by Boogie on topic Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Category: Configuration Tools

Configuration files created attached.Please poke me in good direction.
  • Boogie
  • Boogie
23 Mar 2025 13:10 - 23 Mar 2025 13:13
Replied by Boogie on topic Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Category: Configuration Tools

More screen shots:
I don't understand where is the proper place in MesaCT to set XYZ axes PWM mode, assign pins for it, assign pins for respective encoders. Curious why in CT, under "Firmware' tab -> 'Mesaflash' tab: there is no options available - not possible to pick firmware file, not possible to verify existing one, 'Add firmware' not working (no reaction at all).

I know PID tuning will be from LinuxCNC but it's not starting at this stage.
  • rodw
  • rodw's Avatar
23 Mar 2025 13:08
Replied by rodw on topic Config will not open after Buildbot2 upgade from 2.9.4 to 2.10

Config will not open after Buildbot2 upgade from 2.9.4 to 2.10

Category: Plasmac

For the third time with some more detail. To replicate
1. Install Linuxcnc 2.9.4 (rip should be fine but I used the ISO)
2. Install the Qtplasmac sim to the config folder
3. Open the sim to confirm its working
4. Close the sim
5. Install Linuxcnc 2.10 or run from another RIP folder
6. Open linuxcnc 2.10
7. Open the previously installed sim.
8. Upgrade message should be displayed
9. Repeat 6,7 The upgrade message will be displayed again and Linuxcnc exits without error message. 

I just wanted to test an upgrade from the 2.9.4 ISO to use 2.10 before asking a customer to upgrade his working system. I now know the workarounds but I don't think the bug will bite on a live system

FYI, I have just posted an upgrade script to go from 2.9.4 to 2.10 in the Installing Linuxcnc section that shows what I want to achieve. Becasue Linuxcnc does not maintain a buildbot on Linuxcnc.org, some changes to  the apt folders are required to point to the buildbot2 repo. We follow the Debian standards for APT in the ISO so there is some data in subfolders that needs removing.
Ref: forum.linuxcnc.org/9-installing-linuxcnc...n-2-10-master-branch
  • Boogie
  • Boogie
23 Mar 2025 13:04
Replied by Boogie on topic Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Mesa 7i95T config for workbench tests - to drive H-Bridges + PMDC servos

Category: Configuration Tools

Happy like a kid started tweaking with Mesa:
1. connected, powered and check if visible - all ok
2. mesaflashed used to write bin file from PCW - all seems ok, i can sie PWM instead of stepgens (screen shot attached)
3. installed MesaCT 2.1.7
4. built config as in attached screenshots (grrr how to paste photos into the text here???)
5. run LinuxCNC and crash as per screen shot:(


 
  • snowgoer540
  • snowgoer540's Avatar
23 Mar 2025 12:50
Replied by snowgoer540 on topic Config will not open after Buildbot2 upgade from 2.9.4 to 2.10

Config will not open after Buildbot2 upgade from 2.9.4 to 2.10

Category: Plasmac

Yes, there are over 20 messages saying it upgraded but not one message saying it got an error and failed during that upgrade attempt.

That's because it didn't fail, at least not in the eyes of the try/except handler.

You can see I tried several times tying to get to the bottom of it, each generating a message.

The issue is that on two different PC's, the upgrade to a sim install failed without reporting an error which left me in the dark.

I don't know what you mean by "the upgrade to a sim install". Could you please elaborate?

You seem unwilling to actually test such an upgrade process and instead want to blame my installation.

I wouldn't say I am unwilling, even in the absence of steb-by-step directions from you as to how to reproduce what it is you are experiencing, I took my own steps to try to duplicate your issue:

I removed the package version I had installed, added the secret buildbot, and installed master for bookworm. I then launched linuxcnc by typing linuxcnc in the terminal. Navigated to Sample Configurations > sim > qtplasmac > qtplasmac_l_metric, and clicked OK. It worked fine with no update messages. I repeated for a RIP installation, it worked fine with no update messages.

The thing is that this issue has been solved by the aforementioned commits, and a sim config never needs to be updated, as it has the necessary changes. So it leads me to the conclusion that something went wrong in the process of going from 2.9.4 to 2.10.

Are you copying the config and trying to make a usable machine out of it? Or are you trying to actually simulate your machine?

If it's the latter, there's a way to simulate your actual table.
  • rodw
  • rodw's Avatar
23 Mar 2025 12:48
Replied by rodw on topic e-stop signal from hybrid servo stepper threw Mesa 7i96s

e-stop signal from hybrid servo stepper threw Mesa 7i96s

Category: Driver Boards

As Tommy says connect the alarm output on the drive to to joint.N.amp-fault-in
You may need to invert the signal with the not component. I know I had to.
  • rodw
  • rodw's Avatar
23 Mar 2025 12:43 - 03 Apr 2025 08:57
Script to update 2.9.x ISO to use Linuxcnc Version 2.10 (master branch) was created by rodw

Script to update 2.9.x ISO to use Linuxcnc Version 2.10 (master branch)

Category: Installing LinuxCNC

This script installs linuxcnc master branch (2.10) after you have installed the ISO on the downloads page.Hakan has tested and refined this further down this thread so I have updated the script here.


You may want to move to version 2.10 to get the latest QtPlasmac for example as the version in 2.9.4 is no longer maintained.
\Instructions:
1. Download  attached script
2. Delete the .txt.extension3. Check permisssions are executible (Right click, Properties and check Permissions tab)
4. Run the script from the folder it is downloaded to: sudo ./update-master.sh

The script deletes and modifies some files in the /etc/apt folder and sub-folders.  It does make a copy of the /etc/apt folder into your home folderI tried on one PC and it worked. On another PC it didn't. If it fails, open the file and run each line individually
after the apt upgrade is complete, running linuxcnc should show version 2.10 on startup in the console and the splash screen.
To update down the track
sudo apt update && sudo apt upgrade
  • tommylight
  • tommylight's Avatar
23 Mar 2025 11:43 - 23 Mar 2025 11:56
Replied by tommylight on topic Blown 7i84

Blown 7i84

Category: Driver Boards

Red LED comes on for a very short period when powered on.
EDITED
To late, but just watched the video, so, i would have not removed the OK looking chip at all, it sure looks like something back powered one of the outputs on that chip as you mention on the video.
  • tommylight
  • tommylight's Avatar
23 Mar 2025 11:40
Replied by tommylight on topic e-stop signal from hybrid servo stepper threw Mesa 7i96s

e-stop signal from hybrid servo stepper threw Mesa 7i96s

Category: Driver Boards

Does the drive have a fault output?
Is that fault output wired to Mesa input?
Is the Mesa input pin wired to joint.0.amp-fault in hal?
Those are the things required for a fault to stop the machine, it will not trigger e-stop but it will disable the machine completely, so after fixing whatever the issue was, you can just enable the machine and continue working.
  • endian
  • endian's Avatar
23 Mar 2025 11:37 - 23 Mar 2025 17:39
Replied by endian on topic EL6731 changes cyclically to INIT status

EL6731 changes cyclically to INIT status

Category: EtherCAT

Hello,

if your config with profibus needs a sync movements... It is necessary to use a Equidistant mode... if not it should be in the free run -

DC sync in your case 1C32 parameter is -
 “03 00 03 00 40 42 0F 00 00 00 00 00 00”
- 40 42 0f 00 == 1ms but it is too short and I can guarantee timing incidents ..

Free run in your case 1C32 parameter is - 
 “03 00 01 00 40 42 0F 00 00 00 00 00 00”
 - 40 42 0f 00 == 1ms but real synchronization it based on scan time of profibus

then you configuration is missing the SDOs -
<!--Slave PDO configuration shaping...-->
<!--EL67xx CoE Init Cmd 0 (1C32:00)-->
<sdoConfig idx="1C32" subIdx="complete">
  <sdoDataRaw data="03 00 03 00 40 42 0F 00 00 00 00 00" />
</sdoConfig>
<!--EL67xx CoE Init Cmd 1 (1C33:00)-->
<sdoConfig idx="1C33" subIdx="complete">
  <sdoDataRaw data="03 00 22 00 00 00 00 00 00 00 00 00" />
</sdoConfig>
<!--EL67xx CoE Init Cmd 2 (F800:00)-->
<sdoConfig idx="F800" subIdx="complete">
  <sdoDataRaw data="11 00 01 09 E8 03 0B 00 20 03 09 10 64 7E 04 01 0A 00 04 00 10 00 00 00 00 00 05 00" />
</sdoConfig>
<!--EL67xx CoE Init Cmd 3 (8000:00)-->
<sdoConfig idx="8000" subIdx="complete">
  <sdoDataRaw data="2D 00 0A 00 00 00 00 00 00 00 00 00 00 00 A8 01 00 00 40 34 00 00 00 00 26 02 00 00 00 00 88 01 14 0B BE CE 00 C0 00 08 00 00 00 00 40 00 63 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11 21" />
</sdoConfig>
<!--EL67xx CoE Init Cmd 4 (8010:00)-->
<sdoConfig idx="8010" subIdx="complete">
  <sdoDataRaw data="2D 00 1F 00 00 00 00 00 00 00 00 00 00 00 A0 01 00 00 06 00 00 00 00 00 0A 05 00 00 00 00 80 01 14 0B 81 22 00 00 00 00 C0 07 0D 01 00" />
</sdoConfig>
<!--download pdo 0x1C12 index-->
<sdoConfig idx="1C12" subIdx="complete">
  <sdoDataRaw data="02 00 00 16 01 16" />
</sdoConfig>
<!--download pdo 0x1C13 index-->
<sdoConfig idx="1C13" subIdx="complete">
  <sdoDataRaw data="03 00 00 1A 01 1A 80 1A" />
</sdoConfig>
<!--DP PrmData Slave 010-->
<sdoConfig idx="8001" subIdx="00">
  <sdoDataRaw data="80 01 14 0B BE CE 00 C0 00 08 00 00 00 00 40 00 63 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" />
</sdoConfig>
<!--DP CfgData Slave 010-->
<sdoConfig idx="8002" subIdx="00">
  <sdoDataRaw data="11 21" />
</sdoConfig>
<!--DP PrmData Slave 031-->
<sdoConfig idx="8011" subIdx="00">
  <sdoDataRaw data="80 01 14 0B 81 22 00 00 00 00" />
</sdoConfig>
<!--DP CfgData Slave 031-->
<sdoConfig idx="8012" subIdx="00">
  <sdoDataRaw data="C0 07 0D 01 00" />
</sdoConfig>
<!--Slave PDO configuration shaping end...-->

it will be right behind the "complete" mapping guys but in front off sync managers ... 
How can I understand this?

Your config is missing of the DC configuration adn SDO datas cofig too

What have I forgotten?

If you will choose the DC operation mode - somewhere in the slave config it has to be a DC configuration of the slave - something like 
                    <!-- EL6731 -->
                    <pdo idx="1A80">
                      <pdoEntry idx="F102" subIdx="01" bitLen="08" halPin="state-Slave-F102-01" halType="u32" />
                      <pdoEntry idx="F102" subIdx="02" bitLen="08" halPin="state-Slave-F102-02" halType="u32" />
                      <pdoEntry idx="F102" subIdx="03" bitLen="08" halPin="state-Slave-F102-03" halType="u32" />
                      <pdoEntry idx="F102" subIdx="04" bitLen="08" halPin="state-Slave-F102-04" halType="u32" />
                      <pdoEntry idx="F102" subIdx="05" bitLen="08" halPin="state-Slave-F102-05" halType="u32" />
                      <pdoEntry idx="F102" subIdx="06" bitLen="08" halPin="state-Slave-F102-06" halType="u32" />
                      <pdoEntry idx="F102" subIdx="07" bitLen="08" halPin="state-Slave-F102-07" halType="u32" />
                      <pdoEntry idx="F101" subIdx="03" bitLen="08" halPin="state-EL6731" halType="u32" />
                      <pdoEntry idx="F101" subIdx="14" bitLen="01" halPin="diagFlag-EL6731" halType="bit" />
                      <pdoEntry idx="F103" subIdx="01" bitLen="01" halPin="diagFlagSlave-F103-01" halType="bit" />
                      <pdoEntry idx="F103" subIdx="02" bitLen="01" halPin="diagFlagSlave-F103-02" halType="bit" />
                      <pdoEntry idx="F103" subIdx="03" bitLen="01" halPin="diagFlagSlave-F103-03" halType="bit" />
                      <pdoEntry idx="F103" subIdx="04" bitLen="01" halPin="diagFlagSlave-F103-04" halType="bit" />
                      <pdoEntry idx="F103" subIdx="05" bitLen="01" halPin="diagFlagSlave-F103-05" halType="bit" />
                      <pdoEntry idx="F103" subIdx="06" bitLen="01" halPin="diagFlagSlave-F103-06" halType="bit" />
                      <pdoEntry idx="F103" subIdx="07" bitLen="01" halPin="diagFlagSlave-F103-07" halType="bit" />
                      <pdoEntry idx="0000" subIdx="00" bitLen="08" halPin="GAP-0000-0" halType="u32" />
                    </pdo>
                </syncManager>
                <dcConf assignActivate="1000" sync0Cycle="*1" sync0Shift="0" sync1Cycle="*1" sync1Shift="100"/>    
  • tommylight
  • tommylight's Avatar
23 Mar 2025 11:30
Replied by tommylight on topic Raspberry Pi 4 and bad latency.. SOLUTIONS?

Raspberry Pi 4 and bad latency.. SOLUTIONS?

Category: Installing LinuxCNC

Latency excursions beyond the visible graph area.
  • machinedude
  • machinedude's Avatar
23 Mar 2025 11:26
Replied by machinedude on topic Black Friday Deal got me :)

Black Friday Deal got me :)

Category: Plasma & Laser

my first attempt at a rotary union ended up being a bust. i was going to just eat the cost and buy these but something the manufacture said during a response made me pause on that idea. i was told a 2 Kw motor was the requirements to drive one of theirs. my plan was to drive two of these in series so a 4 Kw motor to do this seemed like a deal breaker. so i decided to take another attempt at one. i got tired of looking for a sealing solution from the manufactures that would work with common stock size and trying to find a certain type of seal in the size i needed. So i did what i had to and took matters into my own hands and designed my own and made a mold to cast them myself. so i will either get thing to work or go down swinging trying :)
  • tommylight
  • tommylight's Avatar
23 Mar 2025 11:23
Replied by tommylight on topic PCIe - No parport registered at "0x " . This is not Always an error.Continuing.

PCIe - No parport registered at "0x " . This is not Always an error.Continuing.

Category: Advanced Configuration

Picture, capabilities access denied, that is usually due to not using sudo, so
sudo lspci -v
see if it shows the driver and kernel module.
Always use sudo when dealing with kernel level stuff, for reading only.
  • kmeld
  • kmeld
23 Mar 2025 10:40
e-stop signal from hybrid servo stepper threw Mesa 7i96s was created by kmeld

e-stop signal from hybrid servo stepper threw Mesa 7i96s

Category: Driver Boards

Hi,
I do not actually know where to start.

I have 3axis cnc mill set up on Mesa 7i96s with hybrid servo stepper drives 2HSS86H-N

currently when stepper drive goes in to error (position following error) motor stops and is not responding but while cnc control does not go in to e-stop mode.

I would like to have it set up in such a way so in such event as one of the controllers goes in to any fault it will automatically trigger e-stop for the whole control.

Could someone help me set this up?
I need help on very basic level in this field.

Cris.
 
Displaying 7621 - 7635 out of 24517 results.
  1. Forum
  3. Search
Time to create page: 0.257 seconds
Powered by Kunena Forum