Advanced Search

I dont have the hardware for the rt1052, but most units arent directly controlling an analog voltage, but rather sending a PWM to an opamp which makes 0-10v. When this is the case, the PWM signal is out of 100, so PWM 100 = 10v = max spindle speed. From the configs Ive seen for the RT1052 I will assume its the same, but I cannot find an example that says otherwise.

many thanks this way I can keep a lot of my own ui stuff just need to move it.
QtDragon seens to be a bit more flexible there.
I really like the look of probe basic and it's now my 3rd machine using it.

My adaptations are usually quite unique to my machines caus they are retrofits of old industrial machines.
I had a basket tool changer and a turn table and automatic doors. (but this machine is gone)
Then there is the partial manual three stage gear box on my lathe in combination with a vfd
An om my current machines the lube and column system.

But what i uses al the time were leds for all the IO's. this helps trouble shooting.

What like is the setup sheet. I think you wrote the bits for me and it didn't get into production.

and I started on the lathe macros with saving the parameters. but I ran out of patience and time.

For me this all is just a hobby and in the past year and a half I had even less time cause I am living in two places until I got my building permit and have the new workshop prpared to move my shit.

Sorry if I was impatient I kind was hoping that it would be just one or two small things i need to change.

And then I looked into alternatives and the documentation for qtdragon was a bit easier to unterstand ho to customize for me. And it looks a bit more flexible.
But lacks a lathe interface and I still hope I can copy pate some of my shit in the custom tab and get it running.
I am kind of lazy when it comes to doing work twice.

And I need to thank you guys for being open source linuxcnc and probe_basic is really impressive and a really great piece of software.
Many thanks for all the work and kind support I am getting here

In this case the control box contains the breakout board

There is no need to re-route signals, you just need firmware that
matches the required pinout.

Firmware is updated with the mesaflash tool, but the first step
is to determine the required pinout of your breakout

Do you have this pinout available?

(a working hal file created with stepconf would include this information)
 

Any idea about the pin out for spindle 0-10v output? PWM I noticed in your config/other pinouts but voltage based seems to be missing.

Thanks again
Alessandro

Hi
I use 7i73 and now I use   IN9 - IN13   for pendant input(For Sellect X, Y,Z, x1 , x10)  and use IN14 and IN15 for encoder pendant 
Now I use all bit input.
Now I connect resistor IN3 -IN7 for pull up done.
I want to use IN3 - IN7 for bit input but it's can't recieved  0 , 1 for trig signal (IN3 - IN7 analog input). 


How to setup ini ,hal for use IN3 - IN7 for bit input or trig signal ? 

 

Thank you ,
Asis

There is no breakout board - the K2 has a control box with a DB25F on the back. I could probably crack it open and see what it's running inside. From there I could likely re-route the lines to bring it back to "standard" pinouts. But it feels like this should be a .hal thing.

When you say "choose firmware" do you mean the firmware on the Mesa card?

Is this something I can configure via the Mesa Configuration Tool?

I agree. My project is in the stand stage on the table. But it works within its limits. However, It's not ok to not have a normal touch when it should be the default.

I spent a fair bit of time getting a simple push-button to Mesa input to cause a jog x increment to occur. Google searches led to numerous threads with others struggling to get this seemingly simple thing to work. According to some of those posts, previous versions of LinuxCNC had a bug related to this and the method to cause a jog appears to have changed as well. So now that I have it working I decided to post what works for me and some of my incorrect assumptions along the way, with the goal of helping others not make the same mistakes I made.. I'm a bit of a newbie to all of this so if anything below appears incorrect please advise and I will correct.

Important things I learned:
1) There are a LOT of pins some with similar names, it helps to get a complete list for perusal:    PCW post=307558 userid=481

2) I assumed that the HAL jog related commands that I was adding to my postgui.hal file would effectively trigger the jog related GUI buttons in axis. My understanding now is that the halui pins are a completely different set of pins/parameters with no connection to the axis GUI buttons. So for example while testing, selecting an increment of say 0.01 in the Axis GUI does not set halui.axis.x.increment to 0.01. If you want an increment of 0.01 you need to explicitly add a line in your hal file to make that happen, for example setp halui.axis.x.increment 0.01.

