erik replied to the topic 'ASI 120MC failes to expose' in the forum. 1 month ago

is your indi driver version compatible with your asi firmware?

right now i've outdated firmware on my asi120, which doesnt work with new indi driver versions, but works find with my pi, which has still an older indi driver installed.

viel glueck

Read More...

erik replied to the topic 'KStars not starting up after indi update!' in the forum. 7 months ago

Solved.

# To use INDI Qt5 Client library only in your application:
#
# find_package(INDI CLIENTQT5 REQUIRED)
#
#   if(INDI_FOUND)
#      include_directories(${INDI_INCLUDE_DIR})
#      add_executable(myapp myapp.cpp)
#      target_link_libraries(myapp ${INDI_CLIENTQT5_LIBRARIES})
#   endif(INDI_FOUND)
Seems not to work.
find_package(INDI REQUIRED client)
..worked for me, though I still had to link to libnova.

Read More...

erik replied to the topic 'KStars not starting up after indi update!' in the forum. 7 months ago

Hi,

has this problem been solved for all clients? I'm writing a little client and am getting problems with the linkage of the client libraries. It did actually work a few weeks ago, but since I upgraded to 1.4 the FindINDI.cmake file gives an error.

CMake Error at CMakeLists.txt:19 (find_package):
  find_package called with invalid argument "CLIENT"
for
find_package(INDI CLIENT REQUIRED)
in cmake.

Using the old FindINDI.cmake gives unsolved references to the INDI::BaseClient class methods.
Package: indi-full
Versions: 
1.4~201705080649~ubuntu16.04.1 (/var/lib/apt/lists/ppa.launchpad.net_mutlaqja_ppa_ubuntu_dists_xenial_main_binary-amd64_Packages)
 Description Language: 
                 File: /var/lib/apt/lists/ppa.launchpad.net_mutlaqja_ppa_ubuntu_dists_xenial_main_binary-amd64_Packages
                  MD5: 39f6de7ad7ceebdae133f1978240e974
 Description Language: 
                 File: /var/lib/apt/lists/ppa.launchpad.net_mutlaqja_ppa_ubuntu_dists_xenial_main_binary-i386_Packages
                  MD5: 39f6de7ad7ceebdae133f1978240e974
 Description Language: en
                 File: /var/lib/apt/lists/ppa.launchpad.net_mutlaqja_ppa_ubuntu_dists_xenial_main_i18n_Translation-en
                  MD5: 39f6de7ad7ceebdae133f1978240e974


Reverse Depends: 
  indi-full:i386,indi-full
Dependencies: 
1.4~201705080649~ubuntu16.04.1 - libindi1 (2 1.2) libindi-dev (2 1.2) libindi-data (2 1.2) indi-bin (2 1.2) indi-eqmod (0 (null)) indi-sx (0 (null)) indi-sbig (0 (null)) indi-apogee (0 (null)) indi-gphoto (0 (null)) indi-qsi (0 (null)) indi-fishcamp (0 (null)) indi-maxdomeii (0 (null)) indi-asi (0 (null)) indi-aagcloudwatcher (0 (null)) indi-ffmv (0 (null)) indi-dsi (0 (null)) indi-qhy (0 (null)) indi-gpsd (0 (null)) indi-mi (0 (null)) indi-duino (0 (null)) indi-fli (0 (null)) indi-nexstarevo (0 (null)) indi-full:i386 (32 (null)) 
Provides: 
1.4~201705080649~ubuntu16.04.1 - 
Reverse Provides:
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:        16.04
Codename:       xenial


Read More...

erik thanked Jasem Mutlaq in topic ASI 120MC failes to expose 8 months ago
erik created a new topic ' ASI 120MC failes to expose' in the forum. 8 months ago

Hey,
I'm having problems with my ASI 120MC. It connects just fine and the client is receiving everything fine. But when I try to make an exposure, doesn't matter how long, it fails to get the image from the camera. It also seems to have problems setting the CONTROL parameter like Gain and so on.

