Blockset described on this wiki is deprecated since 2012.

For Model Based Design (MBD), use the free MPLAB Device Blocks for Simulink, tool from Microchip.
Updated Rapid Control Prototyping (RCP) custom projects are published at:

Customer Feedback

From - Simulink device driver Blockset for dsPIC / PIC24 / PIC32 Microcontrollers --[[User:LubinKerhuel|LubinKerhuel]] 12:40, 3 September 2009 (UTC)
Revision as of 16:38, 16 July 2009 by Malife (talk | contribs)
Jump to navigation Jump to search

This page is for customers' feedback

To edit this page, you must first first Log in / create account (link at top right)

Please write your feelings (good strong points and weaknesses) about the blockset. A small description of projects you are working on would be appreciated. You can add a weblink to projects developed with the blockset, and illustrations. If you do not know how to do it (test with the Sandbox), you can just send me an email with the information.

Thanks for your participation


Use of Lubin's Blockset in the SLUGS Project

I've looked at both alternatives in the market (Microchip's and Lubin's) and actually tested both of them and I have to say Lubin's is much better than Microchip's. For instance the C function call that Microchip implements 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 really like Microchip's products and I think there are many things they are doing very well, but their Simulink blockset is not one of them.

The usage of this blockset has allowed us to develop much faster and with fewer bugs than hand written code. At the same time, by providing the C function-call block he has given the freedom to implement all the required functions. It is so versatile that if you really wanted you could rewrite the whole blockset using C function-calls (not that I would ever do it, but you could). Code generated by this blockset is being used in a UAV and has proven to correctly generate code based on Simulink models.

Overall we are extremely satisfied with the results we've gotten. I highly recommend it.

Mariano I. Lizarraga PhD Candidate UCSC Autonomous Systems Lab [[1]]