jrp
-
Posts
199 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by jrp
-
-
Very strange:
I used a third core module, this time not on veroboard like the other two but on a pcb from mike.
It´s running!
So for one thing i am happy, but on the other hand i would like to know what´s wrong with my core build.
Has anyone experienced problems like me before? A core running only certain apps?
The only difference on my veroboard layouts that i can see is that i tied pin 1 directly to 5v, ommiting the 100r resistor. In my understanding it´s not necessary if the core is not to be resetted under power, right?
I´ll try to trace everything, but i really see no other difference.
Strange, isn´t it?
Edit: Added the 100r on pin 1, no difference.
The Pic that was running the Sid app on the other core is saying bootloader is running again.
scratching my head...
-
As mentioned in my posts,
i disconnected the sid circuitry (no difference, and the testtone app was giving me the 1khz triangle)
i used a different core (no difference)
I tried three midi interfaces on OSX and Windows (no difference)
Only thing i haven´t changed is the PIC as it´s the only 18f4685 i have.
Maybe i got a fake chip? Any tests i could do?
-
i just tried this with a different core module (and i know it´s working, it´s part of the controller i use every day).
Same result with the files i want to use
Mios_v1.9g_pic18f4685 : Application is up and running
setup_6581: Bootloader is up and running.
But what is even stranger: When i try to upload apps meant for the other pic chips like MB_SEQ i get an error:
Detected Mios8 and Mios32 response - selection not supported yet!
-
Well, i have no idea but that the 18f4685 is a newer chip and is it downward compatible. Also i did not test if these applications are running as expected. I have no lcd and no other interface connected. All i could see was that MIOS Studio was saying everything is ok. So i can see that the core seems to be fine and MIDI transmission seems to be working in both directions.
-
Now i had the chance to test on a win7 pc. Same results. I also cut all connections to the sid-module leaving only the pic-core with all pullups and midi i/o. No LCD, no DIns or DOuts. No bankstick, no wires, soldering on any other pin. I even erased the pic and burned the bootloader for the 18f4685 again for a fresh start.
It is all the same:
Uploading MIOS 1.9gfor pic 18f4685 works flawless. Application is up and running. Last Message from core: f0 00 00 7e 40 00 0f 00 00 f7
Uploading Setup_6581.hex returns lots of f0 00 00 7e 40 00 0f xx f7 messages
Then i get Bootloader is up and running and a f0 00 00 7e 40 00 01 f7 every couple of seconds.
Then, if i hit query i get the same, OR:
No response alert, and then
f0 00 00 7e 40 00 0e 03 32 f7
f0 00 00 7e 40 00 0e 03 32 f7
f0 00 00 7e 40 00 0e 06 70 f7
after that it returns to the ever repeating
f0 00 00 7e 40 00 01 f7
Sometimes query returns a application is up and running and the message
f0 00 00 7e 40 00 0f 00 00 f7
f0 00 00 7e 40 00 0e 03 32 f7
f0 00 00 7e 40 00 0e 06 01 f7
only to return to the good old upload request....
All other applications i tried (midibox16e, midibox_seq, Midibox_cv and some more) load without any trouble showing a happy "application is up and running".
What could be the cause of this?
-
I am powering my 7805 regulator from 15v during testing, parallel to my 7812. But i am only running core and sid module (no lcd, no leds) and i put on a heatsink.
5V looks nice and solid on the scope so i see no problem there.
-
Hello,
I rechecked everything so many times... i must see i am stuck :-(
I build a core with 18LF4685 (LF version is compatible, right?) , and a sid module together on veroboard.
The Core is working and recognized, the test-tone application gives me a triangle just as it should.
Now the strange things:
Right now the interconnection test fails with all connections coming from the shift registers. Only CS# (directly driven by the pic) is working correctly.
I changed the shiftregisters to new ones with no effect.
Strangely, when i first did the test everything was fine (although the other problems still where present). It just stopped working.
As soon as i upload any of the MB_Sid applications (setup_6851, setup_6852, etc) I get the message "bootloader is up and running" after reboot.
With every query i get random messages : No connection, bootloader up, application up.
Playing on the keyboard gives me nothing, usually: Sometimes for a brief moment i can see the square wave on my oszi.
Every other application i upload to the core works seems to work, although connectiong a din(1) and uploading MBIO128 gives me CC messages and Note ons. Should be Note On only i think?
But a query will always say : "application up and running", it seems like only the sid applications are affected.
I checked the connections so many times (and i am willing to check again), also all voltages are where they should be.
I included all pullup resistors from the core schematic.
My system is MB Pro with snow leopard and MIOS Studio 2.4.6
I tried a generic 4*4 Midi interface, a Midisport 4*4 and the midi ports from a Motu 8pre. All seem to do the same.
-
I see no reason while this should not work. Maybe someone can confirm this though. My Aout is burried under pcbs in my synth so i can´t just pull a chip.
I have not yet tried the AOUT_NG. I assume it is good enough. The VCOs we want to controll are propably the limiting factor when it comes to tuning...
-
Hello,
I am planing my controller for logic pro. First thing that´s already finnished are dedicated controllers for my favorite eqs and comps based on MB-64e. Very very nice!
No come the next features for witch i will be using a midibox LC.
I have already played around with the LC application on my test bench and really like whats possible.
I do not plan to use any faders, just the VPots and buttons. And LCD, and this is where i once again scratch my head.
I am thinking about a 16 or even 24 channel version using 2-3 cores. Most of my projects come to around 24 tracks, not having to switch banks is great for me.
The problem i see is that with a 40*2 character display per 4 channels this controller will get huge.
Is there any way to display 8 channels on a single lcd like on the MB-SEQ?
So i am interested, what other options do i have. In the documentation it says that graphical lcds or a single 20*4 lcd can be used. How would the information be presented on those?
What about Midibox NG? WOuld it give me better options not possible on the core? I already have a bunch of PIC18F1620 so i would rather use those. I guess with MB-NG it would also be necessary to use one core for each 8 channels, right? Or can it be configured to look like multiple Logic Controlls on multiple midi ports?
Well, i am looking for some general advice...
Thank You!
-
Actually it´s the VC265. I wrote this mistake from memmory... 0,8% accuracy all the same.
I posted a similar question on the german ELKO-Forum and got some really helpful replies i would like to share. Maybe you like to quote this in the documentation, calibration of something that should be this accurate is not as straight forward as one might think.
--- BTW it was also mentioned that the Aout module could be improved if the output opamps were part of the feedback loop of the DAC. I didn´t follow this comment because (i´m not sure about it) i think that this is nonsense since the calibration trimmers would then also be in that loop and the output voltage would have to be scaled down in the feedback loop to match the level of the DAC. Just a thought. ---
With these multimeters some things can be considered to get the most out of them.
- Accuracy is the highest just before a measuring range ends. In this case this applies to voltages just below 4v or 40v. Calibrating to 1v or 8v would thereby not be a wise decission since it´s in the lower range of the Multimeter range.
- Below 4v you get 1mv reading, from 4v on you get 10mv as the smallest division.
- There are errors in the measurement that are chaotic and will change over time depending on temperature and noise. Unit should be powered at least 30 minutes. All measurements should be done in one session under idally the same conditions.
- More important, if you do a series of measurements in the same range one after the other like the 8 CV-outputs, errors will be static (=the same).
So i adjusted the trimmers slightly below their target value, set calibration output to 4v and trimmed just untill the reading jumps from 3.999 to 4.00.
This way there might still be a little error, but it should be as low as it gets with a multimeter like this, AND, most important, all 8 outputs will be very much on the same level.
I would say relative accuracy is most important as the VCOs that are being controlled have trimpots to set their scaling and will get along with a 1,005V/Oct or 0,991V/Oct CV just fine.
I used my ears and a tuner-plugin from logic and was able to get 6 octaves of almost perfect tracking on my 3 music from outer space VCOs.
-
I would be happy to send you a LCD, thank you very much! Just sent you a PM.
-
Hello Thorsten,
I didn´t have the chance to test this just until today. Unfortunately no luck. With the hex you linked i get the message "hello world" from my working LCD. The new ones show nothing. Not even the black row...
I did some testing with a second psu to generate a negative V0. The datasheet says Vdd-V0 is typically 5v but can be 12v max. If V0 is about 8v below Vdd a second row of black blocks appears.
I also noticed the lcd is in some way responding. During booting the core the blocks flash, also with midiio128 the blocks will disapear and reappear with some note on events.
Maybe i should move on...
-
When calibrating my AOut module for use with my analog VCOs i am having trouble getting the values right. I am measuring against ground of the AOut PCB.
On the site "Music from outer space", that is where i got the vco design from, it is suggested to use a voltage source that is within 2ma tolerance.
When trimming to get 2v just right i am reading with my Voltcraft 275:
0V (calibration mode off) : 0,001V
1V : 0,992V
2V : 2,000V
4V : 4,02V
8V : 8,04V
Is this normal? 20mV is a lot when considering the V/Oct scaling.
Maybe my Multimeter is just not accurate enough?
Should i trim so that 1V is just right, or so that 8v is just right?
-
Hm, so this is not the problem. I wasn´t expecting it would.
The application i am running is MB-LC, so the Display should be adressed in 8-Bit mode, right?
If the pinout is different, how can i trace it to the controller? Or differently put, how can i see what the controller is and how can i know what pinout it has?
-
First, if you use differen PSUs you have to connect all grounds.
Just some obvious stuff to consider:
Are the outputs really dead? Have you checked with a different ADSR? Maybe it´s just with the new module?
Is the MBCV listening on the correct midi channel?
Are you using the two gates on the MAX-Chips? If they are really blown you can switch to using the 8 Outputs provided by the core.
If you are using the Gate-outs from the core, you might need a new pic... or use the 2 Gate outs from the AOut-module instead and still haVE ll 8 Gates...(hope you haven´t blown Gate 3-8 by now)
-
Thank you for the hints.
Contrast is working, i can make the black blocks disapear by moving V0 from Vss towards Vdd.
The ribbon is fine and in the right direction. I have dil headers soldered to my lcds, so it is easy to swap and connect different lcds.
My old LCD is working fine with this exact ribbon, the 4 new ones i ordered are not working. So it´s also unlikley that i have a solder bridge on the dil-header.
WHen running the interconection test application i was measuring right at the lcd module.
It just doesn´t make sense at all to me...
-
i tested with another core module with no other modules connected.
Still no difference.
In the data sheet i read some little differences to my working lcd.
working lcd:
Data Setup Time: 60ns
E Rise/fall time: 25ns
non working lcd
Data Setup Time: 80ns
E Rise/Fall Time: 20ns
Everything else seems the same to me.
I only know my way around analog circuit design, so i am used to differences in this order not to couse any trouble.
Still, could this be the cause of my problem?
Thank you!
-
My new 2*40 LCDs are not working... I get the black blocks on the upper line.
I ordered 4 CMC 240-02
Datasheet: http://www.microdevice.de/download/cmc240-02.pdf
They go at ebay for around 9 Euro.
The Core8 is working, PIC is running Mios.
LCD Interconnection application - everything ok
Different brand LCD connected with the same ribbon cable - works.
I checked the datasheet for the new LCDs, pinout is the same as with my old working LCD.
What could be the reason...?
-
Thank you very much, Thorsten. Your efford is really amazing!
I´ll try this today in the afternoon. Currently i cannot download the file you linked, it simply opens in the browser. When clicking download i get an error message the file can not be downloaded. I´m on OSX 10.6.8 Safari and Firefox (both with same result).
I expect copying the code into a new file and naming it mb64e_meta.ini will work just as well.
-
Hello,
maybe someone will run into the same trouble one day, so i post this little info:
If you are trying to upload code via MIOS-Studio and you have Logic running at the same time with a Logic-Control installed (on the same midi port), you´ll end up in an never ending boot-loop and an midi input overrun error.
I was really scraching my head, installing different chips, different core modules, reburning the bootloader several times. Glad i found that it was simply another application interfering with my midi port.
Have a nice day!
-
Funny, i missed the fact that i first have to copy the internal bank to all other banks to make stuff like this work. gave me quite a headache...
-
Midibox LC uses 4 rows of 8 buttons/leds for track select, solo, mute and arm.
I would like to use 8 button/leds instead of 32 and -"how" is the question- flip between select, solo, mute and arm.
I am no programmer, so i am thinking about a different approach that doesn´t touch the code.
Is there a rude trick to wire the buttons/LEDs to all 4 DIn and DOut shift registers and always force 3 shift registers to be inactive?
A simple logic or a 4X4 Switch could be used to activate the registers. No idea if this is possible.
for a singe encoder i already did this using a simple toggle switch to select the pins it connects to, this can be useful for some custom applications...
EDIT: Instead of posting questions it is sometimes better to read a datasheet, pick up that old breadboard and do some testing.
For 74HC165 shift registers this exact behavior is possible by disconnecting Pin 1. This disables the parallel inputs, all other functionality of following chips is remained.
I know, you guys would do this with 3 lines of code anyhow...
But maybe this info is useful to some.
I´ll do some more testing, eg on how to parallel din chains. Possibly possible by or-ing one data line (?)
Could be useful if a user wants two (identical) control surfaces on his Midibox. One by the Computer, one by the mixing desk :)
-
Hello,
I feel almost sorry to bother you with basics, but i can´t figure out how to assign 8 LEDs to display the selected Bank (for a controller with no lcd).
In the ini file i changed the dout mapping like this:
LED_SR1 = 10
Unfortunately there seems to be something missing, it´s not working...
Connections are checked, LEDs are working.
Would be nice if someone has a hint for me.
Here is the section from the ini:
# LED Map: assignes the LED shift registers to the Button Shift
# registers or special values
# Currently following values are supported:
# 0 Default Setting (see Map below)
# 1 Button Shift Register 1 (Button ID #1-#8)
# 2 Button Shift Register 2 (Button ID #9-#16)
# 3 Button Shift Register 3 (F1-F4 and Navigation Buttons: ID #17-#24)
# 4 Button Shift Register 4 (Button ID #25-#32)
# 5 Button Shift Register 5 (Button ID #33-#40)
# 6 Button Shift Register 6 (Button ID #41-#48)
# 7 Button Shift Register 7 (Button ID #49-#56)
# 8 Button Shift Register 8 (Button ID #57-#64)
# 9 Selected Group (1 of 8)
# 10 Selected Bank (1 of 8)
# 11-15 reserved
# 16 MIDI Status received for Button ID #1-#8
# 17 MIDI Status received for Button ID #9-#16
# 18 MIDI Status received for Button ID #17-#24
# 19 MIDI Status received for Button ID #25-#32
# 20 MIDI Status received for Button ID #33-#40
# 21 MIDI Status received for Button ID #41-#48
# 22 MIDI Status received for Button ID #49-#56
# 23 MIDI Status received for Button ID #57-#64
# 24-31 reserved
################################################################################
[LED_MAP]
LED_SR1 = 10 # (Button ID #1-#8)
LED_SR2 = 2 # (Button ID #9-#16)
LED_SR3 = 3 # (F1-F4 and Navigation Buttons: ID #17-#24)
LED_SR4 = 4 # (Button ID #57-#64)
LED_SR5 = 5 # (Button ID #25-#32)
LED_SR6 = 6 # (Button ID #33-#40)
LED_SR7 = 7 # (Button ID #41-#48)
LED_SR8 = 8 # (Button ID #49-#56)
-
gladly i can answer this myself:
I configured the FF events in the midibox64e.ini (linked as a sysex configuration file in the project description) and it worked!
*SOLVED* sid testtone working, but setup_6851 upload not possible, interconnection test fails
in Testing/Troubleshooting
Posted · Edited by jrp
i unsoldered all the pins related to the sid module. It didn´t change a thing.
Now with everything connected again i still have:
Testtone working fine
Sid interconection test all good, but one thing i noticed is that when i play the key to set CS# low, the last digital pin i checked remains high.
According to Mios Studio all pins should be low. Don´t know if this indicates a problem or not.
MB_Sid app is saying bootloader up most of the time, sometimes no connection, sometimes application is up. When that happens i still get no output from the sid, only a steady voltage around 6v. But sometimes when i play a key that voltages steps down mybe 0.5V.
Also i see the clock signal (pin 17 of pic, pin 6 of sid) going on and off every few seconds. With the testtone app it´s steady.
Supply voltages is 5v and stable.