Advanced Search

Thanks for sharing. I did investigate reading the device tree when working on the RP1 driver but took the easy path so as to focus on the DesignWare SPI side of things. Looks like I'll need to rework the board detection. At least the Mesa code will be a great starting point.

I have a small AC rotary but it does not have a nutating joint just a plain old 90° setup.

Hi All,
I plan to upgrade my MH400 e with Linuxcnc. I bought a 6i25 + 7i77 and now I´m starting to configure the Cards In/ -outputs for my Mill. I have a fresh install of Linuxcnc (2.9.4) and run into the problem that whenever I try to configure the PWM Signals of the 7i77 the tap just isn´t there. I had a bit of success when i tried the PnCConf Wizard on the Live distribution, but there I couldn´t configure the encoders on the 7i77. I tried older Versions of Linuxcnc but that also didn´t help. I hope someone can point out my mistake, that I am obviously making because it seems to be working for so many others . 

Thanks for your help,
Simon

Is the 7I77 jumpered for differential inputs?

It may be a noise issue. One way to check if it's a common mode noise issue
(noise that exceeds the common mode range of the RS-422 receivers)
is to enable encoder error reporting:

setp hm2_5i25.0.encoder.00.quad-error-enable true

Once this has been done, inputs that violate the quadrature sequence
(often noise will do this) will set the quadrature error flag:

hm2_5i25.0.encoder.00.quad-error



 

aikiaviator wrote:

What is the process to move the X, Y and Z axis back to mid point, when the machine says cant because limits activated?
 

I think you have this a bit wrong. Home switches need to remain triggered until the end of travel. That way, Linuxcnc know which way for initial homing movement. Take the case  of the X axis, Say the home switch is 40mm from end of travel on the left and it stays triggered to the end of travel. If the home switch is triggered when homing starts, Linuxcnc knows it must travel to the right to find the home switch edge. HOME_OFFSET sets the final position. If this is a shared home/limit switch you need to move to the right so the switch is no longer triggered otherwise it will trigger a limit switch error once homing finishes.

If you have seperate home and limit switches, the final position can be in that 40mm where the home switch is held triggered.

do you have a machine that uses this?

Glad there is some interest in this. I made a bit more progress last night and have now hooked up a hal file, but have not done any more.
We should not hijack this thread but I will raise another thread when I get a it further. 

 

please, could you also put the 'dogleg' dependency on the repo?

You are right, it wouldn't be a problem for configuration only. But I'm using the module to use the TMC5160 without step/dir signals, so I need a fast communication.

I received my RPi5 this week-end and had to change some parts of my code to make it work. Also, with the RPi4, I could control the CS pin "outside" the SPI routine, and use how many pins I wanted to. With the RPi5, this does not appear to be possible. So I will need to make some more changes in the code. I will probably keep the freedom of CS pin choice for RPi4 and use the dedicated CS pins per channel on RPi5.

Hi,

Not sure if this is the correct place to post, as I'm actually not a Remora user but someone trying to use the source code for a LCNC to TMC5160 communication module.

I downloaded the latest official RPi 5 image and could not get a SPI communication with my TMC5160 drivers. I had to force the "rp1" variable to "true" in the code and then found out that my device-tree doesn't have the "soc" folder the script was looking for, but a "soc@107c000000". It seems like there are 2 different dtb files available, the bcm2712d0-rpi-5-b.dtb and the bcm2712-rpi-5-b.dtb. Can someone explain me the difference?

I also had a look in the new spix driver that hm2 component uses, and it reads /proc/device-tree/compatible to detect the board type. Might it be a bit more robust to dtb files changes?
hm2.spix.c:

// Read the 'compatible' string-list from the device-tree
    buflen = spix_read_file("/proc/device-tree/compatible", buf, sizeof(buf));
    if(buflen < 0) {
        LL_ERR("Failed to read platform identity.\n");
        return buflen;    // negative errno from read_file()
    }

    // Decompose the device-tree buffer into a string-list with the pointers to
    // each string in dtcs. Don't go beyond the buffer's size.
    memset(dtcs, 0, sizeof(dtcs));
    for(i = 0, cptr = buf; i < DTC_MAX && cptr; i++) {
        dtcs = cptr;
        j = strlen(cptr);
        if((cptr - buf) + j + 1 < buflen)
            cptr += j + 1;
        else
            cptr = NULL;
    }

spix_rpi5.c:

for(i = 0; dtcs != NULL; i++) {
        if(!strcmp(dtcs, DTC_RPI_MODEL_5B) || !strcmp(dtcs, DTC_RPI_MODEL_5CM)) {
            break;    // Found our supported board
        }
    }

Thanks for your help.

I am closely watching this too. I was trying to make work external homing on Delta B3 servos, but it did not work, no matter how I connected hal pins.
The closest I got was, when I was able to home drive, but it jumped back to original position (if the following error was large enough).

I hope that i am understanding what your asking correctly. The motor is driven by a CL driver from stepper online. I have the motor wired to the stepgen 3 on the board  7i96 and the encoder to the encoder area on the board. Data sheet attached.

my assumption is that there is feed back from the encoder i just can't seem to find our what channels to listen to so i can tune it in. 

 

Yes, it is a differential signal.
I am attaching a screen manual from the servopack.
 
 Two servos are Delta asda-b2 750w and one on the z axis is the Chinese a1-svd 750w and in total there are such symptoms on each axis.
The encoder cable is shielded and a separate analog cable is also shielded, the shield is only connected to the servopack.
Maybe I need to use resistors?

 

Thanks for all the work!
At a first glance I'm a bit confused what you are doing in your test. Why are you using equations 17..20 and 44?

In my opinion the workflow should be like this.
1. eq 25, 26 or 29,30 depending on type of segments (line or arc)
2. eq 31, 32, 33 to calculate the transformation matrix T
3. eq 35 calculate the transformed derivatives
4. eq 39 calculate theta_1,0, _2,0, _1,4 and _2,4
5. eq 40 calculate kappa_1,0, _2,0, _1,4 and _2,4
6. eq 43,42 calculate c_1,0, _2,0, _1,4 and _2,4
7. dogleg to calculate gamma_1,1, _2,1 and s1
8. eq 45 to calculate the rest.

I'll have a more in depth look tomorrow.

azim4411 wrote:

can we use mesa with the existing ferrocontrol motors?
And what mesa cards do we need in total?

You came here to ask for help on something very complicated and very time consuming, yet you did not even bother to spend 10 minutes of your time to have a look through the topic!!!! WTH???
That is very disrespectful to us as we spend a lot of our very valuable time posting and helping others here.
Read the topic, everything is there in great details.