BUG IN PBP 2.50 & 2.50A pic16F688 ??

[Acetronics2]

Rhhaaaaa !!!

Bruce beats everybody ... but how did he know ??? MPsim ???

I just tested an old DS 1820 4 Mhz program ... that still goes pretty well ...



Ho... by the way ...

Bruce, congratulations for your commercial service .... works pretty fine to Europe.

Alain

[Bruce]

Hi Alain,

... but how did he know ??? MPsim ???

I just got lucky and looked at the OWOUT library first. MPSIM would for sure have been my
next choice however.

congratulations for your commercial service .... works pretty fine to Europe.

Thank you. I wish it worked that well to everywhere outside the U.S....;o}

[FRANCISCOGIM]

Hello everybody, thanks for your good Bruce aportacion, I was crazy with this problem. And tell the technicians of Mlasb: A little more care!

Thanks and greetings.

[Bruce]

Hi Francisco,

And tell the technicians of Mlasb

I have already informed MeLabs of the error in the OWOUT routine. I'm sure they will release
a patch shortly to fix the minor error.

This is one major reason it's so nice to have an open library. You're not dead in the water
until a re-compiled patch comes out. Just fix it, and move on. Really a nice feature with PBP.

[FRANCISCOGIM]

I have a question also affects serout/2 because also the same case.

Greetings

[Bruce]

What problem are you having with SEROUT2?

[FRANCISCOGIM]

With this microprocessor the same problem with owinout was detained when the process is executed the command serout2.

[bcd]

Did this ever get fixed ? I can see 2.50a on the Melabs site, but nothing newer. I assume this bug is still valid.

bill

Hi Francisco,


I have already informed MeLabs of the error in the OWOUT routine. I'm sure they will release
a patch shortly to fix the minor error.

This is one major reason it's so nice to have an open library. You're not dead in the water
until a re-compiled patch comes out. Just fix it, and move on. Really a nice feature with PBP.

[skimask]

Did this ever get fixed ? I can see 2.50a on the Melabs site, but nothing newer. I assume this bug is still valid.

bill

I'm not going to mess with my installation...it works too smoothly.
I guess the only way to figure out if 'A' fixed the problem is to install 2.50, check the macro, install the patch, and check the macro again.