Artesia Posted January 20, 2006 Report Share Posted January 20, 2006 Okay... having some fun getting a Din module chain on a midibox seq to accept more than the contorl dial & first chips worth of buttons. also on further investigation with debugging app ...theres a huge amount of ain signals being received by a Ain module that does not exhist... Note, have installed power caps & am fairly sure that all the tie down resistors & soldering joints are in place as they should be.. See here for the project in question: ( http://www.midibox.org/forum/index.php?topic=5818.0 )The nearest problem i could find to this; is the one below mentioning Ain jitter/noise.. however this is with a module present... ( http://www.midibox.org/forum/index.php?topic=5486.0 )To go a little firther into the problem; the first chip on the Din seems to accept triggers fine; however the second one sends the unit cycling through all the menus on any button press... any more chips up the chain & no response... Something to do with the serial chaining of chips i figure...Have also btw tried different pics, on different boards and observed the same issue with random Ain signals being sent en-masse ...anyone have any idea what might cause this freekery ? ..im really quite puzzled Quote Link to comment Share on other sites More sharing options...
raphael Posted January 20, 2006 Report Share Posted January 20, 2006 Okay... having some fun getting a Din module chain on a midibox seq to accept more than the contorl dial & first chips worth of buttons. also on further investigation with debugging app ...theres a huge amount of ain signals being received by a Ain module that does not exhist... Very strange. The SEQ does not support AIN. In main.asm DEFAULT_NUMBER_POTS is set to 0. And MIOS_AIN_NumberSet disables the AIN module of MIOS if it's called with 0 pots (More exact: The timer disables itself like expained in the MIOS sources). So If you have made no changes to the SEQ application, this seems to be a hardware issue.To go a little firther into the problem; the first chip on the Din seems to accept triggers fine; however the second one sends the unit cycling through all the menus on any button press... any more chips up the chain & no response... Something to do with the serial chaining of chips i figure...Yave you checked the connection from pin 10 (SER) of chip 1,2,... to pin 9 (QH) of the following chip? Have you tested this with another DIN module? Quote Link to comment Share on other sites More sharing options...
Artesia Posted January 20, 2006 Author Report Share Posted January 20, 2006 Hi, Thanks...Tried switching Din modules ..same thing unfortunately...Also the Phantom Ain signals are only transmitted via midi when using the "ain64_din128_dout128_v1_3.zip" diagnostic tool...Here is a sample of what it sends ..and the following pic is what appears on the screen 004B2C3E 1 -- B1 36 37 2 --- Control Change 004B2C3F 1 -- B1 06 37 2 --- CC: Data Entry MSB 004B2C41 1 -- B1 07 36 2 --- CC: Volume 004B2C43 1 -- B1 0E 38 2 --- Control Change 004B2C44 1 -- B1 10 37 2 --- Control Change 004B2C46 1 -- B1 12 38 2 --- Control Change 004B2C47 1 -- B1 14 37 2 --- Control Change 004B2C49 1 -- B1 37 38 2 --- Control Change 004B2C4C 1 -- B1 07 38 2 --- CC: Volume 004B2C4F 1 -- B1 37 37 2 --- Control Change 004B2C50 1 -- B1 11 37 2 --- Control Change 004B2C52 1 -- B1 13 37 2 --- Control Change 004B2C54 1 -- B1 11 38 2 --- Control Change 004B2C59 1 -- B1 36 38 2 --- Control Change 004B2C5B 1 -- B1 3A 38 2 --- Control Change 004B2C5D 1 -- B1 3A 36 2 --- Control Change 004B2C5F 1 -- B1 3A 37 2 --- Control Change 004B2C61 1 -- B1 0D 38 2 --- Control Change 004B2C63 1 -- B1 0F 38 2 --- Control Change 004B2C64 1 -- B1 15 38 2 --- CC: 21 (E-MU) 004B2C69 1 -- B1 2E 37 2 --- Control Change Quote Link to comment Share on other sites More sharing options...
raphael Posted January 20, 2006 Report Share Posted January 20, 2006 Also the Phantom Ain signals are only transmitted via midi when using the "ain64_din128_dout128_v1_3.zip" diagnostic tool...Here is a sample of what it sends ..and the following pic is what appears on the screenThats clear. See AIN_NUMBER_INPUTS in main.h and change it to 0 if you have no AIN connected.(No idea for the DIN issue, sorry!) Quote Link to comment Share on other sites More sharing options...
Artesia Posted January 20, 2006 Author Report Share Posted January 20, 2006 ok.. thanks :)giving compiling that a try.. however im figuring that these two anomalys maybe related at the hardware level ..and telling the pic to ignore the ain at the software level may acheive very little... will see.. Quote Link to comment Share on other sites More sharing options...
TK. Posted January 20, 2006 Report Share Posted January 20, 2006 If you would read my replies, propably you wouldn't run into such problems. Not without any reason, I gave you the individual suggestion to use the MIDIO128 application for testing.In the meantime it should be very clearly stated at my website, that the software will send random MIDI events when the analog inputs are not connected to ground. This is especially mentioned in the new webpage I updated after your request for more detailed informations!-> http://www.ucapps.de/mios_bootstrap_newbies.htmlSearch for "Additional Hints"Of course, it's a lot of information, and I don't assume that anybody will understand all terms immediately.But please: if you notice problems, read the relevant HowTo/Troubleshooting pages and check if there is something which could match with the effects you've noticed. This will help you to solve the problem much faster than waiting for an answer at the forum, and maybe by this way you will also get some useful hints which could be useful for upcoming troubleshooting.Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Artesia Posted January 20, 2006 Author Report Share Posted January 20, 2006 okay, sorry there.. had been getting messages mixed up & failed to read everything available..it's an awful lot to get to grips with first time round :) Quote Link to comment Share on other sites More sharing options...
Artesia Posted January 21, 2006 Author Report Share Posted January 21, 2006 Hi,All sorted...Latched down j6/7 & neglected to remember that the chip has its own onboard DAC/AIN section..Many hours of trouble shooting the ain boards pointed the problem down to some incomplete pcb traces on some diy boards made with a friends etching kit ...and afew chips which came out of the surplus pile & where not tested properly..A Quick Errata & some check points that sprang to mind:afew symptoms encountered with interface debugging..1: Random AIN data during testing as above; was due to neglecting to earth the PIC chips own AIN section; as provided by J7.Linking all the pins togeather on J7; -EXCEPT- the 2nd pin (vd/+5v) (as viewed when the notch on the pic is at the 'top').2: Random DIN data transmitted when a 'switch' is pressed... most likely cause is faulty chip; change & see what happens - otherwise check soldering & conncetions around linked chip.3: No button presses received.. Check connections & soldering; however if it occurs along an DIN board chain whereby some chips are working ok; but the last one is exhibiting symptoms as seen in '2' ..then this chip is stopping any good singlas working their way down the line.4: Lights Driven by DOUT board behave erratically/ flicker.. as always.. check connections.However also note that it is vital for reliable opperation - that some capacitors are added onto the power supply rail of the board. use one 47-470uf on the main input & as mentioned in the AIN construction article at ucapps.de a 100nf cap by each chip ideally.5: Two or more buttons trigger the same number on testing...usually just two connection points that are soldered togeather/ touching. Though watch out for any small loose touching wire filaments or tiny splashes at the base of the connection points, which can easily esape detection. 6: constant random signals / afew connections on a DIN board not triggering...Pay particular attention to Resistor (& chip socket) soldering... though all else fails.. try new chip.7: Some LED's are brighter or dimmer than others.Check how much current your leds can handle (10-30ma is the typical range). and either work out safe resistances with abit of math.. or go for trial and error.. replacing the resistor that drives each concerned led with a larger resistance for less brigtness ...and when decreasing the resistor value to gain brightness; be sure to place a multimeter in series with the LED and make sure that the resistance value used does not exceed the LED's max specifyed current (otherwise it'll change colour (often!) & burn out really quick)8: make sure that whatever you are using to power everything (ie the measily 1amp reg & diode bridge on the cpu board) are sutibly upgraded (or other supply built into case) to handle all the power used to drive everything. 1 amp regs & connected in parallel to add up the current handling.. however note that for more than 500ma current handling and they get very hot. they need to be bolted to a metal surface to take the heat away.. usually the case is best. however if it is steel; make sure to use a small sliver of aluminum behind the regs to hlp spread the heat out better. Always use heatsink paste to improve thermal conoductivity.8b: Make sure that whatever ultimately powers the box (wall wart power pack or transformer); that it can provide the regulation circuit with the power it needs too ! :) ...ie a 3.7v 350ma phone charger will not power a regulator circuit that needs 11-20v (12v usually best) at around 800 ma / 0.8 amps.9: Most problems are bad connections / missed wiring or components.. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.