Pic Microcontrollers Forum - Recent Threads

Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

Mila_G — Tue, 28 Nov 2023 23:41:38 GMT

Hello,

please can you help me with the wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877?

I would like to use ADC with references 0.416 V and Vdd (5 V).
It works perfectly when I connect 0.416 V to the Vref- pin (RA2) from an external source.

Then I generate 0.416 V on RA2 from FVR and D/A converter as follows:
FVRCON = 0x84;
DAC1CON0 = 0xA8;
DAC1CON1 = 0x0D;
The DAC also works perfectly and there is about 0.416 V on the Vref- pin (RA2).

But now ADC works only if the negative reference is Gnd. If I switch this from Gnd to Vref- (just by changing ADREF from 0 to 0x10), a failure occurs. The voltage on the RA2 pin changes to 2.1 V (and of course the A/D gives bad results).

Workaround attempts:
- 0.416 V output from DAC to RB7, directly conneted to RA2 via a wire, works just as badly as above.
- After interconnecting via an op amp voltage follower instead of the wire, the A/D starts to work properly.

I assumed the PIC analog circuits were designed for internal connections from the VRef- pin, without any external workaround. Please, advise.

Many thanks.

Mila.

RE: Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

James123 — Thu, 07 Nov 2024 06:39:53 GMT

ADC input signals are really sensitive to source impedance, and it's generally recommended to keep the maximum impedance of your analog signal source around 10 kΩ. If the source impedance is too high, it can lead to longer sampling times, which may mess up your conversion results. This could be one of the issues you're facing when using an internally generated negative voltage reference.
To avoid problems, make sure your circuit design doesn't introduce extra impedance that could affect the ADC's performance. For more detailed information, check out the PIC16F18877 datasheet, especially the sections on ADC configuration and operation.

MAX96717F is not recognized by the GMSL SerDes Gui

bugtech — Wed, 18 Sep 2024 09:23:25 GMT

Hi.

I am using MAX96717F for a task. It worked fine for a week but now suddenly the device is not getting identified by the GMSL SerDes Gui. Although when i configure the CFG Pin, it shows that Serializer Detected.

1: Tried with different firmware (4.55, 4.56, 4.59)

2: Tried with connections (Complete setup, camera to serializer, serializer to deserializer, deserializer to RPi4)

3: Tried without the connection (Only serializer connected by the USB)

4: Tried reninstalling the GUI multiple times. No help!

5: Tried on a different PC. No help!

Stuck here. Unable to understand what can be the issue.

Any help here?

Thanks

RE: MAX96717F is not recognized by the GMSL SerDes Gui

James123 — Wed, 06 Nov 2024 02:06:21 GMT

It seems like there might be a problem with the MAX96717F hardware itself.

PIC18F452 with GPS NEO6M UART

ArthurHEL — Sun, 10 Dec 2023 14:02:14 GMT

Hello,

I'm an electronics student and for my final project I'm trying to display data from a GPS (nemo 6m) operating via RS232 communication on an LCD screen with my PIC18F452. I had made a code for the LCD without a library, which worked without a hitch and which I used in this code.

The code for displaying data from an RS232 communication is relatively simple and works very well with a TTL to USB card.

The code below for displaying GPS data on the LCD works, but only once. When I run the program, it displays the time correctly, but I have to press the reset button to refresh. It seems that the code is stuck somewhere....

After many tests, I don't understand why and that's why I'm coming to you.
Thanks in advance for taking a look.

