Cumulus Support

mcrossley wrote:A wild stab... You don't have Cumulus set to automatically start in some way do you? And a copy is starting up in the background every time you start the computer?

Now that's a thought, as I do have Cumulus start automatically. But looking at Task Manager, only one instance is running and only one set of associated processes.

Good job I didn't start this with much hair on my head, 'cos it's getting thinner by the second.

Netbook, 9 years old, used 'til now for showing a copy of my website - last updated by Win7 2 years ago - took 18 hours to catchup with updates!

WL runs and accepts the data logger (driver dated 2015).

Cumulus runs and sends out to Met Office - though I bet I've lost my Gold Star for the year
However it's not updating my website. Files are being generated as normal but the SCP script isn't transmitting for some reason.

CumulusMX will not find the device - so I've got to try and work that one out.

I've given up on the original PC - it's running happily with two non-weather data loggers so whatever WIn7 update did, it only affected the Davis Logger :chinscratch:

Thanks everyone for your support, patience and ideas.....

Still no joy on website update. Have done a 'fresh' install of WINSCP - it didn't give a choice on where to save it, I'm sure originally I had the choice and the suggestions were to load it into the Cumulus folder?

Edit: Sorted after reading through this thread : https://cumulus.hosiene.co.uk/viewtopic.p ... CP#p131200

CumulusMX, another step forward; for some reason it was trying to connect via COM7, despite ini file saying COM3, but another copy of the ini file from Cumulus allowed access and some success - but then it errors on what looks to be network access? Firewall (Windows) off.

you'll probably need to run the wcp script in a command prompt and see what the error is or turn on logging with winscp.com

so use /log=<logfile> in the command line. put a real filename in where <logfile> is. also make sure "winscp.com" is used and you dont just call winscp as this could call winscp.exe and then break the script.

can you post your winscp command line your using?

Toxic17 wrote:you'll probably need to run the wcp script in a command prompt and see what the error is or turn on logging with winscp.com

Code: Select all

Usage:
WinSCP [/script=file] [/command cmd1...] [/parameter // param1...]
WinSCP [/log=<logfile> [/loglevel=<level>]] [/logsize=[<count>*]<size>]
WinSCP [/xmllog=<logfile> [/xmlgroups]]
WinSCP [/ini=<inifile>]
WinSCP [/rawconfig config1=value1 config2=value2 ...]
WinSCP /batchsettings <site_mask> setting1=value1 setting2=value2 ...
WinSCP /keygen keyfile [/output=output] [/changepassphrase] [/comment=comment]
WinSCP /help

 /script=       Executes batch script file. If the script does not end with
                'exit' command, normal interactive mode follows.
 /command       Executes list of script commands.
 /parameter     Passes list of parameters to script.
 /log=          Turns on session logging to file.
 /loglevel=     Logging level (0..2), add * to enable password logging.
 /logsize=      Enables log rotation and optionally deleting of old logs.
 /xmllog=       Turns on XML logging to file.
 /xmlgroups     Group all XML log elements belonging to the same command.
 /ini=          Path to configuration INI-file.
 /rawconfig     Configures any settings using raw format as in an INI file.
 /batchsettings Updates settings of sites matching a mask using a raw format
                as in an INI file.
 /keygen        Converts private key to .ppk format or edits key. Use /output=
                to specify output file. Use /changepassphrase to change or set
                passphrase. Use /comment= to change or set comment.
 /help          Prints this usage.

 

so use /log=<logfile> in the command line. put a real filename in where <logfile> is. also make sure "winscp.com" is used and you dont just call winscp as this could call winscp.exe and then break the script.

can you post your winscp command line your using?

Many thanks Simon, that's useful for the next time!

I did edit my original message to say I'd got it working. I took a lazy way out, uninstalled the existing, and replaced it with a new copy. I guess somewhere the server key was 'locked' from the original PC.

if you get this issues again after a windows update then just uninstall the windows update.

ALso make sure you have a good restore point now, and make a cold backup too.

Macrium Reflect is an excellent free backup tool much faster than Acronis.

Toxic17 wrote:if you get this issues again after a windows update then just uninstall the windows update.

ALso make sure you have a good restore point now, and make a cold backup too.

Macrium Reflect is an excellent free backup tool much faster than Acronis.

Thank you Simon - Actually I use Allway Sync Pro - and it's been superb program to use. Yes, it only copies files - but it's always given me an opportunity to re-fresh the programs on my laptops/PCs, and allowed for installation of new laptops.....

hi i have a iso off the WeatherLink 6.0.3 if any one need it

dazza1223 wrote:hi i have a iso off the WeatherLink 6.0.3 if any one need it

Sorry, iso?

so u can burn it to a disk or you can have a zip file

dazza1223 wrote:so u can burn it to a disk or you can have a zip file

Ah - sorry - that's OK - I managed to find my copy of weatherlink and used that.

Thank you though...

o ok mate what ther weather up there like?

dazza1223 wrote:o ok mate what ther weather up there like?

Currently sunny! But breezy, though the figures don't feel correct sometimes. We've had a few squalls but nothing unusual.....

craigdamwx.info

o so ur not in the eye off the storm

have u got a website so i take a look

dazza1223 wrote:o so ur not in the eye off the storm

have u got a website so i take a look

Yep - it's the one I posted in the last comment - missing the www etc!