Advanced Search

When running from halcm or halrun isn't it required to create a thread and add the read & write function to the thread, and then issue a start command to get anything to happen ?

And the config file is not in the same place as a normal RPi.

It is in /boot/broadcom/config.txt - this was the case for the 2023 version. And is still the case for the 2024 version. This really needs to be mentioned in the downloads section or even easier spi enable in the image.

Never mind. I figured it out. Needed to manually configure my wired interface to 10.10.10.11/8 and set the jumper on the board for 10.10.10.10.

some error come on when i tried to configure board with pnpconfig after in tried to set the stepper motor movements.

Looks like the SPI device driver is not loaded. maybe someone with experience with
the LinuxCNC RPI image can help with enabling that driver.

The LinuxCNC driver does work however so you should not have any issues running LinuxCNC.

The kernel SPI driver is only needed by mesaflash so unless you need to change the standard
firmware. you should be able to proceed with setting up LinuxCNC.
 

Hi guys!!
have some problem with my rpspi4 and linuxcnc with 7c80. 
Linux pi 6.6.44-rt39 #1 SMP PREEMPT_RT Mon Aug 12 21:10:13 AEST 2024 aarch64 GNU/Linux. I spoke with a person from mesa, he told that spi is disable, i tried to enable on /boot/firmware/config.txt and change # uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on
  
This is the file I installed rpi-4-debian-bookworm-6.6.44-rt39-arm64-ext4-2024-08-12-2149.img.xz

halcmd setp hm2_7c80.0.led.CR02 TRUE
nothing happen in the board, no light come on 
or even the output light come on. 

used linuxcnc because I want to use vismach bc I want to configure a 5 axis machine but haven't find much information on it.sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
open: No such file or directory
No 7C80 board found

 halcmd loadrt hostmot2
