Closed rumengb closed 3 years ago
It does work :) Temperature is decreased or increased 1 degree every 5 seconds/
It just does not work sometimes. I waited for several minutes. Then reloaded the diver.
On Fri, Oct 30, 2020, 3:25 PM Peter Polakovic notifications@github.com wrote:
It does work :) Temperature is decreased or increased 1 degree every 5 seconds/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/indigo-astronomy/indigo/issues/383#issuecomment-719550533, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5EZBOJM6YX2AGU4QIDZKDSNK5FLANCNFSM4TEWFBLA .
It is not only the cooler. When i start guiding with guider imager, start exposures with imager and turn the temperature control on. very often it never starts, sometimes guider freezes like in the example below:
rumen@vega:~/work/indigo_deadlock_detector.git$ ./indigo_deadlock_detector.sh indigo_server Inspecting 'indigo_server' (pid = 363067) for deadlocks [New LWP 363068] [New LWP 363069] [New LWP 363070] [New LWP 363071] [New LWP 363072] [New LWP 363076] [New LWP 363078] [New LWP 363079] [New LWP 363080] [New LWP 363081] [New LWP 363103] [New LWP 363117] [New LWP 363143] [New LWP 363286] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007f2861e8849f in __libc_accept (fd=9, addr=..., addr@entry=..., len=len@entry=0x7ffe95a4b3e4) at ../sysdeps/unix/sysv/linux/accept.c:26 None
Thread 15 (Thread 0x7f283f7fe700 (LWP 363286)):
Thread 14 (Thread 0x7f283ffff700 (LWP 363143)):
Thread 13 (Thread 0x7f2851ffb700 (LWP 363117)):
Thread 12 (Thread 0x7f28517fa700 (LWP 363103)):
Thread 11 (Thread 0x7f28527fc700 (LWP 363081)):
Thread 10 (Thread 0x7f2852ffd700 (LWP 363080)):
Thread 9 (Thread 0x7f28537fe700 (LWP 363079)):
Thread 8 (Thread 0x7f2853fff700 (LWP 363078)):
Thread 7 (Thread 0x7f2858e47700 (LWP 363076)):
Thread 6 (Thread 0x7f2859648700 (LWP 363072)):
Thread 5 (Thread 0x7f2859e49700 (LWP 363071)):
Thread 4 (Thread 0x7f285a64a700 (LWP 363070)):
Thread 3 (Thread 0x7f2861024700 (LWP 363069)):
Thread 2 (Thread 0x7f2861825700 (LWP 363068)):
Thread 1 (Thread 0x7f2861829600 (LWP 363067)):
Blocked threads:
[Inferior 1 (process 363067) detached]
And the exposure becomes busy... and stays like that forever:
it is not new.... it affects 2.0-128 too on both rpi and intel.
The issue is introduced with 2.0-126. it does not happen with 2.0-124.
fixed by 6850e5cbd88f076acde4440724a5d5869df1e057
turn on cooling set target temperate and nothing happens.