Zane, I am stuck in exactly the same place. I downloaded the 1.1.1 image earlier today, flashed it to a new 32gb SD card, booted the Pi with it, let it run for 30 minutes while everything got set up. Confirmed that I could access Makerverse and set up a User account. Then I powered down to relocate the Pi back on my machine and connect to the Arduino.
Connected to the machine, I get to the Create Workspace step. I select the port (ACM0) and baud rate (57600) and click Connect. I then am stuck at the same screen with the warning about querying hardware.
I have stopped at this point and can investigate if you have specific instructions to triage.
Also, while I created the User Account when initially setting up Makerverse, after shutting down, relocating, and booting again that User Account is no longer listed. I added it again. I will check to see if it persists on the next reboot.
For the Rules file, see my post a couple of hours ago.
I had to use ‘touch’ and edited the file with nano on the command line
No idea what happened to my last set up go round. Brand new image for the rPi (makerverse image doesn’t work with my Pi4 8GB) It won’t boot.
At least I get more practice running through the steps
touch creates the file, nano edits it. I made it with nano, but I didn’t see there was a resolution other than that and even after that, adding those lines still didn’t work, so maybe I need to give permission to the rule file… hmmm , I’ll try that… nope no go.
@Bob_Craig: the baud rate for the M2 due board is 38400 and the mega is 57600. You selected 57600 for the due and it won’t talk like that. Not sure if you can edit it or remove it and recreate it. Looks like permissions isn’t an issue, so good job on the progress. Fix that baud issue and you should be running.
I think I see what happened. You’ll note the second time you installed, there was a prompt to re-login. This was an important step. I should have told you to do that after installing Docker and before you tried to use bin/launch.
This was the step with the file that didn’t get edited. I just pushed an update to the README, so you should find both of these corrections I just metioned. In particular, look for sudo nano /etc/udev/rules.d/49-makerverse.rules
I need to make this error message better. I’m going to try to detect the version of firmware you have rather than simply failing. But in the meantime, I would consider simply installing the latest Mega / Holey firmware release, if you have not done so: GitHub - WebControlCNC/Firmware at release/holey
Thanks for the heads-up. User accounts are something I haven’t actually even looked at the code for yet since starting retrofitting this app. But they’re high on my list to taclke, because I want to use the app to control multiple machines from one central “hub” (thus, I want to make sure security is good enough).
Scratch start, full build.
Everything worked this time except for building the service. still get ‘bin/build-service.sh command not found’
Thanks for the hard work!!!
This is the point i gave up with my Pi 3B+ after 2 days. I thought it is my under voltage issue, but 2 days ago makervers was running a 3 hour simulation without any issues. Can’t get it to connect and can’t find logs on the Pi. If I ssh to it and → cat /dev/ttyACM0 ← i get clear position reports, so port and baud are correct. Only change i did was to upgrade holey from 51.27 to 51.28.
This is to the wider group - is there any way to get Webcontrol to install Holey 51.28 firmware?
I confirmed my Holey firmware is currently 51.27 and Webcontrol doesn’t give me the option to go to 51.28. I do have the “Experimental Releases” option turned on but that may not include experimental firmware updates.
I’d like to avoid setting my laptop up again in the shop to run Arduino IDE to accomplish the firmware update if at all possible.
yes. copy the holey-51.28.hex firmware file to the webcontrol/firmware/holey folder
do it by pressing the verify button (checkbox) in the arduino ide, then at the bottom window it will compile and provide a link the the produced hex file. usually in appdata/local/temp/arduinobuild… or something like that if you are on windows.
it was the unplug and plug back in the USB that then activated the 49 rules. It was all there, but didn’t work until the replug. I think the readme is accurate.
Makerverse is running for one due. Will add the second this evening.
./bin/build-service.sh “Install” “pi” seemed to work:
pi@makerverse2:~/makerverse $ ./bin/build-service.sh “Install” “pi”
Makerverse Server will be controlled by pi
Unit makerverse.service could not be found.
