FRAME Application Tests

[Mikrodoktor]

History see
https://github.com/openUC2/TechnicalDocs-openUC2-FRAME/issues/157

Issue documents application tests on FRAME Proto 2 by Armin & Florian.
Purpose: Armin=costumer & uses Comprehensive Operational Manual available on Git Hub to get FRAME installed and operating, Florian=expert :-) understands hardware & software on the level necessary to understand why the applications tests run the way they run, what needs to be changed to solve issues and changes them

IP Address Proto Frame 2 in UC2 Office https://192.168.178.80:8001/ Port In
Moziall Port out https://192.168.178.80:8002/ (not needed for Chrome and others

Starting point and The 2 next goals for Florian and Armin:

• Armin can now access ImSwitch on FRAME Proto 2 RASPI in OpenUC2 lab and load json configuration files, which tell the RASPI about the actual hardware environment. According to Bene when the FRAME is delivered to the customer on default a virtual environment is loaded using <example_virtual_microscope.json>. And the configuration with the matching the hardware of FRAME Proto 2 is FRAME.json
• Load <example_virtual_microscope.json> configuration and understand how the GUI Bene created works. Learn, document and solve issue.
• Load and understand <FRAME.json>. See whether it matches hardware of Proto FRAME 2 and whether everything works the way it is supposed to work. Learn, document and solve issue.

Links for FRAME How to install and operate

Draw IO Flowchart "FRAME How to install and operate" =>saved on google drive (I failed to save and reopen it from GitHub)
https://app.diagrams.net/#G1nzPs6fx7VWnN2OvMbb5j7Q6nAWxIR4Sv#%7B%22pageId%22%3A%22lFMvBwg32kQ6ZB3yEF8b%22%7D
Google Drive Folder
https://drive.google.com/drive/folders/14Y-ICqZvaVVyMTmQIYGfJ2-GPt9eAMlL

FRAME Frontend und Backend
Draw IO Flowchart
https://app.diagrams.net/#G1IjwzSdKkzMOwnRaSOkEcBmKv4_mO5wah#%7B%22pageId%22%3A%22lFMvBwg32kQ6ZB3yEF8b%22%7D
Google Drive Folder
https://drive.google.com/drive/folders/14Y-ICqZvaVVyMTmQIYGfJ2-GPt9eAMlL

Comprehensive Operation Manual
Current released version on GitHub
https://openuc2.github.io/docs/Investigator/FRAME/
Current internal (not-released) GitHub Branch, where Armin documents his testing results.
https://github.com/openUC2/openUC2.github.io/tree/devArmin/docs/03_Investigator/02_FRAME

For Reference only: Miro Board Link updated last on 18th Aug 2025. Not updated anymore
https://miro.com/app/board/uXjVLR91oLU=/

[Mikrodoktor]

Armin=user
test: loading <example_virtual_microscope.json> configuration

GUI does not show, which configuration is loaded and if uploading was succesful.
I do not see a virtual microscope image although I turned the LED on and set it to 1023.

@gokugiant Can you try this and see whether the simulation works for you?

[Mikrodoktor]

The Stage contol does not show which Axes is which. needs to be added.
@gokugiant Can we figure out which is which and add it?
And do you have the FRAME,json configuration?
If so, Please make a proposal on how to proceed to figure out if the hardware of FRAME Proto 2 matches the Config file.

[Mikrodoktor]

@beniroquai @gokugiant
Bitte Flowchart "FRAME Backend und Frontend" prüfen.
https://app.diagrams.net/#G1IjwzSdKkzMOwnRaSOkEcBmKv4_mO5wah#%7B%22pageId%22%3A%22lFMvBwg32kQ6ZB3yEF8b%22%7D

Bene, korrekt so? Bitte Änderungen und Ergänzungen direkt im Dokument.
Florian, macht das für dich Sinn?

Auf Google Drive gesaved => siehe oben
#151 (comment)

[beniroquai]

CC'ing Ethan (in case this becomes relevant at one point).

Also, for brevity, here comes the video that kinda explains the flow of code alongside this page.
https://photos.app.goo.gl/rns94M7ZHPTPT1tD9

[Mikrodoktor]

testing Frontend on https://youseetoo.github.io/imswitch/index.html

• Connect to FRAME 2 Proto => Go to system/connection settings and add IP Address
  
• load example_virtual_microscope.json file
  Virtual microscope simulation for testing purposes.

[beniroquai]

@Mikrodoktor should this go to the docs or what was your plan? :)