Doesn't connect to weather station

[HurricaneTracker]

Cannot connect my USB-Serial adapter to CumulusMX on my Mac. Error file attached.

[steve]

I think perhaps I have to use a different identifier for the serial port on OS X (and probably on Linux too). Probably something like "/dev/ttyS0". Do you happen to know if that's correct?

[HurricaneTracker]

I think perhaps I have to use a different identifier for the serial port on OS X (and probably on Linux too). Probably something like "/dev/ttyS0". Do you happen to know if that's correct?

That sounds about right. Right now I use Cumulus through a Windows virtual environment but it would be nice not to have to do that and just run Cumulus on the Mac, as the version 3.0 looks to do. Good luck resolving this one. Com ports on a Mac aren't always straightforward.

[swyman18]

I think I've got a similar situation, I'm using a VP2 connected via Serial-USB converter and testing on Ubuntu Server 14.04.

When I plug in the converter, I see device /dev/ttyUSB0 appear on my file system. So, I think I need to use that for my "port" setting in CumulusMX. But of course, it will only accept an integer at the moment.

[steve]

It looks like I will have to make the field a string rather than an integer so the device name can be specified.

[swyman18]

With build 3002, I am able to successfully connect my VP2 using a Serial-USB converter on Ubuntu Server 14.04. I used /dev/ttyUSB0 for the device name.

So far, basic functions appear to be working, and I'm uploading successfully to WU and CWOP.

Will play around with the other functions over the course of the next few days.

Great work!

[steve]

Great - thanks for the feedback.

[HurricaneTracker]

Just wanted to add that I finally was able to get CumulusMX talking to my Davis station on my iMac. Ended up needing to use /dev/ttys000, for the serial port, and that worked out great. Thanks for the fix! Everything is loaded and looks like it should, and reporting to CWOP and Wunderground appear to be uninterrupted. Great work!

[steve]

Thanks for that.

[HurricaneTracker]

Well, CumulusMX froze last night and stopped communicating with the Serial Port. Terminating the program resulted in the request for sending you the error files, so here they are. Also, when I tried to fire Cumulus back up, it refused to talk to the serial port again. That is to say, it isn't working at all anymore.

[steve]

2015-01-12 05:32:17.071 Serial device = /dev/ttys000
2015-01-12 05:32:17.073 Inappropriate ioctl for device
2015-01-12 05:32:17.074 Not Connected

I believe that error message means that your system no longer thinks that device is of the correct type for this purpose. What tty devices do you have in /dev/ now?

[HurricaneTracker]

I didn't change anything in settings when the data comms stopped. Still set at /dev/ttys000

I have tried /dev/tty.usbserial-A6031IKP, and at first it did not connect. I restarted CumulusMX with this new setting and it seems to work, but for how long? What caused CumulusMX to stop communicating with the console?

Here is the entire directory of /dev. It's a beast!

bpf1 ptyq6 ptytb random ttyr4 ttyu8
bpf2 ptyq7 ptytc rdisk0 ttyr5 ttyu9
bpf3 ptyq8 ptytd rdisk0s1 ttyr6 ttyua
console ptyq9 ptyte rdisk0s2 ttyr7 ttyub
cu.Bluetooth-Incoming-Port ptyqa ptytf rdisk0s3 ttyr8 ttyuc
cu.Bluetooth-Modem ptyqb ptyu0 rdisk1 ttyr9 ttyud
cu.usbserial-A6031IKP ptyqc ptyu1 rdisk1s1 ttyra ttyue
disk0 ptyqd ptyu2 rdisk1s2 ttyrb ttyuf
disk0s1 ptyqe ptyu3 sdt ttyrc ttyv0
disk0s2 ptyqf ptyu4 stderr ttyrd ttyv1
disk0s3 ptyr0 ptyu5 stdin ttyre ttyv2
disk1 ptyr1 ptyu6 stdout ttyrf ttyv3
disk1s1 ptyr2 ptyu7 systrace ttys0 ttyv4
disk1s2 ptyr3 ptyu8 tty ttys000 ttyv5
dtrace ptyr4 ptyu9 tty.Bluetooth-Incoming-Port ttys1 ttyv6
dtracehelper ptyr5 ptyua tty.Bluetooth-Modem ttys2 ttyv7
fbt ptyr6 ptyub tty.usbserial-A6031IKP ttys3 ttyv8
fd ptyr7 ptyuc ttyp0 ttys4 ttyv9
fsevents ptyr8 ptyud ttyp1 ttys5 ttyva
io8log ptyr9 ptyue ttyp2 ttys6 ttyvb
io8logmt ptyra ptyuf ttyp3 ttys7 ttyvc
io8logtemp ptyrb ptyv0 ttyp4 ttys8 ttyvd
klog ptyrc ptyv1 ttyp5 ttys9 ttyve
lockstat ptyrd ptyv2 ttyp6 ttysa ttyvf
machtrace ptyre ptyv3 ttyp7 ttysb ttyw0
null ptyrf ptyv4 ttyp8 ttysc ttyw1
pf ptys0 ptyv5 ttyp9 ttysd ttyw2
pfm ptys1 ptyv6 ttypa ttyse ttyw3
pmCPU ptys2 ptyv7 ttypb ttysf ttyw4
profile ptys3 ptyv8 ttypc ttyt0 ttyw5
ptmx ptys4 ptyv9 ttypd ttyt1 ttyw6
ptyp0 ptys5 ptyva ttype ttyt2 ttyw7
ptyp1 ptys6 ptyvb ttypf ttyt3 ttyw8
ptyp2 ptys7 ptyvc ttyq0 ttyt4 ttyw9
ptyp3 ptys8 ptyvd ttyq1 ttyt5 ttywa
ptyp4 ptys9 ptyve ttyq2 ttyt6 ttywb
ptyp5 ptysa ptyvf ttyq3 ttyt7 ttywc
ptyp6 ptysb ptyw0 ttyq4 ttyt8 ttywd
ptyp7 ptysc ptyw1 ttyq5 ttyt9 ttywe
ptyp8 ptysd ptyw2 ttyq6 ttyta ttywf
ptyp9 ptyse ptyw3 ttyq7 ttytb urandom
ptypa ptysf ptyw4 ttyq8 ttytc zero
ptypb ptyt0 ptyw5 ttyq9 ttytd
ptypc ptyt1 ptyw6 ttyqa ttyte

[steve]

I restarted CumulusMX with this new setting and it seems to work, but for how long? What caused CumulusMX to stop communicating with the console?

I don't know, I don't have all the answers. I know very little about Macs. That's the point of the beta testing, to get people who know their systems to tell me what the problems are. What was in the diags file at the time it stopped communicating? What type of USB/serial adapter are you using?