Advanced Search

Search by Keyword Keywords:

Search Options

Find Posts from

Sort Results by

Search at a specific date

Jump to Result Number

Search in Categories Also search in sub-categories

Search Results (Searched for: )

Aciera

10 Oct 2024 06:47

Replied by Aciera on topic linuxcnc trajectory planner

linuxcnc trajectory planner

Category: General LinuxCNC Questions

Disregard the above. I was not aware that I needed to go through the usual linuxcnc build process before running the cmake build:

You now need to run 'sudo make setuid' in order to run in place with access to hardware.
user@user-iMac:~/linuxcnc_trajectory_planner/src$ cd ..
user@user-iMac:~/linuxcnc_trajectory_planner$ cd cmake/build/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ make
Consolidate compiler generated dependencies of target motmod
[  5%] Linking C shared library motmod.so
[ 50%] Built target motmod
Consolidate compiler generated dependencies of target tpmod
[ 55%] Building C object planner/CMakeFiles/tpmod.dir/tpmod.c.o
[ 60%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/tc.c.o
[ 65%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/tcq.c.o
[ 70%] Building C object planner/CMakeFiles/tpmod.dir/tp.c.o
[ 75%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/spherical_arc.c.o
[ 80%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/blendmath.c.o
[ 85%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/nml_intf/emcpose.c.o
[ 90%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/libnml/posemath/_posemath.c.o
[ 95%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/libnml/posemath/sincos.c.o
[100%] Linking C shared library tpmod.so
[100%] Built target tpmod
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$

Aciera

10 Oct 2024 06:34

Replied by Aciera on topic linuxcnc trajectory planner

linuxcnc trajectory planner

Category: General LinuxCNC Questions

Does not seem to work for me (missing 'config.h'):

user@user-iMac:~$ cd linuxcnc_trajectory_planner/
user@user-iMac:~/linuxcnc_trajectory_planner$ cd cmake/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake$ cd build/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ cmake ..
-- The CXX compiler identification is GNU 11.4.0
-- The C compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/linuxcnc_trajectory_planner/cmake/build
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ make
Consolidate compiler generated dependencies of target motmod
[  5%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/kinematics/cubic.c.o
[ 10%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/axis.c.o
[ 15%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/motion.c.o
[ 20%] Building C object motion/CMakeFiles/motmod.dir/command.c.o
[ 25%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c.o
/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c:31:10: fatal error: config.h: No such file or directory
   31 | #include "config.h"
      |          ^~~~~~~~~~
compilation terminated.
make[2]: *** [motion/CMakeFiles/motmod.dir/build.make:132: motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:116: motion/CMakeFiles/motmod.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

meister
meister

10 Oct 2024 06:08

Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

fixed, but this error comes only if you do not add .json suffix to your filename.

Thanks for reporting !

OttoDidact

10 Oct 2024 06:04

Replied by OttoDidact on topic My Cable Robot CNC Foam Cutter is running!

My Cable Robot CNC Foam Cutter is running!

Category: Show Your Stuff

Very cool.

Aciera

10 Oct 2024 04:27

Replied by Aciera on topic Slider (scale) to change stepper acceleration

Slider (scale) to change stepper acceleration

Category: pyVCP

INI hal pin values can be changed in gcode during execution but require a queuebuster command (eg M66 E0 L0) to be updated.

phillc54

10 Oct 2024 04:09 - 10 Oct 2024 04:10

Replied by phillc54 on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

Try changing the line below this in your hal file:

# ---JOINT ASSOCIATED WITH THE Z AXIS---

from:

net plasmac:axis-position joint.2.pos-fb => plasmac.axis-z-position

to:

net plasmac:axis-position joint.3.pos-fb => plasmac.axis-z-position

dreBird
dreBird

10 Oct 2024 04:07

Replied by dreBird on topic Joint homing offset and following error - HELP

Joint homing offset and following error - HELP

Category: General LinuxCNC Questions

OK thank you everyone! I ran a live session with the Linux installation disk and changed the thread period back to 1000000 (it was saved at 10000). I then tried 700000 and I got a weird A axis burn out, where the axis rotated very quickly and erratically during the homing sequence. So its back at 1000000.

I ran the latency test and didn't see much difference in Max Jitter (ns), around 20100 at each thread rate tested above. (I could not run LCNC and the latency test at the same time due to conflict with the real time processor).

Mesa 5i25 is connected to the 7i77

PCW

10 Oct 2024 03:26

Replied by PCW on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

OK did not see that hal file (and grep'ed for the db.out pins and did not find them in the supplied hal files)
back to square one I guess...

phillc54

10 Oct 2024 03:15 - 10 Oct 2024 03:19

Replied by phillc54 on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

We kinda do things in a convoluted way, the dbounce component pins are connected by qtplasmac_comp.hal which is in hallib.

qtplasma_comp.hal:

Warning: Spoiler!

# ***** plasmac component connections for a QtPlasmaC configuration *****

# do not make any changes to this file, it may be overwritten by future updates
# make all customizations in custom.hal or custom_postgui.hal

# ---PLASMAC COMPONENT INPUTS---
net plasmac:arc-ok db_arc-ok.out => plasmac.arc-ok-in
net plasmac:axis-x-position axis.x.pos-cmd => plasmac.axis-x-position
net plasmac:axis-y-position axis.y.pos-cmd => plasmac.axis-y-position
net plasmac:breakaway-switch-out db_breakaway.out => plasmac.breakaway
net plasmac:current-velocity motion.current-vel => plasmac.current-velocity
net plasmac:cutting-start spindle.0.on => plasmac.cutting-start
net plasmac:cutting-stop halui.spindle.0.stop => plasmac.cutting-stop
net plasmac:feed-override halui.feed-override.value => plasmac.feed-override
net plasmac:feed-reduction motion.analog-out-03 => plasmac.feed-reduction
net plasmac:float-switch-out db_float.out => plasmac.float-switch
net plasmac:feed-upm motion.feed-upm => plasmac.feed-upm
net plasmac:homed motion.is-all-homed => plasmac.homed
net plasmac:ignore-arc-ok-0 motion.digital-out-01 => plasmac.ignore-arc-ok-0
net machine-is-on halui.machine.is-on => plasmac.machine-is-on
net plasmac:motion-type motion.motion-type => plasmac.motion-type
net plasmac:offsets-active motion.eoffset-active => plasmac.offsets-active
net plasmac:ohmic-probe-out db_ohmic.out => plasmac.ohmic-probe
net plasmac:program-is-idle halui.program.is-idle => plasmac.program-is-idle
net plasmac:program-is-paused halui.program.is-paused => plasmac.program-is-paused
net plasmac:program-is-running halui.program.is-running => plasmac.program-is-running
net plasmac:scribe-start spindle.1.on => plasmac.scribe-start
net plasmac:spotting-start spindle.2.on => plasmac.spotting-start
net plasmac:thc-disable motion.digital-out-02 => plasmac.thc-disable
net plasmac:torch-off motion.digital-out-03 => plasmac.torch-off
net plasmac:units-per-mm halui.machine.units-per-mm => plasmac.units-per-mm
net plasmac:x-offset-current axis.x.eoffset => plasmac.x-offset-current
net plasmac:y-offset-current axis.y.eoffset => plasmac.y-offset-current
net plasmac:z-offset-current axis.z.eoffset => plasmac.z-offset-current

# ---PLASMAC COMPONENT OUTPUTS---
net plasmac:adaptive-feed plasmac.adaptive-feed => motion.adaptive-feed
net plasmac:feed-hold plasmac.feed-hold => motion.feed-hold
net plasmac:jog-inhibit plasmac.jog-inhibit => motion.jog-inhibit motion.jog-stop
net plasmac:offset-scale plasmac.offset-scale => axis.x.eoffset-scale axis.y.eoffset-scale axis.z.eoffset-scale
net plasmac:probe-out plasmac.probe-out => motion.probe-input
net plasmac:program-pause plasmac.program-pause => halui.program.pause
net plasmac:program-resume plasmac.program-resume => halui.program.resume
net plasmac:program-run plasmac.program-run => halui.program.run
net plasmac:program-stop plasmac.program-stop => halui.program.stop
net plasmac:torch-on plasmac.torch-on
net plasmac:x-offset-counts plasmac.x-offset-counts => axis.x.eoffset-counts
net plasmac:y-offset-counts plasmac.y-offset-counts => axis.y.eoffset-counts
net plasmac:xy-offset-enable plasmac.xy-offset-enable => axis.x.eoffset-enable axis.y.eoffset-enable
net plasmac:z-offset-counts plasmac.z-offset-counts => axis.z.eoffset-counts
net plasmac:z-offset-enable plasmac.z-offset-enable => axis.z.eoffset-enable

The times should be set in custom.hal but for some reason in this config they are in custom.hal.new_values and probably should be copied to custom .hal for convenience.

custom.hal:

Warning: Spoiler!

custom.hal.new_values

Warning: Spoiler!

kbec
kbec

10 Oct 2024 02:56

Replied by kbec on topic Help getting started

Help getting started

Category: General LinuxCNC Questions

After a while I found my probe wasn't getting power. My neutral input to my power supply came off somehow.

I was able to get the QTDragon to work.

PCW

10 Oct 2024 02:33

Replied by PCW on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

My guess is it might be the lack of debouncing on critical inputs.

The dbounce components are loaded but the raw parallel port signals
are routed to Plasmac and the dbounce component inputs, but the signal
paths should be:

parallel port pin --> dbouncex.in --> dbouncex.out --> Plasmac

That is you have for example:

net plasmac:float-switch <= parport.0.pin-12-in-not
net plasmac:float-switch   => db_float.in

when it should be something like:

net raw-float-switch <= parport.0.pin-12-in-not
net raw-float-switch   => db_float.in
net plasmac:float-switch   => db_float.out

or the equivalent:

net raw-float-switch <= parport.0.pin-12-in-not => db_float.in
net plasmac:float-switch   => db_float.out

also the debounce times were not set (so would default to 5 servo-thread periods so 5 ms)

cnctrucker

10 Oct 2024 01:45 - 10 Oct 2024 01:56

-- SOLVED -- Inconsistent Probe Performance... was created by cnctrucker

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

I'm stumped -- I just cannot get my probe to work correctly.

Attached is my config archive for review.

My system is a Dell Optiplex 7040 Core-i7, 32 gb RAM, 512 gb SSD, 2 tb hard drive
MosChip PCI 9865 Parallel Card (0xd010) Port 0 Configured As Output
Asix Electronics Corporation AX99100 PCIe Parallel Card (0xb010) Port 1, Configured As Input
Debian Linux 12.7 (Bookworm), Cinnamon Version, Kernel 6.9.7+bpo-rt-amd64
LinuxCNC v2.9.3 compiled from source to DEB then installed through Synaptic.

The table is a DIY using steppers, a SainSmart controller card / breakout board on Port 0, and a bare breakout board with pull-down resistors on Port 1 pins 2-9 for inputs from my proximity limit switches; each axis has a home-min switch and a max switch (8 switches total).

The table homes perfectly. When I do a probe test right after homing, it works like expected -- dropping to probe height, slowing to contact, stopping for a few seconds, then rising to pierce height until the timer expires. When I move to a work coordinate position, the probe test again works perfectly.

Unfortunately, that all blows up when I attempt to run a G-Code program (example below). As you can see in the attached video, the torch drops, makes contact, then immediately rises to safe height -- the program pauses with the error "pierce height would exceed Z axis maximum limit".

I have tried all sorts of values, but nothing seems to do any good; I don't see anything in the program that would cause it.

Perhaps one of our "resident Guru's" can give me some insight into this & help me get it to probe properly?

Config Backup:

File Attachment:

File Name: Plasma_Tab...6.tar.gz
File Size:14 KB

Picture Of Z-Axis:

YouTube Video of Z-Axis Motion During G-Code Program: youtube.com/shorts/k12akteEZmI?feature=share

(Drawing name : Air Connection Plate For Lowboy Neck v5)
(Program Name : AirConnector)
N10 G21
N15 G90 G40
N20 G17 G91.1
N25 G64 P0.254 Q0.254
N30 M52 P1.
N35 M65 P2.
N40 M65 P3.
N45 M68 E3 Q0.

(2D PROFILE3)
(

)
(- NORMAL OPERATION. -)
(

)
(PLASMA CUTTING)
(THROUGH CUTTING)

N50 M190 P1.
N60 F#<_hal[plasmac.cut-feed-rate]>
N65 G0 X111.149 Y67.376
N70 M3 $0 S1
N75 G1 X109.362 Y72.045
N80 G3 X105.479 Y75.195 I-4.67 J-1.788
N90 X95.472 Y26.873 I-3.886 J-24.392
N95 G1 X95.999 Y26.739
N100 X95.999 Y23.749
N105 X107.299 Y23.749
N110 X107.299 Y26.224
N115 X107.299 Y26.765
N120 X107.822 Y26.901
N125 G3 X100.495 Y75.479 I-6.229 J23.902
N130 X96.281 Y72.789 I0.222 J-4.995
N135 G1 X93.976 Y68.352
N140 M5
N145 X171.948 Y55.76
N150 M3 $0 S1
N155 G1 X169.448 Y60.09
N160 G3 X165.118 Y62.59 I-4.33 J-2.5
N165 X165.118 Y38.99 I0 J-11.8
N170 X165.118 Y62.59 I0 J11.8
N175 X160.266 Y61.547 I0 J-11.8
N180 X157.347 Y57.487 I2.056 J-4.558
N185 G1 X156.848 Y52.512
N190 M5
N195 X44.841 Y55.743
N200 G0 X44.841 Y55.743
N205 M3 $0 S1
N210 G1 X42.341 Y60.073
N215 G3 X38.011 Y62.573 I-4.33 J-2.5
N220 X38.011 Y38.973 I0 J-11.8
N225 X38.011 Y62.573 I0 J11.8
N230 X33.16 Y61.53 I0 J-11.8
N235 X30.24 Y57.47 I2.056 J-4.558
N240 G1 X29.742 Y52.495
N245 M5
N250 G0 X-7.53 Y66.216
N255 M3 $0 S1
N260 G1 X-3.2 Y68.716
N265 G3 X-0.7 Y73.046 I-2.5 J4.33
N270 G1 X-0.7 Y101.6
N275 X-0.7 Y102.3
N280 X203.2 Y102.3
N285 X203.9 Y102.3
N290 X203.9 Y38.1
N295 G2 X165.1 Y-0.7 I-38.8 J0
N300 G1 X38.1 Y-0.7
N305 G2 X-0.7 Y38.1 I0 J38.8
N310 G1 X-0.7 Y73.046
N315 X-0.7 Y78.046
N320 G3 X-3.2 Y82.376 I-5 J0
N325 G1 X-7.53 Y84.876
N330 M5
N335 M5
N340 G0 X0 Y0
N345 M30

Trav328

10 Oct 2024 01:36

Replied by Trav328 on topic linuxcnc 2.9.2/2.9.3 toolchanger problem

linuxcnc 2.9.2/2.9.3 toolchanger problem

Category: Advanced Configuration

Hawkes2 , It was that something had gone wrong with the update , even remkving linuxcnc and reinstalling wouldent do it , I had to do a full reinstall of debian 12 with linux cnc 2.9.2 , once I verified everything was working I did the update again and now it's back to working.

PCW

10 Oct 2024 00:53

Replied by PCW on topic Strange problem with axis GUI

Strange problem with axis GUI

Category: AXIS

I would not expect following errors to be GUI related but rather setup or latency related
can you post your hal/ini files?

mBender
mBender

10 Oct 2024 00:45

Replied by mBender on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

Hey, I am trying to get my hand around this. I have started the Docker container in a Virtual Machine. The GUI Starts, but as soon as I click on a board and want to save the config I get the following error.

/riocore$ sudo docker logs -f riocore
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight_i5-v7_0/board.json
WARNING: no plugins configured
ERROR: module/slot is not compatible
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1235, resource id: 9178654, major code: 40 (TranslateCoords), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1524, resource id: 9179451, major code: 40 (TranslateCoords), minor code: 0
ERROR: module/slot is not compatible
ERROR: module/slot is not compatible
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
WARNING: no plugins configured
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 683, resource id: 8648058, major code: 40 (TranslateCoords), minor code: 0
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
ERROR: MISSING PIN CONFIGURATION for 'bit' (bitin)
#update w {'type': 'bitin', 'pins': {'bit': {'modifier': [], 'pin': 'w'}}, 'signals': {'bit': {'display': {}}}}
#update we {'type': 'bitin', 'pins': {'bit': {'modifier': [], 'pin': 'we'}}, 'signals': {'bit': {'display': {}}}}
#update w {'type': 'bitin', 'pins': {'bit': {'modifier': [], 'pin': 'w'}}, 'signals': {'bit': {'display': {}}}}
#update {'type': 'bitin', 'pins': {'bit': {'modifier': []}}, 'signals': {'bit': {'display': {}}}}
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 590, resource id: 8664042, major code: 40 (TranslateCoords), minor code: 0
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
ERROR: MISSING PIN CONFIGURATION for 'bit' (bitin)
#update 2 {'type': 'bitin', 'pins': {'bit': {'modifier': [], 'pin': '2'}}, 'signals': {'bit': {'display': {}}}}
#update down {'type': 'bitin', 'pins': {'bit': {'modifier': [], 'pin': '2', 'pull': 'down'}}, 'signals': {'bit': {'display': {}}}}
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1102, resource id: 8686578, major code: 40 (TranslateCoords), minor code: 0
ERROR: MISSING PIN CONFIGURATION for 'step' (stepdir)
ERROR: MISSING PIN CONFIGURATION for 'dir' (stepdir)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1614, resource id: 8688081, major code: 40 (TranslateCoords), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2612, resource id: 8691031, major code: 40 (TranslateCoords), minor code: 0
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/OctoBot/board.json
WARNING: no plugins configured
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
WARNING: no plugins configured
#update d {'type': 'counter', 'pins': {'up': {'modifier': [], 'pin': 'd'}, 'down': {'modifier': []}, 'reset': {'modifier': []}}, 'signals': {'counter': {'display': {}}}}
#update d5 {'type': 'counter', 'pins': {'up': {'modifier': [], 'pin': 'd5'}, 'down': {'modifier': []}, 'reset': {'modifier': []}}, 'signals': {'counter': {'display': {}}}}
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1781, resource id: 8739807, major code: 40 (TranslateCoords), minor code: 0
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading board: /usr/src/riocore/./riocore/boards/Colorlight5A-75E/board.json
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
WARNING: no plugins configured
Traceback (most recent call last):
File "/usr/src/riocore/bin/rio-setup", line 3582, in save_config_cb
    self.save_config(self.config_file)
File "/usr/src/riocore/bin/rio-setup", line 3593, in save_config
    self.save_config_as()
File "/usr/src/riocore/bin/rio-setup", line 3574, in save_config_as
    name[0] = f"{name[0]}.json"
    ~~~~^^^
TypeError: 'tuple' object does not support item assignment

Displaying 20401 - 20415 out of 24288 results.

Time to create page: 0.646 seconds

All Categories
LinuxCNC
- LinuxCNC Announcements
- General LinuxCNC Questions
- Installing LinuxCNC
- LinuxCNC Documents
Configuring LinuxCNC
- Configuration Tools
- - StepConf Wizard
- - PnCConf Wizard
- Basic Configuration
- Advanced Configuration
- - ClassicLadder
- - EtherCAT
- HAL
- - HAL Examples
User Interfaces
- AXIS
- Gmoccapy
- Plasmac
- pyVCP
- GladeVCP
- Other User Interfaces
- - PathPilot
- QtPyVCP
- Qtvcp
GCode and Part Programs
- G&M Codes
- O Codes (subroutines) and NGCGUI
- - Mill Library
- - Lathe Library
- - Plasma Library
- CAD CAM
- - Post Processors
- - - Fusion 360
- - - MasterCAM
- - - MecSoft
- - NativeCAM
Hardware & Machines
- Computers and Hardware
- Driver Boards
- CNC Machines
- - Milling Machines
- - Turning
- - Plasma & Laser
- Pick and Place
- Additive Manufacturing
Other Stuff
- Show Your Stuff
- Forum Questions
- User Exchange
- Off Topic and Test Posts
- - BeagleBone
International LinuxCNC Users
- Français
- Español
- Deutsch
- Other Languages
- - Russian
- - Polski