Advanced Search

Search Results (Searched for: )

  • unknown
  • unknown
16 Dec 2025 21:20

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

The missing firmware module can safely be ignored.
The above post can be safely ignored as well.
Tho if it is something you can do and can afford, I would recommend looking at the riocore/LinuxcncRIO project as that can connect via ethernet, is creates step/direction in hardware and as such only requires a servo thread. Another plus being you don't require a RTAI kernel. Just mentioning as this might be worth investigating. The developer is very generous with his time as well and the project is very active.
  • langdons
  • langdons's Avatar
16 Dec 2025 21:08

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

Post dmesg output please.

Open up a system CPU monitor app.

Then move the mouse around a lot.

Does CPU usage go up for a process called xorg when you move the mouse around (generally indicates that sofware rendering is being used).

If it ain't broke, don't fix it.

Do you have a dedicated GPU card, by chance?
  • Sekai
  • Sekai
16 Dec 2025 21:01

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

i did notice something weird when i install the kernel.
Its says missing firmware module i915
But the display works great.
  • Hakan
  • Hakan
16 Dec 2025 20:29 - 16 Dec 2025 20:29

Ethercat compatible Encoder board tentative STM32F4 + LAN9252

Category: EtherCAT

It's better I give you a hand in those situations. So you have a version you always can come back to that works.
And then you can be creative on top of that get lost from there.
But what you have described you want to do, you are more or less finished already.
There is of course the whole packaging story, Din-rail? box, other? external power supply, connectors, photo-diodes on encoder input?
Stacking of several units? Can you perhaps use the 16-bit counters and have several counters on board? Is there a MCU with several 32-bit encoders you can use/switch to. Just because it works doesn't mean it is finished. For sure it can be optimized.
Right now it runs in free-run mode, should probably go over to DC-sync mode and there is a bit of programming for that. Same HW though.

Microchip has come out with several schematics for their evaluation boards, here is one ww1.microchip.com/downloads/en/DeviceDoc...PIO16.Mode.Rev.A.pdf Here is another ww1.microchip.com/downloads/aemDocuments...DIG-IO-EVB-REV-B.pdf and you find schematics in my KiCaD files.
  • zoeper
  • zoeper
16 Dec 2025 19:34
Replied by zoeper on topic Avon 3000 Mill retrofit

Avon 3000 Mill retrofit

Category: Milling Machines

