[Class A]

We completely forget about Cam-Control_V2.dll

This post about the software using Cam-Control_V2.dll for the K10D mentions makc (penta-club.ru forum) as the author. Have you tried contacting makc? Might be worth it to obtain some knowledge about Cam-Control_V2.dll.

[tr13]

No, I have not tried and you must remember that program is quite old.
He also managed to use three or four functions only (incuding connecting and disconnecting from camera).
If we'll ask even for such simple things how we could use other, more complicated and hard to understand ones :-) ?

[Zebooka]

About makc program.

It could not switch debug off on K100D Super. Also it turned first four options in debug menu as I remember (DEBUG MODE, CARDDOOR OPEN, WRITE CF VNDR, SCRIPT EN MODE). We tested different parameters for debug-on in DLL's function, but none worked for K100D SUper to switch it off. Don't know why.

Also, if one do not know - you can press [MENU] button in debug menu, to see second screen with other menu items.
There are EEPROM, CPU ROM, DSP ROM, AF PINT DISP functions there.

[Zebooka]

According to Wikipedia:

$ - is string variable
% - int variable

[darky_mtp]

You can use one letter variable :

%C=5
COLOR %C

No need to use ; to end lines

[simico]

No matter how I try (press menu, open card door, closed card door, etc), this doesn't work at all on K-m with 1.10 fw. Nothing happens (except it shows the fw version), no debug menu entries at all.
Are you sure 464 is for K-m and not K2000? They have different fw.

Code:

Km v1.10	MODSET.464
[DEBUG_MODE EN]
[SCRIPT_EN_MODE EN]
[OPEN_DEBUG_MENU]
[SW_DEBUG_MENU EN]

[tr13]

No matter how I try (press menu, open card door, closed card door, etc), this doesn't work at all on K-m with 1.10 fw. Nothing happens (except it shows the fw version), no debug menu entries at all.
Are you sure 464 is for K-m and not K2000? They have different fw.

Code:

Km v1.10	MODSET.464
[DEBUG_MODE EN]
[SCRIPT_EN_MODE EN]
[OPEN_DEBUG_MENU]
[SW_DEBUG_MENU EN]

Use empty formatted flash card, with only one file on it.
Leave one string only - like [OPEN_DEBUG_MENU].
Try turning on with Menu button pressed. Try open CF door.

---

Last edited by tr13; 08-08-2009 at 02:47 AM.

[tr13]

About makc program.
It could not switch debug off on K100D Super. Also it turned first four options in debug menu as I remember (DEBUG MODE, CARDDOOR OPEN, WRITE CF VNDR, SCRIPT EN MODE). We tested different parameters for debug-on in DLL's function, but none worked for K100D SUper to switch it off. Don't know why.

Also, if one do not know - you can press [MENU] button in debug menu, to see second screen with other menu items.
There are EEPROM, CPU ROM, DSP ROM, AF PINT DISP functions there.

Are you related to makc developments?
[MENU] in debug menu on GX20 is not necessary, as you could use cursor to move between screens.

I am interested in lens eeproms.

Another info - I don't see any changes upon AF adjustments in camera EEPROM dumps (see manu item in debug menu).

[Zebooka]

Are you related to makc developments?
[MENU] in debug menu on GX20 is not necessary, as you could use cursor to move between screens.

I am interested in lens eeproms.

Another info - I don't see any changes upon AF adjustments in camera EEPROM dumps (see manu item in debug menu).

I was the one, who tested his program on K100D Super and found solution how to exit debug mode


I have *ist Ds, and two K10D. No GX20/K20D. So my notes about [MENU] button in debug menu apply to yearlier cameras.

And yes, you are right - LENSEEP.ROM doesn't change when AF is adjusted. I've tested this allready with *istDS (few month ago). But it changes when different lens are attached. So I thing this are some values from LENS micro chip. Like aperture values range, focal length, lens id etc.
This could be very usefull. To change lens ID for thrid party lenses, to fool K20D, K-7 and allow lens correction for such lenses.

__________________________

PS:
I could not print integer values (see example below - with %C). I could not summ %C with 1 and setup it into new value (old value is assigned).
IF-ELSE works. I've tested == for comparision.

[tr13]

No I mean xxx.eep file. It is dump of camera eeprom (and you mention dump of lens rom file).
I don't see any changes in it after AF adjusting.

[Zebooka]

SO!

This works:
%A = 1
%B = %A
%B += 1

But this doesn't:
%B = %A + 1

Round brackets ( and ) cause syntax error.

Also I'm unable to print %A or %B value.

In IF i could compare %B with ==, >, < operators

UPDATE:
+=, -=, *= and /= work as expected
Negative values are also allowed.

Boolean operators: ==, !=, >, <, <=, >=

; - comment line

UPDATE 2:

%A = 1
WHILE %A < 3
{
PRINT "Step"
%A += 1
}

[tr13]

Try use C style as I see %x %o %d in file :-)
Also #DEFINE could be used

[Zebooka]

%x, %o and %d could be just for printf function
I also see #DEFINE

[Class A]

I could not print integer values (see example below - with %C).

Have you tried variables without "%", i.e., "A" (floating point) instead of "A%" (integer only)? Might make a difference, but I doubt it. I also doubt that

Code:

PRINT "";A% 
PRINT ""A%

will make a difference.

If the function "STR$" were available you could convert a numeric variable into a string before printing.

BTW, could it be that the "WAIT" command works like the C64 BASIC command "WAIT"?

[tr13]

Use
PRINT "A=%d" %A

works perfectly!!!


As for WAIT command, it is possible, but
WAIT 10 also works, for example.

We need to understand how GOTO and GOSUB work, as they are necessary for complicated scripts.