Note: Using POSIX realtime
hm2: loading Mesa HostMot2 driver version 0.15
halcmd loadrt hm2_rpspi
hm2/hm2_7c80.0: Low Level init 0.15
hm2/hm2_7c80.0: Smart Serial Firmware Version 43
hm2/hm2_7c80.0: 54 I/O Pins used:
hm2/hm2_7c80.0:     IO Pin 000 (TB07-02/TB07-03): StepGen #0, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 001 (TB07-04/TB07-05): StepGen #0, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 002 (TB08-02/TB08-03): StepGen #1, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 003 (TB08-04/TB08-05): StepGen #1, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 004 (TB09-02/TB09-03): StepGen #2, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 005 (TB09-04/TB09-05): StepGen #2, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 006 (TB10-02/TB10-03): StepGen #3, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 007 (TB10-04/TB10-05): StepGen #3, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 008 (TB11-02/TB11-03): StepGen #4, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 009 (TB11-04/TB11-05): StepGen #4, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 010 (TB12-02/TB12-03): StepGen #5, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 011 (TB12-04/TB12-05): StepGen #5, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 012 (TB03-03/TB04-04): IOPort
hm2/hm2_7c80.0:     IO Pin 013 (TB03-05/TB04-06): IOPort
hm2/hm2_7c80.0:     IO Pin 014 (TB03-05/TB03-06): IOPort
hm2/hm2_7c80.0:     IO Pin 015 (TB04-01/TB04-02): Encoder #0, pin A (Input)
hm2/hm2_7c80.0:     IO Pin 016 (TB04-04/TB04-05): Encoder #0, pin B (Input)
hm2/hm2_7c80.0:     IO Pin 017 (TB04-07/TB04-08): Encoder #0, pin Index (Input)
hm2/hm2_7c80.0:     IO Pin 018 (TB05-02): PWMGen #0, pin Out0 (PWM or Up) (Output)
hm2/hm2_7c80.0:     IO Pin 019 (TB05-02): PWMGen #0, pin Not-Enable (Output)
hm2/hm2_7c80.0:     IO Pin 020 (TB05-05/TB05-06): IOPort
hm2/hm2_7c80.0:     IO Pin 021 (TB05-07/TB05-08): IOPort
hm2/hm2_7c80.0:     IO Pin 022 (Internal InMux0): InMux Input Mux #0, pin addr0 (Output)
hm2/hm2_7c80.0:     IO Pin 023 (Internal InMux1): InMux Input Mux #0, pin addr1 (Output)
hm2/hm2_7c80.0:     IO Pin 024 (Internal InMux2): InMux Input Mux #0, pin addr2 (Output)
hm2/hm2_7c80.0:     IO Pin 025 (Internal InMux3): InMux Input Mux #0, pin addr3 (Output)
hm2/hm2_7c80.0:     IO Pin 026 (Internal InMux4): InMux Input Mux #0, pin addr4 (Output)
hm2/hm2_7c80.0:     IO Pin 027 (Internal InMuxData): InMux Input Mux #0, pin muxdata (Input)
hm2/hm2_7c80.0:     IO Pin 028 (TB13-01/TB13-02): SSR #0, pin Out-00 (Output)
hm2/hm2_7c80.0:     IO Pin 029 (TB13-03/TB13-04): SSR #0, pin Out-01 (Output)
hm2/hm2_7c80.0:     IO Pin 030 (TB13-05/TB13-06): SSR #0, pin Out-02 (Output)
hm2/hm2_7c80.0:     IO Pin 031 (TB13-07/TB13-08): SSR #0, pin Out-03 (Output)
hm2/hm2_7c80.0:     IO Pin 032 (TB14-01/TB14-02): SSR #0, pin Out-04 (Output)
hm2/hm2_7c80.0:     IO Pin 033 (TB14-03/TB14-04): SSR #0, pin Out-05 (Output)
hm2/hm2_7c80.0:     IO Pin 034 (TB14-05/TB14-06): SSR #0, pin Out-06 (Output)
hm2/hm2_7c80.0:     IO Pin 035 (TB14-07/TB14-08): SSR #0, pin Out-07 (Output)
hm2/hm2_7c80.0:     IO Pin 036 (Internal SSR): SSR #0, pin AC Ref (internal) (Output)
hm2/hm2_7c80.0:     IO Pin 037 (P1-01/DB25-01): PWMGen #1, pin Out0 (PWM or Up) (Output)
hm2/hm2_7c80.0:     IO Pin 038 (P1-02/DB25-14): IOPort
hm2/hm2_7c80.0:     IO Pin 039 (P1-03/DB25-02): StepGen #6, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 040 (P1-04/DB25-15): IOPort
hm2/hm2_7c80.0:     IO Pin 041 (P1-05/DB25-03): StepGen #6, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 042 (P1-06/DB25-16): IOPort
hm2/hm2_7c80.0:     IO Pin 043 (P1-07/DB25-04): StepGen #7, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 044 (P1-08/DB25-17): IOPort
hm2/hm2_7c80.0:     IO Pin 045 (P1-09/DB25-05): StepGen #7, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 046 (P1-11/DB25-06): StepGen #8, pin Step (Output)
hm2/hm2_7c80.0:     IO Pin 047 (P1-13/DB25-07): StepGen #8, pin Direction (Output)
hm2/hm2_7c80.0:     IO Pin 048 (P1-15/DB25-08): IOPort
hm2/hm2_7c80.0:     IO Pin 049 (P1-17/DB25-09): IOPort
hm2/hm2_7c80.0:     IO Pin 050 (P1-19/DB25-10): IOPort
hm2/hm2_7c80.0:     IO Pin 051 (P1-21/DB25-11): Encoder #1, pin A (Input)
hm2/hm2_7c80.0:     IO Pin 052 (P1-23/DB25-12): Encoder #1, pin B (Input)
hm2/hm2_7c80.0:     IO Pin 053 (P1-25/DB25-13): Encoder #1, pin Index (Input)
hm2/hm2_7c80.0: registered

 

thanks, so much guys for taking the time.
remember, im a rookie on this topic. 

Hello,
Thx for the great work to all contributers. I read this huge threat and hopefully i did not miss my problem. i flashed an old nvem V2 with ethernet with Version 1.0.0
And it worked like a charme. Ping Test fine and even linuxcnc on first try thanks to the videos...
Now my problem... I just have the basic config with 3 Axis as default. The config upload fails...it prints out all Infos, but the upload fails with timeout. I try to solve IT but didn't find the problem. Maybe i can't write on the nvem.
I read it between threats but didn' t find an answer. With full config i do not need to change the config? How do i flash with full config?

Thanks for your Help
Btw. I tried the rt version... Flashing works but i can't ping it. If i get it right, my nvem is too old?
Regards

Looks good

forum.linuxcnc.org/18-computer/44828-rem...board?start=0#231852

I finally finished designing my modular design idea: github.com/festlv/rioctrl-hw

Still have to actually build & test it- I'm fairly sure that there will be f-ups, just hope that nothing too major

