KuroControl program for Pioneer KRP500m/600m and Elites - Page 2

If you're just calibrating you should be fine with lan in vmware or parallels. If you're actually flashing the FW I wouldn't necessarily do it virtualized.

If I read this thread correctly, this will allow you to unlock the ISF modes without the need of the ISF patch from turbe on a 500m?

I don't believe the transient counters mean anything, that's why they start at zero even though the panel has aging hours on it. I'd imagine the the sustain pulse counter is used to adjust dynamic parameters. There are lots of counters.

He he. Im actually very thin(about 60 kilogram)

That was the point made in the KRP thread.

Has anyone confirmed this?

"Flashing the firmware"...?

Ok..how much room on the hard disc is necessary for "wmvare"? There isnt much space left..

(I hope someone will do a simple program for mac in the future..)

I did the same thing but based on the "INPS01" and then "INP" I assume the first FST is a query. Hence the unknown in the model field.

Space isn't so much the issue as processing power and system overhead. Running parallels or vmware fusion means you are running one operating system on top of another one. My recollection from when I used virtualization in the past was that networking was slightly buggy and had some sort of issues unless it was sharing the host (osx) internet connection instead of a straight bypass. It's possible newer versions are better. If you're going to flash, just make sure it hooks up properly with kuroreader which is a passive program (in the sense that it just reads settings basically) first to make sure the connection between the kuro and the mac is good.


Is there any practical difference doing one or the other?

Could be (makes sense). I don't have my SM handy (at work).

Does it strike you as odd that for some settings he has the raw value of 128 as zero (rather than 60)? I didn't think we had that many bits (FF) to play with, but I will have to look when I get home.

Ah, sorry -- yes, a bare FST is a query.

Okay, thanks. So we just need to avoid pressing the Change button for fun to avoid resetting the hours.

So I need Kuroreader and vmware to use this program? And what does it mean when I have to "flash" with Kuroreader?

He is referring to validating IP Control connectivity with KuroReader. No flashing is being done here - it's a configuration change.

Great job on the program xsiv4ce. I highly doubt the hours counter has anything to do with the phosphor wear, but then again I am not sure I want to risk it without confirmation. Wonder if d-nice has any say on this? I emailed pioneer about the hours counter, however I am not sure I am going to get a straight forward answer.

I checked this and the Kurocontrol app is correct, 128 is zero in ISF mode (with a range of 68-188).

I ran the app on my patched KRP. I did not use the Change button since I already have ISF enabled. The software works very well. However, I did find a few bugs:

1. The Gamma selection (for non-ISF modes) has Off, Low, Mid, High. "Off" returns an error, and low, mid, high are Gamma 1,2, and 3 respectively. Gamma 4 and 5 are not selectable. Also, the control is not updated correctly when Refreshed - note that the returned gamma value has 2 additional digits appended to it, which is probably the problem.
2. The Film Mode (Pure Cinema) is missing the Smooth mode selection.
3. The Intelligent Mode setting is not available.

The good news is all of these can be entered manually as a workaround in the Command box. For example, sending GMMS04 or S05 for gamma 4 and 5, PUCS03 for Smooth Pure Cinema, and ITMS00, S01, S02 for Intel mode Off, 1, and 2 respectively.

My mapping notes say:
BRT 068 - 188 (0-120)
CNT 000 - 060 (0-60)
COL 068 - 188 (0-120)
TNT 098 - 158 (0-60)
RHI 068 - 188 (0-120)
CGR 098 - 158 (0-60)
SHP 113 - 143 (0-30)

Which I find quite annoying (rhi/cgr stand for any of those) but it's probably an artifact.

The program wouldn't run in my XP VM (prolly a .net problem) so I used my W7 VM which worked but the gamma box text is clipped and there are various other minor visual glitches.

Inconsistent checksums are another peeve of mine. I ignore them and truncate most return values to six characters. Query commands are the notable exception.

Yeah, Pioneer seems to like confusing us with things, e.g.: [Menu displayed value 0] = [ISF Open Query 128] = [ISF Closed Query 60] = [OSD ISF/Non-ISF 60] = [ISF set value 128] = [non-ISF set value = 60].


It looks like that in native XP SP3, too. And some of the labels intrude on the dropdown list, but insignificantly. Overall, it's a very nice app.

Thanks for the effort, it's a very nice program.

If you're taking suggestions for rev 2 I have only one, add two gang (luma) controls to the gamma box. Most of the time you want all of them to be the same and 99% of the time you want all the adjustments at a given point to be the same.

No offense, but can we keep this thread KuroControl/KRP related. Any VMware or virtualization questions you should really go to a Apple forum. Or visit the manufacturer website for program specs. On a side note I would NEVER flash firmware in a virtualized environment. Esp. a $3500 TV...

I am sure we will all have suggestions for a Rev.2

xsiv4ce, thank you for the program. Are you taking donations for your time and possible future rev.? I have some paypal money to donate for your efforts thus far...

Please pm or post your paypal address.

Thanks

--Robert

Not a bug, but..The OSD (on-screen display) is turned off after connecting. If you don't press the OSD button before exiting to toggle it back on, the level bar will not appear on-screen when adjusting the volume. You can of course restart the app, connect, and then press OSD to get it back.

How do the 9-point gamma numbers translate to something like "50%B -2"? Does "5" mean "50%B 0"?

Also, when changing models, do you manually input a model or is there a list? After changing the model, do you press Power on the remote to turn off the TV when prompted? Or do you press Power on the KuroControl program?

Thanks,

The 1-9 settings are nominally applied to the corresponding 10-90% stimulus values. I'm not quite sure about the first part of your question but on my 500M the values for the mid-range are roughly (not all values measured, useful range is quite limited):

1 | 2.4
2 | 2.3
3 | 2.25
4 | 2.2
5 | 2.1
6 | 2.0
7 | 1.95
8 | 1.9
9 | 1.85

Given the above values setting B6 to 3 would yield a gamma of 2.25 on the blue channel at 60%.

Sorry I wasn't clear! I'm looking at the 500m D-Nice settings, and they look like:

Gamma
10%R -1
10%G -1
10%B -1
20%R -2
20%G -2
...

How do those numbers translate into the numbers in KuroControl? From the screenshots, it doesn't seem to match up.