My INDI version is 1.3.1+r2850~201702231016~ubuntu16.04.1. The version of the asi driver is 0.5+r2850~201702221347~ubuntu16.04.1. The cam itself is about 3 years old, it worked already sometime last year in autumn.

And here goes the log-file. In sec 42 I started an 1 seconds exposure, it obviously failed and later on, in seconds 112 I tried to change BandWidth and later Gain, it both failed.
The error code 16 sttands for ''ASI_ERROR_GENERAL_ERROR//general error, eg: value is out of valid range'', but I've no idea how the values could have been out of range since i set them via the Kstars slide interface and that does not allow to set values out of range...

INFO	15.008676 sec	: Session log file /home/gamepod/.indi/logs/2017-04-06/indi_asi_ccd/indi_asi_ccd_07:37:10.log
DEBUG	24.472871 sec	: Toggle Logging Level -- Driver Debug
DEBUG	32.377863 sec	: Attempting to open ZWO CCD ASI120MC...
INFO	32.837732 sec	: Setting intital bandwidth to AUTO on connection.
INFO	32.839314 sec	: CCD is online. Retrieving basic data.
DEBUG	32.840057 sec	: Control #0: name (Gain), Descp (Gain), Min (0), Max (100), Default Value (50), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840127 sec	: Adding above control as writable control number 1
DEBUG	32.840151 sec	: Adding above control as auto control number 1
DEBUG	32.840173 sec	: Control #1: name (Exposure), Descp (Exposure Time(us)), Min (64), Max (2000000000), Default Value (33000), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840212 sec	: Control #2: name (Gamma), Descp (Gamma), Min (1), Max (100), Default Value (50), IsAutoSupported (False), isWritale (True) 
DEBUG	32.840233 sec	: Adding above control as writable control number 2
DEBUG	32.840266 sec	: Control #3: name (WB_R), Descp (White balance: Red), Min (1), Max (100), Default Value (52), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840285 sec	: Adding above control as writable control number 3
DEBUG	32.840303 sec	: Adding above control as auto control number 2
DEBUG	32.840324 sec	: Control #4: name (WB_B), Descp (White balance: Blue), Min (1), Max (100), Default Value (95), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840340 sec	: Adding above control as writable control number 4
DEBUG	32.840358 sec	: Adding above control as auto control number 3
DEBUG	32.840378 sec	: Control #5: name (Brightness), Descp (Brightness), Min (0), Max (20), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.840394 sec	: Adding above control as writable control number 5
DEBUG	32.840414 sec	: Control #6: name (BandWidth), Descp (USB bandwidth percentage), Min (40), Max (100), Default Value (50), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840430 sec	: createControls->set USB 40
DEBUG	32.841846 sec	: Adding above control as writable control number 6
DEBUG	32.841877 sec	: Adding above control as auto control number 4
DEBUG	32.841899 sec	: Control #7: name (Flip), Descp (Flip: 0->None 1->Horiz 2->Vert 3->Both), Min (0), Max (3), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.841917 sec	: Adding above control as writable control number 7
DEBUG	32.841937 sec	: Control #8: name (AutoExpMaxGain), Descp (Auto exposure maximum gain value), Min (0), Max (100), Default Value (50), IsAutoSupported (False), isWritale (True) 
DEBUG	32.841956 sec	: Adding above control as writable control number 8
DEBUG	32.841981 sec	: Control #9: name (AutoExpMaxExp), Descp (Auto exposure maximum exposure value(unit second)), Min (1), Max (60), Default Value (30), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842000 sec	: Adding above control as writable control number 9
DEBUG	32.842022 sec	: Control #10: name (AutoExpMaxBrightness), Descp (Auto exposure maximum brightness value), Min (50), Max (160), Default Value (100), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842039 sec	: Adding above control as writable control number 10
DEBUG	32.842064 sec	: Control #11: name (HighSpeedMode), Descp (Is high speed mode:0->No 1->Yes), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842083 sec	: Adding above control as writable control number 11
DEBUG	32.842103 sec	: Control #12: name (Mono bin), Descp (bin R G G B to one pixel for color camera, color will loss), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842121 sec	: Adding above control as writable control number 12
DEBUG	32.842141 sec	: Control #13: name (Temperature), Descp (Sensor temperature(degrees Celsius)), Min (-500), Max (1000), Default Value (20), IsAutoSupported (False), isWritale (False) 
DEBUG	32.842160 sec	: CCD ID: 0 Width: 1280 Height: 960 Binning: 1x1 Image Type: 0
DEBUG	32.842179 sec	: Supported Video Format: ASI_IMG_RAW8
DEBUG	32.842220 sec	: Supported Video Format: ASI_IMG_RGB24
DEBUG	32.842240 sec	: Supported Video Format: ASI_IMG_Y8
DEBUG	32.842260 sec	: Supported Video Format: ASI_IMG_RAW16
INFO	32.843264 sec	: The CCD Temperature is 23.000000
DEBUG	32.843313 sec	: setupParams ASISetROIFormat (1280x960,  bin 1, type 0)
DEBUG	41.248927 sec	: StartExposure->setexp : 1.000s
DEBUG	42.455676 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	42.555910 sec	: StartExposure->setexp : 1.000s
DEBUG	43.830414 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	43.930609 sec	: StartExposure->setexp : 1.000s
ERROR	45.257410 sec	: Exposure failed after 3 attempts.
DEBUG	84.000917 sec	: ISNewNumber->set ctrl 0: 70.00
DEBUG	112.985600 sec	: ISNewNumber->set ctrl 6: 52.00
ERROR	112.985666 sec	: ASISetControlValue (BandWidth=52) error (16)
DEBUG	118.390615 sec	: ISNewSwitch->SetControlValue 0 70.00
DEBUG	118.394616 sec	: ISNewSwitch->SetControlValue 3 52.00
DEBUG	118.396215 sec	: ISNewSwitch->SetControlValue 4 95.00
DEBUG	118.397847 sec	: ISNewSwitch->SetControlValue 6 40.00
ERROR	118.397887 sec	: ASISetControlValue (BandWidth=40) error (16)
DEBUG	124.971306 sec	: StartExposure->setexp : 1.000s
DEBUG	126.294383 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	126.394552 sec	: StartExposure->setexp : 1.000s
DEBUG	127.723626 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	127.823817 sec	: StartExposure->setexp : 1.000s
ERROR	128.825398 sec	: Exposure failed after 3 attempts.
INFO	132.411172 sec	: CCD is offline.

