[kepler-dev] [Bug 5332] New: cr1k_d doesn't reliably connect to logger

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5332

           Summary: cr1k_d doesn't reliably connect to logger
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sensor-view
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Fairly often cr1k_d fails to connect to the logger. I get output like:

CR1K sample rate should be 30 second(s)
-> <MAIN> Open Serial Port: /dev/ttyUSB0 Succefully!
-> <MAIN> Connecting to datalogger...
[ERR-recvFrame] timeout (get data 0 bytes)
-> [ERR] cmdRING
-> Link error
-> <MAIN> [ERR] fail to connect datalogger, please check cable
-> <MAIN> [ERR] Driver initialization failed
-> Serial port /dev/ttyUSB0 closed
-> cr1k_d exit


or:


CR1K sample rate should be 30 second(s)
-> <MAIN> Open Serial Port: /dev/ttyUSB0 Succefully!
-> <MAIN> Connecting to datalogger...
-> [ERR] Link State error after cmdRING (09)
-> <MAIN> [ERR] fail to connect datalogger, please check cable
-> <MAIN> [ERR] Driver initialization failed
-> Serial port /dev/ttyUSB0 closed
-> cr1k_d exit


I thought it might be dcd_mgr interfering, but that doesn't seem to be -- in
span.sh, which launches both processes, I added a long sleep between them and
cr1k_d still periodically fails.

I'll add this to the list of questions/requests for ISI folks.
If we're unable to find a better solution, an alternate is to detect the fail
and retry N times.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.