Kurt,
Thanks for the response. I admittedly have not spent a lot of time
t-shooting this yet. I had installed the newest version of mComm on the new
S9 device but saw the same behavior after installing the old version of
mComm that I was using on my S5. I think tonight I will try connecting via
Thanks for the link Josh. I have had great success buying the FTDI
cables for CISCO routers and then replacing the RJ45 end with a DB25 (Or
a DB9 with adapter).
Kurt
On Thu, Dec 27, 2018, at 11:43 AM, Josh Malone wrote:
> Slightly related side note: I, too, recently upgraded to a Galaxy S9
> so
Tom,
That error is usually from a failure to connect. What version of mComm
are you running? I have not played with the Bluetooth connections for
quite some time so I will need to go and look at my notes.
Some things to check.
1) Are you running the same version of mComm on the S9 as on the S5?
Slightly related side note: I, too, recently upgraded to a Galaxy S9
so I've been forced to make the switch from micro-USB to USB C. I
bought a USB-C serial cable and can report that it works great with
mComm and my Tandy machines:
https://www.amazon.com/gp/product/B01K2JUUK8/
Just an FYI for
Quick question for Kurt...I recently upgraded to a new phone (Galaxy S9)
and I am having some trouble getting mComm to run with BT for some reason.
It worked great on my old S5. When I attempt to initiate a bluetooth
connection I am getting a message that "mComm has stopped" then the app
closes
