We need to convert C language drivers from dsPIC33EP512GP506 to dsPIC33FJ128GP306 due to the current unavailability of the former and our current old stock of PCB's with dsPIC33FJ128GP306 which we need to now use. They are very similar and essentially it is the pin usage that has to be corrected.
For a guru on Microchip PIC's this will be quite easy to do.
Very importantly, after I assign this project, there will be no renegotiation of the price. Don't waste my time with low ball bids and then try to ask for more money later. I'm providing the schematics and the source code plus I will answer any questions before final bid. Please do not bid if you do not have relevant experience with drivers on the PIC platform and therefore waste my time. Only make an initial bid once you have checked the details of this project attachments.
In the source code files you will see some code between #if defined(GRIPBOARD) || defined(OLDBOARD) || defined (BELTBOARD) ||defined(BASICGRIP) and #endif that is the current production code for dsPIC33EP512GP506. From a much earlier version of the system that was never in production but does compile for dsPIC33FJ128GP306 is code between
#if defined(SATR2PCB) and #endif. What is needed is the SATR2PCB part to be modified to 1) work exactly the same as the production code for dsPIC33EP512GP506 and 2) works.
I will work with you closely on this project testing modified drivers on my development board and providing results. Typically during business days be able to provide test result feedback in 24 hours. Allow the testing delay in your elapse time for this project. I do expect for the right person this project could be done in a few hours but testing cycles means we are likely to have an elapse time of the project of 1 week
14 freelancers estão ofertando em média $667 nesse trabalho
Can you please send me the project? Is it mplabx project or some other compiler? I have kept 14 days as a buffer , it must get over in a day or two max... but if something doesnt happen,you have to be patient.
Looking on it, you can provide precise information, like which part got what issue during compilation or working incorrectly. That I can quickly narrow down on issues.