I've seen them too - in fact I was thinking about the 183, but I've decided to go for the 533 sensor. In addition to that, UK now has customs, so sadly, this is no longer an option.
I’m bumping up this thread to mention that the strange pattern issue, was caused by the setting at indi panel for 8bit camera mode, that the drivers loads it automatically.
But since today the temperature issue is still there…I was just looking into the GitHub but I am far from a dev to understand the root of the problem
The generic timer call back is used for temperature monitoring
void ToupBase::TimerHit(){
if (isConnected() == false)
return;
if (InExposure){
struct timeval curtime, diff;
gettimeofday(&curtime, nullptr);
timersub(&ExposureEnd, &curtime, &diff);
double timeleft = diff.tv_sec + diff.tv_usec / 1e6;
if (timeleft < 0)
timeleft = 0;
PrimaryCCD.setExposureLeft(timeleft);
}
if (m_Instance->model->flag & CP(FLAG_GETTEMPERATURE)){
double currentTemperature = TemperatureN[0].value;
int16_t nTemperature = 0;
HRESULT rc = FP(get_Temperature(m_CameraHandle, &nTemperature));
if (FAILED(rc)){
LOGF_ERROR("get_Temperature error. %s", errorCodes[rc].c_str());
TemperatureNP.s = IPS_ALERT;
}
else
{
TemperatureN[0].value = static_cast<double>(nTemperature / 10.0);
}
switch (TemperatureNP.s){
case IPS_IDLE:
case IPS_OK:
if (fabs(currentTemperature - TemperatureN[0].value) > TEMP_THRESHOLD / 10.0){
IDSetNumber(&TemperatureNP, nullptr);
}
break;
case IPS_ALERT:
break;
case IPS_BUSY:
// If we're within threshold, let's make it BUSY ---> OK
// if (fabs(TemperatureRequest - TemperatureN[0].value) <= TEMP_THRESHOLD)
// {
// TemperatureNP.s = IPS_OK;
// }
IDSetNumber(&TemperatureNP, nullptr);
break;
}}
SetTimer(getCurrentPollingPeriod());
}