Advanced Search

Billy wrote:

Is the rPi GPIO interface considered fully baked, or is the Mesa 7i96S the smart bet? I would totally love to avoid the $150+ for the Mesa, but only if that does not then cost me an additional $300 in labor time.

 

It depends on what you need. I don't think that the GPIO interface on the Pi is quite as good as a parallel port, and the parallel port is only supported out of habit and as a way to get new users started cheaply. 

You will get more speed out of steppers with a Mesa card, and this is not solely down to step rate. It comes down to the resolution of the increments in step rate as the system accelerates.  If the Pi can do 20kHz flat-out then the slower rates are quantised at 10Khz, 6,66kHz, 5kHz... The motor can't physically follow such large speed steps. The Mesa card can do 20kHz, but also 19.99999 kHz too. And 20.00001

But, you could start with the GPIO and see if it's acceptable for the application. 
 

tommylight wrote:

In short:
RPI can do at most 20000 steps per second, if lucky and with a bit of fiddling (this is from what i read here, i stopped using RPI since version 3B)

The 3B wasn't very useful for LinuxCNC. The Pi4 worked a lot better (and can be used with Ethernet Mesa hardware). The Pi5 is better again. 

The reason I suggested the Pi5 in this context is that if anything goes wrong with the Pi you can just slot in an identical Pi with the _same_ SD card and be back to exactly where you were. 
If using PCs it can be difficult to find an exact replacement. Yes a _similar_ PC might work, and might run properly with the old SSD. But it might not. 

I fixed the missing 7i76eu from the stepper boards variable which caused a partial build of the main.hal file and leaving out the enable and the stepper setp lines.

JT

andypugh wrote:

What's the GUI? It looks specialised.

@Andy

Franco's been teasing us with a Siemens-like panel and GUI for a couple years.  I believe his company does retrofits:

teknix-com-ar.translate.goog/en/control-...en-US&_x_tr_pto=wapp

...and he appears to have done some major-re-writes to LCNC (both code and GUI)
forum.linuxcnc.org/show-your-stuff/48621...e-interpreter#267742
forum.linuxcnc.org/show-your-stuff/52484...control-panel#299250


Looks like he's to the point where his company has user-manuals available:
manual-teknix-cnc.readthedocs.io/es/main...achineInterface.html

But, sadly, he hasn't shared anything more than 'teasers.'

Can you attach your ini file?

Did you skip Drive 0 and Drive 1?

JT

Here is a video i did some 5 years ago, i tested the included rack toolchanger on a machine and it just worked after editing out the sim stuff:

You can try the same thing, namely, make the sim work on another config for parallel port (no need for a machine) and after getting this to work add the required entries from it to your machine config while also editing the tool positions.

Flex GUI is built using the python interface

gnipsel.com/linuxcnc/flexgui/index.html

JT

Thanks for your reply.
Please find attached my back up config.

Also I do not want G53 in my code when I load any .ngc file. Please help as I do not wish to install limit switches to my system. I want to use G31 instead before the cut starts with THC.

Gerne, aber ich bin noch nicht sicher ober der Parameter "7i76 Modus 2 I/O card" so richtig gesetzt ist oder ob ich Linux doch noch auf "UTF-8 EN_US" umstellen muss.
Nachtrag: Zumindest funktionieren jetzt die Endschalter (kann den Status in LinuxCNC richtig sehen, die Schalter ändern sich auch

It sounds a reasonable price assuming they actually keep supporting and updating it. The lifetime license only lasts as long as the site stays up. It will be interesting to see how this develops.

Hallo Raspll,
danke für deinen Post! Jetzt wird mir einiges klarer.
Ich arbeite mich gerade durch das Handbuch um HAL und INI händisch anzupassen.
Genau aus dem von dir beschriebenen Grund.
 

Hello,

My current configuration consists of a 7i96s and a 7i85. A 7i84 is connected to the 7i96s via Smart Serial.
By default, I can flash the original bit file "PIN_7I96S_7I85D_51".

Now I would like to add a PktUART pin for Modbus. Is it possible to connect Modbus to the 7i85, or is that only possible directly with the 7i96s?
My suggestion is attached, but unfortunately, I'm not sure if it's correct.

I've added the following to the first block:
If I link the pins to the 7i85, does that mean I'll use two Smart Serial pins?

The four driver slaves all have the same names within the XML file.

<slave idx="0" type="generic" vid="00400000" pid="00000715" configPdos="true" name="A6">

You need to change the 'name="A6"' parts to something like:

name="A6X" 
name="A6Y1"
name="A6Y2"
name="A6Z"

You also need to change the pins inside the halfile accordingly:

lcec.0.A6X.control-word
lcec.0.A6Y1.control-word
lcec.0.A6Y2.control-word
lcec.0.A6Z.control-word

yes that is y-191, I got to the point where it wants to take the tool, but it won't put it back in the pocket when I choose a new one, down in the header it also says ``no tool''

2 Y191
Pretty sure that is wrong....