Advanced Search

There is a new image coming that has some additional fixes.

For issues in the future please post on GitHub as I'm winding back forum use.
github.com/ozzyrob/linuxcnc-rpi-2.9.7-image-issues

I explain a little better.
It's been a hard slog making these images, and like the previous issue I want to keep all the fixes, issues, tips in one place.
So rather then the forum where it's going to be many different threads I'm want a single point of support.
I did try with the previous, one big thread, and an index to that thread but I still kept having to refer people to the index for the same questions.

The making of these images involved learning the RPi guys build them, working out what can and can't be taken out, some stuff is burried in meta packages, so for instance like piwiz it's burried in a meta package, so it is a little trial and error.
I'll take the blame, as when writing the image I was only setting everything via RPi Imager, which people had tried on the 2.9.3 images. So I thought well let's do that, and have it mentioned in the download section, and in the announcement thread. So that kind of didn't work.
It would have been easier if someone offered to help test in the early days but no one put their hand up. Whilst I knew how to get the image going as recommended, I wasn't aware of what happens when you don't follow the recommended way.
In saying that I have realised a few things. The main being to take a little longer to push them out, and to be clearer when explaining.
So guys if you can work with me on this, especially with reporting issues via GitHub, as I get emails when issues are raised, that would be great.
Thanks
Rob

When y'all say the first boot wizard, do you mean `raspi-config` or `piwiz`? Neither of them are starting for me on first boot with a card imaged with the latest Debian Trixie image I downloaded earlier today. I can't imagine I'm supposed to run a machine while logged into user `rpi-first-boot-wizard`, so something is supposed to change. 

I can `useradd` with the best of them, and I even know how to add a `udev` rules file that opens up the permissions on the GPIO. What I don't know is how the image is designed to be used out of the box.

EDIT: Forgot to mention that `piwiz`isn't found when I try to run it from terminal. `raspi-config` is there and usable, though, so I can get the thing on WiFi to update packages.

Perhaps I was a bit too harsh.

My foot hurts (I dropped a light drill battery charger on it and it really hurts now for no clear reason), maybe that made me cranky and mean.

hi  fdarling ,
Could you share the driver or your modifications to lcec to make a Yaskawa Sigma7 EtherCAT drive to work?
I could get the c file in your tar to compile and I could get the actual position display from a Yaskawa Sigma7 drive on the screen.
The question I have it how to integrate the two domain requirement into the lcec_main.c component.
Hope you can guide me on this.
Thanks,
-automata

Why would the board be rendered unusable?

Just buy replacement 74HCT00 series chips to replace the old TTL chips (or you can buy ttl ones for an exact replacement, but HCT chips are guaranteed to have exactly the same specs, just with a lower power consumption).

Why would you disassemble the board in the first place?

A picture would be helpful.

Please tell us your end goal.

If the processor board still works, use it to help you reverse engineer the I/O pinout of the main board.

You don't need to take something apart to know how it works, though it certainly can be helpful.

Figure out how to power the main board and power it, possibly through a low Ω resistor just to make sure nothing will get fried.

With the board powered, apply 5VDC (regulated) through a resistor to various input pins to see what they do.

You can also check the state of output pins by connecting them to an led through a resistor (make sure not to draw too much current, just in case).

Don't desolder the components from the board, it's essentially pointless.

I don't take that negative a view of clone cards, if they get more LinuxCNC users,
that's basically a good thing. They really should supply source however, but there is no legal
requirement that they do, it just seems it would make the card more useful, and its practically
a necessity with card having expansion connectors and thus the common need to make custom
configurations.

Note that you should be able to safely test different firmware by writing it to the fallback location
then loading the FPGA from this location, then if the card doesn't work, a power cycle will fix it:

mesaflash --device cardname --addr 10.10.10.10 --write somebitfile.bit --fallback
mesaflash --device cardname --addr 10.10.10.10 --reload  --fallback


Note that this only works on Xilinx based cards ( I think all clone cards are Xilinx based )
DO NOT try this on Mesa Efinix based cards.
 

I have a similar machine but also has Z1-Z2 for backgauges.
Something new about some gui that fits to these types of machines ?

unknown wrote:

They should provide the firmware source files as well. Especially the ucf file if it's required you need to modify the firmware. Or otherwise you'll need to perform a boundary scan to work out what FPGA pin does what. One can not be sure if they have followed the same same pin assignments as the Meas schematics. These could change for simpler PCB routing.

