search

ronoth / LoStik

LoRaWAN compatible USB test device
MIT License
134 stars 40 forks source link

LoStik is not recognised on OSX HighSierra #8

Closed krital closed 5 years ago

krital commented 5 years ago

Hi,

do I need some special FTDI / other driver for LoStik to be recognised under OSX? I have tried both with and without a hub and I get no serial device created.

lolsborn commented 5 years ago

Could you paste the output of 

system_profiler SPUSBDataType

We're looking for a device that matches Product ID: 0x7523 and Vendor ID: 0x1a86 if we have that it's probably not a hardware issue at least.

Once we know it's not a hardware issue take a look in /dev/tty.* for some reason the ch340 on my mac shows two devices a tty.usbserial- and tty.wchusbserial the later is the one you want to connect to. If you don't see a device there I recommend taking these steps:

https://medium.com/@tony92151/arduino-ch340-chip-driver-for-high-sierra-39e621dae1e4

The terminal requires CRLF which is your terminal app may or may not use by default. I would recommend starting off using the miniterm.py script in examples mentioned in the readme.

krital commented 5 years ago

Hello,

its not a hardware issue, I can see the device:

USB2.0-Serial:

      Product ID: 0x7523
      Vendor ID: 0x1a86
      Version: 2.63
      Speed: Up to 12 Mb/sec
      Location ID: 0x00200000 / 13
      Current Available (mA): 500
      Extra Operating Current (mA): 0

I can also see it with lsusb: Bus 000 Device 013: ID 1a86:7523 1a86 USB2.0-Serial

What is do not see is a serial device under /dev/tty.* hence I can not run any terminal... I did try with minicom initially against /dev/ttyS0 but that is not the correct serial port. I have faced the problem in the past with various boards and I had to install some FTDI drivers.. I understand though that LoStik uses some other chip?

krital commented 5 years ago

hello, so as the device does not appear, I followed the steps on the medium post above, rebooted my Mac as instructed but I still do not see the device. What do I try next?

krital commented 5 years ago

Answering my own question... It seems that after installing the drivers again and rebooting, I now get 2 serial devices only they are called /dev/ttys000 and /dev/ttys001 . So now I managed to talk to the stick but I am wondering, what controls the name of the serial device.