Anybody any ideas? Thanks in advance!

Erik

Read More...

erik replied to the topic 'INDISERVER does not send BLOBs to client' in the forum. 8 months ago

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

Read More...

erik created a new topic ' INDISERVER does not send BLOBs to client' in the forum. 8 months ago

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

Read More...

erik replied to the topic 'OpenCV' in the forum. 9 months ago

Thanks first of all. I've got another question kinda related to that, but didn't want to start a new thread.

How can I read the number of channels from the camera interface? So, I got the ASI 120 CM, which means it makes color images and it's fits must hence have three dimensions. Is there a property (INDI interface or fits IO) where I can read that from. I wasn't able to find some of that kind yet.

What I alread got is below. Still missing the automated declaration of cv_type.

Thanks in advance!

int cv_type;
      int status=0;
      int nelements=0;
      char error_status[100];
      int nullval=0;
      int anynull;
      int byte_type=0;
      void* memptr;
      fitsfile * fptr=NULL;
      
      fits_open_memfile(&fptr,&(bp->blob),&(bp->bloblen),2880,realloc,&status);
      
      if(status)
      {
	fits_report_error(stderr, status);  /* print out any error messages */
	fits_get_errstatus(status, error_status);
	DEBUGF(INDI::Logger::DBG_ERROR, "FITS Error (open_memfile): %s", error_status);
	return;
      }
      
      switch (cam_env.bits_per_pixel)
      {
	  case 8:
	      byte_type = TBYTE;
// 	      cv_type = CV_8UC3; //f.eks.
	      break;

	  case 16:
	      byte_type = TUSHORT;
	      break;

	  case 32:
	      byte_type = TULONG;
	      break;

	  default:
	    DEBUGF(Logger::DBG_WARNING, "Unsupported bits per pixel value %d\n", cam_env1.bits_per_pixel);
	    return;
	    break;
      }
      
      nelements = cam_env.pixel.area();
      
      fits_read_img(&fptr, byte_type, 1, nelements, &nullval, memptr, &anynull, &status);
      
      if(status)
      {
	fits_report_error(stderr, status);  /* print out any error messages */
	fits_get_errstatus(status, error_status);
	DEBUGF(INDI::Logger::DBG_ERROR, "FITS Error (read_img): %s", error_status);
	return;
      }
      
      img = cv::Mat(cam_env.pixel, cv_type, memptr);


