Advanced Search

Good evening 

I've been using this iso successfully for a while now, i picked up a nice touch screen that works, but would work a lot better if i installed the displaylink drivers. Problem is that when installing this, i get an error that the linux headers are missing. 

Ive tried many of the usual commands to load the headers and nothing seems to be able to find the matching file. Have you got any insight or suggestions? 

If you would like specific error messages i can go through the motions and record these for you. 

Cheers!

i'm not into this stuff, but why would an ST programming utility connect to an NXP chip?

Hi Chris.

I tried creating a Probe routine in MDI mode, just in case I was doing it manually and it was my mistake. I'm getting the same problem in both MDI and MAN modes. I've attached screenshots from both modes.

Thanks a lot.

Same post here:
forum.linuxcnc.org/38-general-linuxcnc-q...n-4-axis-mode#347523

No double posting, please continue in the thread linked above.

the whole connection thing was already working on mesaflash and mesact, i could confirm with mesact, every test was a success. But Linuxcnc would fail, In the end I had to click on the network button top right and then it worked.

As for now i´m okay. Sorry for the rant, but I was used to it being easy setup with Pncconfigwizardo

You need to configure the network on the host for the Mesa card.

Also 192.168.1.121 is not suggested for LinuxCNC use as it's  in
a commonly used NAT range.

Suggested setup is to use the 10.10.10.10 address on the Mesa card
(via the IP address setup jumpers) and set  a static host address of
say 10.10.10.100/24.

At this point you should be able to ping the Mesa card:

ping 10.10.10.10

 

I mean i love the Mesa cards and Linuxcnc, but this card really made me reconsider using Mesa and Linuxcnc. The point where i broke was, after getting it to be recognized by mesaflash and mesact Linuxcnc would tell me network unreachable. This problem followed me through the whole process, either "network unreachable" or "no such device at 192.168.1.121"

EDIT: So far i got it running, but the whole process to get there is tiresome.

It would be normal to select MDI mode to use the probe after running a program.
You probably can't select tools, offsets or file in auto mode too.

let me know if I've misunderstood the problem.

Chris

Done!
Thanks.

Explanations later... sorry.

That's great!


It does need:

setp   hm2_7i97.0.pwmgen.00.offset-mode 1

and not required but an added feature would be:

setp   hm2_7i97.0.pwmgen.00.dither 1


for all 7I97/7I97T PWMgens


Also a better default PWM frequency would be 48 KHz



 

Was this same question asked before on this forum?
-
P.S.
Still did not finish my build of a 4 axis foam cutter, so not yet at this point.

hi I have a 4 axis hot wire foam cutter. i move each axis separate, but I'm wondering if the text below makes sense for, essentially moving U and V with X and Y commands. Thanks

The Fix:
How to make UV emulate XY while keeping their own step calibrations.
To force U and V to mirror X and Y while preserving their independent step calibrations, you must link the signals before the math calculates the motor steps.
In LinuxCNC, you do this by linking the motion controller outputs to both sets of joints, rather than linking the step generators directly.
Open your machine's main .hal file and look for the lines connecting motion.coordinate-system to your joints. Change them to route like this
:hal# Force Joint 2 (U) to listen to the X-axis motion command
net x-output motion.coordinate-system.0.pos-cmd => joint.0.motor-pos-cmd joint.2.motor-pos-cmd

# Force Joint 3 (V) to listen to the Y-axis motion command
net y-output motion.coordinate-system.1.pos-cmd => joint.1.motor-pos-cmd joint.3.motor-pos-cmd
Use code with caution.Why this fixes the calibration issue:
The Signal: LinuxCNC outputs a raw request in millimeters (e.g., "Move X to 50.0mm").The Split: The HAL lines above take that 50.0mm request and send it to both Joint 0 (X) and Joint 2 (U) simultaneously.The Calibration: Joint 0 looks at its own SCALE setting in the .ini file to convert 50.0mm into steps for the X motor. Joint 2 looks at its own independent SCALE setting in the .ini file to convert 50.0mm into steps for the U motor.

I am currently trying to install this and it doesn't validate. When making a bootmedium RUFUS even said, that 1.5GB of the image are missing. Could you please check?

It looks like the 2.9.10 image is half the size of the previous.

The idea/plan is to trace an object (existing part) or a drawing and capture that as a DXF. I don’t have a video of it running but I do have an example from a test run. The image file is what I traced with my machine & the DXF is the result of that trace, there are some issues right now as you can see in the DXF.. The app got "lost" on the smaller radius corner and circle and just started moving back & forth, but the bigger radius and straight line test weren't to bad. I haven’t tried to trace the bottom shape yet, the app isnt ready for that one yet