I've been using machine's at work with WinCNC and it's DOS based predecessor for more than 20 years, and Linuxcnc for a bit over half that time. Personally I would not choose it over Linuxcnc for a new machine build. It works ok, but its configurability is far more limited than Linuxcnc. I also don't fully trust the motion planner in WinCNC. I'm not sure that it really does proper acceleration or deceleration profiles, and it certainly doesn't do jerk limited motion. (If a machine set up with WinCNC is actually doing jerk limiting, it is being done in the servo drive, in spite of what ever WinCNC is commanding them, not because of it.)

Linuxcnc's dialect of G-code seems to be more "normal" and the canned cycles are more Fanuc like than WinCNC's g-code dialect. Also writing macros and subprograms seems easier in Linuxcnc. One think that is easier in Wincnc is setting up repeat arrays, but it uses a propriatary G-code that is unique to Wincnc.(L10).

Also if you ever have trouble with your Wincnc system, and need support, you will likely be stuck with having to pay $3000-5000 to upgrade to the latest supported version. (Has happened to us a couple of times.)

We've had 7 different routers that started out with their software. Only one is still running Wincnc. (The rest are now running Linuxcnc, were sold, or both.)

hello gentelmen,

there is single master EL6751 + single canopen slave .. in my case is the Sew EuroDrive lteb+ which has canopen port directly on board... I did el6751 master component and sew lteb+ component...

there is speed limitation of 4ms scan cycle but it is periodical ... it is defenetly no RT but for spindles with only speed control should be used...

enjoy 

You need to setup a static address on the Ethernet interface
(suggest 10.10.10.100/24 for 7I95T at 10.10.10.10)
 

Okay, got me a USB Wifi dongle. Now I have a regular cat 5 ethernet cable directly connected from PC to Mesa. It's not a cross-over cable; not sure if I need to use a cross-over cable or not (the PC is kinda old).

My ip addr command shows...

cnc@FurniturePro:~/Downloads$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d4:85:64:c0:ab:b1 brd ff:ff:ff:ff:ff:ff
3: wlx0014d1ea4e8e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:14:d1:ea:4e:8e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.127/24 brd 192.168.1.255 scope global dynamic noprefixroute wlx0014d1ea4e8e
       valid_lft 86269sec preferred_lft 86269sec
    inet6 2600:6c50:6700:a52:eab5:d186:da89:5f58/64 scope global dynamic noprefixroute
       valid_lft 542825sec preferred_lft 542825sec
    inet6 fe80::bfb3:191d:7c0d:d6ef/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Now MesaCT cannot find the board.  What am I missing?

Yes you can use it set to speed mode.

I certainly don't have (or even could have) any objections to you making a compatible
daughtercard (or even main card since the hostmot2 firmware is all open source)

My only suggestion would be make sure that your daughtercard is general enough
that it works with other similar interfaces (Parallel, RIO, etc)

The Teknic drives need to be sent a 5-24v enable signal so you will need to dedicate one of your 7i96s's outputs to that. I'd suggest using only one output to enable all of the drives. If you are using Output 0 on the 7i96s for that it would be TB3 pins 13,14. and a 5-24v power source. Connect the +v from the power source to TB3pin14, then TB3pin 13 would go to the +Enable input on the drive (pin4), and the -v from the power source would connect to the drive's -Enable (pin8). Then connect all of the other drives to the same.

The next question is do you want to use the HLFB output on the Teknic drive for anything? The only useful option I can think of for it with Linuxcnc would be to use it for an amp fault signal. Assuming that it can be configured as this, then you'd want to connect it to one an input pins. This could be connected multiple ways. one possibility would be to connect a 5-24v power source to the drive's pin-1 (+HLFB), the drive's -HLFB to the 7i96S's input pin (TB3 pin1 for example) and the -v from the power source to the 7i96S input common TB3 pin 12. (I would probably choose to use a separate input for each servo drive, so that you may know which one is faulted.(

So for example to set up your X axis to use stepgen 0.
teknic pin 1 --> v+
teknic pin 2 --> mesa TB1 pin 3
teknic pin 3 --> mesa TB1 pin 5
teknic pin 4 --> mesa TB3 pin 13
teknic pin 5 --> mesa TB3 pin 1
teknic pin 6 --> mesa TB1 pin 2
teknic pin 7 --> mesa TB1 pin 4
teknic pin 8 --> -v