The position error reporting has been thoroughly tested, until I realized that ‘Wipe Setting’ turns the Fake_Servo off 
Feature request: Allow for the B99 ON to be accepted in the console.
Makerverse v1.1.1 [c] #199 looks great so far (ubuntu and macos). Settings are stored.
What are the values for top and bottom feed ($38 chain over sprocket)?
OK,got it. From the firmware bottom feed should be 2.
Coming soon!
Glad to hear it. Yeah, 2 is the correct value for “Chain off Bottom.” Let me know how calibration goes!
$38 = 2 gives an error
is the bottom feed setting $80? That is what it was labelled as before.
That may be why my calibration is so far off.
Which error? Where?
Chain over Sprocket is $80 on the Due, and should default to 2 (chain off bottom) with the firmware I provided. On the Mega, it is $38 and may default to 1 (chain off top) if I’m reading the code correctly.
As a note to myself, looks like I need a “build config” calibration tab for:
+1 to supporting the MetalMaslow rectangular sled.
I have both metal and maker sleds and I have both due and mega and large and small frames.
I didn’t realize $38 was for the classic. I tried it on the Due. $80 is the command for the due. It accepted it and then I attempted to recalibrate the 4x4 system with the due and metal sled with linkage. I think the issues with my system stem from a short z axis cable because of controller placement: fixed, the slack chain routing - adjusted, and the linkage. can’t do anything about that right now. After moving things a bit to eliminate interference, it is getting closer. Also I fat fingered the workspace distance from the beam by an inch, so that really screwed things up. It looks much much better now. all the holes are between 18 and 35 mm from the “ends” of the board. EDIT: calibration results:
That sounds promising! The target is 25.4mm (one inch), so you’re within 10mm tolerance. This isn’t great yet, but it’s well within calibration’s capabilities to get you to “perfection” IME.
Those calibration results are looking pretty good! Avg. error distance under 2mm and max under 4mm is nice; 1mm/2mm is about as good as I’ve seen.
yeah, I’m convinced it was the top beam measurement that hosed it all up to begin with.
Makes sense! FWIW, using an 1/8" bit is the only way I’ve gotten sub-1mm results. A second round of calibration may still help a little though.
Let’s see some cuts, now 
New build, #200, is uploading now (ETA ~30m). It adds support for some of these more advanced settings, including “chain under sprocket” and “Metal Maslow” sled. I’m about to go calibrate my new Metal Maslow (first time using a 12’ beam and 15’ chains). I believe the settings I will be using are:
I also had to edit my Z steps per rev. to 328 for my particular build.
Selecting the MetalMaslow sled in edge calibration uses the values provided by @Metalmaslow .
Quick tip for anyone who wants to turn on/off router, shop-vac, etc. automatically:
sudo raspi-config (interface options)sudo systemctl enable pigpiod and sudo systemctl start pigpiod
Example (GPIO #5 is my pin):
Following disconnect at the end of a calibration run, I am frequently running into an “abort during cycle error”. Approximately 50% of the time this is accompanied by the Machine Setting “Height” resetting to less than 12 in. The error can always be cleared by adjusting the height back to 48.
I think I just had this happen to me. I believe it was because the sled was moving while I tried to apply the calibration results. I think that I need to create a better UI for applying the settings… stopping the machine, blocking input, waiting for them to be confirmed, etc.
The bit about the height changing is strange, though. If you disconnect and reconnect, is the height still wrong? If so, can you keep an eye on the console and look for something setting the height to that value (i.e., 0.65) the next time it happens?
But this is not triggered by the M3 and M5 commands in the g-code, correct?
Correct. I’m not sure what pins we’d want to use in the Arduino shield, yet. I suppose I could “hack” Makerverse to relay the M3/M5 commands into an event so that you could achieve this…
On the Mega with Holey Firmware and TLE shield is seems to be pin 40=Aux1, that depending on $17 moves a servo (was planed for an actual wall swith), or 2 types of relay.
Is there a way from g-code to RPi GPIO without having it programmed in the firmware?
Still dreaming of spindle speed control, but it’s not done in the Holey firmware, so was hoping for a workaround using the PWM pin on the Pi.
Status update from your worst and most unreliable beta tester: 
On Friday I brought my Arduino setup inside and had everything running near my PC. I have the Rpi4 with 4GB RAM now. I flashed the cnc_ctrl_v1.in.hex file (after renaming it to Holey 58.28). Initially, Makerverse said build #197 and V 1.1.1 (b). It was talking to the Arduino and I was able to make a workspace.
This morning (aprx 2 hours ago) I check on everything again and reboot the Rpi. Makerverse updated to Build #201. Error about incorrect firmware is still not showing up. I move the rig out to the Maslow and get everything plugged in. Makerverse boots up fine and connects, I’m able to access remotely and it talks to the Arduino. I enter the workspace again and the “incorrect firmware” message is back. I attempt to run calibration but the dialog box won’t accept “next” after entering my values (all I changed was from top to bottom for chains). Calibration box, all tabs, will not accept any of my input or move to next tab. I close it out and hit unlock. I receive the “needs calibration” window and close it out. I tried my best to find where calibration lives and open it back up again, no luck.
Maslow now moves with the control panel but everything is inverted. At first, all move arrows (except Z) make sled move diagonally right downward. Check motor cables, one was slightly loose. Now, move arrows move sled but completely inverted to arrow direction. Hit Z axis control and left and right motors both start moving and will not stop.
I reset the Rpi and Arduino and tried the move controls again, same result. I also tried my best to get the calibration dialog to come back up, it will not.
Would it help to send an error report? Will that send you the error data you need?
Version should be this now. Makerverse v1.1.1 [c] #203
Inverted? Check the setting chain over sprocket $38 (1=top/2=bottom
I get that once on every day new connect. Closing the port and opening it solves it, or clicking the (i) button and use the refresh from the ‘controller settings’
Hm, 3 hours ago it was #200? This gut is updating faster then i can say g-code…
I had to install pigpio with
>sudo apt-get install pigpio
and then it worked. I connected a tricolor LED to pins 19 (red), 26 (green), 13 (blue), so I run .sh files for colors on events.
~/green.sh
~/blue.sh
~/red.sh
~/violet.sh
~/white.sh
~/cyan.sh
all make the led a different color by controlling which of the 3 leds are on or off at the same time. Thanks for the echo command. it works awesome.
