Well, I went ahead and tried a couple of things. I forcefully blocked program flow on the microcontroller in order to use USB_BREAK(), then, I called the function from a few interrupt sources to test how it worked, but nothing ever happened. My question now is if this function only works when servic...

Hello Mikroe people. Here I am once again in the adventures of USB using PIC microcontrollers. The question here is really the title, the help section doesn't say much about it but just the fact that it acts as a WDT, but it doesn't give a clue on how it is supposed to be implemented. Just saying th...

@Thomas.Pahl@t-online.de, thanks for the advice. I also thought about using a separate and very small microcontroller just as a WS2812B driver, and to be frank it's not such a bad idea, considering prices for low end PICs now days. The thing here is that, when it comes to lowering prices as much as ...

If I read right, you use interrupts? That is not a good idea with WS2812. Perhaps your problem is there. When I use the software solution all interrupts are off. This interrupt thing was bugging me after I read it, and guess what, it worked, my WS2812B bit-banging works flawless with 24 LEDs, maybe...

Interesting posts right there. From what I see, when people use these Neopixels on PIC, they either don't use any other peripherals on the chip and make it a single purpose application or they use specialized internal components as the CLC. I have come across those PDFs and tutorials with CLC, there...

Wait... I had an idea and I hope people may follow along :idea: Shouldn't I be able to do the same thing proposed in that tutorial, but instead of using the SPI bus, I could use the UART pins? If my FOSC after applying the PLL is 48MHZ, and my instruction frequency is therefore 12MHZ, I should be ab...

Well, I am using my 18F2550 at 48MHZ clock, which turns into 12MHZ instruction cycle. I saw the video, it is in english actually :D. The problem with that method is that I am using INT0-INT2 interrupts on this microcontroller, which are inconveniently located exactly over the same pins for SPI proto...

Hello mikroE people. I recently managed to emulate the WS2812B protocol on a 18F2550 and it kind of works. The problem is that, when toggling some LEDs in a row using a WS2812B ring, it sometimes happens that other LEDs flicker with different unintended colors and brightness, and it happens very ran...

It took me a while to figure out your code, specially because I program PICs with C, but I managed to digest it. I like the way that is being handled, it is quite practical, it works, but it has a bit of a flaw, not too critical though: Encoder Signals.jpeg To explain myself, what you are doing in y...

Hello MikroE people. I was wondering if anyone knows a way of how to use multiple encoders with a low end microcontroller, like the PIC 18F2550. I had the idea to multiplex them, but unfortunately, the cheap KY040 modules have NORMALLY CLOSED channels, which means that, if I multiplex it, every time...

So, I don't know why I didn't think of this before, maybe you get so focused on the complex side of things that sometimes you don't see the easy stuff that is right on front of your nose... I confirmed that the volume behavior is just like that on a computer, or at least on windows, it goes up slowl...

Hello MikroC people. So, after quite a long time messing around with USB HID on MikroC Pro using a PIC18F2550 , I managed to get a volume knob working with my requirements.... kind of ... I was wondering if when lowering the volume, is it supposed to go faster than when volume goes u p? Because that...

Hello once again. The response as a whole is quite educative, though I have to disagree with the fact that anything at all is extensively documented, there are fairly good and basic working examples, but not highly documented, but that's it, the rest of it is a very good explanation of pretty much e...

Hello world. I don't know how to NOT sound like that kind of person, the one who is a big hater on the tool just because things don't work as expected, but even though I don't have decades of experience programming PICs, I am not that of an amateur either, so I usually blame it on myself, until I so...

I tested the project again, implementing now TIMER1 instead of TIMER0 for the same purpose, and the issue is the same. It seems like subsequent calls to any timer faster or at the same speed as USB interrupts, actually affects negatively USB routines , meaning by this that USB cannot coexist with in...