Jump to content

loziniak2

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by loziniak2

  1. It seems Microchip doesn't distribute samples to Poland :-/ and I'd also rather like to buy some replacement in my country than buy 24LC512 abroad and pay for international shipping. BTW, I think I found a place to buy 24LC512s, but knowing alternatives would be good.

    And Atmels have a big advantage - they are almost twice cheaper.

    So, If anybody knew if any of these two will fit, please let me (or anybody who would be interested) know.

    cheers

    Maciek

  2. Hello.

    I'm going to create banksticks module for my seq3 (finally!). But I can't find Microchip's 24LC512 chips in DIP8 enclosure. But I managed to find these two ICs:

    24LC1025 (Microchip's 8x128kb chip, http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en024636 )

    AT24C512B (Atmel's 8x64kb, with 3 address pins, http://www.atmel.com/dyn/products/product_card.asp?part_id=3782)

    Could any of them fit in place of 24LC512?

    cheers

    Maciek

  3. Niby jest, ale z tego co zrozumialem to nie wysylaja do Polski... No i jak wybieram probke, to zamowiona ilosc wyskakuje 1. Czy to znaczy 1 chip, czy 1 tubka?

  4. Hello. I've noticed a strange track buttons behaviour. When I click TRACK2 buttton just after a power-up, the track changes, but when I change back to TRACK1 and again TRACK2, buttons behavior changes and now I can only "checkbox" tracks, not change it, and I cannot "uncheck" track 1. The result is that I havee track1 checked all the time, and I can add any combination of other tracks in group.

    Suprisingly, only TRACK1 button behaves strange. The rest works just as described in manual (click to select, hold to select multiple), so when after a power-up I select any other track and NOT select track 1, everything is fine...

    Is it a kind of bug, or is it something wrong with my hardware? I had seq3.4a firmware earlier, with the same effect...

  5. To jeszcze jedno pytanko ode mnie :-) Macie mo?e namierzone gdzie? w kraju miejsce gdzie mo?na kupi? banksticki? Konkretnie chodzi mi o 24LC512 microchipa, w obudowie któr? da?oby si? jako? wykorzysta? "cha?upniczo"? Najch?tniej DIP albo SOJ. Szuka?em szuka?em i nie mog? znale??... A mo?e czym? to mo?na zast?pi??

  6. Hehe now I'd rather like more to play it than to paint it ;-) But yes, it's my plan - will spray it, probably yellow (like these yellow buttons), dark gray is also an idea, I'll consider it ;-) I'm glad you like it.

  7. First steps done! Baby is walking like a hurricane ;-) There are some issues to fix, and not everything is finished, but it already speaks to my Electribe. Now I'm thinking about a name...

    cheers :-)

    Zdj?cie042_s.jpg

    Zdj?cie043_s.jpg

    Zdj?cie042_s.jpg

    Zdj?cie043_s.jpg

  8. Thanks for your warm words :-) The PCBs were etched by my friend, he's got all necessary chemicals, tools and knowledge. He also helped me to program the PIC, the rest is mine - drilling holes, soldering, designing...

    I don't have many new things to show, because I'm waiting for my front panel, because it's the main element to fit others to. Btw, I'm very happy, because I found a workshop here in Warsaw that will laser-cut the panel, a few internal parts, and do powder-coating of panel, all for less than 20 euro.

    In the meantime, inspired by Sasha http://www.midibox.org/forum/index.php/topic,12941.0.html, I repaired my Roland D-5. I changed all microswitches which had some beer or coffee in them and were getting stuck, exchanged damaged 3rd octave of rubber contacts with good 1st octave, and cleaned all the mess that was inside. I could tell the nutrition habits of previous owner from the content of synth's case ;-)

    greets

    Maciek

  9. There is my front panel design - a png picture and a dxf project made in QCad (http://www.ribbonsoft.com/qcad.html). Maybe it will be of some use for someone.

    Blue lines are holes in panel, which will be CNC-cut. Yellow ones are project of pcbs. And the brown are contours of parts.

    The buttons are (from left to right and top to bottom):

    - "all" and "fast" - these will be frequently used I think so I put them easily accessible by left hand.

    - 4 tracks and 4 groups

    - 3 layers and 3 triggers

    - rew/stop/play/pause/ffwd

    - led bpm display together with beat and midi tx leds

    - datawheel

    - two 2x40 lcds

    - 16 encoders with switch functions (left to right: mute, solo, pattern, song, f1, f2, f3, f4, exit, select, 2x not assigned, scrub, metronome, menu, edit), 3mm leds next to them

    - 16 step switches with standard menu functions, the one in center is 1-16/17-32 view switch.

    4567_panel_2048_png54f0e3d985772fe7bddf7

    panel.dxf.zip

    4567_panel_2048_png54f0e3d985772fe7bddf7

    panel.dxf.zip

  10. Hi all!

    In January I started to build my own seq v3.4. I thought I'll post some info / pictures / files of it, to contribute something, and maybe get some feedback. And I just love to watch others' equipment being built (greetz to Sasha, Gridracer and many others), so I hope someone could enjoy mine too :-)

    I'm building it entirely of parts available locally (posting from USA is far too expensive, and it seemed like challenge to me. Almost everything I need is available here in Poland, the only thing that I didn't manage to find till now is 512kb banksticks in DIP package, but I hope it'll happen at some time...

    I'm going to use a Commodore 64C's case. Maybe I'll build a SID midibox one day using it's chip. I'm planning to rearrange buttons a little, so I can fit everything into the 132.5x400mm front panel. Main difference is I'm using my encoders' "switch" function to get rid of one row of switches. The details will follow.

    The whole welding / pcb / electronics mess is a new thing for me, so I got in touch with one guy who studied and works as an electronic engineer, so he helped me a lot - chose welding iron, recommended some places to buy parts, etched pcbs, and programmed the PIC chip (there were some problems because wi were using non-midibox programmer, see this thread: http://www.midibox.org/forum/index.php/topic,13008.0.html). Great thanks to Grzesiek!

    Ok, so that's for introduction, if I'll recall some more facts, I'll keep posting. Now the pictures :-)

  11. Sorry I didn't follow your link. You've now mentioned this thread in two others, one of them you posted in right before you posted that link, I (ass)u(me)d you were talking about that one.

    The threads:

    http://www.google.com.au/search?hl=en&as_q=thread+hijacking

    Whole idea isn't new, but I didn't know it has a name! I didn't mean to hijack any thread, if I've done that, sorry :-) All that links were intended to redirect people to similar threads, saving someone from lots of searching. Anyway if anything is still wrong, please PM me :-)

    now let's see what my friend says about his burner, maybe this will give us some new ideas.

    BTW, have a nice day :-)

  12. Sadly, 'when you bought it' does not always relate to 'when it was made'. What revision is it?

    Edit: sorry my bad - you said produced not bought. It's probably fine... check the revision anyway, can't hurt :)

    Hmmm are these little letters in circle right to the model number a revision number? then it's "e3". and the lower line reads "0833932". Anyway, isn't eusart bug all about midi data going in both directions? for now I only get the data from core, don't send any.

    I wonder if your friend used HVP mode?

    If I recall well and get the idea what we are talking about, he was using FS mode (it's full speed right?). Or maybe HighSpeed... something similar for sure. Should that be HVP?

    I saw you post in that other thread. it's good to team up, but be careful not to hijack :)

    I'm not sure what thread you're talking about... and hijacking what?

  13. Hi!

    Thanks for answer, and for moving my post to proper location.

    I searched through the site, and I gound info that ID can be changed by IC Prog. But unfortunately it doesn't have my version of pic on the list :-(.

    I checked the .hex file my friend and I were burning on PIC, but it seems that the ID is exctly what I want - 0000000000000000 (screenshot attached). Also in source code of bootloader all options are set to 0 I loaded the bootloader_v1_2b_pic18f4620.hex file into IC-Prog and selected few pic18s - because there were no pic18f4620, I tried a few others - everywhere ID was 0. And from what I found out, this is correct - I use standard MIDI, 2x40 character lcds and I don't want to chain multiple midiboxes. So it seems that it's not the matter of ID.

    But I don't have a midibox pic burner, so I'm not sure if I can use winpic800 with my friend's programmer. We'll see what we can do. Maybe the default settings from winpic800 will work with mplab.

    But still, if anyone knew something about the problem, please let me know.

    cheers :-)

    Maciek

    4531_ICprog_gif205ad6930abe2d1c485726579

    4531_ICprog_gif205ad6930abe2d1c485726579

  14. just found QCad: http://www.ribbonsoft.com/qcad.html

    It's a commercial product (25 $), but the source is GPL'ed.

    Anyone ever tried this?

    Yes, I'm giving it a try. These are my first steps in CAD, but I like to learn new things :-) From what I know, community (GPL) version is fully functional. except few things:

    Note that the community edition does not contain the scripting module or polyline support

    from: http://www.ribbonsoft.com/qcad_downloads.html

    I have few problems with it, but generally it's not hard to use when you learn some basics.

  15. Hello.

    I suppose I have a similar problem. The difference is that in midi monitor of MIOS studio I get:

    0000000-350614 ms | [80 78 00] Channel 1: Note Off C9 velocity: 0
    0000000-350612 ms | [80 00 00] Channel 1: Note Off C-1 velocity: 0
    0000000-350609 ms | [F8] Timing clock
    0000000-350608 ms | [F8] Timing clock
    0000000-350607 ms | [80 00 00] Channel 1: Note Off C-1 velocity: 0
    0000000-350605 ms | [F8] Timing clock
    0000000-350604 ms | [F8] Timing clock

    And it's happening every ~8 seconds, not every 2s.

    My core v3 went through a midi troubleshooting flawlessly (except bad polarization of midi in and out, which is now fixed). The bootloader was burned on PIC by my friend, using standard burner (not the one from ucapps) and MPLAB from Microchip. We couldn't find such information as:

    1. How to set the ID of the core?

    2. My friend said he needed something as "fuse bits"... I'm a complete noob, but he said that this is essential when you want to program PICs.

    3. Also he said there should be some information about timing during programming (this is how I understood this) - whether it's "full speed" or something different.

    4. For me the information about polarization of midi sockets is unclear. Everywhere on the schematics there it's described as "rear view" - but it's not clear if it's rear view of the socket, or rear view of the midi device after assembling (assuming you have midi sockets on back of your device, rear view of device is in fact front view of a socket!). I think it should be more clear described.

    Ok, so what am I supposed to do now? Is there easier solution than to burn the bootloader again? If not, how to set the ID properly and where can I find info about these fuse bits and other stuff?

    thanks in advance

    Maciek

    PS. For the curious ones, I took a photo of my cutie (sorry for a quality):

    zdjcie019nd2.th.jpg

  16. Witam :-)

    W styczniu zabralem sie za skladanie swojego SEQ3. Jak na razie mam zlutowane 3xDIN4 i DOUT4 - jak na pierwsze zlutowane plytki drukowane mysle ze jest niezle, szczegolnie ze plytki wytrawial mi znajomy, a dziurki wiercilem sam :-)

    Swoje projekty skladaliscie z gotowych zestawow, czy sami kupowaliscie czesci w Polsce?

    pozdrowienia

    Maciek

×
×
  • Create New...