I'd like to see other users camera settings and XML setups too, as well as any tips you might find working with this. I had a hard time getting this going so I'm hoping to do some sort of writeup we can put in documents for using Pentax with indi.
One tip I saw recently involved using the camera in mirrorlockup mode with multishot. I read that as long as your exposures are longer than storage time it will hold it up and keep shooting with an intervalometer, but I haven't tested it, and I'm not sure the driver will handle it correctly as is. Sounds like a neat trick that we might make use of somehow, MLU button perhaps?
Woot! (brandishes bug net)
I agree about the library. Since we're usually tied to planetarium software(kstars, ccdiel) it does seem unneeded.
It will be a while before I can test outside again. I have a long list of chores delayed by all the rain and snow we've had. Also waiting for parts as usual. I'll certainly put it on my schedule though. I may try to have it running as a secondary project in time for the lunar eclipse in a few weeks, which will be sure to uncover any bugs ten minutes before the good bit.
"When I connect to KStars, Indi automatically updates location, date and time"
There is a setting in Kstars/indi preferences that lets you choose which way updates go and we usually set it to update the mount time and position stored in the pc. You might check that setting if it's not updating the mount time.
Park position is stored in the xml file at ~/.indi/indi_OnStep_config.xml when you save the form and loaded at connect when the system is set to update the mount. Saving with park at the default (north) home position should fix that to a reasonable figure and is recommended for most portable mount users.
Hope this helps.
- Solved the I/o error. It was related to firmware. We'll need to note that in the tutorial. I had 1.11 and updated to 1.16 which solved the i/o error. Folks can find it at RICOH Japan
- A udev rule to properly assign the port when "pentax" is found might be nice too and might stop the port creep I found after I figured out that first error.
Could I get a copy of a working XML from ~/.indi?
Continuing to have difficulty getting the k5 connected to either Gphoto2 or indi drivers. I now have the latest Gphoto2 and LibGphoto compiled. When I try to connect I get no camera found, unless I set the camera to PTP mode, which won't do any controls or capture. I feel like I'm missing something. It shows up on lsusb as "pentax" and is not mounted as a drive. I've got clear sky for the first time this year. HALP!
@pentaxian23: Thanks. That's a good start and pretty much what I had. looks like I'm still struggling with out of date libgphoto stuff on this new notebook.
Some thoughts on that timing issue you're having: In the gphoto driver, "force bulb mode drops back to regular exposure for <1sec. That may be a clue. I'll know more once I get things working.
I won a k5 at auction the other day and started wrangling it...I remember now what a pita all this was when I was testing for it. I'm thinking about starting a new thread in hopes of getting a tutorial on getting an up to date libgphoto, gphoto2 and camera setup etc. Any help here would also be appreciated and well..helpful.
I can build libgphoto but it doesn't appear to build latest gphoto2. Seems like I recall something weird I had to do but its fuzzy. I'll reread issue 31 and see what I did when I had a few more brain cells connecting. Why do ubuntu based repos all have to have 5 year old junk?
questions for the k5:
what mode ptp or msc?
which bulb mode?
what version of gphoto2 works and what command got results?
Are we using indi_gphoto_ccd or indi_pentax_ccd in indiserver?
Is there already a tutorial I'm not finding?
Will it ever stop raining in Virginia?
Cheers! Happy new Year everybody
Minus 1 for the K3 then.
Thanks @Pentaxian23, thats's good to know. I've been watching Ebay for a k5 but stopped, unsure of driver status. Gphoto dev @msmeissn is a busy guy(so many cameras!), but if you offer to run testing for him and do the logs he may work on it a bit to see if it's got that firmware problem nobody has gotten around yet. He may also already know it does and so hasn't spent time on it for that reason, though he's usually pretty quick to respond in either case. Life may have indeed slowed work as it does to all of us. You might try poking him with a sharp stick(bump the post) to get an answer, though he's probably on holiday right now on way up on some alp safely away from emails.
@phattire72 You might also try testing the camera operation using gphoto bash commands as the indlib library is based on that. I think bulb mode has to be set to a particular type in menus but I can't remember which one works...since mine still does not.
Pentax has not released an SDK/API/protocol list for k series cameras. LibGphoto got some of them working in INDI by making a wrapper for PKtriggercord which in turn utilized some earlier firmware and wire snooping. The later model "consumer" level k-30 k-50 k-70 ones have some firmware issue we've not resolved and so bulb mode has been hit or miss for those models. I had reports that K5 and k3 as well as older models k10d etc. were bulbing correctly.
@KNRO: PKtriggercord made a workaround for the k-70 recently. You might be able to adjust the indidriver to make use of that. ..or Marcus might need to address issues with the new technique on that model at the gphoto end...not sure. I wasn't able to test for it because my k50 didn't like the new procedure.(brrrr shutter of death).
I'm thinking about getting a "flagship" k5 or k3 but it's expensive if it doesn't work out. I'm hoping to hear from users that have been successful using the pentax to bulb.
meanwhile drooling over full frame sony a7's ---you hear that RICOH?
Despite helping get Pentax working in gphoto a while back I still have no joy on bulb mode for my k-50. I'm considering getting a different model to use. Can I get a head count of any Pentax users making use of the Gphoto library in bulb mode on their remote systems - and which camera they have?
Help much appreciated. I don't want to keep buying these things and cant really afford a "new" one after the big mount purchase.
WiFi, bof , I just did the setup to try to help Chris!
I am not convinced WiFi is the right thing to drive a scope.
I also agree it's not a great way to go. I've used wifi to the mount side server before and it's terribly slow and unreliable. At one point I had a long range dongle up on a stick to reach into the house! I use a 1gig cat5e line to the mount computer and usb for everything from there. I use two runs of the stuff to reach north and south facing brick pads in both yards.
I had to rob parts from my OnStep rig to get the new mount going but I have all intentions of setting it back up using older parts(rpi3/canont1i etc.) for general wide field use and testing sometime soon.