Dear all,
Why is that that PIC32 seems to be the least supported chip both by Kerhuel's blockset and Microchip's? (By the way, is Microchip's blockset based on his?)
Is PIC32 likely to receive better coverage soon and leave the "experimental" status?
Thanks in advance. Cheers,
Jorge.
PIC32
-
- Site Admin - Expert
- Posts: 616
- Joined: Wed Mar 07, 2007 11:23 pm
- Location: Bayonne- France
- Contact:
Re: PIC32
Hi Jeorge,
I’ve been developing the blockset for more than three years now. I release a first version in march 2007. Microchip released its blockset in late 2008, about September or October, that is one year and a half after my first release.
Microchip also had the same good ideas to create a NOP block and to add a "C function Call" block which are two very specific blocks. I think that I still have few more ideas since I am using my blockset to build complex automatic systems. For example ideas for tools to check that real time constraint are respected. I am not sure that microchip’s blockset embedded a visualisation system allowing seeing or logging variables evolution in the matlab environment.
Provided someone tested Microchip blockset, it would be appreciated to get a comparative review.
Lubin
As soon as you guys will use it in your projects, it will leave the experimental status. It is still experimental for me since I do not use theses chip in my projects yet. Not but reported yet, but is there anybody using it ?jorge.pelizzoni wrote:Is PIC32 likely to receive better coverage soon and leave the "experimental" status?
Could not answer this question; you should post the question on microchip’s forum. It’s true that I was asked few technical questions by the microchip’s Indian development team few years ago.jorge.pelizzoni wrote:is Microchip's blockset based on his
I’ve been developing the blockset for more than three years now. I release a first version in march 2007. Microchip released its blockset in late 2008, about September or October, that is one year and a half after my first release.
Microchip also had the same good ideas to create a NOP block and to add a "C function Call" block which are two very specific blocks. I think that I still have few more ideas since I am using my blockset to build complex automatic systems. For example ideas for tools to check that real time constraint are respected. I am not sure that microchip’s blockset embedded a visualisation system allowing seeing or logging variables evolution in the matlab environment.
Provided someone tested Microchip blockset, it would be appreciated to get a comparative review.
Lubin
Re: PIC32
I've looked at both and actually tested but of them and I have to say Lubin's is much better than Microchip's. For instance the C function call that they implement you can only pass scalars (i.e. no vectors) which is essentially useless. Also all of their blocks are polled-based instead of interrupt driven, which if you are playing in a classroom it might be OK but if you are doing some serious development is also useless.
We decided to stay with Lubin's blocks for this reason and also for the continuous support. Usually issues that we've had (bugs) have been resolved within 48 hours. Try getting that from Microchip. Don't get me wrong I love the brand and I think there are many things they are doing very well, but their Simulink blockset is not one of them.
Regarding the PIC32 I can not tell, I've only used the dsPIC.
Hope this helps.
We decided to stay with Lubin's blocks for this reason and also for the continuous support. Usually issues that we've had (bugs) have been resolved within 48 hours. Try getting that from Microchip. Don't get me wrong I love the brand and I think there are many things they are doing very well, but their Simulink blockset is not one of them.
Regarding the PIC32 I can not tell, I've only used the dsPIC.
Hope this helps.
Who is online
Users browsing this forum: No registered users and 1 guest