3) The axisui pins don't exist until after the axis-gui has been loaded so all your hal code that requires pins from GUIs, like axisui pins, need to be in a postgui.hal file.  

4) Before homing the motors are jogged as joints, after homing the motors are moved as axes.

5) Before using the halui jog pins ALL of the axis's need to be homed, not just the axis your trying to jog!

6) halui.axis.x.plus jogs continuously while activated, and halui.axis.x.increment-plus jogs by the previously specified increment (once per)

I have attached the relevant portion of my postgui.hal file as an example that works for me using Mesa input 3 as the trigger for a jog x + 0.1 increment.

 

 

Encoder support is also something I am looking to have. Then the rp2040 is then probably not the best option any more. How can I estimate the performance in terms of drive frequency for the axis?

You cannot change the pinout of a specific firmware, you need
to choose firmware that matches the breakout you use.
You can change which stepgen runs which motion axis.

What breakout board do you need to support? For most
breakouts there are specific firmware files that match
their pinouts.

You can check pinouts by looking at the .pin files in the 7I92.zip
firmware distribution zip file (in /configs/hostmot2)

After a bit of trial and error I found the problem, I can now jog from the Arduino board. The fundamental problem was that I was not homing all axis's, I assumed because I was trying to jog x that homing x was sufficient.

I did a little test where I banged in 10 jog increments as fast as I could and none were lost. I'm not using a MPG so I can't comment on the slow response of the ArduinoConnector as noted by blazini36 when using a MPG, however for regular button presses it seems to be doing the job for me.

I have attached the relevant portion of my postgui.hal

Thanks for the help getting this working.
Jeff
 

in PNCConf how do I assign a StepGen to the specific pins on the parallel port?

Background
I found myself with a K2 CNC router.  The parallel pinouts are non-standard

I was able to get it working in StepConf on an old machine with a built-in parallel port, but I wanted to get it running under the 7i92TM.  I have 2 other machines running with these cards.  I configured the card and cold-swapped it into one of the other machines and it worked perfectly.

But I must have just gotten lucky and the pin mappings were magically perfect on those other two machines because I can't find anywhere where I can assign the pins to the axes in PNCCONF.

I think it should be P2 on the attached PNG file, but on the far left column it says, "Num" 0, 1 and 2 and it assigns those to the stepgen.

But I can't figure out how to configure the StepGen to the specific pins.

I know it's some simple step I missed, but I'm totally wrapped around the axle on this.

Thank you,

 

Perhaps the parport_pc module is loaded?
If it's PCIe you could try to disable the active state power management with the kernel parameter: pcie_aspm=off
Otherwise you could try another kernel, this is 6.10:
drive.google.com/drive/folders/1L28lG0zD...2XQJx?usp=drive_link

Yes! I am really happy that I've solved als the Hardware issues.
on the wiring todo list only open points are home and brake of the 4th axis.
And the Tool length sensor.

open software topics are:
migration to 2.9.3 maybe changing from probe_basic to qtdragon
Toolchange seqence
home with index.
Drive feedback

Nice to haves
Load feedback from drives and Spindle
Linear Scales for the Colum (Extension for Z Travel axis to compensate Tool length) To keep the Quill travel as short as possible and make the tool length sensor fully usable.

user tabs are in the sim config folder, you simply turn them on or off in the ini file, there is one for the main tab group and the side bar, so it pretty much covers you for being able to add any functionality you may need. 

now it doesn't work if you are changing the main ui and need to add things in, but if you have a good idea for a change or addition you can alway voice that here or on the qtpyvcp chat.  we incorporate many ideas to make Probe Basic better often.  that is where many of the latest update changes came from, made to fix some shortcomings and add some feature functionality!.

Below is an image of the user tabs. those should also be available in the stable version.  you would simply edit those two files in qtdesigner and they are loaded on start up. this was they travel with your config and are never overwritten on updates.  you can nest tabs to make them infinitely deep to accomodate the most intesnse project additions.

Chris