Thank you! That was much easier than I anticipated. And I even got the Warning from Webcontrol that the Arduino is running a newer version than included with Webcontrol, so the update is confirmed. Now to swap back to Makerverse…
Still no joy - I updated to Holey 51.28 via Webcontrol. Webcontrol complained when it detected that the firmware was then newer than what is shipped with Webcontrol - confirming that the Arduino took the upgrade. However, when I booted back to Makerverse and tried connecting, I still get stuck at the Querying Hardware step.
How are the rx/tx leds on the Arduino reacting? Not sure if you can see them if a motor-shield is on top. Perhaps from a slight angle looking from between the arduino power socket an the usb-socket.
It would interest me if you also see them first flickering and then both freeze light up.
Would you check if you get clear readable position reports as well? Cancel the cat with ‘Ctrl+c’.
Note go to the Settings → General tab and make sure Prereleases are selected so that the auto-updater knows to use the beta channel. You can check version number in the About tab. If you don’t get the auto-updated version after restarting (sudo systemctl restart makerverse
), you may have an old version of the launch script. You just need to update bin/launch
from the repository (git pull
, download the file, whatever is easiest for you). I don’t expect the launch script to keep changing, but for now I’m still tweaking/fixing things.
@Bob_Craig @Gero I just published version 1.1.1-b, which I think should improve connection process. At the very least, it should tell you what it’s seeing. I may have also found why it failed for you.
@Alric_O_Connor this version also has the new Raspberry Pi image, though I haven’t been able to flash and test yet. I’m a bit busy today, and I’m on DSL so it takes hours to download the images after the server builds them However I did just notice that the download size shrunk from 1.3GB to 600MB, which is nice as long as it still works…
This is a failure message. You should not be calling it in that manner. Please run exactly this line:
bin/server install
The way you called it will not work.
edit I can see that the problem was, indeed, the permissions. The chmod
command from my last post will make the command from this post (which is also the README command) work. I will fix this in the git repository so others do not need to do it.
This is not stored after reboot of the Pi. I’m using the SD-card image from the releases. Will the update work with that? The ‘About’ is confusing with the top and bottom line.
Edit: Closing makerverse and on second attempt the "query screen’ will not show up any more until I unplug the arduino (then i get a new port) or i reboot the Pi.
I will flash and test. I have some time and spare SD cards
The not storing part is odd. Can you look at the ~/.makerverse
file on the Pi and make sure it includes the line "prereleases": true,
?
Hm, looks like you’re still on version A. It seems to not notice that B > A, since the check says that B is the latest but you have A, but it thinks you have the latest. Can you please update your bin/launch
script? Just ssh into the Pi and:
cd makerverse
sudo rm -rf bin/launch
wget https://raw.githubusercontent.com/makermadecnc/makerverse/master/bin/launch -O bin/launch
chmod +x bin/launch
Then sudo systemctl restart makerverse
.
You can also look at the logs when it launches, journalctl -xe
should show that it launches with makerverse/core:prerelease
(not latest). And the about screen should show #176 (or higher) at the end.
Is not in the .makerverse. I copied the example and just edited the port and baud.
Does it go under “workspaces”: ?
Success! I’m back in business with the second part. Thank you! RPi 4 arriving end of Sep.
Re: update ti install service. Excellent. I’ll try that in a bit
Re: New image. user name/password (pi/raspbian) not working. tried on the console and SSH
@Alric_O_Connor do you have a screen attached to the Pi? SSH would not work for me until I changed the default password on the Pi itself.
This is the new OS, Raspberry. So, the new password is raspberry.
running bin/launch now
Great. I did just get a successful boot on a RPi4 w/ 2GB. It seemed to take longer than normal and did a few reboots before it was fully up and running,
No, under state
, like this:
"state": {
"checkForUpdates": true,
"prereleases": true,
But it’s concerning to me that it didn’t save. Can you please verify that once the launch script is updated it does save between restarts?
Everything seems to be working. I had to use chmod 777 on ‘bin/service’ and bin/build-service.sh
Just need to connect back up to the Maslow
Good work and fast!
Great! I’m also working on a pre-built image based upon the full Desktop version of Raspbian, that will automatically open to a nice tablet-friendly kiosk page so you can control your machine.
Here’s a pic of my setup. I built this laser engraver last week and am controlling it with Makerverse. The shopvac, etc. are on relays connected to the GPIO pins, so Makerverse can turn them on/off.
My .makerverse file is not being updated at all. I’ll share a screenshot to illustrate. I checked the “Prerelease” checkbox and did Save Changes. I think opened ~/.makerverse in the text editor. As you can see, the settings haven’t been written. In fact, the file hasn’t been touched since I wrote the image.
Your screenshot strikes me as odd. Was it taken from the same computer that is running makerverse? You appear to be editing a file on the local computer, but connecting to a remote instance of makerverse. In the case of the raspberry pi, you must first SSH into the computer and edit the file located there (not a file on your laptop).
I am VNC’d to the RPI from my mac. The screenshot is of the VNC viewer. Makerverse, the browser, and text editor are all running local on the RPI.
Oh, shoot. facepalm. I forgot to update something from .cncrc
to .makerverse
.
The bin/launch
script was just updated again.
cd makerverse
sudo rm -rf bin/launch
wget https://raw.githubusercontent.com/makermadecnc/makerverse/master/bin/launch -O bin/launch
chmod +x bin/launch