ContextI built myself a button box, tactile buttons, d1 mini, mqtt. Then there's a daemon subscribed to that topic, adding the actual button actions. Lot's of fun with it, OctoPrint is so open for that.
Lighting and job controls were easy, now bed level measurement.
I really like the GCODE I have for that in the bed visualizer plugin so I copied that lines and send them to the api as commands
Works like a charm, really feels like the printer+octoPrint+the remote and programing are a robot. I click a button and the printer turns on, Octoprint connects to it, my program gets all the info about printer state and job state, sends the list of GCODEs , everything get's executed, fine. But!
I'm a bit surprised, it's the very same sequence of GCode whether I run it through the blv's 'update mesh now' or from the GCODE sent by my script to octoPrint. M155 S90 and all. G29 takes ages to complete, true. Do I have to configure OctoPrint for it, and where?
When I set a comment in front of "M155 S90", the error does not happen.
But why does that line (and the significantly less temperature reportings) irritate octoPrint when it passed that via the api while it stays relaxed when the call came from the plugin?
Thanks for looking into it!
You are right, just checked and the same thing happens when I call it through the plugin. Without diving into Marlin I guess it's some hard coded minimum over there.
The other thing is that the whole procedure runs ok with "M155 S90" commented out and I believe plugin author recommended it out an abundance of caution. Serial traffic might interfere with the measurements.
I set it to M155 S30 and that gave me temp. reports every 30sec. But the final error message came as well.
I have an external sound card which mostly works fine, except that when its first plugged in, or when I turn on my laptop, the volume gets set to 100%. That is, the overall system volume, as shown in the sound indicator.
What I'm looking for is a terminal command that will set that volume to 50%, so that I can run it on login and not have to worry that the first audio I play is going to blare out at me if I forget to turn the volume down. What commands allow you to change that volume, i.e. the one in the sound indicator?
I've poked around in gsettings and dbus, but have been unable to find anything that would let me set the system volume like that. I do know about alsamixer, but that's not the solution I'm looking for, since that doesn't allow me to change the volume using the sound indicator or my laptop's multimedia keys.
Depending on your soundcard, levels may be different than mine, but you can use alsamixer in the terminal in order to check which levels and which features in your sound card you can call in a command to set the volume as you wish.
In my example, with my principal sound card (I have 2: the embedded and a PCI audio card), levels are from 0 to 100, this way I can change the volume of a desired input/output in my soundcard by dropping in a terminal the next command:
In order to gather information related to your mixer controls, drop the amixer command with no parameters and you will get a list. Or indicate which audio device you wish to see a list of controls with amixer -c X (where "X" is the number of your audio device).
Create another objective called "previous_value" or something like that and copy the value from the first objective (sound) to the one you just created. If the first objective (sound) is higher than the second objective (previous_value), that means the score has increase
To set this up, place down one repeating and one chain command block (see the included screenshot for the command block layout) and set them both to always active and unconditional. Now paste these commands in (in order):
Could someone please assist me in what console command I would need to use to increase my gamestage? I want to test out some ideas on a test world and don't want to have to just sit there and kill thousands of zombies to get it high enough. Any help would be greatly appreciated.
I'm pretty sure I saw there was a console command to force a blood moon to spawn, with an option to also force a particular gamestage. But I don't remember the command, so like theFlu said, type help in the console for a list of available commands.
I want to create a near 100% load on a Linux machine. It's quad core system and I want all cores going full speed. Ideally, the CPU load would last a designated amount of time and then stop. I'm hoping there's some trick in bash. I'm thinking some sort of infinite loop.
Repeat the command in the curly brackets as many times as the number of threads you want to produce (here 4 threads). Simple enter hit will stop it (just make sure no other dd is running on this user or you kill it too).
The idea is to calculate a hash sum from an infinite datastream (eg. /dev/zero, /dev/urandom, ...) this process will try to max out a cpu-core until the process is aborted.To generate a load for more cores, multiple commands can be piped together.
You can call that in a subshell and run in the background. Doing that $num_cores times should be enough. After sleeping the desired time you can kill them all, you get the PIDs with jobs -p (hint: xargs)
Using examples mentioned here, but also help from IRC, I developed my own CPU stress testing script. It uses a subshell per thread and the endless loop technique. You can also specify the number of threads and the amount of time interactively.
This asks for ps output of a 1-minute average of the cpu usage by each process, then sums them with awk. While it's a 1 minute average, ps is smart enough to know if a process has only been around a few seconds and adjusts the time-window accordingly. Thus you can use this command to immediately see the result.
awk is a good way to write a long-running loop that's CPU bound without generating a lot of memory traffic or system calls, or using any significant amount of memory or polluting caches so it slows down other cores a minimal amount. (stress or stress-ng can also do that if you either installed, if you use a simple CPU-stress method.)
It's a counted loop so you can make it exit on its own after a finite amount of time. (Awk uses FP numbers, so a limit like 2^54 might not be reachable with i++ due to rounding, but that's way larger than needed for a few seconds to minutes.)
I used perf to see what kind of load it put on the CPU: it runs 2.6 instructions per clock cycle, so it's not the most friendly to a hyperthread sharing the same physical core. But it has a very small cache footprint, getting negligible cache misses even in L1d cache. And strace will show it makes no system calls until exit.
The most "friendly" to the other hyperthread on an x86 CPU would be a C program like this, which just runs a pause instruction in a loop. (Or portably, a Rust program that runs std::hint::spin_loop.) As far as the OS's process scheduler, it stays in user-space (nothing like a yield() system call), but in hardware it doesn't take up many resources, letting the other logical core have the front-end for multiple cycles.
Have you ever wondered how to extend your root or home directory filesystem partition using LVM? You might have low storage space and you need to increase the capacity of your partitions. This article looks at how to extend storage in Linux using Logical Volume Manager (LVM).
The process is straightforward. Attach the new storage to the system. Next, create a new Physical Volume (PV) from that storage. Add the PV to the Volume Group (VG) and then extend the Logical Volume (LV).
Look at the picture below. The red line mark shows the original size of the root mount point. The xvdc disk is the new disk attached to it. Extend the root partition to make it 60G in size.
Next, you need to identify the Volume Group (VG) to which you are extending the new disk with the vgs command. Mine is called centos, and that's the only VG available currently on my LVM.
The lvs or lvdisplay command shows the Logical Volume associated with a Volume Group. Use the lvs command, and the Logical Volume you're trying to extend is the root, which belongs to the centos VG. As you can see above, you've already extended the VG. Next, extend the Logical Volume.
You can extend any other partition with the steps shown. You just have to ensure you're using LVM and know the partition you're extending. If you want to learn more about LVM, check out other articles from Enable Sysadmin by searching LVM.
The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. The content published on this site are community contributions and are for informational purpose only AND ARE NOT, AND ARE NOT INTENDED TO BE, RED HAT DOCUMENTATION, SUPPORT, OR ADVICE.
So, i know we can't increase the tether distance on xbox anymore, but can it be done by editing the game files on pc? I run a dedicated on PC for my friends on xbox with max level 300 dinos and stacks and such, so i know a little about changing the files. Hoping there was something for tether distance on non dedicated. The purpose of this is to be able to transfer from ark to ark with my friends without having to rent servers. I know that everyone will have to transfer all at once, but im fine with that. But the tether distance is just dumb.
I hate to be the one to tell you but no it cannot be done. In fact due to the windows 10 version just being the xbox version played via emulator any changes to the ini files would make it incompatible with crossplay. Unfortunately you will have to deal with the tether, only play one map at a time, rent a couple servers or find an unofficial with rates/stats that you and your friends enjoy.
Those things you have changed are in the values they give you to change. Tbh I was giving you facts so that you know your options rather than wasting hours trying to figure it all out, not overally interested in whether or not you believe its how it works at all.
3a8082e126