Like I said I tried the run.py file incrementally on a BRAND NEW image before any updates. Only grabbed the configuration files, machineface and cetus from github into home folder.
The response of the run.py was typically what you should see when running however the instance did not show up on multiple machinekit client devices. THEN I updated and upgraded with the same typical run.py results with no instances in machine client. So FINALLY I installed machinekit-dev which is what produces the configserver error. But I suspected it also has necessary files to run Machineface. The purpose of the screen shot was to show that, after I produced the configserver error(in the terminal on the screenshot), I verified that both the configserver.py(including line:16) and message_pb2.py existed. Despite the error saying it did not. Merely trying to help narrow down where it might be coming from. On Jul 14, 2016 3:07 AM, "[email protected]" < [email protected]> wrote: > > On 14/07/16 01:19, 'IonicBasher' via Machinekit wrote: > >> On Sunday, July 10, 2016 at 4:38:52 PM UTC-6, IonicBasher wrote: >> >>> Getting this error when trying to run Machineface on latest image both >>> classic machinekit and jessie. >>> >>> Unsure of what that's about. Axis loads up fine with sample CRAMPS >>> configuration. >>> >>> Followed this guide as usual: >>> >>> https://github.com/the-snowwhite/CRAMPS2/wiki/BBB-CRAMPS-Machineface-3D-Printer-Out-Of-The-Box-Experience >>> >>> Except with: >>> https://github.com/strahlex/MendelMax-CRAMPS >>> >> Okay. I tried installing by packages on a stock debian image but failed >> to open even the sample configuration for cramps. Another problem for >> another time. >> >> I reflashed the latest wheezy image of machinekit to climate possible >> sources of errors. >> >> I tried running strahlex/MendelMax-CRAMPS/run.py incrementally. >> >> First I got Machineface, Cetus, Mendelmax-CRAMPS then tried the run.py. >> It showed the correct start text but failed to show up on multiple machine >> kit client devices. >> >> After apt-get upgrade and update yielded the same result. >> >> After "apt-get install machinekit-dev" the above error occurs. >> >> I verified all files (configserver[line:16], message_pb2) were still >> there. They were. >> >> The attached picture should show all files and error. I'm confused now. >> >> You are confused!? Please read the title of this thread. > > Instead of quoting your original question and then ignoring my advice on > that subject and talking about a completely different subject, please just > try what I suggested. > > Your install presumably worked fine until you tried "upgrading" by > overwriting a binary image with packages, so just download the image again > and all should be as before. > > If you wish to raise another issue, please do it as described in > http://www.machinekit.io/docs/getting-help > > Random screen captures are no use in reproducing any problems > > Incidentally, there is a message_pb2.pyc file in your file manager > capture, which shows the message_pb2.py file HAS been found and used. > A pre-compiled version has been created to speed the next access. > > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit > --- You received this message because you are subscribed to a topic in the > Google Groups "Machinekit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/machinekit/jdpypzDCsg4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