Technical specification:
16MHz quartz

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:9e23c30e-6a3c-4a0d-b52a-fdddefe1750c:type=text&text=%2F%2F%20Pour%20les%20commandes%20du%20LCD%20%3A%20https%3A%2F%2Fbinaryupdates.com%2Finterface-lcd-with-lpc2148-arm7%2Fjhd162a-lcd-command-codes%2F%0D%0A%2F%2F%20Voir%20datasheet%20p174%20et%20p176%20%3A%20https%3A%2F%2Fww1.microchip.com%2Fdownloads%2FaemDocuments%2Fdocuments%2FMCU08%2FProductDocuments%2FDataSheets%2F39564c.pdf%0D%0A%23include%20%3Cp18f452.h%3E%20%0D%0A%23include%20%3Cdelays.h%3E%0D%0A%23include%20%3Cstdio.h%3E%0D%0A%20%0D%0A%23pragma%20config%20OSC%20%3D%20HS%20%20%20%2F%2F%20Travailler%20%C3%A0%2016MHz%0D%0A%23pragma%20config%20PWRT%20%3D%20ON%20%0D%0A%23pragma%20config%20BOR%20%3D%20OFF%20%0D%0A%23pragma%20config%20WDT%20%3D%20OFF%20%20%0D%0A%23pragma%20config%20LVP%20%3D%20OFF%20%20%0D%0A%20%0D%0A%0D%0A%2F%2F%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%20D%C3%A9clarations%20des%20PINs%20de%20sortie%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%0D%0A%2F%2F%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%20Output%20PIN%20declarations%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%0D%0A%0D%0A%2F%2F%20D%C3%A9finition%20pour%20broches%20en%20sortie%0D%0A%2F%2F%20Definition%20for%20output%20pins%0D%0A%23define%20data4DEF%20TRISBbits.TRISB4%0D%0A%23define%20data5DEF%20TRISBbits.TRISB5%0D%0A%23define%20data6DEF%20TRISBbits.TRISB6%0D%0A%23define%20data7DEF%20TRISBbits.TRISB7%0D%0A%23define%20RSDEF%20TRISCbits.TRISC0%0D%0A%23define%20RWDEF%20TRISCbits.TRISC1%0D%0A%23define%20EDEF%20TRISCbits.TRISC2%0D%0A%0D%0A%2F%2F%20D%C3%A9finition%20pour%20l%27%C3%A9tat%20des%20broches%20%28m%C3%AAme%20que%20pour%20TRIS%29%0D%0A%2F%2F%20Definition%20of%20pin%20status%20%28same%20as%20TRIS%29%0D%0A%23define%20data4%20PORTBbits.RB4%0D%0A%23define%20data5%20PORTBbits.RB5%0D%0A%23define%20data6%20PORTBbits.RB6%0D%0A%23define%20data7%20PORTBbits.RB7%0D%0A%23define%20RS%20PORTCbits.RC0%0D%0A%23define%20RW%20PORTCbits.RC1%0D%0A%23define%20E%20PORTCbits.RC2%0D%0A%0D%0A%2F%2F%20Param%C3%A8tre%20interne%20%28pas%20toucher%29%0D%0A%2F%2F%20Internal%20parameter%20%28do%20not%20touch%29%0D%0Aint%20delai%20%3D%201%3B%0D%0A%0D%0A%0D%0A%2F%2F%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%20Toutes%20les%20fonctions%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%0D%0A%0D%0A%0D%0Avoid%20LCD_Cmnd%20%28unsigned%20char%20cmnd%29%0D%0A%7B%0D%0A%20%20%20%20%2F%2F%20Permet%20d%27appliquer%20les%20bits%20de%20la%20commande%20sur%20les%20bonnes%20PINs%20de%20sortie%20%28en%20fonction%20des%20define%29%0D%0A%20%20%20%20%2F%2F%20Enables%20command%20bits%20to%20be%20applied%20to%20the%20correct%20output%20PINs%20%28depending%20on%20define%29%0D%0A%20%20%20%20data4%20%3D%20%28cmnd%20%26%200x10%29%20%3E%3E%204%3B%0D%0A%20%20%20%20data5%20%3D%20%28cmnd%20%26%200x20%29%20%3E%3E%205%3B%0D%0A%20%20%20%20data6%20%3D%20%28cmnd%20%26%200x40%29%20%3E%3E%206%3B%0D%0A%20%20%20%20data7%20%3D%20%28cmnd%20%26%200x80%29%20%3E%3E%207%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20RS%20%3D%200%3B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20Mode%20commande%0D%0A%20%20%20%20E%20%3D%201%3B%0D%0A%20%20%20%20Delay10KTCYx%20%28delai%29%3B%0D%0A%20%20%20%20E%20%3D%200%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20data4%20%3D%20cmnd%20%26%200x01%3B%0D%0A%20%20%20%20data5%20%3D%20%28cmnd%20%26%200x02%29%20%3E%3E%201%3B%0D%0A%20%20%20%20data6%20%3D%20%28cmnd%20%26%200x04%29%20%3E%3E%202%3B%0D%0A%20%20%20%20data7%20%3D%20%28cmnd%20%26%200x08%29%20%3E%3E%203%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20E%20%3D%201%3B%0D%0A%20%20%20%20Delay10KTCYx%20%28delai%29%3B%0D%0A%20%20%20%20E%20%3D%200%3B%0D%0A%7D%0D%0A%0D%0Avoid%20LCD_Charact%20%28unsigned%20char%20charact%29%0D%0A%7B%0D%0A%20%20%20%20%2F%2F%20Permet%20d%27appliquer%20les%20bits%20du%20caract%C3%A8re%20sur%20les%20bonnes%20PINs%20de%20sortie%20%28en%20fonction%20des%20define%29%0D%0A%20%20%20%20%2F%2F%20Enables%20character%20bits%20to%20be%20applied%20to%20the%20correct%20output%20PINs%20%28depending%20on%20define%29%0D%0A%20%20%20%20data4%20%3D%20%28charact%20%26%200x10%29%20%3E%3E%204%3B%0D%0A%20%20%20%20data5%20%3D%20%28charact%20%26%200x20%29%20%3E%3E%205%3B%0D%0A%20%20%20%20data6%20%3D%20%28charact%20%26%200x40%29%20%3E%3E%206%3B%0D%0A%20%20%20%20data7%20%3D%20%28charact%20%26%200x80%29%20%3E%3E%207%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20RS%20%3D%201%3B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20mode%20caract%C3%A8re%0D%0A%20%20%20%20E%20%3D%201%3B%0D%0A%20%20%20%20Delay10KTCYx%20%28delai%29%3B%20%0D%0A%20%20%20%20E%20%3D%200%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20data4%20%3D%20charact%20%26%200x01%3B%0D%0A%20%20%20%20data5%20%3D%20%28charact%20%26%200x02%29%20%3E%3E%201%3B%0D%0A%20%20%20%20data6%20%3D%20%28charact%20%26%200x04%29%20%3E%3E%202%3B%0D%0A%20%20%20%20data7%20%3D%20%28charact%20%26%200x08%29%20%3E%3E%203%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20E%20%3D%201%3B%0D%0A%20%20%20%20Delay10KTCYx%20%28delai%29%3B%20%0D%0A%20%20%20%20E%20%3D%200%3B%0D%0A%7D%0D%0A%0D%0A%0D%0Avoid%20init_LCD%20%28void%29%0D%0A%7B%0D%0A%20%20%20%20%2F%2F%20Mise%20en%20sortie%20des%20PINs%20choisis%20en%20sortie%0D%0A%20%20%20%20%2F%2F%20Output%20selected%20PINs%0D%0A%20%20%20%20data4DEF%20%3D%200%3B%0D%0A%20%20%20%20data5DEF%20%3D%200%3B%0D%0A%20%20%20%20data6DEF%20%3D%200%3B%0D%0A%20%20%20%20data7DEF%20%3D%200%3B%0D%0A%20%20%20%20RSDEF%20%3D%200%3B%0D%0A%20%20%20%20RWDEF%20%3D%200%3B%0D%0A%20%20%20%20EDEF%20%3D%200%3B%0D%0A%20%20%20%20RW%20%3D%200%3B%0D%0A%20%20%20%20LCD_Cmnd%280x28%29%3B%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20Mode%204bits%2C%202%20lignes%20%0D%0A%20%20%20%20LCD_Cmnd%280x01%29%3B%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20Clear%20l%27%C3%A9cran%0D%0A%20%20%20%20LCD_Cmnd%280x0C%29%3B%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20Display%20on%2C%20cursor%20off%20%280x0F%20-%20Display%20on%2C%20cursor%20clignotant%29%0D%0A%7D%0D%0A%0D%0Avoid%20init_UART%28void%29%20%7B%0D%0A%20%20%20%20SPBRG%20%3D%2025%3B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%2F%2F%20Bas%C3%A9%20sur%20la%20formule%20%28%28%284000000%2F9600%29%2F64%29-1%29%20%2F%2FMettre%20la%20trensmition%20sur%202400%20si%20SPBRG%3D25%0D%0A%20%20%20%20TXSTAbits.SYNC%20%3D%200%3B%20%20%20%20%20%20%20%20%20%2F%2F%20Mode%20asynchrone%0D%0A%20%20%20%20TXSTAbits.BRGH%20%3D%200%3B%20%20%20%20%20%20%20%20%20%2F%2F%20Mode%20low%20speed%0D%0A%20%20%20%20RCSTAbits.SPEN%20%3D%201%3B%20%20%20%20%20%20%20%20%20%2F%2F%20Activer%20le%20port%20s%C3%A9rie%20%28TX%20et%20RX%29%0D%0A%20%20%20%20RCSTAbits.CREN%20%3D%201%3B%20%20%20%20%20%20%20%20%20%2F%2F%20Activer%20la%20r%C3%A9ception%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%0D%0A%7D%0D%0A%0D%0A%0D%0A%0D%0A%2F%2F%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%20Code%20Principal%20%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%0D%0A%0D%0Avoid%20main%20%28void%29%20%0D%0A%7B%20%20%0D%0A%20%20%20%20char%20tabGPS%5B100%5D%3B%0D%0A%20%20%20%20int%20i%3B%0D%0A%20%20%20%20int%20y%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20init_UART%28%29%3B%0D%0A%20%20%20%20init_LCD%28%29%3B%0D%0A%20%20%20%20%0D%0A%20%20%20%20while%20%281%29%7B%0D%0A%20%20%20%20%20%20%20%20%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20Charger%20le%20tableau%20avec%20les%20donn%C3%A9es%20du%20GPS%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20Load%20table%20with%20GPS%20data%0D%0A%20%20%20%20%20%20%20%20for%20%28i%3D0%3Bi%3C100%3Bi%2B%2B%29%7B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20while%20%28PIR1bits.RCIF%20%3D%3D%200%29%3B%20%20%20%20%20%20%20%20%20%2F%2F%20Attendre%20qu%27un%20caract%C3%A8re%20soit%20re%C3%A7u%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20tabGPS%5Bi%5D%3D%20RCREG%3B%20%0D%0A%20%20%20%20%20%20%20%20%7D%0D%0A%20%20%20%20%20%20%20%20%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20Parcouir%20le%20tableau%20et%20afficher%20ce%20qui%20nous%20interesse%20%0D%0A%20%20%20%20%20%20%20%20%2F%2F%20Browse%20the%20table%20and%20display%20what%20interests%20us%20%0D%0A%20%20%20%20%20%20%20%20for%20%28y%3D0%3By%3C100%3By%2B%2B%29%7B%0D%0A%20%20%20%20%20%20%20%20%20%20%20if%20%28tabGPS%5By%5D%20%3D%3D%20%27G%27%20%26%26%20tabGPS%5By%2B1%5D%20%3D%3D%20%27P%27%20%26%26%20tabGPS%5By%2B2%5D%20%3D%3D%20%27R%27%26%26%20tabGPS%5By%2B3%5D%20%3D%3D%20%27M%27%26%26%20tabGPS%5By%2B4%5D%20%3D%3D%20%27C%27%29%7B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Cmnd%280x80%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B6%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B7%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28%27%3A%27%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B8%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B9%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28%27%3A%27%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B10%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20LCD_Charact%28tabGPS%5By%2B11%5D%29%3B%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7D%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%20%0D%0A%20%20%20%20%7D%0D%0A%7D%20%0D%0A]

