@madgrizzle, yes, I can inspect the html code. Curious that I haven’t imported groundcontrol.ini yet, but here is the webcontrol.json from my pi. webcontrol.json (33.5 KB)
Well, I’m thinking somehow the latest docker got built with an old copy settings.html template. Not sure how because the code that @Jim_Temple was able to show me isn’t the correct code. I had to rebuild my RPI recently and maybe I somehow grabbed old software in the process.
in the webcontrol port field, what options does it list? can you go to the
command line and do
ls /dev/tty*
and report what you see (make sure the arduino is connected when you do this)
if you do this with and without the arduino connected, you should see the
difference, and that is the port you need to configure webcontrol to use.
David Lang
1 Like
That did it @dlang! The Arduino was getting mounted as /dev/ttyACM0, so I typed that into the Maslow settings and it connects now! Thank you!
1 Like
Ok, so I don’t know what happened, but my dev RPi was way behind and there were 17 files modified when I pulled from github. Sorry about that. It’s now up to date.
I’m moving to less popup messages and started with sled alarm. It now reports in an alert field above the the play/pause/stop buttons. If the alarm goes off, the stop button will glow to let you know you need to press it to clear the alarm.
There’s also a PID tuning page. I use accordion controls, so click on the header and the controls will appear. The first set allow you to position the motors. Each button turns the motor the specified direction for an amount of time listed on the button. Don’t use the 10 buttons because you might get a disconnect error (it apparently doesn’t send a position update as its turning and thereby causes groundcontrol to think the controller is disconnected).
The velocity and position controls allow you to run the tests commands. I think @krkeegan did them, but it might have been @bar. Note: version 2 of the tests aren’t working exactly correctly right now… so don’t try them. I’ve got to fix a few things and make some of the data use a secondary axis on the graph. Read this page to see what the inputs are:
Please let me know how your data looks… I’m trying to tune my four motor design and am curious what a stock machine looks like.
1 Like
I am back at the computer / Maslow for an hour or two. I will try to connect again. When I get onto WebControl, it will automagically update the most current software, correct?
I will give @dlang’s solution a shot.
No, it will not automatically update webcontrol (only webmcp is updated automatically). When you boot, bring up WebMCP and click the Update Webcontrol button. After it says the update is done, you can start webcontrol.
Hopefully you won’t need to. The comport refresh button should be back.
Yes, I just updated and the refresh button is now there and it does work now! Thanks @madgrizzle!
1 Like
I am also connected on the proper com port (firmware update was successful, comport button is available), and it appears that the RPi is now properly connected to the Maslow. I don’t currently have any Gcode loaded, but I should be able to jog the sled using the arrow buttons, correct? I am not getting any response yet. But, all looks to be talking correctly.
Yes, you should be able to move the sled using the buttons. Try hitting the stop button and see if that helps.
Unfortunately, it doesn’t.
When I ran into that it was because I had the power cable plugged into the Arduino instead of the shield. Plugged it into the shield where it was supposed to be and restarted WebControl. That fixed that.
I helped him through it using direct messages… didn’t want to spam the thread. But that was one of the thoughts I had, but he said he had it working in groundcontrol so I figured he didn’t change it.
1 Like
There were several issues that @madgrizzle helped me resolve. One was on the software side, including omitted html code from an older version which he corrected. Another was selecting the correct port. The first half of the port issue was related to the software correction mentioned above, the second was user error - I had to select the correct port from those available.
In all, we got everything worked out, Maslow responds properly on RPi with WebControl now, and I am extremely grateful to @madgrizzle for all his hard work walking me through the process. I know this is not his regular job, but he gave me the time anyway. You don’t find that kind of devotion very often!
-Jim
6 Likes
Great Work @madgrizzle 
1 Like
What version of firmware does Webcontrol need to operate? I would like to test webcontrol out but in our makerspace I need to keep it running with ground control until we make a firm swap over. But I would like to test it and write our user documentation before I commit. Can this be done?
It’ll work with the stock firmware, though it will popup a warning when you start that some of the features aren’t available (namely optical calibration). I’m thinking of doing away with that since it’s a bit of a nuisance to those with stock firmware. Save your groundcontrol.ini file off somewhere so you can import it and (hopefully) the settings will stick.
Also, it does not work with holey calibration firmware yet since there’s no way yet for webcontrol to recognize the firmware as not being stock (so for double negative).
I am still running an old firmware/GC software so I am sure I need to upgrade to the latest but would be great to bounce between two until we are sure we want to commit.
What version are you running? The only real issue is if the firmware doesn’t support certain settings that were added later, like chain stretch… but the firmware might just ignore it so I’m not sure it really matters.