I'm late on this thread but I'll put in my two cents. Yes, mComm will work over
bluetooth. The problem is TS-DOS. Without additional delays, it times-out. And
on top of that the hardware must support RST/CTS. When I was working on the
bluetooth code for mComm, I used an off the shelf RS232 to Bluetooth device
which had CTS/RTS flow control built in. After many hours of frustration, I
found that if I changed the delay values in TS-DOS, it worked reliably, but
definitely slower. I posted some REX images of TS-DOS with delays added in the
members file area for those interested in testing. I stress 'testing' as its
still in that phase. Steve did some testing with BlueM but he had some issues
as I recall.I have not done much with it over the past two months. There seems
to be several variables between the hardware and TS-DOS. I decided to stick
with a wired connection until I have time to pick it up again.
Kurt
On Thursday, June 30, 2016 11:49 AM, Chris Ratcliffe <[email protected]>
wrote:
Apologies - I see it does use bluetooth.
Chris Ratcliffe/ Animation / Graphics / Creative Code
44 (0) 7973 299 138 / [email protected] GUILD TV LTD / http://www.theguild.tv
On 30 June 2016 at 17:45, John R. Hogerhuis <[email protected]> wrote:
You don't need GetBlue if you are using mcomm for android.
I think you need Rex or some way to run a customized tsdos optrom though.
On Thursday, June 30, 2016, Hiraghm <[email protected]> wrote:
I just purchased the GetBlue app to connect my Model 100 to my Note 5 Android
phone.
I downloaded mcomm for android... is that enough by itself to use my phone as
storage for my M100?
Is there a guide somewhere on how to set up GetBlue / mcomm ?