RE: PIC18F452 with GPS NEO6M UART

ArthurHEL — Mon, 11 Dec 2023 08:47:31 GMT

Hello again,

Your reply made me think a lot and after a few tests, I found out what was wrong and it's quit simple ahah.

When I come out of my first loop, I have to disable communication (probably to avoid reading unwanted data) and re-enable it when I've finished displaying my various data!
I've displayed the time and one of the two GPS coordinates and it's working perfectly!

Thanks for your help, have a nice day!

RE: PIC18F452 with GPS NEO6M UART

JWx — Sun, 10 Dec 2023 19:50:16 GMT

it seems that it generates buffer overflow - what happens when (inside second loop) y > 95? Loop reads data beyond tabGPS end... Question is if it can hang the code? Maybe you can put some debug (cycle some led or print on uart console) inside while loop to check if it iterates or stops?

RE: Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

scottiebabe — Wed, 29 Nov 2023 16:42:54 GMT

You may consider doing the operation digitally. Your increasing the sensitivity 8% or 0.1 bits changing the FSR from 5V to 4.6V. You could subtract 416 mV in software. Sounds like a neat project, best of luck.

RE: Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

shabaz — Wed, 29 Nov 2023 16:36:29 GMT

You explicitly mention in your workaround attempts:

Workaround attempts:
- 0.416 V output from DAC to RB7, directly conneted to RA2 via a wire, works just as badly as above.