Read More...

pauledd thanked erik in topic Increasing max CCD Simulator size? 9 months ago
erik thanked Jasem Mutlaq in topic OpenCV 9 months ago
erik replied to the topic 'Increasing max CCD Simulator size?' in the forum. 9 months ago

Only way coming to my mind is to go into the ccd_simulator.cpp and change the max value of the SIM_XRES and SIM_YRES Number Properties in initProperties().

bool CCDSim::initProperties()
{
    //  Most hardware layers wont actually have indi properties defined
    //  but the simulators are a special case
    INDI::CCD::initProperties();

    IUFillNumber(&SimulatorSettingsN[0],"SIM_XRES","CCD X resolution","%4.0f",0,4096,0,1280);
    IUFillNumber(&SimulatorSettingsN[1],"SIM_YRES","CCD Y resolution","%4.0f",0,4096,0,1024);
    IUFillNumber(&SimulatorSettingsN[2],"SIM_XSIZE","CCD X Pixel Size","%4.2f",0,60,0,5.2);
    IUFillNumber(&SimulatorSettingsN[3],"SIM_YSIZE","CCD Y Pixel Size","%4.2f",0,60,0,5.2);
    IUFillNumber(&SimulatorSettingsN[4],"SIM_MAXVAL","CCD Maximum ADU","%4.0f",0,65000,0,65000);
    IUFillNumber(&SimulatorSettingsN[5],"SIM_BIAS","CCD Bias","%4.0f",0,6000,0,10);
    IUFillNumber(&SimulatorSettingsN[6],"SIM_SATURATION","Saturation Mag","%4.1f",0,20,0,1.0);
    IUFillNumber(&SimulatorSettingsN[7],"SIM_LIMITINGMAG","Limiting Mag","%4.1f",0,20,0,17.0);
    IUFillNumber(&SimulatorSettingsN[8],"SIM_NOISE","CCD Noise","%4.0f",0,6000,0,10);
    IUFillNumber(&SimulatorSettingsN[9],"SIM_SKYGLOW","Sky Glow (magnitudes)","%4.1f",0,6000,0,19.5);
    IUFillNumber(&SimulatorSettingsN[10],"SIM_OAGOFFSET","Oag Offset (arcminutes)","%4.1f",0,6000,0,0);
    IUFillNumber(&SimulatorSettingsN[11],"SIM_POLAR","PAE (arcminutes)","%4.1f",-600,600,0,0); /* PAE = Polar Alignment Error */
    IUFillNumber(&SimulatorSettingsN[12],"SIM_POLARDRIFT","PAE Drift (minutes)","%4.1f",0,6000,0,0);
    IUFillNumber(&SimulatorSettingsN[13],"SIM_ROTATION","Rotation CW (degrees)","%4.1f",-360,360,0,0);
IUFillNumberVector(SimulatorSettingsNV,SimulatorSettingsN,14,getDeviceName(),"SIMULATOR_SETTINGS","Simulator Settings","Simulator Config",IP_RW,60,IPS_IDLE);

from here: ccd_simulator.cpp

Read More...

erik created a new topic ' OpenCV' in the forum. 9 months ago

Hi,

I'm currently writing a little client in cpp to automated evaluate images and check wethere there are satellites in image. I'm using linux, the cameras are an EOS 6D and an ASI Zwoptical 120 color CMOS.
For image processing I'd like to translate the images coming with the newBlob Function of the baseclient as IBLOB structs to an cv::Mat. What the constructor of the cv::Mat needs is a pointer to the start of the image data, not sure if void* blob does that job (?), and the bytes per pixel. Last is in the CCD_INFO NumberVectorProperty, but I'm still needing the void pointer to the binary data. Can I use the pointer contained in the struct or is there f.eks. any fits header i've to consider as well?

By the way, what exatly is in the format string?

Thanks for any help! :cheer:

typedef struct {			/* one BLOB descriptor */
  /** index name */
  char name[MAXINDINAME];		
  /** this BLOB's label */
  char label[MAXINDILABEL];	
  /** format attr */	
  char format[MAXINDIBLOBFMT];	
  /** malloced binary large object bytes */
  void *blob;			
  /** bytes in blob */	
  int bloblen;			
  /** n uncompressed bytes */
  int size;				
  /** pointer to parent */
  struct _IBLOBVectorProperty *bvp;	
  /** handy place to hang helper info */
  void *aux0, *aux1, *aux2;		
} IBLOB;


Read More...

erik replied to the topic 'Controlling with a gamepad more than my telescope' in the forum. 2 years ago

Update.
So, I got it to work. It's the compiling environment, that made the point.

New Question:
Since i want to 'command' making a picture from my gamepad, whats the best way to program that in the callback function of those gamepad buttons, as it is done in the telescope driver? Or, for example, to turn on the preview or make an image of N seconds shutterspeed from within the driver callback function?

Read More...

erik replied to the topic 'Controlling with a gamepad more than my telescope' in the forum. 2 years ago

I'm pretty much stepping on the same place since last Thursday and can't get what's missing, i transfered anything in LX200generic, which was about the controller, function calls, etc., to the GPhoto driver gphoto_ccd.cpp + .h.
Next step is always to try to compile it like normal, using cmake/make. I always get the above error message.

Any hints would be greatly appreciated! I'm nearly running on my gum. :-D

Read More...

erik replied to the topic 'Controlling with a gamepad more than my telescope' in the forum. 2 years ago

To me it seems like he somehow does not get the definitions of the indicontroller-methods, but I do not know, if I'm supposed to #include the indicontroller.cpp in the Gphoto.cpp or whereever, since I've only got those C++ skills which I learned during my studies. ;-D

_____
INDI Lib Version 1.0.0, compiled from source
Linux tyrion 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02) x86_64 GNU/Linux

