Advanced Search

Still for sale.

Hi,
only one 7c81, you tip has done the trick. Thank you!
but the next problem occured
The error changed to:
/intos.hal:88: parameter or pin 'hm2_7c81.0.7i77.0.1.analogout0-scalemax' not found

so checked this line in the old, working hal, without the 7i78, and its exactly the same. What does change here when i use 2 daughterboards?
Any Ideas?

EDIT:
i have also tried to change the channel number to 0:
hm2_7c81.0.7i77.0.0.analogout0-scalemax'
and 2 and 3

How many 7c81 are in use?
for one only, delete the line containing 1
addf hm2_7c81.0.read
addf hm2_7c81.1.read
Pretty sure this should only be used if you have 2 of 7c81, 0 and 1 there are enumeration for 2 of 7c81 not the add on cards, they do have their own enumeration after the model number, example:
hm2_7c81.0.7i77.0.0.input-07
First 7c81 that has the first 7i77 attached, first is always 0 with Mesa and LinuxCNC enumeration.
Had a look at your hal, there is more editing required, so it might be easier to make a new config with a single 7c81.

Hi,
thanks for your fast reply.
if you read in the hal, there is written :
addf hm2_7c81.0.read
addf hm2_7c81.1.read
for both cards
.0 is the 7i77 and .1 is the 7i78
I interpreted the documentation that it should be done like this.
Any advice how it is configured correctly?

HAL: ERROR: function 'hm2_7c81.1.read' not found
./intos.hal:16: addf failed


should be
hm2_7c81.0.read

Raspberry Pi 4 Model B Rev 1.2
Mesa 7c81
Debian GNU/Linux 12 (bookworm) 6.1.54-rt15 #1_RT Fri Nov 17 17:02:27 AEST 2023 aarch64

I installed LinuxCNC 2.9.3 from the linuxcnc ISO image a couple of years ago, and upgraded to 2.9.4 yesterday by:
$ sudo apt update  && sudo apt full-upgrade

I now have:
rick@raspi4:~$ dpkg -l | grep linux-image
ii  linux-image-bcm2711-rpi-4            6.1.54-rt15-1                           arm64        Linux kernel, version 6.1.54-rt15
rick@raspi4:~$ dpkg -l | grep linuxcnc
ii  linuxcnc-doc-en                      1:2.9.4                                 all          motion controller for CNC machines and robots (English documentation)
ii  linuxcnc-uspace                      1:2.9.4                                 arm64        motion controller for CNC machines and robots
ii  linuxcnc-uspace-dev                  1:2.9.4                                 arm64        PC based motion controller for real-time Linux

rick@raspi4:~$ uname -a
Linux raspi4 6.1.54-rt15 #1 SMP PREEMPT_RT Fri Nov 17 17:02:27 AEST 2023 aarch64 GNU/Linux

Is there a newer RT kernel then the one from 2023 ?
If so, how can I upgrade the kernel without having to reload the entire system from the latest ISO image ?

TIA,
Rick
 

I thought EINT might be the issue, there's a 1k pullup to 3.3v, the top 8 data lines have a 1k pull down.

Might be C5 around the L1 inductor, I installed a 100nf cap instead of a 4.7uf.

I don't know if that will make a lot of difference.

I've run a config, no hardware connected to the board yet, but no errors. Tho I assume writing to the flash is more of a load. It's bound to be something stupid on my behalf.

The major difference is the WP on the flash is just held high, any chance that the circuit around the WP on the flash is causing the issue, there's no reset device connected. Tho the EPP & SPI based on the 7c81 have been the same.

Just gone 3pm here in Sydney.

No something interesting.

I worked on a little project using an FPGA dev board to run MESA's hostmot2 firmware. First attempt was based on the 7c81 using either SPI (raspberry pi) or EPP (best on motherboard based parallel ports). The issue with the board I used is that the EEPROM need to be changed and the headers were already soldered on.
That same hardware can also be used with the LinuxcncRIO project.

Another project I had a go at was modding the 7i90 Smart serial firmware to support 4 encoders to run on a dev board.

For my latest I've grabbed a different dev board (eeprom is correct size & bought with the headers unslodered, but this time I'll be trying a Ethernet interface, chip is same as use on the Mesa products, so no having to rewrite a driver, which requires a couple of steps, first being working out the instructions of the softcore, working how the driver talks to the chip and then how it integrates with the rest.

Some pics, 2x17 ports from breakout boards (mesa 25 pin daughter boards can be used as well) and 4 extra pins for 2 smart serial ports or extra I\O.