I'm merely explaining the pointlessness of doing that, since the datasheet makes it clear that would not be possible.

You have a solution, which is a buffer.

If you are unwilling to accept a workaround, then I'm no expert here but it's clear from the datasheet that what you're suggesting is not possible.

Check the diagram below. The negative reference input to the ADC comes from either a pin, or from ground. You can see it in red.

The DAC output (described as a DAC reference output in the datasheet) in usable internally , as an input to the channel (shown in blue below), not as a input to the ADC negative reference.

If you provided more information about your actual use-case (what you're measuring for instance) then maybe there are other solutions, but trying to make an internal connection that doesn't exist won't work.

RE: Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

Mila_G — Wed, 29 Nov 2023 12:49:27 GMT

I have read the PIC specs carefully: "A buffer must be used on the DAC reference output for external connections to the DAC1OUT1/2 pins.", see above. But I would like to use internal connection! No user external circuitry conneted to the RA2 pin, no wiring, but only internal connection from RA2 to the ADC ref. input inside the MCU.

Many thanks. Mila.

RE: Wrong operation when using internally generated negative voltage reference for A/D converter on PIC16F18877

shabaz — Wed, 29 Nov 2023 01:50:21 GMT

I didn't read it all, and I have not used a PIC for many years, but looking here:

If I've understood your requirement right (I might not have - I'm not used to these registers and other detail you mention) it's not a surprise if wiring the DAC to anything requires a buffer. The DAC appears to be composed of a ladder of resistors with no buffer from what I can tell, so yes, you'd need to add your own buffer (e.g. op-amp) when realistically connecting that externally to anything.

