Did you try to redo it? If you have the same experience, do you have a different SD card you can try?
Indeed, user error. I reformatted the SD with SD Card Formatter (per Raspian setup instructions). I burned the prebuilt image to SD. Success on format and burning. Put SD in Raspberry, fired it up. I eventually realized that I needed to have a monitor and keyboard hooked up, so that I could get the IP address from the startup mumbo-jumbo, most of which I don’t understand (though I did find the IP). Once I put that in the web browser, I found WebControl just fine. I have imported GC settings using dialog box, though I don’t know if that has completed properly. I now have my RPi in the garage and hooked to the Maslow. WebControl is fired up, but the Maslow doesn’t respond to inputs (clicking the arrow buttons). I may need to play with it some more to see if there’s anything I’ve missed. Maybe I need to reboot the Pi with Maslow hooked up, or restart the Maslow or something.
The other weird thing is, upon subsequent attempts to start up the RPi hooked to the monitor, the IP address has changed to a very long number that is different from the first one I recorded. I have read here and elsewhere about bots looking out for brand new devices on the net, could this have happened to mine?
If it shows its connected, try hitting the stop button. Top right corner of screen has two “buttons”. Left one shows status of connection between your browser and webcontrol. Right one shows status of connection between webcontrol and the arduino controller. If the right one reads the com port you have assigned, then it’s connected. Try the stop button and see if that fixes it.
Right button shows not connected. How do I assign the com port? I don’t recall if it ever displayed a notice about first time use, so I don’t know if it ever found/selected a com port.
Also, I did a bit of research and set a static ip address for the pi so I could easily access it. I’ve never worried too much about network security. Hope I don’t have to start now.
Thanks again for all your help. It has definitely helped me get off the ground on this stuff.
–Jim
WebMCP is throwing a near constant stream of “connecting” and “is unavailable or in use”. Occasionally I see “I’m connected!” and “Client disconnected”
Go to Settings->Maslow Settings and then click the ‘refresh’ button next to the ComPort setting… it will query the RPI for a list of available ports. If it shows up, try ttyacm0 (or something)
If that’s in the webcontrol messages column, that’s normal because the port selected is unavailable. webcontrol tries to connect every 5 seconds or so.
That’s just a quirk with the browser communications with webmcp… not sure why it happens, don’t worry about it.
That’s sort of odd. That happened to me the other day and after I looked at the code, the refresh button came back. Can you try refreshing the browser and let me know what happens.
Refresh had no effect.
Really odd… I’d ask you to look at the browser code, but that’s rather complicated to do… so instead, go to webmcp and shutdown webcontrol and after it does, restart it. Let me know if that changes things.
Okay, now I can’t even get back to webmcp! Aaagh!
RPi is showing up as connected to my WiFi, but browser says site can’t be reached at http://xxx.xxx.x.xx:5001
I’m experiencing the same issues as @Jim_Temple: No connection to controller, no COM port specified and no refresh button in Maslow Settings. 
Are either of you computer savvy enough to inspect the html code?
I shut down and restarted the RPi, and am able to get back to WebControl. But, still no com.
I can look it up, but I may not be able to understand it. Some is moderately readable. What am I looking for?
I’m send you a direct message to avoid spamming this thread.
There appears to be code missing from the setting’s HTML page. I’ll have to rebuild things tonight. Maybe an old file got used to build it… weird.
@Jim_Temple or @vancek, are either of you able to send me your webcontrol.json file located on your RPI in the .WebControl subdirectory? I think something is happening during the import of groundcontrol.ini that might be messing with the webcontrol.json file.