Advanced Search

that should fix it, if the parameters are not listed in the var they are volatile which is why it works if you enter in the current running instance but doesn't work on restart as the volatile parameters are dumped on exit.  adding in the parameter to the file converts it to persistent!  and will store through restarts.  be aware that if you create a new var file and they are zeroed out, you must renter or run the parameter update via the button in the ui for each section to update the parameter settings and resynchronize. this should never become an issue unless you corrupt your var file or copy a different var in for some reason.  just a heads up on it though!

Thanks for a quick reply!

I updated the configuration, copied over the subroutines and python folders but I missed the var file. I'll update it and report back.

probe basic release you are now on requires the latest subroutine files be copied over as the method of which the parameters are stored has been changed, they are now stored in the var file and the var parameters must also be added in the var file. run a comparison of the updated sim config folder for the var file to show what lines must be added.

there should have been a white notes screen with this documented on requiring changes when you first started probe basic. change notes will always be posted there for releases requiring users to make changes to their configs.

all parameters required for the latest probe basic version are listed here:

kcjengr.github.io/probe_basic/probe_basic_parameters.html


and to see what files may require editing see the configurations docs here:

kcjengr.github.io/probe_basic/machine_config.html

Update: I've tryied not disabling the servos on E-Stop, they jerk anyway. My guess is that the tuning is probably constantly applying some torque and it gets released as soon as the loop stops

PCW wrote:

MPG1-A 7I96S IN0
MPG1-B 7I96S IN1
MPG2-A 7I96S IN2
MPG2-B 7I96S IN3
GND 7I96 IN COMMON

This does mean the other 7I96S inputs are sinking inputs
(pull high to activate)

quick sanity check, first time looking at the 7i96s, if an MPG is connected to IN1,2 and is a 5v mpg, do the remaining inputs need to be 5v also or can they be 24v? ie is mixing voltages ok here?

      HiI am running on Bookworm and trying to setup QTPlasmaC. My repository is pointed at builsdbot2.highlab.com as the master on buildbot.linuxcnc.org seems to be broken with no release information.This is the error I get.

Change end = 60.00001 to end = 100.00001 and it generates a 198MB file that also loads in a second and runs fine. So the key slowdown is trying to load a file that size into a QPlainTextEdit. I assume but have not tested that the plotter will cause it to be very slow to load.



JT

I created a Flex GUI without a gcode preview or the plotter and it loads and runs a 118MB file with no problems.

I created a test file with this bit of python code
JT

I recently did an upgrade of Probe Basic and LinuxCNC, here are the versions I upgraded from and to.

linuxcnc-uspace/linuxcnc 1:2.9.3 amd64 [upgradable from: 1:2.9.2]
python3-qtpyvcp/stable 4.1.2 all [upgradable from: 4.0-124.dev]
python3-probe-basic/stable 0.6.0 all [upgradable from: 0.5.3-219.dev]

After doing this upgrade and updating the corresponding Probe Basic configuration files I've come across an odd error relating to probing.

When I try to do any probing I get the following error message even though I already have to correct tool loaded.

 

 

If I re-enter the value "1" in the "Probe tool" field under "Probing parameters" everything works again until I restart Probe Basic.

here, check over all of your hal for duplications, a realtime component must only be loaded once in a single hal file, preferably the main hal since it is loaded first.

 

[qtpyvcp.app.launcher][[36mINFO[0m]  Loading POSTGUI_HALFILE: /home/cnc/linuxcnc/configs/Black_Phanter/postgui.hal (launcher.py:98)
not: already exists

not
^^^ already exists, looks like maybe you are trying to load it twice in different locations

Sorry forgot to clarify, from sd card to archive image.

[begin_off_topic_rant]
I can't stand wearing jeans or any long pants, why they insist we wear long sleeve shirts and long pants is the Aussie summer is beyond me, then they have a big song & dance about heat stress and keeping liquids up.

Funny thing the shunters on the rail said long pants were a safety issue and dont have to.
And don't get me started on having a ruptured disc diagnosed as a pulled muscle.
[end_off_topic_rant]

are you using sudo ??? do not !

go into the Gateware folder:
and type make:
then type (to check again):
I am really at a loss

Well after finally working out my chinese dev board was dead, second one that has failed, I loaded a Numato Mimas Spartan 6 board with 7c81 firmware modded to suit and can confirm RPi5 communicates. To make things more fun the CE0 line on my Pi is not playing so had to swap over to CE1.

So after 12 months of bitching & carrying on I'm a happy camper.

Now time to design & build some interface boards. Yay!

Quick update, the Chinese dev board is not at fault, it was the usb-blaster programmer I was using (was constantly incorrectly identifying the flash chip and programming the sram had issues as well), switching to a FT2232 based programmer allowed resuming of programming the above mentioned board. No need to design interface boards.

With regards to the "firmware=hm2/7c81/G540X2.BIT" this is not required as the 7c8* & 7i* boards have the firmware programmed into flash that retains the firmware during power off. The firmware is programmed once and only reprogrammed when you require a new configuration.

So I can run gw_sh from anywhere, I also edited my .bashrc to make the PATH permanent.
Here is the terminal text, it is still saying it cant see the gowin path, interesting the first line saying XDG_RUNTIME_DIR is not set, I have no idea what that is but it doesn't sound good...

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
loading config: riocore/configs/TangNano9K/config.json
loading board: /home/gus/riocore/./riocore/boards/TangNano9K/board.json
rm -rf rio.fs rio.json rio_pnr.json rio.tcl abc.history impl
gw_sh rio.tcl
make: gw_sh: No such file or directory
make: *** [Makefile:34: impl/pnr/project.fs] Error 127
loading: riocore/configs/TangNano9K/config.json
loading board setup: TangNano9K
loading toolchain gowin
writing gateware to: Output/TangNano9K/Gateware
!!! gateware changed: needs to be build and flash |||
WARNING: can not found toolchain installation in PATH: gowin (gw_sh)
  example: export PATH=$PATH:/opt/gowin/IDE/bin
writing linuxcnc files to: Output/TangNano9K/LinuxCNC
rm -rf rio.fs rio.json rio_pnr.json rio.tcl abc.history impl
gw_sh rio.tcl
make: gw_sh: No such file or directory
make: *** [Makefile:34: impl/pnr/project.fs] Error 127