[Kristine RogersParticipant]

I did try resynchronizing the battery and solar panel this morning for SL133.  The sensor was shut off at 9:06 a.m. and turned back on at 9:09 a.m.  Hopefully this resolves the issues that we have been having.

[Carol ArmstrongParticipant]

This is the report for 8/14/19.

@zador SL130 – W Branch Red Clay – There are still no signal transmissions since 7/10/19.  Is the data being saved on the sd card?

@rogers SL133-Upper Paulinskill  – Resynchronizing the battery did not solve the low battery problem, though the battery does not reach as low a level as before.  It continues to flag down to 3.6-3.7 v.  Rachel Johnson, is the battery pattern typical of moisture on the battery?  Even a small amount of moisture seems to affect its performance.

@gosse @anderson SL151-Naylor’s Run – Turbidity is highly elevated and there might be significant material wrapped on the sensors.  The battery is rapidly declining without significant recovery, now down to 3.62 v, and it might need to be charged.

@williams – sl170-Chestnut Run – Turbidity reached floor level (~1 NTU) on 7/22/19 and has not changed significantly since then even during events of high depth.  Could this be normal at this site?

@johnson – SL172 – Indian Field Br – Turbidity is extreme – ~1000 NTU – and sensors might be embedded in sediment or wrapped.  Battery is declining rapidly and is now <3.7 v.

