Camera Settings Control for K1 Max with new hardware version

[loosegoosage]

Curious if this is something that can be requested or not. I am going to assume it is not a bug, but rather a case of being unsupported, since the script basically states that "You have the new hardware version of the camera and it's not compatible!"

[Hammerfest]

That is correct!

Creality changed the camera module hardware, as such the new hardware does not respond to the commands exposed on the older hardware.

If anyone is a hardware/firmware hacker and can find out what commands it can/does accept or MAKE it accept commands it would be welcomed greatly.

IMHO, the new camera sucks by comparison, if you add extra lighting you cannot make adjustments to compensate :(

[loosegoosage]

Well thats dookie, guess they are trying to cut costs or something. I will have to live without for now unless i can break down its barrier..... :(

[mfraser]

Does lsusb reveal any information on the new camera? The older one is this http://linux-hardware.org/?id=usb:0c45-6366

[loosegoosage]

Does that printers camera work in klipper?

[spitfire]

If I understand it correctly that is the same as the one dedicated for Creality Ender 3 v3 KE, which is based on Klipper, and pretty similar to K1

[loosegoosage]

Ok, i will see what i can figure out maybe somehow its doable.

[loosegoosage]

@mfraser it looks to be the exact same driver, im guessing it has dual support for 720 and 1080 on the old? odd it shows as 2 devices with slightly different specs.

[spitfire]

on Creality Ender 3 v3 KE with the Nebula camera it is showing:

[#] lsusb
Bus 001 Device 006: ID a108:2231  USB2.0 Hub
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and

[#] v4l2-ctl --device=/dev/video4 --all
Driver Info:
	Driver name      : uvcvideo
	Card type        : CCX2F3298
	Bus info         : usb-13500000.otg_new-1.1
	Driver version   : 4.4.94
	Capabilities     : 0x84200001
		Video Capture
		Streaming
		Extended Pix Format
		Device Capabilities
	Device Caps      : 0x04200001
		Video Capture
		Streaming
		Extended Pix Format
Media Driver Info:
	Driver name      : uvcvideo
	Model            : CCX2F3298
	Serial           : 1234567890
	Bus info         : 1.1
	Media version    : 0.1.0
	Hardware revision: 0x00000310 (784)
	Driver version   : 4.4.94
Entity Info:
	ID               : 1
	Name             : CCX2F3298
	Type             : V4L2 I/O
	Flags            : default
	Major            : 81
	Minor            : 4
	Pad              : 0: Sink
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
	Width/Height      : 1920/1080
	Pixel Format      : 'MJPG' (Motion-JPEG)
	Field             : None
	Bytes per Line    : 0
	Size Image        : 1572864
	Colorspace        : Default
	Transfer Function : Default (maps to Rec. 709)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
	Flags             :
Crop Capability Video Capture:
	Bounds      : Left 0, Top 0, Width 1920, Height 1080
	Default     : Left 0, Top 0, Width 1920, Height 1080
	Pixel Aspect: 1/1
Selection Video Capture: crop_default, Left 0, Top 0, Width 1920, Height 1080, Flags:
Selection Video Capture: crop_bounds, Left 0, Top 0, Width 1920, Height 1080, Flags:
Streaming Parameters Video Capture:
	Capabilities     : timeperframe
	Frames per second: 15.000 (15/1)
	Read buffers     : 0
                     brightness 0x00980900 (int)    : min=50 max=160 step=1 default=-8193 value=128
                       contrast 0x00980901 (int)    : min=50 max=160 step=1 default=57343 value=128
                     saturation 0x00980902 (int)    : min=50 max=160 step=1 default=57343 value=128
                            hue 0x00980903 (int)    : min=50 max=160 step=1 default=-8193 value=128
 white_balance_temperature_auto 0x0098090c (bool)   : default=1 value=1

which looks very similar to the first one, no video5 or H.264 anywhere though.

[spitfire]

Is the new revision of camera better in any way?

[loosegoosage]

Tbh, I never seen the old nor did I look up to compare. I would hope so, but then again like I said in an earlier reply I wouldn't doubt them just cutting cost.

[rocklee5]

I have the old Camera and I am facing this error " You have the new hardware version of the camera and it's not compatible!" when trying to install the camera control script.

[MzTechnology97]

I just tried to connect to the camera via serial, I soldered some wires to the PCB on TX, RX and GND and I managed to connect. Unfortunately access is password protected.

Serial init OK!jz_serial_init ok
pll_init:366
pll_cfg.pdiv = 10, pll_cfg.h2div = 5, pll_cfg.h0div = 5, pll_cfg.cdiv = 1, pll_c fg.l2div = 2
nf=84 nr = 1 od0 = 1 od1 = 2
cppcr is 05405100
CPM_CPAPCR 0540510d
nf=84 nr = 1 od0 = 1 od1 = 2
cppcr is 05405100
CPM_CPMPCR 07d0590d
nf=110 nr = 1 od0 = 1 od1 = 2
cppcr is 06e05100
CPM_CPVPCR 06e0510d
cppcr 0x9a773310
apll_freq 1008000000
mpll_freq 1000000000
vpll_freq = 1320000000
ddr sel mpll, cpu sel apll
ddrfreq 500000000
cclk 1008000000
l2clk 504000000
h0clk 200000000
h2clk 200000000
pclk 100000000
sdram init start
REG_DDR_LMR: 00000210
REG_DDR_LMR: 00000310
REG_DDR_LMR: 00000110
REG_DDR_LMR, MR0: 00f73011
T31_0x5: 00000007
T31_0x15: 0000000c
T31_0x4: 00000000
T31_0x14: 00000002
INNO_TRAINING_CTRL 1: 00000000
INNO_TRAINING_CTRL 2: 000000a1
T31_cc: 00000003
INNO_TRAINING_CTRL 3: 000000a0
T31_118: 0000003c
T31_158: 0000003c
T31_190: 00000020
T31_194: 0000001f
DDR PHY init OK
DDR Controller init
SDRAM init ok
#######norflash id 00204017#####
#######norflash model XM25QH64C#####

spl_sfc_nor_load_kernel ...
boot uImage...

uImage size = [3628865]
OK
images->ep = 802699c0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10.14__isvp_swan_1.0__ (root@ubuntu) (gcc version 4.7.2 (Ingenic r2.3.3 2016.12) ) #1 PREEMPT Tue Aug 22 09:55:24 CST 2023
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 RESET ERROR PC:D0004154
[ 0.000000] CPU0 revision is: 00d00100 (Ingenic Xburst)
[ 0.000000] FPU revision is: 00b70000
[ 0.000000] CCLK:1008MHz L2CLK:504Mhz H0CLK:250MHz H2CLK:250Mhz PCLK:125Mhz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 0033b000 @ 00010000 (usable)
[ 0.000000] memory: 00465000 @ 0034b000 (usable after init)
mdev is ok......
ifconfig: socket: Address family not supported by protocol
/system/init/app_init.sh: line 8: anticopy: not found

Ingenic-uc1_1 login: INFO(KIVA): AntiCopy_Verify ...
INFO: anticopy verify OK!
INFO(KIVA): AntiCopy_Verify ...ok
INFO(KIVA): kiva_load_config_init ...
INFO(KIVA): kiva_load_config_init ...ok
INFO(KIVA): kiva version = 2.0.0
INFO(KIVA): ucamera_system_init ...
INFO(KIVA): ucamera_system_init ...ok
INFO(KIVA): module_led_init ...
INFO(KIVA): module_led_init ...ok
open config file/system/config/update.config failed
can't load update.config
INFO(KIVA): module_ucamera_init ...
[Ucamera]: [INFO]: Video Start.

INFO(KIVA): module_ucamera_init ...ok
INFO(KIVA): module_autofocus_init ...
INFO(KIVA): module_autofocus_init ...ok
INFO(KIVA): kiva_process_init ...
INFO(KIVA): kiva_process_init ...ok
---- FPGA board is ready ----
Board UID : 30AB6E51
Board HW ID : 72000460
Board rev. : 5DE5A975
Board date : 20190326

[Ucamera]: UVC: Setting format to: MJPG 1920x1080

[Ucamera]: UVC: uvc event stream on!

ERROR(UVC_CONTROL): imp sys not ready, wait and retry:1
INFO(UVC_CONTROL): set Antiflicker level:1 fps:25
INFO(UVC_CONTROL): set Fixedcontrastattr mode = 0 OK!
[Ucamera]: UVC: Starting video stream.

Ingenic-uc1_1 login: root
Password:
Login incorrect

[Hammerfest]

A quick search shows at least 3 instances where there is a hardcoded password, maybe creality or ingenic didnt change it?

"ismart12"

[MzTechnology97]

I have already tried several generic passwords including this one, but unfortunately it is incorrect. You should do a dump of the chip and try to find out the password or change it.
If I can, I can try to make a dump and share it. Maybe someone can find it.

[Hammerfest]

would the firmware be on that XMC(?) chip next to the T31 or would it be on the T31 itself?

[MzTechnology97]

on the chip next to the t31. XM25QH64C chip flash 8 MB

[spitfire]

Is this new or old? I guess it’s new some it says it’s unsupported

[MzTechnology97]

it looks the same as mine. So it should be the new version.

[MzTechnology97]

I just did a rom dump.
I share it, maybe someone can do something.
https://drive.google.com/file/d/1BTP2MI3MZi9E_O_2lNqhfJjOpJXjcjWm/view?usp=sharing

[MzTechnology97]

In the end I decided to completely remove the creality camera and replaced it with a good webcam of much better quality and I can easily set the image parameters.

[spitfire]

I have no intention of doing that, and I hoped it could work with Creality's camera. I think I'd rather have what I do now, rather than buying another one and trying to safely mount it inside.

[Hammerfest]

totally understand not wanting to futz with it MzT, your route is the best route if ya can afford it

thank you for at least opening the door, hopefully someone more knowledgeable then I takes interest!
VERY MUCH APPRECIATED <3

[spitfire]

So what did you get/how did you mount it?

[MzTechnology97]

I used a webcam that I used with my old printer. I simply disassembled it and adapted it to be placed in almost the same position as the original and changed the lens to a 140 degree one.
https://a.co/d/0IyVSUK