Most ports are owned by root, are members of groups such as dialout (or others). Ports enumerated under /dev have similar permissions. Build 380.08 is rather dated, will get you going with CoolTerm and probably Chilipeppr, but Chillipeppr works best with enhanced tinyG status messaging that is in 438.02 FW (and beyond).Ī couple hints on the behavior you are seeing, based on Linux behavior.Īccess denied – Linux files have permissions rwxrwxrwx for self-group-others. What version of the serial-port-json-server do you have installed? Version 1.77 is the latest.įINALLY, know that I will then recommend you update your tinyG FW to build 438.02. Hopefully someone who is more familiar with you version of MACos will stop by and more precisely speak your language.ĪND, when you are finally getting a usable tinyG USB connection, get CoolTerm working again as it is somewhat simpler than Chhilipeppr. See if any of this produces useful information. In Linux, from CLI, that would be ‘cat /var/log/messages | tail’, outputting USB related messages similar to dmesg above (tail by default prints only bottom 20 lines) If MACos does not support ‘dmesg’ from the command line, look with an editor at the bottom of the system messages file. If there is nothing in the ‘dmesg’ report, perhaps try a different USB cable? It would not be the first time the cable turned defective in one of these adventures.ġ2. If the new USB device insertion was seen by MACOS, you will then likely see some error messages related to install driver failure for the new USB device. If you do not see a new device appear in /dev, still check the output of ‘dmesg’ command. In this file (URL) you will see the results of the dmesg command on my Linux machine, The top three lines are a disconnect event, the balance are the messages issued by the USB services after re-insertion, loading and starting up the driver.ġ1. In Linux, a ‘dmesg’ command will dump a long stream of messages, the most recent of which should be related to the USB insertion. Open a command line console window in you GUI. Devices appear as /dev/ttyUSB0 (Linux speak, not MAC) only after USB insertion detection and proper driver startup.ġ0. If there is no change in the /dev/ device list, you likely have an ftdi driver install issue. You should see a new device appear under /dev, with connect time the insertion of the tinyG USB cable.ĩ. Now insert tinyG’s USB into the MAC, then refresh you GUI again (or it may auto-refresh).Ĩ. TinyG still not connected, refresh your file manager GUI.ħ. Hit the reset button, it will reboot(this is probably redundant, but ensures a clean boot, free of power up induced glitches, should they exist).Ħ. Without connecting tinyG yet, power it up and wait for the flashing LED to stop flashing (boot is complete). The most recent, and probably everything, will have a date field that is same as the boot time.ĥ. With a GUI file manager, navigate to /dev and click the GUI to sort the display of devices under /dev by date, decending order, most recent on top.Ĥ. Step one is to get MACOS properly accepting a connection from tinyG.ģ. I know MACOS has its roots in Unix so is similar, but unique in detailed ways I am not familiar with. I cannot help directly with MACOS specifics, I run on Linux, so will speak Linux and expect you to translate to MACOS dialect. You need to resolve the usb port connectivity issue before moving on to CP. Based on your description, your issues are between MACOS and tinyG for now and you have CoolTerm installed. I re-installed the drivers, checked all of the above… is there any help you guys can think of that i’m not thinking of? I am totally not seeing tinyg usbserial port connection. I tried swapping out the usb but it doesnt help.Īlso I have reset tinyg and it seems to boot up (red SpDir light flashes for 5 secs then pwm light comes on solid) My usb serial port on my mac does to work because I can see an arduino usbserial port when i plug in arduino via a usb. dev/tty.Bluetooth-Incoming-Port /dev/tty.Bluetooth-Modem When I scan in terminal here are the only ports listed: So I reinstalled the drivers from here, but still I cannot see the serial port listed. So I restarted my computer, and then opened coolterm but the usb serial port will not show up for tinyg. So i went back to coolterm and tried to connect, as described here, which was working fine yesterday, and repeatedly got an error 100 access denied when I tried to connect to the usbserial port. However, today I tried to get chilipeppr running, installed and ran the serial port json server, and couldn’t connect to the port that tinyg was on (usbserial.xxxx). I just started working w/ it yesterday and was sending it test files through coolterm. Hi I am using Tinyg v8 fw 380.08 on mac osx mavericks 64 bit.
0 Comments
Leave a Reply. |