@wang SL176 – Schuylkill River/Bartram’s Garden – On MMW, both DO measurements are labeled as percent of saturation, but the second one appears to be DO ppm.  The labels are identical and the data is not.  You could report it to MMW via bithub (https://github.com/ODM2/ODM2DataSharingPortal/Issues), which get the message to the MMW engineers at Limnotech.

@fenchel SL191 @crothers – Schuylkill Greenways – Conductivity and depth became very abnormal on 8/10. Turbidity also became very stable and low on 8/11. Temperature of the water and logger box merged on 8/12. DO continues to be measured but lost its cyclical patterns on 8/10. Appears that this large stream went dry? If so, this is the first time this has happened since installation, and could explain the abnormal signals.

[Carol ArmstrongParticipant]

This is the report for 8/20/19.

@morgan SL132-Mill C-Hickory Hills – The battery might need to be recharged because it is persistently dropping and now 3.65v.

@gosse, @anderson SL151-Naylor’s Run – The battery appears to need to be recharged.

@bressler, @johnson SL172 Indian Field Br battery is declining and now 3.55 v.  Unknown station manager now; was Sarah Johnson of Littoral Society.  Please inform who is maintaining this sensor station, if anyone.

@wang SL176 Schuylkill R – Bartram’s Garden is not transmitting since 7/19/19 (not to MMW or Dreamhoster).  Is cellular signal lost?

[Carol ArmstrongParticipant]

This is the report for 8/27/19.

@lawler SL102-Musconetcong D – Water depth dropped below 0; did stream dry and sensors become fully exposed?

@baldino SL116-West Portal B – Data not available on either portal after 7/26/19. Is data being saved to sd card?

@gosse, @anderson SL151-Naylor’s Run.  Has sensor station been stabilized after major discharge event?  Data appears normal.

@wilson SL169-Cherry at pour point.  Turbidity is 500-1400 NTU.

@ferrell SL190-Independence School.  Water depth dropped 59 mm in five minutes today – what could cause this? Water was steady at around 160mm and then dropped to 104mm at 09:41 (EST) and remained at this level the rest of the day today. This is an historic low for this site, except one abnormal signal last December.

[Carol ArmstrongParticipant]

Report for 9/3/19

@nlawler SL102 Musconetcong D, water depth levels do not appear normal – near zero unless sensors were moved and are higher in the stream. Could you update my information?

@roth @gisondi Pennpack sites, SL111 and SL112 are both transmitting on Dreamhoster again and the data of the past month could not be found on MMW.  Cannot see the history on Dreamhoster because these are early sites with a great amount of data.  Looking at history based on forum notes, SL111 Pennpack U-Pennypack Parkway does not appear to have been cleaned, however this stream fouls frequently and runs warm.  Does this site need more volunteer assists?

@cbaldino SL116-West Portal B – Data not available on either portal after 7/26/19. Is data being saved to sd card?

@lblanton SL117-Sandy Run –  Battery at 3.34 v.

@lblanton SL118-Wissahickon.  Turbidity data showing a square wave pattern in relation to non-peaking water depth that does not appear normal. Square wave turbidity covarying with depth occurs during baseflow. Data stopped transmitting to MMW on 8/29/19.

@gmadden SL122-Buckwha D-Creyer.  Data not transmitting to Dreamhoster or MMW. Is data being saved to sd card?

@krogers SL133 Upper Paulinskill at Sussex C.  Turbidity is the only variable that does not appear on MMW – can it be added? Full history of data apparently overloads Dreamhoster, so cannot check history beyond current 48 hours. Battery continues to drop down to 3.6 v.

@sjohnson sl172 Indian Field Br – Battery is persistently declining and now 3.40 – can it be recharged?  Turbidity is elevated and flashy, and has increased.

[Carol ArmstrongParticipant]

Report for 9/9/19

@lblanton SL117 Sandy Run – the station stopped transmitting on 9/2/19 when the battery was at 3.34 v.

@smorgan SL132 Mill Ck – The battery was recharged on 8/26 but began to drop immediately, now at 3.73v. This problem, of the battery apparently losing v after recharging, developed about 8/1/19. Do you need to replace the battery or is there another reason?

@jmoore, @lmoore SL150-Marsh Ck-Fairview – Four times today the turbidity signals dropped and then returned to same level 10 minutes later.  This occurred when water depth was at levels in which normal looking turbidity signals have been seen in the past.  Do you attribute the pattern of sudden drops in turbidity to the low water?  However, this pattern is new.

@sjohnson SL172 Indian field Br – Transmissions stopped on 9/8/19 at 17:36 when battery flatlined at 3.38 v. Turbidity was highly elevated.

[Kristine RogersParticipant]

If I cut back some of the tree and shrub branches that are reducing the amount of sunlight that reaches the solar panel, do you think the battery voltage will go back up to where it needs to be or is it so low that there’s a larger problem and it’s time for a new battery?

[David BresslerParticipant]

@rogers, re the battery at your station, it seems to be charging well even though it is dipping kind of low (3.6v) at night.  This is ok but yes definitely if you clear veg from around the solar panel that would help.  Also keeping that veg away from the logger itself is a good idea because it’ll reduce the chances of water and insects and whatever else accessing the box.

[Carol ArmstrongParticipant]

Report for 9/18-19/19

@lawler SL102 Musconetcong U-Riverside Is conductivity reading at 0 uS/cm because water depth is low, 10-25mm? Beginning at the end of August, conductivity began to go to 0 uS/cm during low flow while before that there was high conductivity even during low flows. Did point source pollution decrease during September?

@blanton sl117 Sandy Run.  This site is back on line as of 9/13.  When the battery was recharged, it only returned to 3.81v, and was in decline a few days later.  @Hicks and @Johnson, thoughts on this?  Site does not use a solar panel.

@blanton, @torun sl118 Wissahickon.  @bressler  Data stopped transmitting from dreamhoster to MMW on 8/29.  Not sure if your use of the data requires this, but based on recent Dreamhoster data, the turbidity data appears strange.  At similar low water depths in the past, turbidity was measured at high levels at times, as expected from the urban setting.  Now, no peaks are measured at the same low water depths.

@shanemorgan sl132 Mill C-Hickory Hills.  Data stopped being sent on 9/15 to MMW, battery at 3.6v.

@moore @kalusky sl150 Marsh Ck D-Fairview Rd.  @hicks, @johnson, @bressler.  Strange turbidity signals since 9/9/19. During water peaks, turbidity increases as expected from possible debris or blocking of light from optic window, but during the high water peak the turbidity reading drops to negative value then shoots back to prior level. Only occurring during high water peaks, and not all water peaks. Could there be something unusual sitting around the sensors? Or is it a sensor or board problem?

@anderson @gosse @eiannelli @biannelli sl151 Naylor’s Run.  On 9/17/19, the depth jumped from 484mm to 498mm in five minutes, and then remained at about 500mm. Heather noted prior sudden increases. Any idea about the area around the station that could be causing these sudden increases? The increases are not so great that they are completely implausible. The depth seems to come down after a rain event. Is there a facility nearby sending water directly into the stream?

@melvin @ruggiero SL 172 Indian Field Br.  The battery is low and stable at 3.38v.  Could it be recharged? Turbidity still highly elevated.

@lawler, @reeves SL179 Lubbers Run.  Battery is persistently declining, now at 3.59v. Turbidity highly elevated.

[Jim MooreParticipant]

It looks to me like a loose wire connection on the turbidity sensor and at hi water there is increased flow which wiggles the cable enough to cause an intermittant.  I noticed that the ctd indicated water level is negative but this could just be offset error and the sensor is in water hence normal turbidity readings.  See attached screen shot.

Carol- would you suggest a field visit.  We could pull the sensor and wiggle the wires to see if we can duplicate the readings?

Attachments:

1. 

   Screen-Shot-2019-09-20-at-9.45.31-AM.png
   

[Author]

Posts