Advanced Search

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.

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?

Oh yes I see only the yellow is on. Red light is not lit on the bottom.

Do you have a red LED illuminated on the 7I77?

With 7I77 field power you should have gotten 2 new LEDs:

yellow LED CR3 and red LED CR16
(when running, red LED CR16 should extinguish and green LED CR15 should blink)

Is W1 in the left hand position?

I figure you might ask for the pinout from mesa flash so here is that.

I added 12v field power to the 7i77 but still am getting the pin doesn't exist error. I do have a new light on the 7i77 though.

The 7i77 must have field power or the field I/O pins will not be present:

hm2/hm2_5i25.0: IO Pin 003 (P3-15): Smart Serial Interface #0, pin tx1 (Output)  << 7I77 analog out is working as it needs only 5V
hm2/hm2_5i25.0: IO Pin 004 (P3-03): Smart Serial Interface #0, pin rx1 (Input)
hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort  << This is the 7I77 digital field I/O. It's not working, likely because 7I77 field power is not present
hm2/hm2_5i25.0: IO Pin 006 (P3-04): IOPort
 

I have it hooked up to a 5 volt supply. Lights turn on. Also need to figure out how to make the 7i84 I have get detected when connected to the 7i74. The 84 has 12v field power

Hey and thanks for the effort!
I tried a sim config and set the "halui.maschine.on" and I get "halui.maschine.is-on" to change state to on. With off it works in the other direction.
I then tried the same thing with my config (pendant off) and it works! When I turn my pendant on things go down hill... I then press the reset button on the pendant and I can get my "halui.maschine.is-on" to get stuck either on or off. If it is stuck, it does not change whith the GUI button either.
This is beyond confusing to me. Why does my cofig do that from version 2.9.5 onward?

Thanks for confirming it´s a bit strange
I´ve now tried again the newer probescreen v.2.9 where I didn´t connect the toolchange pins (this was the initial reason for using the older screen v1). It seems to gerneral work, too. But with a strange behavior like in v1.

Probing in Z seems to work fine. When I touch Probing from X-, Y- the machine starts moving in X+ direction until it prompts "finished without probing..". It should move in X- first, Z down, and then X+ for touching.. Crazy behavior.
In my case it starts directly moving X+ without moving Z..

I allready checkt the macro files. everything seems to be okay. any idea how to debug it?