Setting up a Sutron Station

[cmcguire]

When setting up a new Sutron Station in SODA it is important to select the right driver (I don't think you can change the driver after you've added the station, let me know if that's wrong).

8210's use the SUTRON driver.
8310's use the SUTRON2 driver.
X-Link's (including GPRSLink/IridiumLink/SatLink) use the SUTRON_LINK driver.

@Patrick Larson

[Patrick Larson]

Still having no luck getting station to give data. The datalogger was changed from a 9210 to 8310. The 8310 has the same data output format/protocols as the 9210 so I just changed the parameter names to the new ones and tried to execute a download in SODA. It has no trouble executing successfully but it fails to download any data. I have since tried deleting the station and replacing it. It still claims that it successfully executes but it forgets to get the data. Anybody run into this and how did you solve it?

[cmcguire]

Can you post what site your working with and some screen shots of the current settings?

[Patrick Larson]

The station is R-Sutron(6132585000)

[cmcguire]

I dialed in with Putty and checked out the datalogger's settings.  The Station is set to 8310 on the site but on SODA it was set to a Water Survey ID.  I changed the ID in SODA to 8310 and changed the Log File name from SSP.LOG to DATA.LOG.  Is it working properly now?

[Patrick Larson]

It appears to be sort of working. There is data in the SODA "HG" and "New transducer" timeseries but nothing in "PP". Data is going to WISKI into the "HG" folder but not to "PP". That is likely to be because WISKI won't let me change the timeseries exchange number from Rideau,R-SUTRON(6132585000),PP,Highres to Rideau,R-SUTRON(6132585000),New transducer,Highres. There are still some issues but at least some data is moving somewhere.

[Patrick Larson]

I spoke too soon. Data is not moving to WISKI. i still don't get why the data all of a sudden is going into the SODA HG and New transducer timeseries but not the PP which is set up pretty much the same as New transducer. And, of course, the other question, why it won't export to WISKI.

[cmcguire]

Are you able to phone the gauge and view the settings with a terminal emulator?  Is the PP data recording ok? 

It looks like SODA added the 'New Transducer' time series in SODA because PC was recording but not configured in SODA.  If you pull up the data logger settings on a terminal emulator, check the HG settings and then make sure they match the same way for PP and PC in SODA.  I would configure PC so it's more clear in SODA.

If the level data isn't making it into WISKI it's likely an issue with the agent/import ID or overwrite settings.  You can change the import ID in the WISKI Agent but not the Exchange ID in SODA (as far as I can tell the two IDs match though).  When I polled the station this morning I can see that the data from SODA made it into WISKI yesterday but not this morning.  What has changed between now and then?

[Patrick Larson]

It has been getting there through the magic of cut and paste. Are you saying that SODA added the New transducer series? I still don't see anything different between PP and New transducer other than the names so can't figure why PP doesn't find any data and why HG started to get data. Both HG and PP are in keeping with the other station setups. The parameter names in the gauge setup are entered properly (Stage and TipBkt).

When I try to change the exchange number in the agent in WISKI from PP to New transducer, I get an error message but PP is still not pulling in the data so I continue to be at a loss there.

You mention PP and PC - what is your point there?

[cmcguire]

Ok, I thought it had imported properly.  What's the last time you've manually imported data? 

If SODA downloads a time series that is not configured for that site, it makes a new one.  I dialed your logger with Putty and see that only Stage and TipBkt are recording.  TipBkt is recording the PC.  PP is not a configured measurement on this datalogger. 

SODA Error
My guess is this is what happened:
1. PC had the wrong ID.Name under Sensor Configuration.
2. SODA made a generic time series for the TipBck data.
3. The name was corrected but there were two time series with the same name so it didn't know where to put the data. I've attached a picture of the log that helped to determine it.  I polled it around noon and received PC and HG data.

WISKI Import Error
I don't have permission to play with your WISKI Agent so this is what I would try:
1. Since it's your Original time series, uncheck Allow Edit and check Overwrite Interpolated Values.
2. In SODA your Exchange ID is listed as Rideau,R-SUTRON((6132585000),PP,Highres but in WISKI the Import ID is: Rideau,R-SUTRON(6132585000),PP,Highres.  Make these the same and click 'Export to Server' in SODA and F5 in WISKI to see if it comes in.
3. PP has the same issues set out in 1 and 2 so if it doesn't work you will have to contact @cvance and see if there's an internal block keeping the ZRXPs from WISKI.

On a side note your datalogger is set up for EDT instead of EST so you might run into some weird time stamps in WISKI.

[Patrick Larson]

Last manual download was yesterday at 13:00 . This is a Parks Canada gauge and I have asked to the point of nagging that they keep EST but it is not a concern for them. I will make the changes you have suggested and see where that gets things.

[Patrick Larson]

Success. Changed PP to PC in WISKI and SODA. Took out extra bracket. Other changes you suggested, did an execute and off went the data to WISKI. Thanks.