Welcome, Guest
Username: Password: Remember me
27 Feb 2017
INDI development team is happy to announce the release of INDI Library v1.4.0. This new exciting release builds on the maturity of INDI Library and comes with many new supported devices and fixes for existing drivers. Several improvements and enhancements are included in this release including native support for Cygwin and MacOS platforms in addition to Linux, BSD, and Windows (Client only).
Read More...
  • Page:
  • 1

TOPIC: INDISERVER does not send BLOBs to client

INDISERVER does not send BLOBs to client 1 month 3 weeks ago #15848

  • emk
  • emk's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 14
  • Thank you received: 1
So, I'm still writting this client to automated evaluate images, either in FITS or any other format which ist supported by dcraw, cfitsio or opencv.
I've a EOS 6D and a ZWOptical ASI 120MM camera in usage. They both work fine using them with indiserver 1.3.1 and kstars. The last as client.

My problem is, that the newBlob method of my client is not called after I successfully send the sendNewNumber command containing the new CCD_EXPOSURE property, by neither the EOS nor the ASI driver. (Successfully like, I get an response of the server and the mirror of the EOS for example does ''klick'') If I do the same using KStars the image arrives rapidly. Or if I have both, KStars and my client, running and the client did order an exposure, the made image only arrives at the KStars client.

Before doing any images I send the UPLOAD_MODE property for both like in the following example
if( !strcmp(property->getName(), "UPLOAD_MODE") )
      {
	ISwitchVectorProperty *upload_mode;
	upload_mode = cam_env1.cam->getSwitch("UPLOAD_MODE");
	if (upload_mode == NULL)
	{
	  IDLog("Error: unable to find %s %s property...\n", cam_env1.cam->getDeviceName(), "UPLOAD_MODE");
	  return;
	}
	upload_mode->sp[0].s = ISS_ON; //to client
	upload_mode->sp[1].s = ISS_OFF; //save local
	upload_mode->sp[2].s = ISS_OFF; //both
	sendNewSwitch(upload_mode);      
      }
where cam_env1 is a struct containing the INDI::BaseDevice pointer to the camera which arrives with the newDevice methode of the client.

The exposures are ordered like
void cl_Client::takeExposure(st_CameraEnvData* cam_env)
{
  INumberVectorProperty *ccd_exposure = NULL;
  ccd_exposure = cam_env->cam->getNumber("CCD_EXPOSURE");
  
  if (ccd_exposure == NULL)
  {
    IDLog("Error: unable to find %s CCD_EXPOSURE property...\n", cam_env->cam->getDeviceName());
    return;
  }
  
  IDLog("Requested a %f seconds exposure for %s.\n", cam_env->requested_exposure_time, cam_env->cam->getDeviceName());
  ccd_exposure->np[0].value = cam_env->requested_exposure_time;
  sendNewNumber(ccd_exposure);
}

Do I overlook something?
I'd be very thankful for any help or hints.

Regards
Erik

Please Log in or Create an account to join the conversation.

INDISERVER does not send BLOBs to client 1 month 3 weeks ago #15867

  • pch
  • pch's Avatar
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 32
  • Thank you received: 27
Did you call setBLOBMode() ?
See also github.com/indilib/indi/blob/master/libi.../tutorial_client.cpp
Patrick
The following user(s) said Thank You: knro, emk

Please Log in or Create an account to join the conversation.

INDISERVER does not send BLOBs to client 1 month 3 weeks ago #15966

  • emk
  • emk's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 14
  • Thank you received: 1
Thanks alot! That made the job.

I worked with the Client Development Tutorial: www.indilib.org/develop/tutorials/107-cl...opment-tutorial.html
There is no setBLOBMode Function mentioned. Could that be added?
Anyway, I shoud have stumbled earlier about that by myself.. :whistle:

Erik

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.124 seconds

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!

Gallery

Replica

Why INDI

Replica