Problem with OS X and cu.usbmodem

[Marius Heil]

Hello,

not strictly an nrf question, but I am having trouble communicationg with the developer dongles under OS X. I am using screen to connect to my terminal and the input and output seem to work at first, but as soon as I copy and paste a longer command, it appends "USB" to that string. Don't know where it comes from. If my string gets longer, it will crash the serial port. Are there any specific drivers for the USB to Serial Bridge that I could install?

Thanks, Marius

[RK]

That's the most bizarre issue I've heard yet .. randomly appending 'USB' to something. The developer dongles support a standard USB CDC device for which the driver in OSX is one of the most mature around, I've run all sorts of different CDC devices over it and never had an issue. There used to be odd issues with FTDI based devices, but even those appear now to be fixed. So no you should need no special driver.

'screen' is a bit old however and not updated in a long time, and not perfect for straight serial communication. I use CoolTerm (freeware.the-meiers.org) which, despite being written by a guy who claims he's not a programmer, and in RealBasic too, is stable, has all the features I've ever needed and 'just works'. I also have something called 'SerialTools' which I think came free from the mac app store but mostly use CoolTerm. I've used that with serial devices from 300 to 115200 baud, with and without flow control, on nordic chips (really segger chips as they provide the serial interface), TI chips, Atmel chips and FTDI chips and had no problems.

Perhaps if you try a different serial program you'll have better success, either way I'd recommend giving that a go and seeing if it helps.

[Marius Heil]

Thanks, the problem is that I want to communicate with the dongle with Java, I was using this library: code.google.com/.../ which works absolutely fine on Linux and Windows but seems to have a Problem on OS X 10.10. When I send long commands (longer than 70 chars it seems to send USB for whatever reason). I tested it on OS X 10.9 and did not have that problem.