> Hey Josh, Trying out the instructions you posted, but unable to get past the ar command line.
"ar x mComm_1.2_all,deb" ends up at another command prompt. From what I can tell does not “open” the .deb file. Tried ar -x with the same results. Wondered if all was a11, but saw that it is indeed all. I was able to install pyserial-3.4 so not a total loss. My work week ended at 4am so maybe I should get some more rest before exploring this further today. God bless, GregS <>< > ar x mComm_1.2_all.deb > > On Oct 14, 2020, at 5:13 PM, Joshua O'Keefe <maj...@nachomountain.com> wrote: >> I'll try mComm after dinner. I unpacked the .deb back when it was released >> and have it lying around somewhere. > > Apologies for replying to myself, but I have successfully run Python mComm on > macOS Catalina 10.15. It took a bit of doing: > > Predicate to this: having a sane python install (I use homebrew); maybe you > can make it work with system python but I'm allergic to system python on OS X. > > ar x mComm_1.2_all.deb # open up the deb, note command is not tar > tar xvf data.tar.xz # extract the contents > cd usr/share/mcomm # get in there to the script > virtualenv venv # create a venv for its dependencies, optional if you don't > use virtualenv > source venv/bin/activate # activate the venv > pip3 install pyserial # this is the module it needs > python3 ./mcomm.py --path="${HOME}/model100/stash" > --port=/dev/tty.usbserial-A1084AEN # your parameters will differ > > You may want to install it somewhere more permanent. I tested with the > script where it lay in my downloads directory but against my real M100 data > set. > > >