Advanced Search

Your pc is to old, see the requirements at the top of the installation docs, it states the minimum opengl requirements for vtk which is the backplotter used in probe basic and qtpyvcp uis. Can use a graphics card to resolve or a newer pc.

The user tabs are predefined ui's, you should be able to copy and paste to them. The latest version uses the var files for all parameters so they are callable from toolchange remap, same for all probe paramaters so they work if called from gcode etc.

Qtdragon is a good option too, more flavors is a good thing. As for leds for IO, I had that in there at one point but it caused some issues on faster machines and some computers, it slowed the non realtime layer down for some reason so I removed. But all that is available with halshow.

rthorntn wrote:

Awesome, did you use any opto-couplers/digital isolators, are the nine 16-pin IC's only level-shifters?

Well spotted, correct, those 9 parts are indeed the level shifting. Features digital isolation also, all in one part. I apologize for omitting the schematic for now, once I have it cleaned up and arranged I'll put it up. I'd like to test the board prior though. Regardless, here's a visual below of how it's arranged (ten inputs). Additionally, I'm getting us an ultra-low ripple Isolated 12V Supply done for that board. Plugs right on the main. If we are to isolate this FPGA/Motion Control thing, might as well isolate it true & properly!! 

Here's the cool visuals:

RMJ wrote:

please let me know where to find instructions on how to start a cut in the middle of the file so at least cut recovery is simpler. 

 

  Run From Line allows starting from almost anywhere in a cut file.

Try

locate ethtool

to see if its installed

if it is found, you may need to give the complete path

if it's not installed you will need to install ethtool

sudo apt-get install ethtool

hi,
I'm running into issues running the probe basic simulator. I first tried the APT stable and then the probe basic.deb install (both resulting in different errors)

-  What Linux OS being used including kernel type?
      debian 12 (bookworm)
      Linux 6.1.0-21-rt-amd64
-  What version of Linuxcnc is installed?
      2.9.2
-  What version of QtPyVCP and Probe Basic is installed?
     QtPyVPC_4.1.2-17
     Probe-Basic 0.5.4-83
-  How did you install Probe Basic? Quickstart guide? Dev Guide?
      Probe basic .deb install (kcjengr.github.io/probe_basic/quick_start.html)
-  Have you gone through your ini and hal files and compared to the sim config files to make any changes needed?
     n/a - simulator broken
-  Have you added all of the necessary files in your config folder that probe basic needs to run?
     n/a
-  Have you tested the sim version to see if the problem exists there also? (if the sim functions properly, it is a good indicator your issue is in your config)
    yes - error report attached
-  Add specific details and circumstances surrounding the issue or your question.  The more details the better!
    using a dell insprion 530, i've tried using an NVIDIA quadro k620 as well, but ran into driver issues
    error message after .deb install:2024-08-13 15:25:38.813 (  17.105s) [        4A454040]   vtkShaderProgram.cxx:438    ERR| vtkShaderProgram (0x514b550): 0:1(10): error: GLSL 1.50 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES/usr/bin/linuxcnc: line 977:  5077 Segmentation fault 

system info in screenshot, errors in deb install txt file

Thank you for all of the resources so far, and thanks in advance for the help!

Seig X1 micro mill moved from an old computer with a parallel port breakout to a Mesa 7i96 board
Had a tool touch off sensor installed from the old setup - linked to probe.in
Installed the scripts to have m6 do a manual change with tool probe - currently doesn't update work offset on an M6 rpobe
Added a 3d touch probe for work probing using or2 to link to the probe.in signal
Both the probe and tool length sensor activate a probe event when activated.

Using the "touch off tool" option in Probe basic correctly sets the tool length and I can get the correct offsets by loading the probe, touching off, probing the work piece and then loading the tool and touching off (tool length updates in tool table)
But using a tXX M6 will load the tool, touch off but it doesn't update the tool table of work offset.
Is there a tutorial on modifying the tool-change.ncg script to update the tool table the same way that tool_touch_off.ncg?

Or, even better, has anyone done a similar setup that I can duplicate?

I included my hal and ini files for reference

Thanks
Aaron


 

Limo wrote:

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?

I think this is how to do the math for the axis timing, im fairly sure its the same idea
linuxcnc.org/docs/devel/html/motion/twea...ose_your_base_period

If encoder support is what you need, the rp2040 does not support encoders at this time, and im not sure if it will or what its limits will be. the RT1052 will probably be your best bet if you want something ethernet

In the sample configs included with linuxcnc, you can see examples here

github.com/LinuxCNC/linuxcnc/blob/master...tepper/7i90.ini#L127
github.com/LinuxCNC/linuxcnc/blob/master...tepper-rpspi.hal#L80

I think that the pulse width is called "Step  On-Time" in pncconf

The firmware and pin files are in this zip file:

www.mesanet.com/software/parallel/7c81.zip
 

I got a command not found
 

linuxcnc.org/docs/stable/html/config/ini....html#sub:ini:custom

JT

In this case this was just a proof of concept test. Now that I understand how it works, I will expand. I'm probably not going to use the actual Mesa inputs, I have a SAMD21 on my custom control board that if all goes to plan will emulate the ArduinoConnector project sending button presses to halui and also receive data back from halui. I have this working now for a few points on a little nano board. Next step is to port that nano code to the SAMD21 and then expand for all required points.

Ok I changed the "actual servo period" to 1000000 in pncconf

Feeling not to smart at the moment... where do I find "step pulse width" in pncconf and I have searched the file system and do not see any files starting with 7c81

Sorry for the dumb questions... my google foo needs some help for this kind of stuff

There is information in the 7I97T manual (page 13)
for making a cable for any Sserial device (like the 7I84)

The 7I97T has a single RS-422 interface so can only connect
to a single 7I84 unless you add and additional expansion daughter
card (or simple 1 chip RS-422 interface) to the 7I97Ts P1 expansion
connector.


Do you have the drive and encoder pinouts?