First off is the FPGA from aliexpress:
 

The Ethernet board, this is experiment only, the FPGA board sits on top, disregard the type of 2x25 headers they can be changed to suit. Should have the boards in a couple of weeks.
 

One of the daughter boards from the orignal project.
 

 

 

Thanks for the info!
I've ordered a 7i78 now.
Is there anywhere a bitfile for the 7c81 with 7i77+7i78 available?

There's so many different configs available, and you can even build your own firmware from source. So the manual is pretty generic.

Off track
I haven't use the 7i96, I have a 7i92/7i76 for the mill, with a couple of extra boards, I've hacked to together some FPGA dev boards to use self built 7c81/7i90 firmware. SPI & EPP is easy pcb wise, but I'm having a go at a board using ethernet based on the 7i92 schematics.
On Track

The mesa hardware & firmware is really versatile. Actually the 7i90 would be a great way to learn to program FPGAs as the I\O is 5v tolerant, most dev boards are only good for 3.3v or the smoke comes out.

Assuming you use the 7c81's FGPA for stepgen and don't sofware step, you don't need a base thread so latency requirements is much relaxed. I'd be happy with anything under 130,000 with 200,000 at a pinch

Hi guys!I am on a new Project and found a mesa 7c81 an 7i92 on the flewmarket... dont know why someone sell it on a flewmarket...i start reading about the 7c81 and look to my boxes and found a raspberry pi 4 b version with 8gb ram.. oki load the image for the sd card from the linuxcnc website and bring it up.i isolate cpu 1 2 3 but latency doesnt go down.

Any tips?
in the config i disable audio blueetooth and overclock to 6v and 2000mhz..

which information i can share to get the cow frome the ice?

thanks all


 

 

 

Just my take on it. There are many ways to run linuxcnc, keep that in mind.

My questions:
* What should I run LinuxCNC on?  I've got a spare RPi 4 sitting in my drawer.  I've got a couple of Supermicro Intel Atom-based ITX server motherboards lying around.  What's the most intelligent way to go?

Atom is probably below the acceptable performance limit, but anything faster than that. There are some new mini-ITX main-boards with N100 integrated. CPU performance is more for the user experience, the later HMIs (or guis) may need a bit faster CPU, while the old Axis works with anything. For the cnc part it is about real-time jitter and there usually are ways to tweak settings to come to low jitter. I go with N100 nowadays, but its just one of many possibilities. Once you have seen the newer guis you will want to use one of those. And need at least some CPU performance. I ran on RPi4, I would think a step up to RPi5 would be nice.

* It seems that a parallel port interface is the "old-school" way of doing things.  Now, it seems that most prefer an Ethernet interface.  Is there a disadvantage of going one way or another?

Stepper performance (steps/seconds), number of IOs, and other types of IO than digital IO is what makes people move away from the parallel port. Plus that main-boards nowadays seldom have a parallel port and need to have one added.

* Since I have to replace the steppers anyway, is it foolish to go with a "traditional" setup rather than Ethercat?  It seems like Ethercat will be considerably more expensive (like twice the price or more) - but is it worth the price?

You won't get anything extra from the milling machine using EtherCAT. It is a different way of doing the same thing.

* Everyone seems to agree that Mesa boards are the "gold standard."  How do Pico Systems' boards compare?  Jon Elson lives like 20 miles from my house.  Does anyone have experience with his customer service?  Is it foolish to consider anything other than a Mesa?

From what I can see, and I may be wrong, the Pico Systems' board connect to the parallel port? If you go with a parallel port solution that can work. Mesa's board on the other hand typically use EtherNet, SPI, PCIE, or PCI (and maybe more) to connect to the computer. This gives speed and reliability.

* If I go with a Mesa setup, which direction should I go?  If I use the RPi, I could go with the 7C80 or 7C81 - I could also run an Ethernet setup.  If I use the server motherboard, I could go with a parallel port setup or an Ethernet setup.  Is there an advantage of going one way or another, here?

I've only used Ethernet setup and see few reasons to do anything else. If you are only ever to use Raspberry one can think of the 7C line. I would like to keep all options open as far as possible.

* If I go with a given Mesa board, what else will I need to buy?  It seems that some of the Mesa cards (like the 7C80 and the 7I95T) will hook directly to the stepper drives, while others require a separate daughter card (BoB)?

Send Mesa a mail with those questions, they are usually very happy to help. For a normal stepper motor system I would look at 7i96, which connects to the stepper driver with the step/dir/enable signals.

* What hardware (if any) would I need in order to use the encoders on the steppers as a DRO?  Will any of my hardware selection above affect my ability to have this feature?

