Advanced Search

I am facing a very similar situation. (almost identical to the above descriptions)
I had some issue with the Linux installation to do apt-get, so today I tried to install the latest ISO image new.

Then the Mesa card was not giving any response at all.

I tried lots of different things. Now in my desperation I tried to ping the card from a windows computer and the 4 green LEDs on the 7i95 start with some life signs) aa ping. 192.168.1.121 gives me responses.

Verdict: Probably some mishap with the networkadapter on the NUC PC.

Any advise how to narrow down the Ethernet problem on the Linux installation?

I can also change the card to 10.10.10.10 and ping it from the Windows machine.
My assumptions

• 7i95 card seems not to be damaged
• 5 V power seems O.K.
• the patch cable is not causing the issue 

       Hi,
I am trying to assign to a macrobutton in QtDragon an o-word script that would allow me to toggle the button to switch on and off a laser.
The laser is connected to an output pin (hal_pi_gpio.pin-10-out) and this pin is connected to a signal (laser-on).  But, it doesn't seem to work. Enclosed are the custom M100 macro (to obtain the actual value of the output pin) and the o-word subroutine called by MDI-COMMAND = o<laser_on> call. Any idea why this won't work. Any suggestions how to do this?  Many thanks !!

Well, I went through the website.

But, I want to know about the exact hardware configuration. That is not given in the website.

 

I'm building the carousel at the moment, it's a ride along design with a geneva drive wheel.
Also with a retractable dust sucker, so should be fun to get this all to work.



 

Got it to work with auto extending the probe.
I've programmed the probe to automatically extend when the machine is in probing motion state.
The motion state 5 (probing) is setting a flipflip signal, which is bound to the output pin for a relay and pneumatic valve.
The flipflop bit resets when the machine program is in idle state (which for some reason seems to be inverted "program-running").

Altough I probably add a manual switch or button later, as this way you can't really accurately place the probe before starting the subroutine.
And it also extends when doing a tool offset measurement.

Here I was probing a set square:


 

Small question, after I restart PB I lose the values in the Probe screen and the settings for the Tool setter (like spindle head distance).
How are those retained normally? It didn't happen at first, so must have happened while editing .HAL and .INI.

Tool offsets and WCO do get saved, no issue with those.
 

I was asking as I was wondering what is the practical resolution. Everyone talks about better resolution, but do we practically need this "better" resolution? From mesa website: "10 bits at a 1 KHz sample rate and 12 bits at a 250 Hz sample rate"
is 250 Hz update slow? is 10-bits @ 1 kHz not enough? Heard somewhere that 0.01" THC control accuracy today is pretty good and pairing it with other info that 1 V arc voltage change relates to ca 0.004" (varies but can be used as rule) gives 2.5V arc voltage change. 300 V range @ 10-bit gives 300mV resolution. If 250 Hz is enough then 12-bit gives 73 mV.

I know 0.1 nV is better, but do we need it?
It's just because i have two plasma sources: Powermax 45XP and CUT 70P from Stahlwerk. I'm not going to buy CPC kit for 45XP so THCAD-300 will be more universal. I don't know if my 45XP has any divider installed inside. I don't know if CUT 70P has divider as well. I'm away so have no access to machines to open them and check internals. But I have now option to buy THCAD cheaper (shipping to US instead of to europe to avoid unnecessary and significant costs).

Hi all!

I need a little help understanding the easiest way to implement an axis that is not moving in a linear fashion.
The Z-axis that is going to control the "bed height" of my machine has similar mechanics as a good old fashion car jack (that you keep in the car with your spare tire) and a stepper motor where you would hook in your crank.
This means that one turn on the crankshaft translate to a different "Z" movement depending on where on the lead screw you are.
I have done my best to study the KINS and trivkins man pages but it seems like they are generally describing much more complex behaviors than what is necessary for my use case.

Just to be clear, I'm not asking for the math that describes the movement, only how to implement it in LinuxCNC.

Can this be done with some lines of HAL or does it have to get more complicated? Can someone nudge me in the right direction?

Thunar has a plugin that lets you create shares directly from the Thunar file manager, which is the default for XFCE4. No need to manipulate the smb.conf file. Unfortunately debian doesn't provide a package for this.

HansU post=320986 userid=27132I think it's good to have an information system that notifies also about new features that are disabled by default (for compatibility reasons).

 
Could be possible read notifies from release_notes.txt?
github.com/LinuxCNC/linuxcnc/blob/master...py/release_notes.txt

For example read only text block with "LCNC 2.9" or "LCNC 2.10"
I like it too.

The thing is if you had of asked you would do have been advised on the limitations of software step generation. It's not a finding, it is something that is known. And I could have directed you on how run 7c81 firmware on a $40 spartan 6 dev board, or been directed to one of the other projects.

I fail how your last post explains what I questioned.

If you want to delve into industry standard, what ever that may mean, you'll have to realise that the RPi isn't certified for industrial applications.

Furthermore I'd like to see the reference to that quote. None of it makes sense. It would appear you chose the wrong hardware setup for for application. Did you realise max step rate was related to latency and therefore the base thread ?

I mean by that you need additional hardware to get good results. The Pi alone even the 5 cannot handle it is my finding and conclusion.

""I think this was mentioned in the instructions that the PREEMT linux kernel was compatible only, but not recommended as 'industry standard'.""

What do you mean by this ?

I guess you haven't seen this:
github.com/ozzyrob/Linuxcnc-FPGA

After using two model of pi (4B and 5) I still get disappointing results. Even at slow printing speeds around 25mm/s there is layer shifting and unreliable motion throughout the operation. I believe now that pi + GPIO struggles to keep up with the pulse generation. Even though I am doing indexed printing (orienting the bed only between sections of printing, so no full 5 axis kinematics) My application is a 5 axis (3 + 2 tilting bed) 3d printer.

I think this was mentioned in the instructions that the PREEMT linux kernel was compatible only, but not recommended as 'industry standard'. Since I cant afford a Mesa FPGA card I am going for klipper on an Octopus board and try my best there. Thanks everyone for being super helpful. And if anyone is interested my 5 axis slicer is on Github, it is A Blender addon that works if you also have the Cura engine up and running. You would be able to slice more complicated models with overhang and printing it by rotating the bed (if you do have this kind of setup).

github.com/bbo-git/5AxisSlicerBlenderAddon

Cheers!
Jairo