I have this one sequence (attached) that roughly seven seconds in, turns on channels 15 and 16. The only thing that clears the channels is a power cycle.
I have pulled all of the PICs from the Renard64 XC, verified the programming, and re-programmed them. I then installed just two PICs for channels 1-16. When I run other sequences, everything works just fine. When I run this sequence, I get the stuck channels.
I've swapped the order of the of the PICs. I've also opened a new Vixen file, and pasted just channels 1-8 into it. Could someone try the vixen file to see if it locks up your PIC? Any other thoughts as to what it could be?
Here is the programming firmware: 2007-12-29 v 206 with 57600 and PWM. Vixen is 2.0 with the latest version.
[andy@aria Renard64]$ pk2cmd -pPIC16F688 -frenard_20071229_206.hex -y
PICkit 2 Verify Report
12-10-2008, 19:53:58
Device Type: PIC16F688
Verify Succeeded.
Operation Succeeded
[andy@aria Renard64]$ pk2cmd -pPIC16F688 -frenard_20071229_206.hex -m
PICkit 2 Program Report
12-10-2008, 19:54:03
Device Type: PIC16F688
Program Succeeded.
Operation Succeeded
I have also found a dimming sequence that turns off both channels. It is in another Vixen sequence.
It would help if you attached your profile too.
Here is my profile, and here is the sequence that turns off the two channels around 2:15. The channels turn on around 3 seconds with the previous sequence from the first post.
Andy
In your profile, you only have the Renard set for eight channels, but you have 24 channels for your sequence. Change your renard setup in your profile to 24 and it will clear it. It just worked for me.
Worked for me too.
While your at it, also check the box in the plugin setup, to "hold the port open ..."
I'll give it a try.
As for the keep port open, it causes my QEMU-KVM (virtual Windows XP under Linux) to throw an error. With it unchecked, my programs run without giving me a permission denied opening COM1.
Andy
Ok, with the changes to the profile to manage all the channels, channels 15 and 16 still light, but then go out. I am not setting either channel on, so this still looks like some kind of glitch.