If you mention your actual end requirement (including what you're actually trying to connect the ADC to), and why the external buffer is not usable, then perhaps a different or better solution could be provided.

RE: And the PIC Fans go wild - PIC18 in Tesla Roadster BMS

michaelkellett — Thu, 23 Nov 2023 08:43:06 GMT

Kudos to Elon and Tesla for actually open sourcing this kind of stuff.

I can't think of any other major car maker to do so.

Just a pity Elon can't be more consistently admirable 🙁

And the PIC Fans go wild - PIC18 in Tesla Roadster BMS

scottiebabe — Wed, 22 Nov 2023 19:33:48 GMT

https://service.tesla.com/roadster

RE: And the PIC Fans go wild - PIC18 in Tesla Roadster BMS

Fred27 — Thu, 23 Nov 2023 08:27:05 GMT

*Starts rummaging through parts bin looking for a PIC18 and a Lotus Elise*

RE: And the PIC Fans go wild - PIC18 in Tesla Roadster BMS

scottiebabe — Wed, 22 Nov 2023 20:09:10 GMT

LOL 😭 That;s too funny! Lots of standby legends BAT54, 1n4148, LP2985

RE: And the PIC Fans go wild - PIC18 in Tesla Roadster BMS

Jan Cumps — Wed, 22 Nov 2023 20:05:04 GMT

checking for a 555 timer ...

PIC10F microcontroller output pin tolerance to overriding voltages

davebullockmbe — Mon, 06 Nov 2023 09:44:42 GMT

I am using PIC10F microcontrollers in a wireless project that has evolved into needing to use an 'in circuit' programmable radio IC.

The problem is that the GP2 pin of the PIC would be connected to the DATA input (and programming) pin3 of the radio IC.
The whole circuit is running off 3v7 lipo battery.
My question is will the PIC GP2 output be destroyed when programming the radio IC. ?

Thanks in anticipation....

Dave

RE: PIC10F microcontroller output pin tolerance to overriding voltages

michaelkellett — Tue, 07 Nov 2023 09:17:26 GMT

You can set GP2 as an input to prevent it from loading the radio pin during programming:

From the Microchip data sheet.

5.2 TRIS Registers
The Output Driver Control register is loaded with the
contents of the W register by executing the TRIS f
instruction. A ‘1’ from a TRIS register bit puts the corresponding
output driver in a High-impedance mode. A
‘0’ puts the contents of the output data latch on the
selected pins, enabling the output buffer. The exceptions
are GP3, which is input only and the GP2/T0CKI/
COUT/FOSC4 pin, which may be controlled by various
registers. See Table 5-1

RE: PIC10F microcontroller output pin tolerance to overriding voltages

davebullockmbe — Mon, 06 Nov 2023 20:58:41 GMT

Yes the problem with adding a diode in series with the data line is as you say the data pin of the radio chip will float and so need a resistor to pull it down. Unlike Microchip datasheets I cannot find any information about the internal structure of these radio IC's ie. whether they have internal pull-ups/downs. I have just about run out of board space and am struggling to add even one more component.
However putting the PIC10F202 into reset would be a great idea but doesn't this need extra PIC code to force the o/p pins into tristate. I don't think toggling MCLR does this on it's own?
Dave

RE: PIC10F microcontroller output pin tolerance to overriding voltages

scottiebabe — Mon, 06 Nov 2023 17:35:39 GMT

If you could hold the processor in reset, GP2 would be tri-stated...

RE: PIC10F microcontroller output pin tolerance to overriding voltages

dougw — Mon, 06 Nov 2023 17:29:24 GMT

Actually, you could replace R6 with a diode and D2 with a resistor. Then you would just need a jumper to the data pin (and a cut to the original path).

RE: PIC10F microcontroller output pin tolerance to overriding voltages

dougw — Mon, 06 Nov 2023 17:22:46 GMT

You might also need a pull down resistor unless you can just short out D2.

RE: PIC10F microcontroller output pin tolerance to overriding voltages

davebullockmbe — Mon, 06 Nov 2023 15:24:49 GMT

HI thanks for your considered replies. I had thought about a jumper but board space is too tight. Maybe I can make room for a 0402 schottky diode though. I was hoping I would get away without reworking the board but you have confirmed my doubts. Thanks Dave

RE: PIC10F microcontroller output pin tolerance to overriding voltages

dougw — Mon, 06 Nov 2023 14:30:31 GMT

Could you use a Schottky diode in series to protect the PIC?

RE: PIC10F microcontroller output pin tolerance to overriding voltages

JWx — Mon, 06 Nov 2023 13:53:12 GMT

maybe some OR gate could be placed between if external programming is needed? Or even removable jumper - even if GP2 will not be destroyed by forcing it into opposite state, it could interfere with programming signal...