nfsservice to run on CMU add this to startup so it always starts and added
/etc/exportsfile to CMU
ntp.conf( add this to the installation doc )
/media/imageson BBB is the SD card. 16GB
/lbc) in SVN
testtrackersprograms using the
ccdctrlclient on the BBB.
|high|| Not controlling the shutter. We tried from the
Update, 20161007: FP has given Alessandro a procedure to check out the shutter control wiring on the SPC card.
|high|| cannot take an image longer than 30secs. The CTR code does not return the HB method that ccdctrl calls until after it finishes integration - by then it has turned off because it thinks it's not communicating to the BBB.
(see screenshot below)
Update 20161017: SkyTech has updated the software and KS has verified the fix.
|SkyTech, mutex problem|
|high|| PRU timeout (
AdP suggested this was a timeout on the number of pixels expected. KS made a test resetting the expected pixels when windowing is requested, which worked.
Is this a new API feature? If so, we need to make sure it's set correctly for all cases.
AdP says: "This have been one of the latest problems with SkyTech. There is a problem with the new version that did not exist in the previous. Now the controller does not know how many pixels to wait for and the
|high|| Once we started using the high-level testing, we saw RPC timeouts between CMU and BBB - seen this on presets, stop, query
preset timeout is 40s
open/telemetrycheck are 20s
close/init are long, 120s
resume/query are only a 2s timeout
shutter/upload/stop only 10s
expose is set to exposure time+24+6(if flushing)+1
save is set to 40+10 if not MT, otherwise 10s
|med||saw blank fits filenames at one point (20160729, 19:36, 19:43, etc), this occurs when we have telemetry error during exposure||INAF/LBTO|
|high|| saw seg faults of the
also saw this when I had a query timeout and it did a destroy of the status RPC handle
|maybe need to make sure we can get out of the HB error more easily. Since it is a new feature, maybe it should be easier to recover from. We may run in to it a lot due to the resource availability of the BBB.|
|med|| recover in camera code wants to do a stop/initialize, but that hangs in
AdP says: "Do not be reluctant too much. On Windows mutexes could be multiple locked if this happens in the same thread. Posix threads are not the same some maybe release is required."
KS changed stop to release the mutex and made resume lock the mutex again, to enable.
| there's a TOO FEW or TOO MANY CTR error now; we can change the code to not calculate and check for it
If it times out like the windowing case for too few, how do you ever get TOO FEW as an error?
| saw a PRU timeout and then a
| add a close of the log file to the
| test mounted drive from archive to BBB,
we checked later and it was ok - must have been related to some other weirdness
ccdctrldirectory on BBB. Lots of confusion about why the hard flush every time we take a sci image with the test program. The test program is really minimally modified, so I have to think it worked this way before. FP said it should flush after safety off and after it has been a long time since exposure.
ExecuteWipeTableturn off on LBC should do a
poweroffon the BBB before turning off CCD controller Thursday, we connected to the red tech detector. By 3pm, Fernando was happy with the results from the red tech. Send Bellesi document comments - just a couple Made few
TelemetryCheck(check telemetry on test program) doesn't look at the new status structure - probably should, and print it out.
CHECKOFFmacro turns enables the clock and bias lines via the API, which turns the voltages on. Modified
testtrackersto work with a single channel (like we need when testing CCD controller), or both (like we need for testing image analysis). Modified
trackers.cto pay attention to IA enable from config before doing any IDL stuff (open/close). Modified
testcamerato spawn a thread querying status every 10secs, otherwise the hardware shuts down on us (bias values of 0) if we don't take images constantly. When do we see the _1, _2, _3, _4 fits files? How does the high level software set the multi-fits vs multi files?
ErrorCheckAndRecoveris called for preset, expose, save. It tries one re-init cycle.
test.cthat FP would like
Ciao Kellee,The only updates were to
the controller is now working in SkyTech for long exposure images: they changed DLL to get that result.
We had some problems with test program because of a new parameter (maybe you inserted it)
on the stop and resume functions to trigger safety stop. In my mind stop and safety are very different things and they should not be called in correlation, but of course you addressed a problem in this way and if it works it is fine for me.
So please rename the attached file to .zip and extract at least CTR_PROCEDURES and ccdctrl.c code and test.c code (in ccdctrl.c I changed the error returned to allow working without shutter connected, but Fernando will explain more). Ciao
Andrea and Fernando
|PNG||60secexposurenohb.PNG||manage||153 K||29 Jul 2016 - 18:33||UnknownUser||Long exposure timeout|
|PNG||PRUTimeoutWithWindowing.PNG||manage||85 K||29 Jul 2016 - 18:34||UnknownUser||Windowing exposure timeout|
|PNG||StatusCheckDuringHBERror.PNG||manage||85 K||29 Jul 2016 - 18:34||UnknownUser||Status check during HB|