For Mesa to answer, I think you are looking at a 7i85. From what I understand, encoder counting is done by the FPGA, so the card must either do it itself on the FPGA board, or have a connector that allows a daughter board to connect the encoder inputs. The 7i96+7i85 does that.

* Will a cheap Amazon/Aliexpress stepper motor/drive/power supply set work, or will I need to buy the stepper drives separately?  If I need a particular stepper drive, should I go with a Gecko or something else?

Yes, will work fine, just size it to suit the stepper motors. I have good experience with such stepper drives.

* If I run a touchscreen and a pendant, is there any reason why I will need a keyboard hooked up to this machine (once it is configured)?

Depends on the gui and how well touch screen input is integrated. For example, I run the qtdragon gui and there the keyboard input is well integrated. Except when I need to edit the G-code file, then I bring in the keyboard. Normally I have it tucked away though.

Hi everyone,
I'm hoping that someone can help me get my head wrapped around this, and point me in the right direction.  I've spent over a dozen hours reading through threads on this forum and elsewhere - yet, I can't figure out how to proceed.

My machine is a Bridgeport Series I CNC (Boss 6) mill - and it's sitting in my shop in original condition.  I'm new to CNC (having only dabbled with my Ender 3 3D printer).  However, a close friend of mine who's helping me has a couple of HAAS mills and is a guru with Autodesk Fusion.

I've investigated numerous options for updating this machine.  The more I study this, the more confused I've become!  The simplest answer for a person like me seems to be to install an Acorn board.  I'd rather not.  I don't want to get vendor-locked (more than I have to).  The thought of a company going under and leaving me in the position of having to gut the machine and start over is not appealing.  I don't want to pay a subscription.  I like the openness and configurability of LinuxCNC, and I'm a big fan and daily user of Linux (Red Hat Academy instructor).

My goals:
* Get the old Bridgeport back to making chips again.
* Have the ability to both use this machine as a CNC, and as a glorified manual machine (using LinuxCNC as a DRO).
* Not spend thousands of Dollars on this project (if possible!).

My thoughts:
* Mount a 12" touchsceen monitor in the original control panel housing for interacting with LinuxCNC.
* Hang a pendant on the side of the original control panel housing.
* Pick up a Huanyang VFD for the spindle drive (these seem to be well-supported and well regarded?).
* Replace the ancient original Bridgeport steppers with modern closed-loop NEMA 34's (1100-1200 oz in).

My questions:
* What should I run LinuxCNC on?  I've got a spare RPi 4 sitting in my drawer.  I've got a couple of Supermicro Intel Atom-based ITX server motherboards lying around.  What's the most intelligent way to go?
* It seems that a parallel port interface is the "old-school" way of doing things.  Now, it seems that most prefer an Ethernet interface.  Is there a disadvantage of going one way or another?
* Since I have to replace the steppers anyway, is it foolish to go with a "traditional" setup rather than Ethercat?  It seems like Ethercat will be considerably more expensive (like twice the price or more) - but is it worth the price?
* Everyone seems to agree that Mesa boards are the "gold standard."  How do Pico Systems' boards compare?  Jon Elson lives like 20 miles from my house.  Does anyone have experience with his customer service?  Is it foolish to consider anything other than a Mesa?
* If I go with a Mesa setup, which direction should I go?  If I use the RPi, I could go with the 7C80 or 7C81 - I could also run an Ethernet setup.  If I use the server motherboard, I could go with a parallel port setup or an Ethernet setup.  Is there an advantage of going one way or another, here?
* If I go with a given Mesa board, what else will I need to buy?  It seems that some of the Mesa cards (like the 7C80 and the 7I95T) will hook directly to the stepper drives, while others require a separate daughter card (BoB)?
* What hardware (if any) would I need in order to use the encoders on the steppers as a DRO?  Will any of my hardware selection above affect my ability to have this feature?
* Will a cheap Amazon/Aliexpress stepper motor/drive/power supply set work, or will I need to buy the stepper drives separately?  If I need a particular stepper drive, should I go with a Gecko or something else?
* If I run a touchscreen and a pendant, is there any reason why I will need a keyboard hooked up to this machine (once it is configured)?

Sorry for all of the (possibly stupid) questions.  The DIY CNC and especially the LinuxCNC ecosystem is far more vast than I imagined.  I really did attempt to "do my homework" before asking.  There just seems to be a lot of somewhat conflicting information (possibly, due to changing technologies and best practices over the years?).

Thanks for any advice that you can provide to me!