Skip to content

Conversation

@3DPrintingGeek
Copy link
Contributor

No description provided.

root and others added 10 commits April 21, 2024 09:38
When the new revision of the AI cam is detected, the script shows an error,
and prevents installing the macros.
This makes sense if the AI cam is the only installed cam, but not if one has
installed an additional USB cam, connected to the front USB port.

The change gives an option, too continue the installation in that case,
by asking if the user wants to continue.
The old script didn't allow to install the camera settings macros, when the new HW revision of the AI cam has been detected,
even when the additional USB cam could benefit from being controlled by the macros.

The changes made in this commit give a warning about the new HW revision not bein compatible but allow the user to acknowledge
that he wants the camera settings macros installed nevertheless.
When using additional cameras there must be a way to select for which camera the subsequent macro calls
of the camera settings macros should be executed.
The default camera is the Creality AI camera.

Usage:
Before calling one of the other macros, make a call to CAM_SELECT cam_device=n
with n being the number of the cameras video device.
E.g.:
If your second USB cam is /dev/video5 then call "CAM_SELECT cam_device=5".
Every other camera macro call will now be for this camera until changed by another CAM_SELECT-call.

Note:
Not all camera macros will work with every camera, and some only if the camera is in a specific mode.
It depends mostly on the cams hardware capabilities.
Calling the CAM_SETTINGS macro will show the available settings and their current values.
USB camera support is installed into $INITD/S50_usb_camera
This change changes the wrong directory S99_usb_camera to S50_usb_camera
@some-du6e
Copy link

im going to try this with my stock nebula pad cam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants