Advanced Search

I have just now added another wire going to 7i84 field power so now A and B has power. I added the line you suggested having both serial 0 and sserial 1 called out. I still am currently getting the same error that the pins on 7i84 don't exist.

forum.linuxcnc.org/9-installing-linuxcnc...-64?start=110#290282
Second part of that post ONLY!

The red light is on yes, I don't have power to a and b just one. I was thinking the jumper position tied the 2 together but I could be wrong

After running sudo apt-get install -f I've got this:

dpkg: error processing package linux-image-rt-amd64 (--configure):
dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-40-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-6.1.0-40-rt-amd64
linux-image-rt-amd64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Then went with

sudo apt-get check
apt-cache depends

I got this:

milos@cnc:~$ apt-cache depends linux-image-rt-amd64
linux-image-rt-amd64
Depends: linux-image-6.1.0-40-rt-amd64
milos@cnc:~$ apt-cache depends linux-image-6.1.0-40-rt-amd64
linux-image-6.1.0-40-rt-amd64
Depends: kmod
Depends: linux-base
|Depends: initramfs-tools
Depends: <linux-initramfs-tool>
dracut
initramfs-tools
tiny-initramfs
Conflicts: linux-image-6.1.0-40-rt-amd64-unsigned
Breaks: fwupdate
Breaks: initramfs-tools
Breaks: wireless-regdb
Recommends: firmware-linux-free
Recommends: apparmor
Suggests: linux-doc-6.1
Suggests: debian-kernel-handbook
|Suggests: grub-pc
|Suggests: grub-efi-amd64
Suggests: extlinux
Replaces: linux-image-6.1.0-40-rt-amd64-unsigned

what should I do next? I don't understand this.

Some versions of LinuxCNC require the sserial_port_n stanza or the port is not enabled  (for ports 1,2,3)

Is the 7I84 red LED illuminated?

Do you have field power supplied to both A and B 7I84 field power sections?
 

I added port 1 and it did t change anything, I also tried getting rid of the port call-out as I read in another forum post that if you don't specify then all ports are available. Neither changed the results

Because P1 pins are all assigned  to sserial_port_1, I would not expect
them to be enabled unless sserial_port_1 is enabled in the hal file,

something like:

loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=6 sserial_port_0=000 sserial_port_1=00000000"

It seems as if the internal port p1 is not showing up in my pins... I'm not sure why that is

I know this is an old thread, but are you willing to share your fiber laser configs? I’m starting this project currently and curious about how you handled things like auto focus, laser pwm, etc

After the initial hick-ups with Lan connection, I hoped everything will be smooth sail, but it looks like no luck.
I tried a couple of times to install it from scratch, but same problem is there initramfs tools error code 1. Wondering why it looks for raspi when I am not running Rospi?
What can I do to properly finish with installation? 

Thanks,
M

dkms: running auto installation service for kernel 6.1.0-40-amd64.
dkms: autoinstall for kernel: 6.1.0-40-amd64.
Setting up libqt5opengl5:amd64 (5.15.8+dfsg-11+deb12u3) ...
Setting up linux-headers-rt-amd64 (6.1.153-1) ...
Setting up libgimp2.0:amd64 (2.10.34-1+deb12u3) ...
Setting up libpoppler-qt5-1:amd64 (22.12.0-2+deb12u1) ...
Setting up linux-headers-amd64 (6.1.153-1) ...
Processing triggers for systemd (252.39-1~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for shared-mime-info (2.2-1) ...
Processing triggers for debianutils (5.7-0.5~deb12u1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-40-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return c
ode 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Processing triggers for ca-certificates (20230311+deb12u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
 linux-image-6.1.0-40-rt-amd64
 linux-image-rt-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

I've recently bought a Harrison Alpha 330 with a broken computer. I am
going to convert this lathe to linuxcnc using my own motor drives.
 
Since this lathe was using a Fanuc controller and I could not find
sufficient information about the Fanuc encoder protocol, I decided to
try to reverse engineer the protocol. And it seems I have succeeded and
would like to share what I have learnt about the protocol, in case anyone
else wants to re-use their Fanuc encoders.
 
The motors present are beta1/3000 or A06B-0031-B077 (X-axis) and
beta2/3000 or A06B-0032-B077 (Z-axis)
 
First of all the code can be found in
github.com/mark-v-d/motor_control/tree/fanuc
 
Both the file software/xmc4400/src/encoder.cpp and
software/xmc4400/src/crc_lut.h should contain all
the information necessary.
 
/* Fanuc***********************************************************/
   Datarate is 1024kb/s. Send a positive pulse on REQ (pin-5) of 7..9us
   to get a response.  The response is 4 frames of 1 start bit, 16 data
   bits and 1 stop bit.  After the 4th frame the CRC is transmitted,
   without a preceding startbit.  The way to capture it, is to change
   the word length of the 4th frame to 16+1+5 bits.
 
    1st status
        0xe000  3-msb changes, reason unknown
        0x0100  index seen
        0x0005  always there so-far.
    2nd 16-bit counter within revolution
    3rd revolution counter
    4th absolute
        0x8000  Always set?
        0x03fc  Commutation angle? After index the same as 2nd>>4
    5th 5-bit CRC
 

okay I am now trying to figure out what I need to do to make the 7i74 communicate to the 7i84. it has a pwr LED on and nothing else.

You likely need a sserial_port_1=0000XXXX or similar in your hal file

it is in the righthand position for seperate field power from vin. is that vin for the logic seperate from that of the 5v vin on the left hand plug?

The VIN jumper is completely unrelated to the 5V side. Typically it should be left in the default left hand position
so VIN comes from VFIELD. If it's in the right hand position, the VIN pin on TB2 must be supplied with +8 to +32VDC

okay I am now trying to figure out what I need to do to make the 7i74 communicate to the 7i84. it has a pwr LED on and nothing else.

I misunderstood the wording in the manual. now that the jumper is over to the right it is lit up and I am making more progress with getting this thing to work.