I am currently using a Cr 1000 that is used to run a YSI Inc/ Integrated Systems Vertical Profiler to collect hydrografic information. The program/code is generated on a YSI wizard and then I edited to suite my needs.
Current set up is
Cr1000(187) to Cr1000(188) to null modum to IP for remote connection via Logger net. I am using (188) as a router to my (187) They are in the same box, one is for met data and one for hydro.
Thre are ports and flags you have to set to initate the profiling sequence and it then runs a hydrograhpic profile every hour.
The problem I am having is that the code restes the modum every night, and then the data logger resets following that but it does not contiunue with the profling until I return and set the ports and flags to the appropiate setting.
So, my questions are...
Is it neccesary to reset the datalogger after a modum reset? For communications maybe? I had read this reset was not neccesaly safe from some post on this site.
Is it neccesary to reset the modum nightly?
Is there a way to make the datalogger set the ports and flags appropiatly upon the reset?
Thanks.
You should check with YSI Integrated Systems. Their embedded program code is very large.
Very large... And a lot of unnecessary stuff that I have been removing.
The datalogger does not need to be reset, and normally wouldn't with the program generated by the YSI software.
Reseting a modem is sometimes necessary, and is probably done as a preventitive measure.
It is quite possible you accidently removed a necessary part. I suggest going back to the last point that sampling part of the program was working correctly in your program, then working up from there.
I have not messed with this portion of the program yet. It is in the begining of the program (I pasted below.) About 18-25 lines in is where it does the modum reset every night just before midnight. And when it does this it follows with an event message Data logger Rest Line 28 and 29 is the "DataLogger Reset" which is the event message I get follwing the modum reset:
2017-07-18 09:42:52.58 0 "Modem ON - Reseting at 1432 / 1440" "modemCurrMin(585); modemResetMin(1432)"
2017-07-18 09:45:17.5 1 "***** Datalogger Reset *****" "Program Signature: 39663; Profiler version: 26.684; debug: 0; Modbus: 0; [35117]."
And when I go back on Logger net Flag (2) has retunred to High, which is the set up mode. So I assume it has actualy done a reset on the datalogger (watch dog maybe? I feel like I had to put one of those in the box.) I understand why the modum reset is important, but if I am using (188) as my router which is directly connected to the null modum and IP should my second cr1000 (187) even be resetting the modum? I feel like that should be (188)s job.
I am also considering chaning that last line I pasted below to Flag(2) = false So that bring the question is =true and =false the same as Flag 2 High and Flag 2 Low? becase if so changin that to false my prevent it entering set up mode upon that modum/data logger reset. Thoughts?
BeginProg
_SndMoving = true
If _sondetype = 1 Then
LineEnd = CR
Else
LineEnd = CRLF
EndIf
ProgSignature=Status.ProgSignature(1,1)
_initDbg = 0 '#PFL_Debug#
_Debug = _initDbg
RealTime(rTime)
currJulianTime = (rt_Hour * 3600) + (rt_Minute * 60) + rt_Second
If (CommMode <> 2) Then
bModemOn = true
PortSet(9,NOT(bModemOn))
modemCurrMin = rt_Hour * 60 + rt_Minute
_temp4 = 0
If (modemCurrMin MOD modemOFFInterval) > modemOFFOffset Then _temp4 = 1
modemResetMin = (((INT(modemCurrMin/modemOFFInterval) + _temp4) * modemOFFInterval) + modemOFFOffset)
EventMsg = "Modem ON - Reseting at " + modemOFFOffset + " / " + modemOFFInterval
EventDetails = "modemCurrMin(" +modemCurrMin+"); modemResetMin(" +modemResetMin+")"
CallTable EventLog()
Else
bModemOn = true
EndIf
resetModem = 0
moveToSameTDCntr = 1
EventMsg = "***** Datalogger Reset *****"
EventDetails = "Program Signature: " + ProgSignature + "; Profiler version: "+ progVersion + "; debug: "+ _Debug + "; Modbus: "+ CommMode + "; [" + currJulianTime + "]."
CallTable EventLog()
Call ResetToDefaultValues()
PortsConfig (&B00000111,&B11111111)
_FirstTim = 1
ScanCounter = 0
DoLoopCounter = 0
sndInfoType = 5
GetSondeInfo()
CallTable EventLog()
If (CommMode) Then Call GetSondeParameterOrder()
_stabDelay = 60000 '#PFL_StabDelay#
Flag(2) = True
Changing Flag(2) to false did do what I expected, but just lead me to another problem. Thanks for the help. Delte this is neccesary.
Hello HKing,
I am the lead for two YSI profilers with what sounds like a similar setup, each has two CR1000, one for sonde data and one for met data. We use Sierra RV50 Airlink modems. Our regime is user defined depth w/o depth sounder. 6 profiles in the summer, 3 in the winter. I don't think I am having the same issue as you with the CR1000 logger resetting after the modem reboots, but they are going into setup mode very frequetly. We used to run 6600 YSI sondes, but have recently switched to EXO sondes with a EXO Link adapter. Since making this switch both units have been running intermittentlty at best. We used to have a lot of issues with the aging 6600s, but now I'm more suspect of the progaming to run EXO sondes than the sondes themselves. I have been asured by YSI that the sondes are set up for deployment correctly.
I'm mostly wondering are you running EXO sondes? And if so what version of the YSI wizzard do you run? Are you having more success since you last posted to this thread?
Thanks!