I'll bet there's something I'm missing!

[Altocumulus]

Windows 7 Home Netbook

I've finally lost patience with Cumulus 1 - its ability to always want to become unresponsive when I want to view anything from the menus, so.....

Downloaded latest MX
Installed in its own directory
Transferred copy of Cumulus.ini and data files, from Cumulus1
Running MX as Administrator, but startup states cannot connect to station.

Checked Cumulus1 can connect.
Notebook rebooted
Cumulus can still access station, but MX can't. (Cumulus off during MX startup.)

I'm flummoxed .....

[PaulMy]

Can you see any issues in your MXdiags?

Enjoy,
Paul

[LAdrain]

Check cumulus.ini in the Directory you created that under "Station" you have an entry "Port=x" where x is your connected USB port.

[ExperiMentor]

Check cumulus.ini in the Directory you created that under "Station" you have an entry "Port=x" where x is your connected USB port.

Two things wrong here.
First, for CumulusMX, this file was renamed from cumulus.ini to Cumulus.ini (ie starts with an upper case C in MX). Did you rename the file when you copied it across? If not, maybe that is the cause of your problem?

Second, the line in the Cumulus.ini file is not "Port= ...", it's "ComportName=..."

My Cumulus.ini starts:

Code: Select all

[Station]
Type=5
Model=
ComportName=/dev/ttyUSB0
Latitude=47.4041666666667

[Altocumulus]

Hi guys, I'll check all those.

Cumulus.ini already came across with a capital C

[Altocumulus]

My .ini file starts....

[MainForm]
Left=39
Top=6

[Station]
Type=1
Model=
Port=3
Latitude=57.3633333333333

[Altocumulus]

Can you see any issues in your MXdiags?

Enjoy,
Paul

Hi Paul, from my last attempt to connect there's a section towards the end where there is this little bit under Davis LOOP


2019-11-23 16:36:07.618 Station type = Davis
2019-11-23 16:36:07.618 LOOP2 enabled
2019-11-23 16:36:07.618 Serial device = COM1
2019-11-23 16:36:07.618 Serial speed = 19200
2019-11-23 16:36:07.806 The port 'COM1' does not exist.
2019-11-23 16:36:07.806 Not Connected
2019-11-23 16:36:08.002 671 web tags initialised
2019-11-23 16:36:08.295 HTML root path = C:\cumulusMX\interface
Exiting system due to external CTRL-C, or process kill, or shutdown

You can see from my previous post, the ini file contains Port=3 - is this the culprit?

[Altocumulus]

Wondered if it was the LOOP2 - but my console is running firmware version Rev 1.9 - as it was from new in 2011.....and posts elsewhere suggest that this Rev supports LOOP2

[Altocumulus]

Maybe solved.

Changed the Port line in the .ini to ComportName=COM3 and I'm now connected and processing....

[PaulMy]

Maybe solved.

Changed the Port line in the .ini to ComportName=COM3 and I'm now connected and processing....

Interesting! Hopefully all is now good with yours.

I run both Cumulus1 and CumulusMX
Cumulus1 with Davis Envoy/USB logger and the cumulus.ini uses Port=4
CumulusMX with Davis Vue console/WiFiLogger and the Cumulus.ini uses ComportName=COM0 which is not an issue as this is an IP setup and the IP address is set later in the file.

Initially I copied my Cumulus1 cumulus.ini to the CumulusMX folder and I don't recall changing Cumulus.ini from Port=4 to ComportName=

Enjoy,
Paul

[Altocumulus]

All now seems to be good, Paul - thank you.

It's a strange one, especially as the installation implied there was little difference between the two ini files except the capital letter (which mine already had). But it's the only thing I've changed between success and failure - so I'll take it as good!

[mcrossley]

As well as making sure the ini file is capitalised, there are some changes to make to the contents...

• If you are using your 'old' Cumulus.ini file, make sure your 'ftp site' section is [FTP site] with 'site' in lower case
• The NOAA filename template needs to be changed to reflect the new date/time format strings in MX