Add docs for how to build a new image

[decentral1se]

Seen from https://github.com/Tenrec-Builders/pi-scan/blob/master/make/README.md, we know that there is a build process to produce a new image but it is not clear how to do that process immediately. I remember messing with debian packaging and chroots before and ending up with getting into difficulty for some $reason on my host computer with mounts. I'd really appreciate some instructions for producing a new pi-scan image.

[duerig]

The build process is just a variant of the pi-gen system for making normal Raspberry Pi images. This has been mostly a one-person project and so there was little need to urgently publish the build process. But if there is interest , I can create a resository for the build scripts that is publicly available. In addition to these issues, you have also emailed me personally. So ping me when you are comfortable with the vanilla pi-gen process and I'll link you the repo for building these variant images.

…

On Sun, Jan 19, 2020, at 4:59 AM, decentral1se wrote: Seen from https://github.com/Tenrec-Builders/pi-scan/blob/master/make/README.md, we know that there is a build process to produce a new image but it is not clear how to do that process immediately. I remember messing with debian packaging and chroots before and ending up with getting into difficulty for some $reason on my host computer with mounts. I'd really appreciate some instructions for producing a new pi-scan image. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#17?email_source=notifications&email_token=AAGWYTBN3HRE2SJIKQOWO7LQ6Q6BLA5CNFSM4KIY2MY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHFQLHA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWYTH74MWS6E5JD5NVWI3Q6Q6BLANCNFSM4KIY2MYQ>.

[abevoelker]

I started working on this here: https://github.com/abevoelker/pi-gen

I got pretty far, however currently Pi Scan is failing to start due to this error:

lupa._lupa.LuaError: [string "<python>"]:2: module 'chdkptp' not found:

It seems to be an issue reported with chdkptp.py:

• Python3.6 compatibility  jbaiter/chdkptp.py#6 (comment)
• I found that the encode=None at the lua runtime was the cause of the issue, but now I can't install the package. jbaiter/chdkptp.py#12

However I'm not sure how to resolve it at the moment. python --version is 2.7.18 so it shouldn't be a Python 3 issue (I think).

[abevoelker]

Okay I got past that error. Very weird but apparently pip install wasn't running chdkptp.py's setup.py instructions to build chdkptp.so, so it couldn't be found. I switched to python setup.py install and it works and Pi Scan is booting up now. Haven't tested actually scanning anything yet though

[geneb]

On Tue, 13 Sep 2022, Abe Voelker wrote: Okay I got past that error. Very weird but apparently `pip install` wasn't running chdkptp.py's `setup.py` instructions to build `chdkptp.so`, so it couldn't be found. I switched to `python setup.py install` and it works and Pi Scan is booting up now. Haven't tested actually scanning anything yet though

Thanks for your work on this! It's hugely appreciated. g.

…

-- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://scarlet.deltasoft.com - Get it _today_!

[gnl42]

So I wanted better support for Canon R100, and I now have a build that mostly works based on https://github.com/abevoelker/pi-gen

There are a couple of issues I haven't been able to solve:

• gpio is missing
• USB (stick.py) isn't working. To get around it I added a option to start ssh and using file system for the images and I can use sftp to transfer the images for post-processing
• I can't get the build to use touch.ini. It works when I manually change the config.ini file (both mouse and touch works)
• config.txt should go into /boot/firmware/config.txt
• I can't figure out what the default PW is? the documented PW doesn't work

pi-scan now captures the cr3 file from the cameras but can't preview it, needs jpg versions as well

My work is in:

• https://github.com/gnl42/pi-scan
• https://github.com/gnl42/pi-scan-tenrec

George

[gnl42]

I should add that I'm not a Python programmer so my approach was very much with a sledge hammer, and there is code that can be refactored better for P3

[duerig]

Great work on this! This is pretty old code at this point and is no longer maintained. But it looks like you have most of it worked out. The mouse/touch thing is just a script that replaces config. See 'mouse.sh' and 'touch.sh'. So you should just change config in the most convenient way for you. You should run passwd yourself and change the password to something unique before connecting it to any network. Maybe just comment out the gpio stuff? This only matters if you want to use a pedal attached to the GPIO pins to trigger a capture. My understanding is that the maintainer of the gpio python library eventually abandoned it and so it may be that you want to look into how modern Pi distributions interact with the pins and just adapt the code to use that instead. If you are using gphoto to interact with the cameras, take a look at the documentation there. It may be that you just need to tweak an option to get jpg instead of the raw files. Or to get both.

…

On Mon, Dec 9, 2024, at 11:15 AM, George Lindholm wrote: I should add that I'm not a Python programmer so my approach was very much with a sledge hammer, and there is code that can be refactored better for P3 — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWYTET4SL2UJ4ASVC54SL2EXM5XAVCNFSM6AAAAABTIMZLJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRYHE4DMNRQGU>. You are receiving this because you commented.Message ID: ***@***.***>

[gnl42]

config.ini is weird. I install the touch.ini it works if I restart main.py. But if reboot, kivy doesn't start up and I have to revert to the default version.

The PW was mostly an annoyance while I was testing out the changes and I had to reset after every build.

The code is actually calling the 'gpio' command, no python used. So there is just a complaint on the console.

Yeah, I had to configure the camera to create both raw and jpg. The problem is that so much of the code assumes jpg file extension/file type so just raw files don't work too well