Thanks, are you saying that pic16f877a is not suitable for this project? No that is not what he is saying ! He is saying he compiled the code for an 877 as he propably does not have an 877A (it is a very old chip) and you can use the code as a reference but you need to change the micro controller s...

Lana Thank you for trying to convince me that mE is working on the dsPIC compilers ,I have to believe you however experience with mE has shown me otherwise over the last 10 years we are now at end August 2016 say it is true then a update should be around end October 2016 ,Will this be an update as w...

Our developers are updating dsPIC compilers at this moment, and in new release which should be in 1-2 months, Whaha ha :shock: This your colleague said in February we were expecting the release in June 2016 and now you say again the same thing what shall we believe from mE you people are just unbel...

@diode_blade As a user of Proteus for about 10 years I can say it is a very nice tool for testing PIC C code. As a +30 year professional engineer I have used this application to simulate the microcontroller operative processes for many commercial product designs. The issue with ANY simulation tool ...

As Dave has mentioned use a device that has an dedicated QEI interface for the Rotary encoder however you should in my opinion consider a dsPIC33EP as it has the processing power
for the needed engine calculations

It is better to do everything yourself in code

This one of the things users has been asking from mE for many years however it is not possible to do this by using this compiler library files
you have to set and configure the PWM module yourself in code to be in complimentary mode then it will do exactly what you want

nadir.celebic wrote: Currently, the dsPIC33EV family is not supported by our tools,
We should support it soon.

This mE said 4 years ago when this family was released soon you say we will see

We have in plan to add support for PIC32MZ EF family in the next release wha Again one of those automated replies, Are you aware that it has been a very long time since mE did anything usefull to the compiler ?your r comment of the next release has no meaning unless you say when you intend to do th...

I feel/read like times have changed: While Microchip WAS strongly behind with the programmer environment , MikroE WAS ahead. Now Microchip got somewhat better while MikroC-PIC only gets minor cosmetic updates. I am sorry to say but you have no clue what you are talking about . (1) MCHP has always s...

biljana.nedeljkovic wrote: @p.erasmus, there will be more PIC/dsPIC devices supported in the upcoming updates.

I really hope this is true, I am sceptic about this as many of your Support Team people exactly said these same words over the years and the result showed otherwise

I don't think that this is a place for redirecting our users to other compilers/toolchains, Lana with all respect I did not redirect this person to another toolcahain(read his post) he is already using Harmony with mE mini32 board ,you directed him to your compiler and I gave him my opinion and exp...

I suggest you to try our compiler mikroC PRO for PIC32, demo version is free: Well you will be very sorry when you follow this advise ,mE updates the PIC compilers evry 3-4 years and some families of mcu's never gets implemented in the compilers read the getting started manual for Harmony and solve...

you can wait for the standard reply of: `unfortunately it is not supported yet, will forward/suggest to developers, will be fixed in a later update.` Thats what you will hear from mE. come back in 3 more years to find nothing has been done unfortunately this is true your chances of it being fixed a...

My guess is that compilers updates will be to merge Visual TFT into the Compilers like already announced but very few update to the compilers themselves. I can only agree with this as it has been the trend the last few years all new things you add to the ARM compiler get implemented in the other co...