I did just this and I’m all set up again.
Now to find some time to the the holey triangle callibration
1 Like
Can you do the holey calibration with WebControl?
I’m sure I can… just will take some time to do. I honestly haven’t been following the development much since I’ve been working on other things. It seems to be mature so I can start looking into it, but lots of stuff is going on in my RL atm and it will take time to get to it and get it done… Of course, someone else could work on it if they feel inclined 
4 Likes
I’ve pushed new dockers for webcontrol and webmcp with a number of QoL improvements. No support for holey calibration yet as I have to deal with conflicting firmware keys.
4 Likes
I’m noticing that tool changes don’t actually stop the process. It pauses for half a second and then just takes off again with the old tool in.
Here’s a snippet of the G-code
(1001)
(T1 D=19.05 CR=0 TAPER=90DEG - ZMIN=-2 - SPOT DRILL)
(T3 D=3.175 CR=0 - ZMIN=-5.953 - FLAT END MILL)
(T4 D=6.35 CR=0 - ZMIN=-5.953 - FLAT END MILL)
G0 G40 G90 G17
G21
G0 Z7.35
(TRACE1)
T1
M3 S4840
G0 X152.901 Y225.312
G0 Z2
G1 Z-2 F4623.
G1 X153.137 Y225.072 F400.
G1 X153.397 Y224.874
…
G1 X238.986 Y197.634
G1 X239.131 Y197.435
G1 Z2 F4623.
G0 Z7.35
(DRILL1)
M5
T3
M3 S10000
G0 X292.1 Y152.4
G0 Z2
G1 Z-5.953 F762.
G0 Z2
G0 X12.7
G1 Z-5.953 F762.
G0 Z2
G0 Z7.35
(2D CONTOUR1)
M5
T4
M3 S10000
G0 X-5.08 Y151.765
G0 Z7.35
G1 Z-2.953 F762.
G1 Z2 F3175.
G1 Z-2.953 F762.
G1 X-4.445
G1 X-3.81 F3175.
…
Can you try to edit the file and put the M5 and T3 commands on the same line and see if it gives the same results?
Unable to start webmcp after reboot.
Last evening everything was working fie ad I did some sample cuts. I had to reboot the Pi today to move the power cord to another outlet. After doing so, webmcp won’t start at all. Looks to me like it doesn’t appreciate something in the latest pull.
Here’s the output from journalctl -xe (which systemctl status recommends)
pi@maslow:~ $ journalctl -xe
May 13 10:41:14 maslow docker[904]: da37bd2a5530: Already exists
May 13 10:41:14 maslow docker[904]: 62d1ead54be7: Pulling fs layer
May 13 10:41:14 maslow docker[904]: 883758bf361a: Pulling fs layer
May 13 10:41:14 maslow docker[904]: 8eb1b0cc4875: Pulling fs layer
May 13 10:41:14 maslow docker[904]: f444dc1e378e: Pulling fs layer
May 13 10:41:14 maslow docker[904]: 5f9310f1f528: Pulling fs layer
May 13 10:41:14 maslow docker[904]: 5f9310f1f528: Waiting
May 13 10:41:14 maslow docker[904]: f444dc1e378e: Waiting
May 13 10:41:15 maslow docker[904]: 8eb1b0cc4875: Verifying Checksum
May 13 10:41:15 maslow docker[904]: 8eb1b0cc4875: Download complete
May 13 10:41:32 maslow docker[904]: 62d1ead54be7: Verifying Checksum
May 13 10:41:32 maslow docker[904]: 62d1ead54be7: Download complete
May 13 10:41:33 maslow docker[904]: f444dc1e378e: Verifying Checksum
May 13 10:41:33 maslow docker[904]: f444dc1e378e: Download complete
May 13 10:41:33 maslow docker[904]: 5f9310f1f528: Verifying Checksum
May 13 10:41:33 maslow docker[904]: 5f9310f1f528: Download complete
May 13 10:41:36 maslow docker[904]: 62d1ead54be7: Pull complete
May 13 10:41:58 maslow docker[904]: 883758bf361a: Verifying Checksum
May 13 10:41:58 maslow docker[904]: 883758bf361a: Download complete
May 13 10:41:58 maslow sudo[958]: pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl status webmcp
May 13 10:41:58 maslow sudo[958]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
May 13 10:41:59 maslow sudo[958]: pam_unix(sudo:session): session closed for user root
May 13 10:42:14 maslow sudo[967]: pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl status webmcp
May 13 10:42:14 maslow sudo[967]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
May 13 10:42:14 maslow sudo[967]: pam_unix(sudo:session): session closed for user root
May 13 10:42:30 maslow sudo[888]: pam_unix(sudo:session): session closed for user root
May 13 10:42:35 maslow sudo[980]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/systemctl start webmcp
May 13 10:42:35 maslow sudo[980]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
May 13 10:42:37 maslow docker[904]: 883758bf361a: Pull complete
May 13 10:42:38 maslow docker[904]: 8eb1b0cc4875: Pull complete
May 13 10:42:43 maslow systemd[1]: webmcp.service: Start-pre operation timed out. Terminating.
May 13 10:42:43 maslow dockerd[478]: time=“2019-05-13T10:42:43.871903762-04:00” level=error msg=“Not continuing with pull after error: context canceled”
May 13 10:42:43 maslow systemd[1]: Failed to start WebMCP.
– Subject: Unit webmcp.service has failed
– Defined-By: systemd
– Support: https://www.debian.org/support
– Unit webmcp.service has failed.
– The result is failed.
May 13 10:42:43 maslow systemd[1]: webmcp.service: Unit entered failed state.
May 13 10:42:43 maslow systemd[1]: webmcp.service: Failed with result ‘timeout’.
May 13 10:42:43 maslow sudo[980]: pam_unix(sudo:session): session closed for user root
Any thoughts?
hmmm… I’m not the docker guru, that’s @johnboiles… and I didn’t work on the pre-built image.
Regardless, can you try the following:
docker run -it -v $HOME/.WebControl:/root/.WebControl -v /var/run/docker.sock:/var/run/docker.sock -p 5001:5001 -e HOST_HOME=$HOME --network=host --privileged madgrizzle/webmcp
That’s the command I use to start webmcp on my development RPI.
That seems to have worked. Thanks!
Looks like we need to extend the timeout on the systemd unit for webmcp
I’ll try to push a new version this weekend with some tweaks (but have family in town for twins’ birthday)
I’ve added a page for PID tuning… would like some feedback to know if it works. My setup at the moment is not a standard Maslow so I don’t know if the results I’m seeing are correct or not.
I’ve also tweaked the “sled not keeping up” alarm and moved it to an alert… and when it happens, the stop button starts to “glow”. Click stop clears the alarm message.
1 Like
While you’re at it, I was thinking a Feed Forward algorithm would be nice. 
Sorry. I typed as I was thinking.
Nonetheless, I do think Feed-Forward content in the controller would be an improvement. This is something I have had on my mind for a while. The problem with feedback control is it operates on, requires, an error. In CNC, errors are a bad thing. Having cut out the Meticulous Z-Axis, I had some non-straight lines that should’ve been straight. The curvature was too tight to be mis-calibration. I believe it is related to PID controller error (Setpoint-Actual).
1 Like
I think he is just thinking of a screen in webcontrol to help configure the
existing PID parameters rather than making changes to the firmware (which would
be needed to deal properly with acceleratin and feed forward)
David Lang
P.S. any further thoughts on making the holey firmware use version +200 to make
it easy to differentiate it from stock?
1 Like
Sorry. I haven’t got to that yet. It is not a big change. Hopefully this weekend, but my parents are coming into town, so …
Correct.
First off, thanks to @madgrizzle, @johnboiles, @Joshua and @dlang among others for becoming the default “product support” for WebControl. I have read the entire thread (whew!) to try to answer my questions before I ask. I like to think I’m not a computer novice, but most of the programming stuff in this thread is waaay over my head (I learned Basic maybe 3 decades ago). So, with that said, here’s where I’m at:
I have my Maslow built and calibrated with the stock configuration under Ground Control. I have not yet cut any other pieces, including the final sled (which I hope to do soon). My first brand new RPi ever was delivered last week, so I am a complete Newb with that system and I need help. It is a RPi 3B+, and I have put it together and powered on. I have an old Samsung tablet that I intend to use over WiFi with WebControl.
Questions:
- When I image the SD card, do I wipe (reformat) all the stock stuff that came on the card (NOOBS) and start with a clean install of the MaslowPi Lite image? Do I need to do any other setup of the RPi before I load Maslow image? Is it a simple copy/paste to the SD?
- When I add groundcontrol.ini to the SD card, does it go in a specific folder? Related, when the instructions say put it on the computer you are using to communicate with WebControl, does that mean the Pi (Maslow Control) - or the Tablet (or laptop, desktop, etc, where you view WebControl)
- Does the MaslowPi Lite image automagically set up the WiFi connection?
- I am completely unfamiliar with “add your wpa_supplicant/ssh files to boot”. Can someone please clarify? How do I do this? Is this the WiFi connection referenced in Question 3?
Any help will be greatly appreciated. Perhaps my questions can lead to clarifications in the GitHub WebControl/GettingStarted, particularly for those of us just starting with RPi’s and wireless access.
Thanks!!!
–Jim
1 Like
You need to burn the prebuilt image to the SD card… I think I use etcher for it. I don’t think need to reformat it first. Folow this, jumping to Step 2 since you have the pre-built image already.
- When I add groundcontrol.ini to the SD card, does it go in a specific folder? Related, when the instructions say put it on the computer you are using to communicate with WebControl, does that mean the Pi (Maslow Control) - or the Tablet (or laptop, desktop, etc, where you view WebControl)
You don’t need to add it to the SD card. When you run webcontrol for the first time it tells you about importing groundcontrol.ini. Go to Actions, Import groundcontrol.ini and it will give you the ability to upload. It’ll then process the upload and hopefully import all the settings… Warning, settings still give me a fit from time to time… I know there’s still bugs there.
Hopefully answered in response to first question.
1 Like
Thanks so much for the near immediate response! I wasn’t expecting anything so quickly!
Quick search revealed https://www.techspot.com/downloads/6931-etcher.html , is that what you use?
I will proceed and let you know how everything turns out, possibly later this evening (real world work is pending)
Thanks again,
Jim
I downloaded from:
I believe there may be some form of user error in flashing the device. Etcher seems to be working fine (it completes the flash), but I may have messed up the formatting or something on the SD. Etcher says “1 Failed device”, and the popup balloon window says “\.\PhysicalDrive2: Source and destination checksums do not match: 4f226e2da8b33f3f!==1e24172c9389a5aa”
Any thoughts on how to recover? I feel like my posts need to be in the “No Judgement” section!
–Jim