Can pin select be changed during operation?

[RoGuE_StreaK]

Not sure of the correct terminology here, so forgive me if it's been answered before, my searches didn't find a relevant result.

I have a PIC24FJ64GA004, which has lots of remappable peripheral pins. I believe you use #pin_select in the defines to set these, before the main begins operation?
But let's say I have two RGB LEDs, only three PWM channels available, and six RPn pins available; is there a way to re-define the PWM pins during operation, so I can use one RGB LED and then remap to use the other RGB LED? This wouldn't be a "mid flight" requirement, I could stop everything before changing from one to the other if required/possible.

It's just a passing thought that popped into my head when I realised that my changing another part of the project had freed up a few more remappable pins.

[PCM programmer]

Previous thread on dynamic PPS for the PIC24:
http://www.ccsinfo.com/forum/viewtopic.php?t=44325

[FvM]

Changing peripheral pin select at run time requires direct writes to special function registers, because #pin_select only works for the initial setting. You have to figure out the right PPS registers and codes from the datasheet. As mentioned in the linked thread, the compiler startup code fails to lock PPS registers (up to recent versions), so you can simply write it without previous unlock.

[RoGuE_StreaK]

Thanks guys, will see if I can re-wire my PDB design and see how it goes. No big deal if the second LED doesn't work out, I'll just dump it.

Is it OK to leave the PPS registers unlocked (as they are now anyway), or are there reasons why I should lock them again after the change?

[FvM]

The locking feature is intended to prevent from unintentional configuration changes, which can be a safety requirement. There's even an IOL1WAY fuse to block further unlock operations. But I don't think either of these options will be necessary in normal applications.