XY_Offset
ASO Keyword Dashboard
Tracking 139 keywords for XY_Offset in Google Play
XY_Offset tracks 139 keywords (no keywords rank yet; 139 need traction). Key metrics: opportunity 71.2, difficulty 44.5.
Find the XY offset per toolhead or Z-probe for Klipper
Tracked keywords
139
0 ranked • 139 not ranking yet
Top 10 coverage
—
Best rank — • Latest leader —
Avg opportunity
71.2
Top keyword: minimum
Avg difficulty
44.5
Lower scores indicate easier wins
Opportunity leaders
- 64.8
minimum
Opportunity: 74.0 • Difficulty: 43.8 • Rank —
Competitors: 869
- 65.7
moves
Opportunity: 74.0 • Difficulty: 45.0 • Rank —
Competitors: 926
- 62.6
colored
Opportunity: 74.0 • Difficulty: 40.8 • Rank —
Competitors: 540
- 65.4
print
Opportunity: 74.0 • Difficulty: 46.0 • Rank —
Competitors: 583
- 62.6
android phone
Opportunity: 74.0 • Difficulty: 59.9 • Rank —
Competitors: 516
Unranked opportunities
minimum
Opportunity: 74.0 • Difficulty: 43.8 • Competitors: 869
moves
Opportunity: 74.0 • Difficulty: 45.0 • Competitors: 926
colored
Opportunity: 74.0 • Difficulty: 40.8 • Competitors: 540
print
Opportunity: 74.0 • Difficulty: 46.0 • Competitors: 583
android phone
Opportunity: 74.0 • Difficulty: 59.9 • Competitors: 516
High competition keywords
make
Total apps: 325,888 • Major competitors: 20,137
Latest rank: — • Difficulty: 57.5
find
Total apps: 310,056 • Major competitors: 17,818
Latest rank: — • Difficulty: 58.3
like
Total apps: 291,639 • Major competitors: 22,623
Latest rank: — • Difficulty: 60.6
using
Total apps: 220,824 • Major competitors: 12,059
Latest rank: — • Difficulty: 56.7
start
Total apps: 203,549 • Major competitors: 13,115
Latest rank: — • Difficulty: 56.1
All tracked keywords
Includes opportunity, difficulty, rankings and competitor benchmarks
| Major Competitors | |||||||
|---|---|---|---|---|---|---|---|
| focus | 70 | 100 | 51 | 76 61,004 competing apps Median installs: 855 Avg rating: 4.1 | — | — | 1,989 major competitor apps |
| internal | 73 | 100 | 44 | 67 16,981 competing apps Median installs: 1,070 Avg rating: 3.9 | — | — | 613 major competitor apps |
| make | 65 | 100 | 57 | 88 325,888 competing apps Median installs: 2,543 Avg rating: 4.0 | — | — | 20,137 major competitor apps |
| phone | 67 | 100 | 60 | 83 153,671 competing apps Median installs: 3,558 Avg rating: 4.0 | — | — | 9,548 major competitor apps |
| via | 68 | 100 | 53 | 81 115,591 competing apps Median installs: 1,831 Avg rating: 4.0 | — | — | 4,539 major competitor apps |
| within | 68 | 100 | 51 | 80 102,272 competing apps Median installs: 1,538 Avg rating: 4.0 | — | — | 4,028 major competitor apps |
| clean | 70 | 100 | 49 | 75 49,244 competing apps Median installs: 1,282 Avg rating: 4.0 | — | — | 2,281 major competitor apps |
| used | 68 | 100 | 54 | 81 115,656 competing apps Median installs: 3,163 Avg rating: 4.0 | — | — | 5,072 major competitor apps |
| image | 70 | 100 | 50 | 76 56,441 competing apps Median installs: 3,414 Avg rating: 4.0 | — | — | 3,273 major competitor apps |
| using | 66 | 100 | 57 | 85 220,824 competing apps Median installs: 2,910 Avg rating: 3.9 | — | — | 12,059 major competitor apps |
| find | 65 | 100 | 58 | 87 310,056 competing apps Median installs: 2,793 Avg rating: 4.1 | — | — | 17,818 major competitor apps |
| rate | 70 | 100 | 47 | 75 50,671 competing apps Median installs: 3,191 Avg rating: 4.1 | — | — | 2,295 major competitor apps |
| added | 71 | 100 | 51 | 73 41,413 competing apps Median installs: 4,600 Avg rating: 4.0 | — | — | 2,592 major competitor apps |
| speed | 70 | 100 | 53 | 76 58,547 competing apps Median installs: 4,754 Avg rating: 3.9 | — | — | 4,940 major competitor apps |
| move | 70 | 100 | 51 | 75 50,455 competing apps Median installs: 3,048 Avg rating: 4.0 | — | — | 3,402 major competitor apps |
| start | 66 | 100 | 56 | 84 203,549 competing apps Median installs: 2,650 Avg rating: 4.0 | — | — | 13,115 major competitor apps |
| run | 70 | 100 | 51 | 74 45,233 competing apps Median installs: 3,886 Avg rating: 4.0 | — | — | 3,647 major competitor apps |
| minimum | 74 | 100 | 44 | 65 11,724 competing apps Median installs: 6,053 Avg rating: 4.0 | — | — | 869 major competitor apps |
| moves | 74 | 100 | 45 | 66 13,506 competing apps Median installs: 2,563 Avg rating: 4.0 | — | — | 926 major competitor apps |
| tools | 69 | 100 | 51 | 77 67,904 competing apps Median installs: 1,425 Avg rating: 4.0 | — | — | 3,453 major competitor apps |
| colored | 74 | 100 | 41 | 63 8,580 competing apps Median installs: 2,906 Avg rating: 4.1 | — | — | 540 major competitor apps |
| always | 67 | 100 | 53 | 82 141,560 competing apps Median installs: 1,760 Avg rating: 4.1 | — | — | 6,534 major competitor apps |
| like | 65 | 100 | 61 | 87 291,639 competing apps Median installs: 4,548 Avg rating: 4.0 | — | — | 22,623 major competitor apps |
| player | 70 | 100 | 52 | 75 51,506 competing apps Median installs: 5,337 Avg rating: 4.0 | — | — | 4,352 major competitor apps |
| know | 67 | 100 | 54 | 82 132,786 competing apps Median installs: 2,074 Avg rating: 4.1 | — | — | 6,049 major competitor apps |
App Description
Find the XY offset per toolhead or Z-probe for Klipper
My 3D printer has 2 toolheads, a 3dTouch Z-Probe and runs Klipper.
kTAMV, for Klipper, failed sometimes to detect the nozzle on my printer or the offsets were just off. Sometimes its caused by a not clean nozzle but a new, clean, dark colored nozzle also failed. Its not always clear why it went wrong. Its not possible to manually select a detection method or to tweak the parameters of the used methods. The detection methods are global and not per extruder.
This app, minimum Android 8.0+ (Oreo), uses OPENCV's blob, edge or hough circles for nozzle detection. Select None (no nozzle detection) or one of the 6 nozzle detection methods. Per extruder the selection and preparation method can be selected manually. But an automatic find "Find 1st fit" is also possible. This performs a 'brick' find, through the preparation and then detection methods, until the 1st solution with only 1 blob detection. When the found solution is confirmed during a number of frames the find stops. With "Find continue" the blob detection is forced to continue with the next method or preparation method. It now includes a kind of microscope-camera-moved-detection.
Almost all parameters can be tweaked, most of them per extruder. There is ample opportunity to screw image preparation and/or nozzle detection up.
If you don't have an Android phone you can run the app from your home computer using an Android app player like Blue Stacks, LDPlayer, or other alternatives.
Note: The app could be a heavy CPU load and memory consumer for your phone. The app will drop camera frames depending on the speed of the phone. Within Klipper the webcam frame rate can be set, probably for internal usage in Klipper, but via the network the app still gets the full frame rate (in my case ~14 fps) of the camera.
I use microscope cameras with USB cable (check its height before buying, the USB cable adds 4-6 cm).
Before you start:
- set all gcode offsets to zero in the Klipper configuration file
- clean all nozzles of any filament particles
- retract the filament, per toolhead, 2 mm so that the filament is not visible as a blob in/on the nozzle
- make sure the microscope camera has a solid pedestal and does not move due to vibrations when the toolhead/bed moves (via the USB cable !!).
I had to 3d print a pedestal, added thin rubber pads to its bottom and pin down the USB cable to the bed before it was stable.
- home all axes before you position the camera on the build plate.
You will have to 'lower' the buildplate before the camera will fit.
Manually adjust the focus of the camera.
Pin the USB cable to the build-plate to prevent very tiny movements !!!
- Select a reference extruder from which the other extruder offsets will be calculated.
If applicable, start with the extruder which has the Z-probe attached too it.
- Note: 'dark' nozzles are much more difficult to detect