If the firmware ever gets corrupted for some reason, you want to be able to reflash it.

It probably won't get corrupted, but you really should have the firmware just in case.




I fixed an old TORCAM CNC at my school.

I had to purchase new drivers because the old ones were basically just complicated space heaters by the time I got to them (they were from 1993!).

They worked fine about 5 or so years prior, but when I tested them all they did was couse the motor to make high-pitched noises.

I'm 99% sure the issue was corrupt firmware.

I could have reflashed them (I would have needed an eprom programmer or something, it probably would have ended up costing more than the replacement drivers), but the firmware, as far as I know, was never released!

Copying someone else's device and selling it as though you are the creator and it is genuine (which in this scenario are mutually exclusive, but whatever) is pretty uncool (and probably illeagal).

If buying a legit MESA card was hard for some reason, I think you might be able to justify buying a counterfeit knockoff.

However, if you can easily buy a legit one, it seems a bit unethical to break patent law, steal intellectual property, and get support from MESA even though they won't make a dime off the purchase.

Found my AND8 hal component again! Will post it here for reference.

I think I should update my axis control logic to fault after a timeout of n.nn seconds of greater than n.nn minimum servo amplifier power and less than n.nn minimum joint velocity.

I ran into a situation where the encoder reading was incorrect, joint 6 was cranked against + hard stop, and the motor was holding stalled at max power.

This sounds like a bad way to fry a DC Servo, and we no longer have a spare. This axis has limit switches wired to the servo amp but not to LinuxCNC; I'm surprised the servo amp did not disable. I would spend more time diagnosing that; however, Cybelec couldn't provide manuals to me for these amplifiers because I am outside of their service region. Also, this is the ONLY axis on this machine with limit switches and the reason why I chose to move this one first. Plus, I think I will need to look into hard stop homing for Z1 and Z2, those have no homing or limit switches; only encoder feedback.

I see I need to fix my brake logic: I've been noticing glitches in joint motion and have discovered that when I am moving the joint slowly for longer than my servo-to-brake delay, it will lock the brake momentarily then release it again. I will just need to have it monitor several values besides j6-pwm-cmd. I'm thinking velocity feedback and distance-to-go. This will be directly related to the timeout logic above.

Once I get it right I want to rewrite it in a custom hal component which I plan to reuse on additional joints. The other joints with no brake probably need a parameter to switch off the unlock feature so it does not use the servo enable delays and cut servo amp output during no motion.

The R axis motor gets hot if it has to hold the axis against gravity for extended periods.

Hello.
All the links are broken.
So sad because I'm trying to run ethercat in my CNC and I'm having serious troubles to start them. Sometimes I have no idea if I'm making wrong things or there are problems with the repositories

Regards

Ich hab das alles noch nicht so ganz verstanden das bedeutet also dass die mesa karten dann mit smart serial miteinander verbunden werden oder wie ? Bzw wofür sind dann diese 25 poligen sub d stecker an den mesa karten da smart serial doch nur 8 pins braucht als stecker ? Und weche alternative gibt es zu der 7i77 da diese schon seid drei monaten ausverkauft ist bei den bekannten importeueren ? 

Hi,
Thanks.
Here is my current status again:
I am currently using cia402.comp and cia402homecomp.comp from @MobiusToast. 
What works: 
Switching on drives, moving and feedback.
All pins in the hal have been checked and are working
What doesn't work: Homing. Homing is started and drives start moving. 
Home-dog switch and hardware limit switch are ignored.

I have now gone through the whole thread again.
As I see it, and hopefully I have understood correctly, the drives are put into homing mode (0x6060 = 6).
The servos perform the homing independently. 
The homing status can be read via 0x6041 bit 15.
The evaluation is performed by cia402homecomp.comp and reports Linuxcnc homing completed.
Is that correct?

What do I need to do?
I need to connect the home-dog switch to the touch probe 1 (DI5), then it should work.
So first I need to order a cable for CN1. Stepperonline did not supply that.

regards 

Andre

thank you, I managed to make a path for the first 3 tools that read ini by delta y, but the problem remained with the 4-5-6 because the raster between the tools is not the same as 1-2-3 because the motor and the ballscrew go in the middle of the machine, which was bothering them, so the other 3 tools are spaced out, I have to figure out how to do it via delta y or how to write for each tool separately... I hope I can solve it somehow.