I made some progress today. Hooked up all limit switches and the "E-stop out" output.It functions, but I have trouble measuring the output using a multimeter and I suspect it need to be pulled up (using the 7i77D with sinking outputs.
I did manage to run the Default LinuxCNC logo engraving Gcode without the belts connected, and it was good to see the motors doing their thing at LinuxCNC;s command.
Another observation: If I actuate a limit (+vector or -vector, not the overtravel), the control trips the estop circuit, instead of just holding feed in that direction. is this correct?
I am trying to get as far as possible using PNCConf as HAL is still foreign to me.
Next would be to get the rest of the E-stop (including overtravel) circuit connected and tested before I hook up the belts.
Homing on this machine used to involve looking for the -vector switches (could be +Vector on Z) and reversing direction off the limit until the index marker is found. Can this be set up using PNCConf as well?
  • Chad
  • Chad
16 Dec 2025 19:15

Remora 1.1.0 + BTT Octopus – jog overshoot and joint following error

Category: Computers and Hardware

Hi,I have been fighting with Remora on a Raspberry Pi for about 3 months now and I am running out of ideas, so I’m asking for some help.Hardware / versions
  • Raspberry Pi: (model + RAM ).
  • BTT Octopus: (exact version, e.g. v1.1, STM32F446).
  • LinuxCNC: version from the official RPi image.
  • Remora: 1.1.0 – STM32 firmware for the Octopus from the 1.1.0 release, LinuxCNC component compiled from 
    remora-1.1.0/LinuxCNC/Components/Remora/remora.c
    .
Why I switched from SKROn SKR 1.4 with Remora 0.1.0 I constantly get “bad SPI payload” and E‑STOP, even after improving the wiring (short cable, ground every second wire, shielded cable, common GND). In that old Remora version there are no 
SPI_clk_div
 / 
PRU_base_freq
 parameters, so I cannot slow down the SPI clock from the LinuxCNC side.Because of that I moved to a BTT Octopus with Remora 1.1.0, which gives me 
SPI_clk_div
 and 
PRU_base_freq
 so I can reduce SPI speed.What happens on the Octopus
  • SPI now looks stable: when I run the heater/wire only (no axis motion) I don’t get any “bad SPI payload” at all.
  • I load the component like this:
loadrt remora SPI_clk_div=128 PRU_base_freq=40000
(Values can be changed, this is just what I’m testing now.)
  • The motors move, in the correct direction, but I have two problems:
  1. Jog incremental overshoot
    In incremental jog (for example 1 mm or 10 mm) when I press the jog “+” button and release it, the axis moves noticeably more than the requested increment.
    It looks like Remora/stepgen continues to output steps for a short time after LinuxCNC has stopped the move.
  2. Joint following error after a few cm of travel
    With conservative parameters (see JOINT_0 below) the axis can travel a few centimetres and then I get a joint following error.
    With SKR + Remora 0.1.0, using the same HAL/INI values for SCALE, acceleration, max velocity and FERROR, I never had following errors – only the “bad SPI payload” issue.
Current 
[JOINT_0]
 section in my INI
[JOINT_0] TYPE = LINEAR HOME = 0 HOME_OFFSET = -10 MIN_LIMIT = -0.001 MAX_LIMIT = 450 MAX_VELOCITY = 10 MAX_ACCELERATION = 200 STEPGEN_MAXACCEL = 300 SCALE = (current value – was 50 originally) FERROR = 50 MIN_FERROR = 20 HOME_SEARCH_VEL = -1.5 HOME_LATCH_VEL = -0.5 HOME_IGNORE_LIMITS = YES HOME_SEQUENCE = 0
Relevant HAL fragment (Octopus / Remora connection)
loadrt remora SPI_clk_div=128 PRU_base_freq=40000 # add remora and motion functions to threads addf remora.read servo-thread addf motion-command-handler servo-thread addf motion-controller servo-thread addf remora.update-freq servo-thread addf remora.write servo-thread # --- Joint 0 (X) --- setp remora.joint.0.scale [JOINT_0]SCALE setp remora.joint.0.maxaccel [JOINT_0]STEPGEN_MAXACCEL net xpos-cmd <= joint.0.motor-pos-cmd => remora.joint.0.pos-cmd net xpos-fb <= remora.joint.0.pos-fb => joint.0.motor-pos-fb net j0enable <= joint.0.amp-enable-out => remora.joint.0.enable
(If anything in this mapping looks obviously wrong, please point it out.)What I have already tried
  • Reduced 
    MAX_VELOCITY
    MAX_ACCELERATION
     and 
    STEPGEN_MAXACCEL
     a lot and increased 
    FERROR
    /
    MIN_FERROR
    . This delays the following error but does not remove it.
  • Tried to tune 
    SCALE
     using G‑code (G91 / G0 X100 and measuring real travel). Even with reasonable SCALE values I still see overshoot in incremental jog: the axis moves clearly more than the selected increment.
  • On SKR 1.4 with old Remora 0.1.0, with the same mechanical setup and same SCALE / accel / maxvel / FERROR, jogging and running G‑code worked fine (no following errors, no overshoot). The only issue there is the fixed, too‑fast SPI that causes “bad SPI payload”.
Questions
  1. Is this kind of jog overshoot in incremental mode a known configuration issue with Remora 1.1.0 + Octopus (for example related to PRU_base_freq, servo thread period, or some Remora parameter), or is it more likely that I have a clear mistake in my HAL/INI?
  2. What SPI / PRU settings do people successfully use on a BTT Octopus with Remora 1.x? Is 
    SPI_clk_div=128
     and 
    PRU_base_freq=40000
     reasonable, or should I change these?
  3. Does anyone have a working LinuxCNC config (INI/HAL) for Remora 1.1.0 + Octopus in plain step/dir mode and would be willing to share the relevant 
    loadrt remora
     line and joint settings?
  4. Are there any STM32/Octopus‑specific considerations in Remora (different expectations for SCALE, FERROR, etc.) when migrating from an LPC/SKR setup?
My main goals are:
  • to get rid of the jog overshoot in incremental mode,
  • to choose sane parameters so joint following error does not appear every few centimetres at reasonable speeds.
Any hints, working examples, or “known good” values for an Octopus setup would be very much appreciated.

my octopus config.txt:
{
  "Board": "BIGTREETECH OCTOPUS",
  "Modules": [
    { "Thread": "Servo", "Type": "Reset Pin", "Comment": "Reset pin", "Pin": "PC_15" },
    { "Thread": "Base", "Type": "SPI", "Comment": "SPI interface to Raspberry Pi", "CS Pin": "PA_4" },

    { "Thread": "Base", "Type": "Stepgen", "Comment": "X - Joint 0 stepgen", "Joint Number": 0, "Step Pin": "PF_13", "Direction Pin": "PF_12", "Enable Pin": "PF_14" },
    { "Thread": "Base", "Type": "Stepgen", "Comment": "Y - Joint 1 stepgen", "Joint Number": 1, "Step Pin": "PG_0", "Direction Pin": "PG_1", "Enable Pin": "PF_15" },
    { "Thread": "Base", "Type": "Stepgen", "Comment": "U - Joint 2 stepgen", "Joint Number": 2, "Step Pin": "PF_11", "Direction Pin": "PG_3", "Enable Pin": "PG_5" },
    { "Thread": "Base", "Type": "Stepgen", "Comment": "V - Joint 3 stepgen", "Joint Number": 3, "Step Pin": "PG_4", "Direction Pin": "PC_1", "Enable Pin": "PA_0" },
    { "Thread": "Base", "Type": "Stepgen", "Comment": "B - Joint 4 stepgen", "Joint Number": 4, "Step Pin": "PF_9", "Direction Pin": "PF_10", "Enable Pin": "PG_2" },


{
    "Thread": "Servo",
    "Type": "Digital Pin",
            "Comment":                      "X limit",
            "Pin":                          "PG_6",
            "Mode":                         "Input",
            "Data Bit":                     0
    },



{
    "Thread": "Servo",
    "Type": "Digital Pin",
            "Comment":                      "Y limit",
            "Pin":                          "PG_9",
            "Mode":                         "Input",
            "Data Bit":                     1
    },

{
    "Thread": "Servo",
    "Type": "Digital Pin",
            "Comment":                      "U limit",
            "Pin":                          "PG_10",
            "Mode":                         "Input",
            "Data Bit":                     2
    },
{
    "Thread": "Servo",
    "Type": "Digital Pin",
            "Comment":                      "V limit",
            "Pin":                          "PG_11",
            "Mode":                         "Input",
            "Data Bit":                     3
    },

{
    "Thread": "Servo",
    "Type": "Digital Pin",
            "Comment":                      "B limit",
            "Pin":                          "PG_12",
            "Mode":                         "Input",
            "Data Bit":                     4
    },

 
 {
    "Thread": "Servo",
    "Type": "PWM",
            "Comment":                      "PWM for heating",
            "SP[i]":                        5,
            "PWM Pin":                      "PA_1",
            "PWM Max":                      256,
            "Hardware PWM":                 "True",
            "Variable Freq":                "True",
            "Period SP[i]":                  1,
            "Period us":                    500
    }
  ]
}


my .ini file:
[EMC]
MACHINE = Remora-XYUV
DEBUG = 0
VERSION = 1.1

[DISPLAY]
DISPLAY = axis
EDITOR = gedit
FOAM = 1
GEOMETRY = XY;UV
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 2.50
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 25.00
DEFAULT_ANGULAR_VELOCITY = 36.00
MIN_ANGULAR_VELOCITY = 0
MAX_ANGULAR_VELOCITY = 45.00
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = ~/linuxcnc/nc_files
OPEN_FILE = ./foam.ngc
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm

[KINS]
JOINTS = 5
KINEMATICS = trivkins coordinates=XYUVB

[FILTER]
PROGRAM_EXTENSION = .py Python Script
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 100000
SERVO_PERIOD = 1000000

[HAL]
HALFILE = remora-xyuvb.hal
POSTGUI_HALFILE = postgui_call_list.hal

[TRAJ]
AXES = 5
COORDINATES = X Y U V B
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
DEFAULT_LINEAR_VELOCITY = 2.50
MAX_LINEAR_VELOCITY = 25.00
NO_FORCE_HOMING = 1

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl
EXTERNAL_OUTPUT_0 = motion.analog-out-00

[AXIS_X]
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
MIN_LIMIT = 10
MAX_LIMIT = 450

[JOINT_0]
TYPE = LINEAR
HOME = 0
HOME_OFFSET = -10
MIN_LIMIT = -0.001
MAX_LIMIT = 450
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 937.5
SCALE = 50
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.000
HOME_SEARCH_VEL = -1.5
HOME_LATCH_VEL = -0.5
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 0

[AXIS_Y]
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0

[JOINT_1]
TYPE = LINEAR
HOME = 0
HOME_OFFSET = -10
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 937.5
SCALE = -50
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.000
HOME_SEARCH_VEL = -1.5
HOME_LATCH_VEL = -0.5
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 1

[AXIS_U]
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
MIN_LIMIT = 10
MAX_LIMIT = 450

[JOINT_2]
TYPE = LINEAR
HOME = 0
HOME_OFFSET = -10
MIN_LIMIT = -0.001
MAX_LIMIT = 450
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 937.5
SCALE = -50
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.000
HOME_SEARCH_VEL = -1.5
HOME_LATCH_VEL = -0.5
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 0

[AXIS_V]
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0

[JOINT_3]
TYPE = LINEAR
HOME = 0
HOME_OFFSET = -10
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
STEPGEN_MAXACCEL = 937.5
SCALE = -50
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.000
HOME_SEARCH_VEL = -1.5
HOME_LATCH_VEL = -0.5
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 1

[AXIS_B]
MAX_VELOCITY = 23.75
MAX_ACCELERATION = 750.0
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0

[JOINT_4]
TYPE = LINEAR
HOME = 0
HOME_OFFSET = 1
MIN_LIMIT = -0.001
MAX_LIMIT = 200.0
MAX_VELOCITY = 23.75
# MAX_ACCELERATION = 750.0
MAX_ACCELERATION = 500.0
# STEPGEN_MAXACCEL = 937.5
STEPGEN_MAXACCEL = 537.5
SCALE = 50
FERROR = 1
MIN_FERROR = .25
HOME_OFFSET = 0.000
HOME_SEARCH_VEL = 1
HOME_LATCH_VEL = 0.1
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 2

my .hal file:
# --- load the realtime components
loadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=5

loadrt remora

# --- estop loopback, SPI comms enable and feedback
net user-enable-out      <= iocontrol.0.user-enable-out        => remora.SPI-enable
net user-request-enable  <= iocontrol.0.user-request-enable    => remora.SPI-reset
net remora-status        <= remora.SPI-status                  => iocontrol.0.emc-enable-in

# --- add the remora and motion functions to threads
addf remora.read servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf remora.update-freq servo-thread
addf remora.write servo-thread

# ------- Joint 0 (X / Tower 1) -------
setp remora.joint.0.scale         [JOINT_0]SCALE
setp remora.joint.0.maxaccel      [JOINT_0]STEPGEN_MAXACCEL

net xpos-cmd      <= joint.0.motor-pos-cmd  => remora.joint.0.pos-cmd  
net j0pos-fb      <= remora.joint.0.pos-fb  => joint.0.motor-pos-fb
net j0enable      <= joint.0.amp-enable-out => remora.joint.0.enable
net X-stop        remora.input.0          => joint.0.home-sw-in joint.0.neg-lim-sw-in joint.0.pos-lim-sw-in

# ------- Joint 1 (Y / Tower 1) -------
setp remora.joint.1.scale         [JOINT_1]SCALE
setp remora.joint.1.maxaccel      [JOINT_1]STEPGEN_MAXACCEL

net ypos-cmd      <= joint.1.motor-pos-cmd  => remora.joint.1.pos-cmd
net j1pos-fb      <= remora.joint.1.pos-fb  => joint.1.motor-pos-fb 
net j1enable      <= joint.1.amp-enable-out => remora.joint.1.enable
net Y-min         remora.input.1            => joint.1.home-sw-in joint.1.neg-lim-sw-in joint.1.pos-lim-sw-in

# ------- Joint 2 (U / Tower 2) -------
setp remora.joint.2.scale         [JOINT_2]SCALE
setp remora.joint.2.maxaccel      [JOINT_2]STEPGEN_MAXACCEL

net upos-cmd      <= joint.2.motor-pos-cmd  => remora.joint.2.pos-cmd
net j2pos-fb      <= remora.joint.2.pos-fb  => joint.2.motor-pos-fb
net j2enable      <= joint.2.amp-enable-out => remora.joint.2.enable
net U-min         remora.input.2            => joint.2.home-sw-in joint.2.neg-lim-sw-in joint.2.pos-lim-sw-in

# ------- Joint 3 (V / Tower 2) -------
setp remora.joint.3.scale         [JOINT_3]SCALE
setp remora.joint.3.maxaccel      [JOINT_3]STEPGEN_MAXACCEL

net vpos-cmd      <= joint.3.motor-pos-cmd  => remora.joint.3.pos-cmd
net j3pos-fb      <= remora.joint.3.pos-fb  => joint.3.motor-pos-fb
net j3enable      <= joint.3.amp-enable-out => remora.joint.3.enable
net V-min         remora.input.3            => joint.3.home-sw-in joint.3.neg-lim-sw-in joint.3.pos-lim-sw-in

# ------- Joint 4 (B / Rotary Table) -------
setp remora.joint.4.scale         [JOINT_4]SCALE
setp remora.joint.4.maxaccel      [JOINT_4]STEPGEN_MAXACCEL

net bpos-cmd      <= joint.4.motor-pos-cmd  => remora.joint.4.pos-cmd
net j4pos-fb      <= remora.joint.4.pos-fb  => joint.4.motor-pos-fb
net j4enable      <= joint.4.amp-enable-out => remora.joint.4.enable
net B-min         remora.input.4            => joint.4.home-sw-in joint.4.neg-lim-sw-in joint.4.pos-lim-sw-in

net heat_pwm motion.analog-out-00 => remora.SP.5
  • DemonClaW
  • DemonClaW
16 Dec 2025 17:45
Replied by DemonClaW on topic No linuxcnc widgets in designer

No linuxcnc widgets in designer

Category: Qtvcp

Does someone have this trouble up to date? Have tryed all of it but nothing worked
  • tommylight
  • tommylight's Avatar
16 Dec 2025 17:41

Updating from LINUXCNC - 2.8.4-23, Mint 20.3 - gmoccapy lathe structure

Category: Gmoccapy

Mmmmm shinny ...
I would venture a guess at it being a motor and ballscrew holder/mount with belt going inside of it ?
  • tommylight
  • tommylight's Avatar
16 Dec 2025 17:22

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

Nice, that is still very usable.
-
RTAI kernels always had issues with hardware, mostly graphic where the resolution would be stuck at 640x480 with no options to change it, there are some examples i posted on this forum when i tested some old PC's.
And i do recall one PC would lock after a while or running LinuxCNC, at random, usually once every two to three days.
  • PCW
  • PCW's Avatar
16 Dec 2025 16:43
Replied by PCW on topic 7i96s + 7i78

7i96s + 7i78

Category: Driver Boards

7i96s_7i78d.bin would be the correct bin file for a 7I96S+7I78

This is available from Mesa's web store, in the software support .zip file
 
  • Sekai
  • Sekai
16 Dec 2025 16:35 - 16 Dec 2025 16:36

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

Use this ISO
www.linuxcnc.org/iso/linuxcnc-2.7.14-wheezy.iso
Boot the PC from it and run the tests in Live mode, meaning do not install, see if it hangs.
 



 

I tried it its above 35000 and it never froze
  • nanowhat
  • nanowhat
16 Dec 2025 16:29 - 16 Dec 2025 16:29
Replied by nanowhat on topic StepperOnline A6 Servo

StepperOnline A6 Servo

Category: EtherCAT

DI3 is by default active low. Parameter C04.09 controls whether DI3 is active high or active low.
  • langdons
  • langdons's Avatar
16 Dec 2025 16:25

Updating from LINUXCNC - 2.8.4-23, Mint 20.3 - gmoccapy lathe structure

Category: Gmoccapy

Looks cool and well-made.

What does it do/what's it for?

Did you design and machine it, or "just" machine it?
  • langdons
  • langdons's Avatar
16 Dec 2025 16:24

Advantech PCM 9362 freze when opening latency-test

Category: Computers and Hardware

Use this ISO
www.linuxcnc.org/iso/linuxcnc-2.7.14-wheezy.iso
Boot the PC from it and run the tests in Live mode, meaning do not install, see if it hangs.
Literally what I said in my post before it "mysteriously" disappeared into thin air.

(no offense to you)

Sigh...
1. You literally repeated my already existing post
2. You linked the wrong ISO location for the same ISO
That can and will absolutely raise suspicion.

I think we must have posted at the same time or something.

I swear this post was in the "No Replies" section when I replied to it.

Weird.
  • Dudelbert
  • Dudelbert
16 Dec 2025 16:14 - 16 Dec 2025 16:17

Considering a Full Rewire on a Working Schaublin 125 CNC

Category: Turning

Hi,
I want to give a quick update on my work, the belt for the Spindle encoder has been replaced.
Two belts have been installed same as RotrySMP has done. But I thought about this and think it is les helpful as I originally thought.
As this belt will likely “Dye” of old age, in that case the other one will also be brittle due to age already, but now it is in there and it does not hurt anything.

With the Spindle in good shape now I could test the full machine. Everything worked fine. Interestingly most of the “extended” machine was not even conked to the controller but controlled by directly wired relays, even with a notable amount of safety by locking functions out.
This includes the full tool changer, variator and back gear.

At this point I noted down some of it and started tearing the electronics and pneumatic bay down.
I also dismounted and shortened the electronics box.Their seems to be space for everything in the former pneumatics bay. If that is the case I will use the electronics box for tool holders, chucks and that stuff, if I need more space I will use that space as needed.
Also I did make up a bit of a control panel in CAD and made a cardboard variant.

I think that is it so far.
Martin
Displaying 76 - 90 out of 21729 results.
Time to create page: 0.212 seconds
Powered by Kunena Forum