do we need to reinstall or just update the launch file?
Just the launch file. I think the above block of code should work to do so.
Hopefully we’re approaching the last time I have to ask you to do a manual update. Once the launch file is stable, everything else can self-update.
I’m getting Permission Denied when I try to do the wget. I tried again with copy/paste from above just to be sure I had the command right.
Did you delete the file first? The sudo rm rf line. If that still doesn’t work, try adding a sudo in front of the wget (and subsequent chmod)
That was it - I had to add “sudo” for both the wget and chmod commands.
After restarting the Pi (faster for me and less error prone than restarting the service) the .makerverse file is properly updating with configuration changes.
I restarted again so the “prerelease” setting would take effect. Startup of Makerverse was much slower (expected I guess since it should update). After waiting 5-10 minutes (I was multitasking) I came back to it and Makerverse was running. I confirmed it is running 1.1.1[b] via the About box.
However, when I go to the Home tab and New Workspace, Makerverse will no longer show the comm ports available. That was working before the latest bin/launch and update to 1.1.1[b].
Standing by…
Most up to date image (pre-release) looks good. Only problem I have is getting wifi up and running,
I dug around a bit after noting ‘wifi disabled by rfkill’ (or similar) I did run rfkill enable all
verified the contents of the settings file for wlano. used ifdown -a, ifup -a no joy
Going to connect to the Maslow and see if I can get it to connect
This is typical of a freshly install Raspbian. Doing the sudo raspi-config should enable Wifi.
Hm, I just followed the same update steps without problems on my RPi imaged install.
Things to try:
- Re-plug the USB cables & refresh the port list
- Restart
- Make sure you can still access the port e.g.,
cat /dev/ttyACM0or whatever it is - Make sure the port has the correct permissions, i.e.,
ls -la /dev/ttyACM0should showcrw-rw-rw- 1 root dialout 166, 0 Sep 3 19:39 /dev/ttyACM0
Holey schnilies, I’m up!!!
Just need to fix wifi
1 Like
Permissions match. I haven’t physically touched the Pi, so I don’t think it is a cable issue but can check that later. I did restart but no change.
When I do cat /dev/ttyACM0 I was getting normal logging before the update. However, now I get garbage. Could the baud rate have gotten corrupted somehow?
pi@makerverse:~ $ cat /dev/ttyACM0
b���"�9@M@I(M� ��J<�
O
O���7�M�M-b�9@�@bI�\E��V��+f�^��-!�o�"� ����XE� ��u{ @!I) I`I(Ih@r��^[��
o��)"�b�'XE�X/\3I��Q
I I(!H)I)@ I@I Ih��?^���P{T/�S#�d4BsRS�e<p��� �!O*
#W�Q��� )I I(!I)HK HIaIiI�(�+:��
C8sn�\
ϩ!�c�=&
�Md �C���{8rX��|D�`GZEE�`Ih`I)@)) ! !)A
@C���qZ��1/L?N�x
4�"� ��)�XO� ��q{(I )H IIA hIaIs��^�
n��)"���� �ҨܱH
�
��q[)A!H)H) IAIH @IIAr(�k,��bC8{n�L0M�24�oEIMI
�K���;�q�9S�!��n��iI!I()H )@)AAA
�\E��V��+N�^��
1�Z�v p�rA�!��N�(I)A(A(A)) AI@KHIH��E��B�q+L�^�x
4���V�
��K*3���g|�!H! A!IK@ @I!Ia��"t:��I just moved USB cables and powered down and restart the Pi again. ‘cat’ still is generating gibberish.
Just because, if you haven’t pull the USB cable and put it back in while the Pi is running.
FWIW, I did this. Though I was moving from the USB3 ports to the USB2 ports.
Baud rate should be 57600 for the old board I think
I poked around and found that the port was defaulting to 9600. Not sure but I suspect when it was working before I had tried configuring Makerverse and it set the port to 57600 before I ran ‘cat’.
Anywhoo, I went back to Makerverse now and it did populate the ports and I was able to pick ACM0 and set 57600. That got me to the Create Workspace screen again and I have the newer error message.
Keep in mind that I am 100% (ok 99.99%) convinced that Holey 51.28 is already running (because Webcontrol reports that and complains that it is newer than the 51.27 that ships with Webcontrol).
One other thing to note - when running ‘cat’ after configuring Makerverse to use 57600, ‘cat’ does output readable text. In the log, there is a occasionally occurring ‘error: Bad number format’. I have no idea what may be coming through that can’t be parsed.
2 Likes
Question about the calibration and the MetalMaslow sled.
Anyone using one? I’m hoping the ‘edge of the sled’ is the same as the wood sled
Suggestions?
Do I need to even bother? Set up on WebControl seems to be pretty solid
Okay, let’s try this. Makerverse is looking for the Firmware Version X and PCB vY Detected lines which the Maslow Classic firmware should print out when it connects. You’re probably familiar with seeing this when you connected to Web Control. You can also find it when you connect to the Serial Monitor on the Arduino IDE, as well. I believe if you issue a $$ and B05 command it will also trigger this output. Can you get me those lines?
I just got my own metal maslow a few days ago. Unfortunately, it is not a uniform radius (the bottom is longer than the top), so it will not work well with Edge Calibration. For now, I’d recommend skipping to Precision Calibration 
But I’m going to code in an option that knows the MM dimensions.
1 Like
Sorry for the delay. Had a guest and Friday/Saturday here is like Saturday/Sunday for you if you are lucky enough to have a 5 day working week. After a 4:7 score in billiards and whisky on Mohmds side, beer on my side, he left. Slightly handicapped and having another 4 hours to balance time difference and fully motivated… I copied the .makerverse from here as per link in the read me. Perhaps here was my mistake to not trust in that it would be created by itself. examples/.makerverse
So count the curly brackets and add the hole section and guess where the closing bracket goes?
Disclaimer: Don’t take me serious tonight, whatever i say. We are all the human family.
Hm? That’s not in the readme, I don’t think?
I also have a metal sled, but I have the linkage instead of the ring, so the radius is different and I have to manually set it.
