Advanced Search

I asked because i do not do NDA, ever.
Make a list of what you need and post it here, i am pretty sure someone somehow will help with it.

I really want to have it documented with a print so 10 yesrs down the line its easy to fix. Correct components selected. I can work alongside you tell you what components I already have. You make a wiring diagram that is easy to follow that includes the components and wire size/grade. Make suggestions for bulk head connectors etc that are high qaulity for a reasonable price. I know you were watching my build on the forum. I make a list of the parts I have at my disposal. Anything I missing tell me what to buy. I build it and help me with trouble shooting if I need any, but shouldn't need much help with that. I got linux cnc to work on my band saw project so im not a absolute beginner, but im not a electrical engineer either. The machine will never need to pass any sort of code inspection or be sold to the public.

If you want me to sign a nda I can. Im not building tables to make money. I just want the one im retrofitting for myself to be safe and reliable. I dont expect any nda from anyone. Im open to sharing all work on the forum. Or keeping it secret if you dont want to give out ur secrets. I dont really think its super crazy complex or anything to put this together but I would like to have the components properly sized and interference to be accounted for. Just need some help finishing my project. Its alot of planning and to have someone more exp who can reference me in the right direction would save me many hours of planning and potential down time.

Can you post your current hal/ini files?

Hi everyone,
this is my first time using LinuxCNC and a Mesa board. I received my 7i95T a few days ago and have been running several tests since then.
I installed LinuxCNC 2.9.4 on an old desktop PC and everything runs smoothly. After that, I updated the system and installed the Mesa Configuration Tool, since I read that the 7i95T cannot be configured with the standard PNCconf wizard.I successfully connected to the board using the default IP address 192.168.1.121, and the PC communicates with it correctly.
Because I need a PWM output for my 0–10 V analog converter (my VFD does not support RS-485 unfortunately), I downloaded the appropriate firmware, flashed it to the board, and the update went fine.
After completing the basic configuration, I switched the GUI to qtDragon_hd for a better interface. LinuxCNC loads without errors, and I was able to test one axis (stepper + proximity sensor) without issues.Where I’m stuck: PWM generationReading the HMIDs, I can see that the last stepgen has been replaced by a PWM generator, but I’m not understanding how to properly use this PWM output.Here’s what I tried:

• I connected the PWM signal to pin 9 on the 7i95T header.
• I left the DIR pin disconnected for now because I only need the spindle to run clockwise.
• I connected my 0–10 V PWM-to-analog converter, but no voltage output appears.
• I also tried checking the signal using an oscilloscope, but I get no PWM activity at all.

So at this point I’m not sure whether:

1. I misconfigured the PWM generator in LinuxCNC/HAL,
2. I am misunderstanding how the PWM output on the 7i95T is supposed to work.

Additionally, I need to set the PWM frequency to 2 kHz (my converter requires ≤2 kHz), but I don’t know where to configure that correctly.

Also, I would also like to use my MPG wheel.
My idea is:

• connect the MPG encoder to the left-side encoder input (ENC0),
• connect the MPG pushbuttons and the selector to the input pins on the right side, according to the Mesa Config Tool assignments.

Can someone confirm whether this wiring plan is correct?
Thanks a lot to everyone in advance!

I should also add that the "STATUS.homed.onVal..." method does work on VCPSettingsPushButton type buttons but not on SubCallButton types. Setting the .setEnabled(False) property of either does not work directly.

Edit: In good news, the new version seems to have solved my issue with the UI locking up after using a probing routine. Probing is working great now.

www.instagram.com/reel/DRLRtaqEhp7/?igsh=MWtobW01d2J6bDdjeQ==

now I have to fine-tune the motor, which for now does not vibrate, but only at higher speeds, then connect the spindle and, of course, the racktoolchange (the first time I try it, I hope I can conclude something from the example) thanks for the advice and support

been having some trouble with getting my 7i73 keyboard matrix to interact with the machine. could be just a me issue, it is currently abouyt 32 degrees f and I cant feel my hands out here. tried searching for answers and gotr some but the buttons dont do anything in either halshow or halscope. I have attached my hal files that involve the matrix.

Would you recommend just uninstalling probe basic and starting over?

Never mind.

Buster.
If you teach how exactly, poke your nose into the "download, enter" type of instructions, then I can. Alas, in this area (patches, sources) I am weaker than in other areas.
While I’m trying to put v2.9.4 on the free partition and even with this there are problems - in the instructions
linuxcnc.org/docs/2.9/html/getting-start...#cha:Installing-RTAI
the required repository is specified with an error, the kernel itself is installed with errors, and For several years now they have forgotten to indicate in the instructions what to do first -

apt-get purge linuxcnc-uspace
apt-get purge linuxcnc-doc*

and then more
apt-get install linuxcnc

Yep. That was it. God I do not feel bright. Thanks for the help on this.

Yeah. Reviewing my notes its 5i25_7i76x2.

I think I just got something to click looking at these with fresh ideas. on Pncconf under the "Num" column that's not the DB25 pin, but IO number, so when I have my config configured for 7i76x2 and I want I/O 7 for Z Axis Stepgen, my joint3, that's actually Pin 17 on the DB25... I totally thought it was all mapped 1 to 1.

Currently the master builds are failing:
buildbot2.highlab.com/buildbot/#/grid
And no debs are uploaded if the build fails.

I am not sure what the current problem is, possibly something in the docs.

You could try building from source, it's not particularly difficult.

RotarySMP wrote:

You are making good progress. Once you have it all running, I will have to use your HAL and Ini to upgrade my machine to 2.9 

The updater script _should_ handle any necessary HAL changes. 
Not a lot changed between 2.8 and 2.9 (2.7 to 2.8 was the big shift)