Advanced Search

I feel that making this as an EtherCAT slave might open something of a licensing can of worms. But it already has Ethernet port for command input, and I would expect the STM32 to have the CPU horesepower to handle the protocol.

But note also that the previous STMBL works brilliantly with LinuxCNC and Mesa smart-serial with no additonal drivers or software needed. It's so simple it feels like you have missed something:

github.com/freakontrol/stmbl/blob/main/d...nuxcnc/stmbl.hal#L15

Well, it's likely to depend on the pinout of the BoB.

So the first thing to try would be to find which firmware suits the BoB, as the pin assignment of the 7i97 is fixed by the firmware.
(Whilst you could switch it by rewiring the cable between the BoB and the 7i97, doing that with ribbon cables is fiddly at best)

If you start linuxcnc from the command-line then as soon as the Mesa card loads it will print out the pinout (even if the startup of LinuxCNC subsequently fails)

Start with the config tool that gets closest, and then accept that you are probably going to have to do some hand-editing of the HAL file later.
(The initial concept of HAL was for it to be entirely hand-generated, you shouldn't be scared of it)

You can contact me via the github page if you like me to guide you on the ethercat thing.
You find a working Kicad schematics in the github files. Hardware interface is SPI (4 wires),
3 interrupt lines and perhaps one reset line. In software you need to respond on interrupts
every 1 ms (typically) by reading pdo data, do the things you need to do, and write pdo data
takes about 100 usecs or therearound. A cia402 implementation is a bit more with the state
machine, it's all in software though.

 

You say that you don't know Python, so do you know C? (Or classic ladder)

If you know C then you could look at making a custom realtime component (it's easy with halcompile)
linuxcnc.org/docs/devel/html/hal/comp.html
You could maybe start with the timedelay component and add your extra features.
github.com/LinuxCNC/linuxcnc/blob/master...nents/timedelay.comp

Otherwise, you can almost certainly assemble the behaviour you want from existing, standard HAL components. For example maybe a flipflop
linuxcnc.org/docs/stable/html/man/man9/flipflop.9.html
with a timerdelay to reset it, with some HAL logic elements to control the inputs.

For an x86 (Standard PC) system you can change your repository settings to point to the buildbot: buildbot2.highlab.com
But as you can tell if you look there, we don't have any arm64 machines building images there.

So, that just leaves building from source. Which is actually fairly straightforward. Also, if you build from source you can have both versions co-existing on the same machine, if you want.

linuxcnc.org/docs/devel/html/code/building-linuxcnc.html

If you want to have the very latest version then don't try the tarball route, go straight to using Git. That way each update is just a case of "git pull", followed by "make".

Compiling "run in place" as described there is quickest and most adaptable, but it does mean that you need to perform the incantation:
(Yes that really is dot space dot slash)
To start Linuxcnc. But you can make a desktop shortcut to do this.

If you build and install a .deb then it will look exactly like a standard installation, with the downside that every update will take about an hour to buid and install, rather than a few seconds.

You will need to install git, and a whole lot of dependencies. Don't be surprised by this.

meister wrote:

I would prefer the route described above,
it's easier to always be up to date via git.

The most complicated part of the installation is the toolchain, which has to be installed manually. Everything else is just copy paste

Agreed just a pull and there you go.  Thanks.

I can’t figure out how to set up a bob on the 7i97t.
It’s just a  simple pass through breakout.
Can I use the idc26/bob with normal 7i97t firmware?

I was trying to set it up using my existing hal file, but I don’t know what the idc pins are. Like the equivalent of hm2_7197.0.ssr.00.out-1 or hm2_7197.0.inmux.00.input-1.

Ive tried setting it up in mesact with both 7i97t_d.bin and 7i97t_5abobd.bin, but inputs/outputs 16+ are grayed out.

I also tried with pncconf. If I use the inputs/outputs in the io3 tab, then linuxcnc won’t launch saying they don’t exist. 


 

I would prefer the route described above,
it's easier to always be up to date via git.

The most complicated part of the installation is the toolchain, which has to be installed manually. Everything else is just copy paste

This is correct.

hallo servus und grias di!

Schöne grüße aus der AIRPOWER 2024 Region, es geht laut her und es gibt neu Entwicklungen.

Nachdem der MiniPc den Elektronischen Himmel Erreicht hat Musste ein neuer her,

MINIS Forum, Läuft und ich habe noch eine Neue Originalverpackte 7i76E bekommen.
Da ich nur die dinge im Hintergrund erledige und alles einstelle und besorge, ist hier meine frage

Braucht die 7i76E bei der Netzwerk Einstellung ein Gateway?

Ich habe dem PC nun 192.168.1.20 > 255.255.255.0 und als Gateway die Karten IP die Standard ja 192.168.1.121 sein soll

nicht dass ich dem Kollegen der in der Zwischenzeit die Mesa 50 km weit weg anschließt und mit Computern so gar nichts am Hut hat einen Rechner gebe der dann nicht verbindet

danke dir im voraus und schöne grüße aus der Steiermark

Have a look at the 'message' component:
linuxcnc.org/docs/stable/html/man/man9/message.9.html

Hello.
Please tell me how to implement the output of messages in the LCNC when a signal is sent to a certain pin HAL.
I need to output messages about device and signal malfunctions when the PIN is set to TRUE. For example, I send a signal to the PIN DIN0 and the message "fan on" is displayed, I send a signal to the PIN DIN1 and the message "Pump on" is displayed.
I would like to see these messages in the standard place for outputting LCNC error messages.
Thank you for your attention and help.

It might help www.govinfo.gov/content/pkg/GOVPUB-C13-7...a686274dfb3187ad.pdf this paper were writen by NIST(Same institute developed EMC) its use EMC(Linuxcnc's was once EMC)

Hi
Oliver has made some .deb packages, presumably, to setup the reqiured tool chains and packages. Any instructions on usage for us dummies and does the package take away some of the steps defined above?

that kind of system solves the surface area contact so you get the most out of a belt, but it does not look to be a reduction from what i could tell. The idea i have could be configured to work the same way though.

when you get into the servo side of things the encoders are a lot better than what you find on these cheap closed loop steppers and the reduction is less of a big deal as long as the motor can do it[s job.

for what i built i have far more potential speed than space to ramp up to my top end speed so a 3 to 1 reduction would land me in the 4,000 micro step range with a .0002 resolution. one other thing would be the extra torque on the X axis which is powered by a single motor. the tandem axis has a lot more grunt with 2 motors.