I am working on OpenFlexure Connect and I want to save captured images as TIFF instead of JPEG for my work. I have cloned the openflexure-microscope-server repository to my local Windows computer and have written some code. However, the challenge I am facing is how to sync my code from Windows to the Raspberry Pi. I am looking for a workflow where I can clone the server, make my intended customizations, and still have access to the microscope for testing. Any advice..
There are notes for developer installation workflow somewhere that @bprobert wrote.
I shall have a look. here: Video Walkthroughs for Software Dev and Simulation
The code sits on the SD card and you can just swap the files with SSH, or run git commands. Try var/openflexure? For the experimental versions that I’m working on, I usually install the default raspbian and follow the dev documentation here: OpenFlexure Microscope Server Developer Guidance to setup a server that I start with the venv + open-flexure-server commands. This is to have a full desktop env, rather than the -lite image that is provided for the V3 versions for now.
I recently changed a few files on an HQ version of a microscope that I was sending out to someone on the default -lite image though, so pretty sure that’s the simplest way to do it.
Thank you very much. I will try that and see how it goes.
After cloning the repository following the OpenFlexure Microscope Server Developer Guide on my Windows laptop, I am trying to connect to my Raspberry Pi so that I can run and test the modifications I have made.
Both the Raspberry Pi and my laptop are connected to the same local network. I intended to use SSH to connect to the Pi, but it keeps prompting me for a password. As far as I can remember, I did not set a password when configuring the Raspberry Pi on the SD card.
Is there another way to transfer my code from the laptop to the Raspberry Pi and test it, or is there a way to regain access without knowing the SSH password?
If you’re using a recent (i.e. server version 3) image, if you don’t set a password, the password is locked by default (this is a security measure, introduced upstream by Raspberry Pi). If you visit the forum post announcing the latest alpha release, there are instructions there explaining how to use Raspberry Pi Imager v2 to burn an image, which includes a step that lets you customise the username and password.
Burning a new SD card will erase everything that’s currently saved, so you should back up any images that you would like to keep.
It is worth mentioning that @j.stirling is currently working through a rewrite of the camera API for the next release of the software - and one thing that should do is make it easier to add additional output formats. So, if you have the option to wait a bit, this is a feature that should be easier to add in a couple of months.
1 Like
It should be easiest to add from this branch:
1 Like