I have the full set of codes if or when I get the discrete on / off codes I will forward the code set for inclusion in RC database section, power toggle code in pronto hex below.

Power Toggle: 0000 0067 0000 0044 0155 00A9 0016 0040 0016 0040 0016 0040 0016 0015 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0015 0016 0040 0016 0040 0016 0432 0155 00A9 0016 0040 0016 0040 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0040 0016 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0432

if this is any help, thanks adam.

Well.  It probably won't use the same code set as a pioneer receiver, as Pioneer would assume you would have multiple devices by them in your system.

You have the decode, based on your toggle, for the IRP and device number.  With a pronto or other device, you could fire the full code set for p=Pioneer and d=167.

Alternatively, you can hope that Pioneer codes follow some logic, like Sony codes, that the object numbers across device (and subdevice lines) do the same thing (using object 46 for P-On and Object 47 for P-Off).  In which case, I would try objects 26-35 just for safe overlap.  

Thanks for your reply, But it goes completely over my head.

If I was able to generate all the possible codes for this unit would it
not be risky to start firing codes without knowing what they do, could I brick the unit by firing some service codes etc.

I think a long time ago I saw someone post a toggle code, and they got a reply saying try these for discrete on / off and they worked, is this not possible.

excuse my ignorance, but I am lost with your answer.

thanks, adam

Forgive me.  I should have approach my reply differently.  People who access this forum are at all different levels of understanding, and my reply wasn't catered to that.

I will tell you that just under a year ago, I had little understanding of the things I had typed in my reply.  It took a few well placed post by 3FG that really began the foundations that lead to self-exploration and understanding.

Here is my own post that gave a better explanation of what I said previously:

[Link: remotecentral.com]

With regards to your question about danger of firing codes.  Is there a risk?  Of course.  However, the risk is minimal.  There are code sets that have a service mode discrete code.  (Sharp comes to mind).  This code simply allows you to enter service mode.  Most of these service mode menus are not easy to navigate.  It is difficult to accidentally press a button.  (Assuming one isn't just mashing navigation and enter buttons on their remotes).  Other companies like Samsung and Sony require a combination of buttons to be pressed on the remote to enter service mode.

The IR emitter on your device is designed to accept basically all the IR light that comes into it, including codes from other remotes and ambient light.  It is manufactured to only accept a a certain frequency and modulation, so that, for instance, your remote control for your Air Conditioner doesn't turn on your TV.  However, there can be overlaps.  I remember my HDMI switcher remote control would tell my fan to oscillate.  I mention all of this because it is possible, in theory, (and I have seen it in action), for ambient light like sunshine to be within that frequency and modulation and wavelength for your device to respond.  (I had an old LG TV that would turn on when the Sun would shine through a certain window).  It is therefore slightly logical to assume that a manufacturer is not going to create a code that might do random damage to a device, as is is possible for another remote control, ambient light, or ignorant (unknowning) end user to fire that code.  Make sense?