Read More...

erik replied to the topic 'Controlling with a gamepad more than my telescope' in the forum. 2 years ago

Having a problem compiling the gphoto code, after putting the function calls from lx200generic into gphoto for joystick usage.

<code>:~/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0$ make
[ 25%] Building CXX object indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/gphoto_ccd.o
In file included from /home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.h:28:0,
from /home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp:40:
/usr/include/libindi/indicontroller.h:76:18: error: ‘function’ in namespace ‘std’ does not name a template type
typedef std::function<void (const char * joystick_n, double mag, double angle, void *context)> joystickFunc;
^
/usr/include/libindi/indicontroller.h:81:18: error: ‘function’ in namespace ‘std’ does not name a template type
typedef std::function<void (const char * axis_n, double value, void *context)> axisFunc;
^
/usr/include/libindi/indicontroller.h:86:18: error: ‘function’ in namespace ‘std’ does not name a template type
typedef std::function<void (const char * button_n, ISState state, void *context)> buttonFunc;
^
/usr/include/libindi/indicontroller.h:121:30: error: ‘joystickFunc’ has not been declared
void setJoystickCallback(joystickFunc joystickCallback);
^
/usr/include/libindi/indicontroller.h:127:26: error: ‘axisFunc’ has not been declared
void setAxisCallback(axisFunc axisCallback);
^
/usr/include/libindi/indicontroller.h:133:28: error: ‘buttonFunc’ has not been declared
void setButtonCallback(buttonFunc buttonCallback);
^
/usr/include/libindi/indicontroller.h:148:5: error: ‘joystickFunc’ does not name a type
joystickFunc joystickCallbackFunc;
^
/usr/include/libindi/indicontroller.h:149:5: error: ‘buttonFunc’ does not name a type
buttonFunc buttonCallbackFunc;
^
/usr/include/libindi/indicontroller.h:150:5: error: ‘axisFunc’ does not name a type
axisFunc axisCallbackFunc;
^
/home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp: In constructor ‘GPhotoCCD::GPhotoCCD()’:
/home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp:167:47: error: invalid conversion from ‘void (*)(const char*, ISState, void*)’ to ‘int’ [-fpermissive]
controller->setButtonCallback(buttonHelper);
^
In file included from /home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.h:28:0,
from /home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp:40:
/usr/include/libindi/indicontroller.h:133:10: note: initializing argument 1 of ‘void INDI::Controller::setButtonCallback(int)’
void setButtonCallback(buttonFunc buttonCallback);
^
/home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp: In member function ‘virtual void GPhotoCCD::processButton(const char*, ISState)’:
/home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp:1335:22: error: return-statement with a value, in function returning 'void' [-fpermissive]
if (rv) {return true;}
^
/home/erik/indilib/libindi_3rdparty-test/libindi_3rdparty-1.0.0/indi-gphoto/gphoto_ccd.cpp:1341:13: error: return-statement with a value, in function returning 'void' [-fpermissive]
return true;
^
indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/build.make:54: recipe for target 'indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/gphoto_ccd.o' failed
make[2]: *** [indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/gphoto_ccd.o] Error 1
CMakeFiles/Makefile2:75: recipe for target 'indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/all' failed
make[1]: *** [indi-gphoto/CMakeFiles/indi_gphoto_ccd.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
</code>

Thanks for any help anyway, although it might be a pretty simple solution, since I'm not a High-End Programmer.
Regards

Read More...

erik replied to the topic 'Controlling with a gamepad more than my telescope' in the forum. 2 years ago

I'll report.

Read More...

erik created a new topic ' Controlling with a gamepad more than my telescope' in the forum. 2 years ago

Hey,
I'm not new to programming, but after all couldn't actually say that I'm pretty experienced.

INDIlib running with my LX200 GPS works pretty good, also with the gamepad. I'm using a Logitech Inc. WingMan Gamepad. Version 131328. Kinda pretty old, I think from 2000. However it works fluently.
The gamepad has 2 axes and 11 buttons. I pretty much enjoy it to use it with the telescope via kstars (or from console) + indilib.
The lx200 driver offers the possibility to use 3 buttons for different slewing speed, 1 for parking, 1 to abort any movement and the 2 axes for slewing.
Leaving me, in this case, 6 unused buttons.

I know this question might be too general, but actually i don't really know how to attack this problem/question, so... I more or less just need a base to work upon, some ideas. :-D
How could I possibly set a buttons function to, for example, make a picture, maybe a fits, using my Canon EOS 6D?

Do i have to write a new driver with the enable joystick option implemented as in lx200generic.cpp or can I somehow implement it in a already existing driver or just writing myself a new client, who is doing this task?
Best solution for me would be, to just have maybe a driver more to start with kstars, enable for both the joystick option and GO (, which would mean to write a new driver). Kinda just like now with the telescope.

Thanks for replying ahead.

Greetings
Erik

Read More...

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!