Problems with Acoupel Midi > CV Pic program

diablojoy · Posted: Mon Dec 13, 2010 12:46 am Post subject:

maybe throwing you a curve ball, not sure. pic's are not my thing yet
however that debug code may be pointing you in a reasonably logical direction to follow
[quote]

Blue Hell · Posted: Mon Dec 13, 2010 6:48 am Post subject:

fonik · Posted: Mon Dec 13, 2010 7:13 am Post subject:

anyways, if someone successfully built this module, the problem will not be in the code (porimary). could it be a bad collaboration between the PICkit2 and the code?
i have the feeling, that i am way too deep in the issue - actually it should not be any issue, if others build this project without any issue...

i am puzzled.

diablojoy · Posted: Tue Dec 14, 2010 1:23 am Post subject:

perhaps a gentle enquiry to rykhaard he has bought a pickit3 some few months ago he may have come across this or something similar enough
I do have a feeling it is something simple in the communication between
the PIC and the pickit2 however as jan said using the internal osc and having a midi interface is not great perhaps an out of spec PIC ? though the internal clock is trimmable going by the data sheet . have you tried another PIC yet ?
please post your result if you do resolve this as i do have an ulterior motive, I was planning to buy a pickit2 myself early next year
for the acoupel master clock and cv recorder projects and therefore problems like this one are of some concern to me

fonik · Posted: Tue Dec 14, 2010 5:20 am Post subject:

ejr27233 · Joined: Feb 08, 2010 Posts: 43 Location: UK

As the OP I've tried everything and still cant get it working......
what it has done is make me look into PIC's and Midi > CV and I'm thinking of trying to design /program a combination of 16fXXX PIC (external crystal) and one of these
http://docs-europe.electrocomponents.com/webdocs/0e43/0900766b80e439ff.pdf
to get 6 CV's, 6 velocities and 6 triggers. Ideal for midi guitar and very cheap as the DAC is about 8 euros.

Does anyone know if this combination would work??

fonik · Posted: Tue Dec 14, 2010 2:57 pm Post subject:

Quantizer:

today i think i managed what you suggested in regards to the config bits.

i switched to debug mode and built the project. then i run debug. as before all the code protection was switched off by MPLAB. i then EXPORTED the file via file/export menu to hex code, while i checked off the "config bits are set in code" option in the confog window.

i then was able to load the hex without any error message into the PICkit2 programmer software - and write, verify, and read the code without any error.

alas, the quantizer does not do anything Crying or Very sad

so for now i am not far from wanting to surrender. last option was to breadboard again...

mattias · Joined: Jan 26, 2010 Posts: 28 Location: Cologne

Sorry to jump into this thread. I also had trouble with the HEX file from acoupel.com for the MIDI2CV version 2.3.

The issue with the source was in the __CONFIG -line. After some adjustments it worked for me.

The original bit-string for the __CONFIG line from acoupel.com seems to be broken:

I think the line

__CONFIG(1111111101011000);

should read

__CONFIG(0b1111111101011000);

or

__CONFIG(0b11111101011000);

(notice the leading "0b".)

Please note that the new source code uses symbols instead of single bits for the __CONFIG line.

ACS_MIDI V2.3.1a.hex

Description:

working image for MIDI2CV Version 2.3

Download

Filename:

ACS_MIDI V2.3.1a.hex

Filesize:

7.76 KB

Downloaded:

98 Time(s)

ACS_MIDI V2.3.1.c

Description:

working sourcecode for MIDI2CV ver 2.3

Download

Filename:

ACS_MIDI V2.3.1.c

Filesize:

9.99 KB

Downloaded:

82 Time(s)

ejr27233 · Joined: Feb 08, 2010 Posts: 43 Location: UK

Many thanks for that.
I'll try it as soon as I get chance.

mph · Joined: Aug 25, 2007 Posts: 66 Location: France

Hi

may I suggest you to post in the french Yusynth forum: Alain Coupel has a dedicated subforum ( called "ACXSynth" ). And I think it's not a problem if you post in english. So you could have help from the man himself.

http://forum.yusynth.net/

I haven't finished this module yet, but it seems the V2.3 is working for other people with no problem.

Good luck.

fonik · Posted: Mon Jan 03, 2011 4:48 am Post subject:

thanks for the hint.

did anybody here built the quantizer?

yusynth · Joined: Nov 24, 2005 Posts: 1162 Location: France

mph · Joined: Aug 25, 2007 Posts: 66 Location: France

Sorry Matthias, I don't even know if someone build the quantizer on the yusynth forum... never seen a build report for this module.

But you should ask Alain for this one too ( his nickname on yusynth/forum is "München").

PickNick · Joined: Oct 16, 2009 Posts: 80 Location: BP

hi!
i tried the latest midiCV hex via PicKit2///hex from mattias.
looks ok!
there was no protection error:)
i will try the circuit soon!
thx!

ACS · Joined: Oct 09, 2010 Posts: 2 Location: Paris

Hi everybody,
the problem you have seems to come from the __CONFIG macro.
You can find a new version of my firmware on my new website : www.acxsynth.com

(I changed my name, I'am not ACS anymore but ACX !)
This new site is still under construction, there are a lot of mistakes, but the firmware for MIDI2CV is OK.

Happy new year !

Alain

MirlitronOne · Posted: Wed Aug 29, 2012 10:23 am Post subject:

fonik · Posted: Wed Aug 29, 2012 11:47 am Post subject:

no, it is still sitting on my workbench...

but now that you remind me i will give ti a 2nd try (without creating a project in the MPLAB).

MirlitronOne · Posted: Wed Aug 29, 2012 3:11 pm Post subject:

Well, it's a long while since I did any PIC programming, but I recall that the configuration data had to be in one part of memory and the program somewhere else. I'm using a Phyton programmer which is a pretty good piece of kit, but it just seems to take the raw hex data and try to slap it straight into the chip. If I simply try to load it up, it fails. If I offset the loading to start at location 100, it loads and verifies perfectly - but the quantizer still doesn't work. Like you, I've thoroughly checked all the support circuitry.

Looks like I'll have to go back to the textbooks... But somebody out there must know how to get this to work.