Advanced Search

another option would be shiftregisters,
this works great for DC-PWM signals and also for not too fast encoders, but you should test it first.
my favorite at the moment is the Devantech iceWerx iCE40-HX8K, which has many IO's and can also be soldered well by hand

www.youtube.com/shorts/BiJppd6_cA4

github.com/multigcs/rio-motoman

Hi,
I'm trying to customize the QtDragon screen. I'm copying using qtvcp copy. but when I start I get an error. The screen copy is called inova. With QtAxis everything is fine.

Good morning everyone!
I am new to linux(cnc), but I am making progress
The next item on my todo list is to setup a VNC server on my cnc machine. 

I read that linuxcnc 2.9.3 (or debian12) has a pre-installed vncserver (x11vnc?). Would you recommend this one over tigervnc etc?
And if so.... could someone tell me how to use it?
Simply connecting to that machine from another vnc client doesnt work out of the box.

Regards
Sebastian

Hello,

For some reason, reading a variable from the ini.file no longer works. Get the error message that the variable is not defined. However, the whole thing worked until the beginning of the year, but so far I didn't do anything unless it was updated today on the occasion.

Here is the excerpt from the INI and the sub -program for tool measurement.
Linuxcnc is the current 2.10 QTDragon HD.

INI
[WERKZEUGWECHSEL]
WECHSEL_POS_X                       = 150
WECHSEL_POS_Y                       = 20
WECHSEL_POS_Z                       = 0
WL_POS_X                            = 6.934             #(Position Taster X)
WL_POS_Y                            = 11.154            #(Position Taster Y)
WL_POS_Z                            = -100              #(Position sicheres Z, etwas laenger als laengstes Werkzeug, hoehe Taster beruecksichtigen)
WL_WEG_ZUM_SENSOR                   = -70               #(Messdistanz, Weg innerhalb der Taster ausloesen muss)

Tool length
#1801=#<_ini[WERKZEUGWECHSEL]WL_POS_X>                                  (Position Taster X)
#1802=#<_ini[WERKZEUGWECHSEL]WL_POS_Y>                                  (Position Taster Y)
#1800=#<_ini[WERKZEUGWECHSEL]WL_POS_Z>                                  (Position sicheres Z, etwas laenger als laengstes Werkzeug, hoehe Taster beruecksichtigen)
#1804=#<_ini[WERKZEUGWECHSEL]WL_WEG_ZUM_SENSOR>                         (Messdistanz, Weg innerhalb der Taster ausloesen muss)

If something has changed in the syntax, if I assign the values ​​directly in the measurement, I don't get a mistake.
I found it pleasant to have the values ​​in the Ini.

I somehow don't get the measurement routine built into Qtdragon. I work with two buttons switched in series as an opener. What one is installed and the other flies to workpiece height measurement.

Thank you very much and have a nice weekend Frank.

OK cool, thanks for that, I think I'll try it out. The tangnano is doing the job nicely so far but runs out of pins quickly when you include 4 axis closed loop with index pulses.

Cheers.
Russell.

Yes there is a mux4. But then you will one have 2 selction bits and he needs three. Assuming there is a fourth state where nothing is active otherwise mux4 is doable I would say.

in the near future. The stepper-ninja hal driver run in the servo-thread so the minimum width of one input is 1 servo thread refresh in length, with 1KHz servo-thread its 1mS, something like this: when you see a ruler, all 1mm division represents a servo thread cycle, the signal only starts in the divisions and only end on the divisions. With low spindle speed its probably working, but if you want better threading you use printer port for the lathe spindle encoder.

only the onboard mii chips do not run, the w5500 runs with all boards and toolchains.

the programmer on the additional board is very slow, better use a USB blaster to access the JTAG pins, it works great with openFPGAloader

I would prefer the i5, it has the ECP5 on it and is best supported. It's also so big that you won't get it full

Cheers,
Olli

 Hallo,
I tested the new version today and noticed that when I round the corners P64 P10.0 the speed of the axis (joint) does not behave as expected (yellow circle).
The acceleration (green circles) is interrupted by (blue circles) whereby the change in acceleration (jerk) appears to be too large.
At P64 P0.0 the axis (joint) behaves as expected.
Can this behavior be set via parameters?

 

Gruß
Rüdiger

Hello,

let check this topic  ... It will be in the general 99% same as for CanOpen setup.. but datas config should be little bit different...

regards E..

I have never had issues mounting the THCAD inside the control box. The plasma has a CNC interface connector so its designed for this.
You will not have issues.

You should just need to use HOME_OFFSET to get your gantry square and rely on your encoders to keep them that way

Look at the example in the docs for a MPG for axis selection and scaling. I think there is also a MUX4

Oops, just thought. the tension should be able to be done using home offsets

Once the fabric is tensioned, linuxcnc should be able to use the joint axes to control 4 motors in unison. Normally, it is just used for 2 on both sides of a gantry but I know its Been used on a 4 joint Z axis where all 4 corners are lifted..