| *** tpb has joined #timvideos | 00:00 | |
| mithro | mparuszewski: it is likely I'll be around tomorrow morning earlier, I'm going to try and make some very early meetings at work but haven't had much success doing so in the past. | 00:00 |
|---|---|---|
| ayush3504 | mithro: another thing, for the measurements, I'm not able to find any photographs of the digilent boards that have been taken from top. They're all taken from an angle that makes it impossible for me to measure that way. So the only way I see is to ask people and Digilent support. | 00:03 |
| mithro | ayush3504: I don't think the angle makes much difference | 00:03 |
| mithro | at the size, perspective doesn't make a huge difference? | 00:04 |
| ayush3504 | mithro: I don't know depends on what we consider as huge. The ratios of the sides would change unless it's a front/top view. | 00:06 |
| mithro | if you have the right dimension within +/- a couple of millimeters that should be a good start | 00:07 |
| ayush3504 | mithro: will try | 00:07 |
| mithro | ayush3504: do your best and include information on your errors | 00:08 |
| ayush3504 | mithro: yep | 00:09 |
| ayush3504 | mithro: for the bidirectional thing, how about giving it as an option, because we always have rx, tx pairs anyway and even the drivers come in pairs. Should we let it be an option to populate (or connect through wire) the board with an optional input connector? | 00:11 |
| mithro | ayush3504: so, first I think we need to think about the idea of daughterboards working stand alone, versus requiring the motherboard to work | 00:17 |
| mithro | ayush3504: if we go the route of requiring all daughterboards to work stand alone accepting RS232 input then the RX/TX for MIDI + DMX is going to require a microcontroller on the daughterboard to do the translate from RS232 to MIDI/DMX | 00:18 |
| ayush3504 | mithro: agree | 00:19 |
| mithro | ayush3504: otherwise the microcontroller could "sit inside" the FPGA | 00:19 |
| ayush3504 | mithro: RS232 to MIDI doesn't need translation | 00:19 |
| ayush3504 | mithro: IR needs, if not using the IrDA | 00:20 |
| ayush3504 | mithro: for midi<->rs232, take a look at this http://www.cinetix.de/interface/tiptrix/midipc_engl.png | 00:21 |
| mithro | ayush3504: does that actually work? IE are the voltages actually spec compliant or only "kinda works" ? | 00:23 |
| ayush3504 | mithro: the only difference is midi operates at some fixed baudrate and uses slightly different current/voltage levels | 00:23 |
| mparuszewski | mithro: I am back. :) | 00:23 |
| ayush3504 | mithro: have to check that, that's not a circuit i'm treating as final | 00:23 |
| mithro | ayush3504: okay | 00:24 |
| ayush3504 | mithro: you mentioned about midi having some other connector besides xlr-3? | 00:25 |
| mithro | be back in 5, need to reboot computer | 00:26 |
| mparuszewski | mithro: Can we talk about all things tomorrow 10pm UTC? :) I feel really tired, sitting at a computer trying not to sleep. | 00:31 |
| mithro | mparuszewski: lets try and do that, I can't guarantee I'll be around then | 00:33 |
| mparuszewski | If you have time now, we can also talk now. I thought that you are talking with ayush :) | 00:33 |
| mithro | mparuszewski: we can try and catch up tonight too | 00:34 |
| mithro | mparuszewski: when will you be back? | 00:34 |
| mithro | mparuszewski: I can multitask :), but if your tired I think it's better to post pone it | 00:36 |
| mithro | ayush3504: search for "midi sound card connector" | 00:36 |
| mithro | ayush3504: http://www.allpinouts.org/index.php/MIDI_soundcard_-_keyboard | 00:37 |
| tpb | Title: MIDI soundcard - keyboard - AllPinouts (at www.allpinouts.org) | 00:37 |
| mparuszewski | Great, thank you. :) I can talk tomorrow from 3 pm utc to 11-12 pm | 00:38 |
| ayush3504 | mithro: Ah, I know that one. I think we should not worry about the connectors in midi (and dmx) because we can solder them. I could not find any particular model of Right angled, PCB mount XLR-3 connectors that are well-stocked. So we will be manually soldering the connectors anyway. | 00:39 |
| mithro | mparuszewski: what is your timezone again? | 00:40 |
| mithro | ayush3504: the MIDI soundcard connector seems semi-standard for a PCB mountable connector? | 00:40 |
| mithro | ayush3504: would it fit on a daughterboard at the moment? | 00:40 |
| ayush3504 | mithro: No, because my daugherboard width is limited (as of now) with DB9 connector width which is 31 mm. DB15 is going to be wider for sure. | 00:41 |
| mparuszewski | +2 UTC, its 2.40 am now :) | 00:41 |
| mithro | mparuszewski: is that Warsaw? | 00:42 |
| mparuszewski | Yes | 00:42 |
| mithro | mparuszewski: 3pm utc seems to be 11pm for me, so if I'm going to catch the early meetings tomorrow I should be in bed by then | 00:43 |
| mithro | mparuszewski: lets aim for sometime between 6am (10pm your time) and 9am (1am your time) tomorrow? | 00:44 |
| mparuszewski | Ok, I will be available then for sure. :) | 00:45 |
| ayush3504 | mithro: and I added 10 mm more to the 31 mm so that we have some extra clearance (5mm each side) for the cables. There's always some extra plastic 2-3mm at the sides of the DB9 connector in cable. And there needs to be some space for using the thumbscrews. | 00:45 |
| mithro | ayush3504: how much wider would the daughter board be to fit that MIDI connector? | 00:45 |
| mithro | ayush3504: what about the good old PC parallel port? | 00:45 |
| mparuszewski | See you tomorrow, have a nice day, bye! :) | 00:46 |
| mithro | mparuszewski: sleep well! | 00:46 |
| ayush3504 | mparuszewski: bye :) | 00:47 |
| ayush3504 | mithro: parallel port? that's like 3 times a serial port | 00:47 |
| techman83 | mparuszewski: cya! | 00:47 |
| mithro | ayush3504: could we have "double width" daughterboards? | 00:48 |
| mithro | ayush3504: (IE daughter boards which cover two "slots") ? | 00:48 |
| ayush3504 | mithro: hmm, we sure can. But i wish to stick with soldering for another reason. The PCB mount connectors are more expensive than the panel mount type. | 00:49 |
| mithro | ayush3504: when you say "soldering" you mean cables from the holes to the connectors? | 00:50 |
| ayush3504 | mithro: i'm talking about connectors like these: http://www.networktechinc.com/nti/images/items/db15m-sldr.jpg | 00:50 |
| ayush3504 | mithro: these would need to be soldered to the daughtere board through a ribbon cable | 00:51 |
| mithro | ayush3504: I'm confused? | 00:51 |
| ayush3504 | mithro: so if we go with these type of connectors instead of PCB mount ones, we may not need to consider increasing width of daughterboards | 00:51 |
| ayush3504 | mithro: if you see the back pins of these connectors we need to solder wires on it. It isn't designed to be soldered on pcb. | 00:52 |
| mithro | ayush3504: okay, I think for anything apart from the XLR connectors we probably want to go PCB mount? | 00:55 |
| Joelw | Slightly less annoying than solder-type DB connectors is using IDC connectors, e.g. http://www.crystalfontz.com/backlight/db9F_2x5_ribbon_straight.jpg | 00:55 |
| ayush3504 | mithro: another point, when you panel-mount a connector, any stresses during cable connector would be handled by the chassis. But in can of PCB mount, it will be the daughterboard PCB handing the stress. If you want a PCB connector that is also fastened to the chassis it will require us to have tight tolerances of dimensions. | 00:56 |
| ayush3504 | mithro: two typos above: connector->connection, can->case | 00:58 |
| mithro | ayush3504: I think we probably still want to go the PCB mounted, we have pretty tight tolerances for the Atlys part of the case if using a model where the connectors are exposed directly rather than broken out. | 01:00 |
| mithro | ayush3504: it also gives us the option of doing non-direct by using short cables | 01:02 |
| ayush3504 | mithro: another point: the daughter board isn't directly fastened to the chassis. We're relying on the soldered headers for the mechanical support. So it's sensitive to stress. I've seen that over time, header pins can slip against their soldered joins no matter how nicely they have been soldered. | 01:03 |
| ayush3504 | mithro: yes, IDC connector looks good. I wonder if it's not too costly. | 01:03 |
| ayush3504 | thanks Joelw | 01:07 |
| Joelw | IDC connectors shouldn't be a lot more expensive, and they're a bit easier to put together - I just crimp them in a vice, which is loads faster than soldering them up. | 01:09 |
| Joelw | You can probably get them pre-made as well. | 01:10 |
| mithro | ayush3504: so, where is your table of mechanical sizes? | 01:10 |
| mithro | ayush3504: can you port your table in the serial expansion board to a spreadsheet so you can add a bunch more detail? IE We should include info on the that MIDI connector and parallel ports | 01:11 |
| ayush3504 | mithro: ok, shouldn't we use comment section for this. coz we won't be adding more rows to this. Just saying, coz I like to have things in one place | 01:14 |
| mithro | ayush3504: we will be definately be adding more rows to this | 01:14 |
| mithro | ayush3504: plus more details | 01:14 |
| ayush3504 | mithro: ok | 01:14 |
| mithro | ayush3504: again, these are "living documents" they will change / adapt / grow as we get more information | 01:15 |
| ayush3504 | mithro: ok. https://docs.google.com/spreadsheets/d/1lOAKj-r80o0KVlB-AP-42tiUY0Hg50EkQTgRwYNMilk/edit?usp=sharing | 01:16 |
| tpb | Title: Connector specifications for serial expansion board - Google Tabellen (at docs.google.com) | 01:16 |
| mithro | ayush3504: please fill in the details | 01:19 |
| ayush3504 | mithro: sure, why do we need rj12? | 01:20 |
| mithro | ayush3504: it is an alternative option for RS422/RS485 | 01:21 |
| mithro | ayush3504: you should include all the different connector options in that spreadsheet too | 01:21 |
| ayush3504 | mithro: have you seen it used somewhere? | 01:21 |
| mithro | ayush3504: IE the PCB mount verses IDC connector verses wiring | 01:22 |
| mithro | ayush3504: not really, but it can't hurt to have the information in the spreadsheet | 01:22 |
| ayush3504 | mithro: there's also a spreadsheet for other components, make sure we don't have to duplicate stuff in both of the spreadsheets https://docs.google.com/spreadsheets/d/1aRptrpgD-d-2AC1fpn9-YvU7Zk_CA3oa4D0pKFP3bTM/edit#gid=0 | 01:25 |
| tpb | Title: Cost spreadsheet for Serial Expansion Board - Google Tabellen (at docs.google.com) | 01:25 |
| mithro | ayush3504: great! You could combined the two spreadsheets if you want and just use two different sheets | 01:26 |
| ayush3504 | mithro: ^ i will be filling this in detail when I start doing the schematics. | 01:27 |
| ayush3504 | mithro: good idea, I forget about using sheets every time | 01:28 |
| ayush3504 | mithro: GPIO and parallel ports look very similar, should we skip one of them or combine maybe? | 01:29 |
| mithro | ayush3504: no, too much information is better then too little information | 01:29 |
| ayush3504 | mithro: didn't get the context | 01:30 |
| ayush3504 | mithro: i was talking about combining the daughter boards, we can get a parallel port to work as gpio right? | 01:32 |
| mithro | ayush3504: I think they might be similar but the parallel port is going to be too wide I think | 01:32 |
| ayush3504 | mithro: what would you be using parallel port for? because it's too wide | 01:32 |
| mithro | ayush3504: GPIO type things, but as I said we might want double width daughterboards | 01:33 |
| ayush3504 | mithro: for GPIO type things I think the screw headers are more convenient | 01:34 |
| mithro | ayush3504: possibly but I don't want to rule out the parallel header just yet. | 01:35 |
| ayush3504 | mithro: anything that works for standard parallel port may not work either, because it's all emulated through a serial port i guess. | 01:36 |
| mithro | ayush3504: mayb e | 01:40 |
| shenki | mithro: re: fx2, yeah, if i had infinite amounts of free time i'd re-write the firmware on a cortex m0 | 01:46 |
| shenki | ayush3504: hey | 01:46 |
| shenki | ayush3504: mithro said you're looking through the linux usb serial driver | 01:46 |
| shenki | ayush3504: what are you trying to figure out? | 01:46 |
| ayush3504 | shenki: hey :) | 01:46 |
| mithro | ayush3504 / shenki: we need to figure out if the usb-serial driver in Linux already supports multiple serial ports on a single end point | 01:47 |
| shenki | ok | 01:47 |
| mithro | shenki: I'd like ayush3504 to look into it and ask you questions about it | 01:49 |
| shenki | im trying to figure out what that would look like | 01:50 |
| ayush3504 | shenki: we don't seem to have much endpoints on the FX2, so we want some way to multiplex these serial ports over a pair of In/Out end-ponts | 01:51 |
| mithro | shenki: I'm guessing the data we send to the USB controller with some type of "send to this actual port" prefix | 01:51 |
| shenki | ok | 01:52 |
| shenki | we shouldn't be looking to create yet another usb serial device. usb cdc is the way to go | 01:53 |
| mithro | shenki: usb-cdc doesn't support that idea | 01:55 |
| ayush3504 | shenki: yes but the usb cdc as specified in specs takes 3 endpoints - Int In and Bulk In/Out and we don't have that many left on fx2. So we're looking for a workaround. | 01:55 |
| mithro | shenki: so I think we want see if there is a device supported by the usb-serial driver that we could emulate | 01:56 |
| ayush3504 | shenki: like this one - https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/serial/io_edgeport.c | 01:56 |
| tpb | Title: kernel/git/torvalds/linux.git - Linux kernel source tree (at git.kernel.org) | 01:56 |
| mithro | ayush3504: how is those mechanical information going? | 02:00 |
| ayush3504 | my net died a few minutes ago. will be back in a while. | 02:04 |
| mithro | ayush3504: Google Docs have offline support if you enable it | 02:04 |
| ayush3504 | yep thanks, but i need to surf web to fill in the info | 02:05 |
| *** CarlFK has quit IRC | 02:11 | |
| CARAM_ | mithro: I have flumotion docker image mostly done if you'd like to take a look or give feedback | 02:17 |
| CARAM_ | just some minor stuff left for watchdog / register | 02:18 |
| mithro | CARAM_: I probably won't get a chance to review it until the weekend at the earliest | 02:18 |
| mithro | CARAM_: so you should put instructions on your blog and then link it here | 02:18 |
| mithro | CarlFK might give it a try | 02:19 |
| mithro | aps-sids might also be another person to look at it (he is doing the flumotion porting to latest gstreamer) | 02:19 |
| CARAM_ | mithro: sounds good. | 02:23 |
| CARAM_ | here are the current instructions: http://mstritzi.nfshost.com/blog/index.php/posts/running-a-flumotion-docker-image | 02:55 |
| tpb | Title: Running a Flumotion Docker Image - Max Stritzinger (at mstritzi.nfshost.com) | 02:55 |
| CARAM_ | as stated, the current use of pushconfigs is undesirable, so my next step is to cut that out | 02:56 |
| *** mparuszewski has quit IRC | 03:11 | |
| *** CarlFK has joined #timvideos | 03:34 | |
| *** ChanServ sets mode: +v CarlFK | 03:34 | |
| *** Niharika has joined #timvideos | 04:35 | |
| mithro | ayush3504: how is it going? | 05:31 |
| ayush3504 | mithro: just signed in now from another place | 05:31 |
| ayush3504 | mithro: can we talk about the daughter board stacking idea? | 05:32 |
| mithro | daughter board stacking idea? | 05:32 |
| ayush3504 | mithro: you mentioned about stacking the daughterboard layout on the slot? | 05:32 |
| mithro | ayush3504: you mean including the idea of including RS232 daughterboard on the mainboard so it can be used without any daughterboards? | 05:33 |
| ayush3504 | mithro: there wasn't any daughterboard for rs232, it's was always there as a default option. | 05:34 |
| mithro | ayush3504: we talked about this last night, we should design rs232 as if it was a daughter board, then just copy the daughterboard onto what would have been the blank space for the daughter boards | 05:35 |
| ayush3504 | mithro: but then, will have to send rx tx ttl signals straightaway to the db9 footprint. So db9 footprint wouldn't make sense | 05:37 |
| mithro | ayush3504: we also talked about that - the idea of just having TTL signal into the daughter boards and making the daughterboards compatible with TTL or RS232 signals | 05:38 |
| ayush3504 | mithro: and that wasn't clear to me, and still isn't. so you said you'll make a diagram to explain | 05:39 |
| mithro | ayush3504: what is not clear? The signals from the board motherboard to the daughterboards being TTL? | 05:40 |
| mithro | ayush3504: that also solves the duplicate RS232 drivers | 05:40 |
| ayush3504 | mithro: i have an easier solution to the duplicate rs232 driver problem, it's just to short the rx, tx pins through jumper resistors | 05:41 |
| ayush3504 | mithro: with the line driver ic pads unpopulated | 05:41 |
| mithro | ayush3504: but then the motherboard needs to be modified depending on the daughterboards which are connected | 05:42 |
| mithro | ayush3504: special cases are bad | 05:42 |
| ayush3504 | mithro: but when sending ttl to the daughter board it doesn't make sense to have DB9 connectors. And I don't know how to make the daughterboard compatible with rs232 as well as ttl. | 05:43 |
| ayush3504 | mithro: ^ using the same rx. tx lines | 05:44 |
| *** mparuszewski has joined #timvideos | 05:44 | |
| ayush3504 | mithro: can we have a dedicated coupling header on the daughter board to to accept ttl signals? and leave the db9 to accept rs232? | 05:46 |
| mithro | ayush3504: that is an option | 05:46 |
| mithro | ayush3504: another option is to do some research and figure out the RS232 to TTL conversion methods | 05:46 |
| mithro | ayush3504: you should be able to think up a circuit to do the 12V -> 5V and -12V -> 0V | 05:51 |
| ayush3504 | mithro: yes but doesn't the line driver do this? | 05:51 |
| ayush3504 | mithro: my concern is supporting TTL and RS232 logic levels on the same pins | 05:51 |
| ayush3504 | mithro: which looks difficult and optional provided we can use another header for TTL stuff. | 05:52 |
| ayush3504 | mithro: i don't see any harm in putting a dedicated ttl header. and that solves the issue of customizing motherboard | 05:54 |
| mithro | ayush3504: putting a dedicated ttl header is an option, but how do you keep your daughterboards should also work independently? | 05:55 |
| ayush3504 | ayush3504: by populating DB9 female and line drivers in the daughterboard. | 05:55 |
| ayush3504 | mithro: e.g. for a rs485 daughter board the daughterboard would have RS232 port>rs232 line-driver>-->rs485 line-driver>rj45 jack> | 05:58 |
| ayush3504 | mithro: between the two line drivers the signals are ttl and will be also connected to the ttl header | 05:58 |
| ayush3504 | mithro: so if we use the daughterbaord with motherboard, we can skip the rs232 port and line driver | 05:59 |
| mithro | ayush3504: that sounds reasonable | 05:59 |
| mithro | ayush3504: so a "rs232" daughterboard would be just a TTL->RS232 driver then? | 06:00 |
| ayush3504 | mithro: yes, that can be an option. or you can just populate a DB9 male on the front footprint on motherboard and populate the line driver on the motherboard | 06:01 |
| ayush3504 | mithro: by front footprint i mean the one that is outwards | 06:02 |
| mithro | do any of the daughterboards need the line driver apart from the rs232? | 06:03 |
| ayush3504 | mithro: midi | 06:04 |
| ayush3504 | mithro: ir, if you use IrDA protocol | 06:04 |
| ayush3504 | mithro: err , no not the ir | 06:04 |
| mithro | ayush3504: this information should be in connecter specification | 06:04 |
| mithro | ayush3504: as I see at the moment, it's rs232 and midi? | 06:05 |
| mithro | ayush3504: so it seems better to think of them as part of the daughterboards then? | 06:05 |
| ayush3504 | mithro: you mean combining these two? | 06:06 |
| mithro | ayush3504: no | 06:07 |
| ayush3504 | mithro: didn't get you | 06:07 |
| mithro | ayush3504: I'm saying we shift the rs232 line driver to be part of daughter boards rather then the main board | 06:08 |
| ayush3504 | mithro: ok, got it. makes sense | 06:09 |
| mithro | ayush3504: once we have the daughterboards / motherboards all figured out, we can then look at how to make it so "empty" slots can be directly populated with rs232 | 06:09 |
| ayush3504 | mithro: for the empty space we can just clone in one of the daughter board layouts, so that will be like a default daughterboard, which is preferable rs232 | 06:12 |
| mithro | ayush3504: exactly, that is what I have been banging on about | 06:12 |
| ayush3504 | mithro: :P | 06:12 |
| ayush3504 | mithro: instead of having autodetection for each of these daughter boards, can we just program the EEPROM which we'll be using for serial expansion board? | 06:15 |
| mithro | ayush3504: that is an open question | 06:16 |
| mithro | ayush3504: how many daughter boards have we got now? | 06:16 |
| ayush3504 | mithro: 8 including rs232 and parallel port and gpio | 06:17 |
| mithro | ayush3504: with the TTL design, can we do the RC style auto-detection? | 06:17 |
| mithro | how accurate would we need to be? | 06:18 |
| mithro | if we wanted to make sure we could have up to 32 different daughter boards? | 06:18 |
| ayush3504 | mithro: yes, that'll work but why do we need it if we can program our customization in the eeprom.mcu in serial expansion board | 06:18 |
| *** wanig has quit IRC | 06:19 | |
| *** techman83 has quit IRC | 06:19 | |
| mithro | ayush3504: I'm talking about the daughterboards on the serial board, what if someone changes a daughterboard and forgets to reprogram the EEPROM? | 06:20 |
| *** wanig has joined #timvideos | 06:23 | |
| *** techman83 has joined #timvideos | 06:23 | |
| *** kornbluth.freenode.net sets mode: +v techman83 | 06:23 | |
| ayush3504 | mithro: changing daughter boards won't be so easy enough to forget though since we'll be soldering them? :p | 06:25 |
| mithro | ayush3504: are we? Having dynamically swappable seems like a good option to preserve? | 06:26 |
| ayush3504 | mithro: umm, okay | 06:26 |
| mithro | ayush3504: we may want to go the solder route, but I don't think we can make that decision at the moment? | 06:27 |
| ayush3504 | mithro: well in a future design we can have daughter boards / expansion boards that you can slide in and out, would look kind of fancy ;) | 06:29 |
| mithro | ayush3504: the 2.54mm male headers have female versions | 06:29 |
| ayush3504 | mithro: yes they have, but i recommended soldering to give some mechanical strength | 06:30 |
| mithro | ayush3504: so how many pins are you looking at for the interface to daughter boards now? | 06:31 |
| ayush3504 | mithro: 7 pins for the DB9, 10 pins on TTL header - rx,tx,rtc,cts,dsr,dtr,detect,5v_iso,gnd,NC | 06:32 |
| mithro | NC ? | 06:35 |
| ayush3504 | mithro: not connected | 06:35 |
| mithro | detect is? | 06:35 |
| ayush3504 | mithro: rc | 06:35 |
| mithro | ayush3504: which ones are for rs232, which ones are extra? | 06:35 |
| ayush3504 | mithro: the first 6 of the ttl ones and ground | 06:36 |
| mithro | ayush3504: so detect is for the auto-detect of the daughterboards? | 06:36 |
| ayush3504 | mithro: yes | 06:36 |
| mithro | ayush3504: okay, so how many daughterboards could you have with that? | 06:37 |
| ayush3504 | mithro: more than 32 easily i guess | 06:37 |
| mithro | how many pins on the VHDCI connector? | 06:38 |
| ayush3504 | mithro: i have to see whether the logic level thresholds change with conditions like temperature | 06:38 |
| ayush3504 | mithro: that's a good question. I had posted a question for you in the snippets - do you want h/w control in all of the ports? | 06:39 |
| mithro | ayush3504: lets start with yes and then go back if we don't think we have enough ports | 06:40 |
| ayush3504 | for each hardware control supported port, we'll need 6 pins | 06:40 |
| ayush3504 | 2 pins for the I2C | 06:40 |
| ayush3504 | 6 h/w controlled ports i guess | 06:40 |
| ayush3504 | h/w flow controlled* | 06:40 |
| mithro | ayush3504: so? (VHDCI pins - 2) / (6 + ??) == XXX ports? | 06:43 |
| mithro | this should all be in your spreadsheet | 06:43 |
| ayush3504 | mithro: sure | 06:46 |
| ayush3504 | mithro: you may want to review the flow control heading in my document https://docs.google.com/document/d/1xIML-TEmq--nJXuKta11v-6DK-Rkrs5hGJjJTQXrQUg/edit#heading=h.r91870d6fq3n | 06:46 |
| tpb | Title: Serial Expansion board design - Google Docs (at docs.google.com) | 06:46 |
| mithro | ayush3504: I don't think any of the stuff raised there is that relavent at the moment | 06:47 |
| mithro | ayush3504: it will become relevant if we don't think we have enough ports | 06:47 |
| ayush3504 | mithro: ok | 06:47 |
| ayush3504 | mithro: on the PIC18F which pins should I be using | 06:50 |
| mithro | ayush3504: don't worry about the PIC for now | 06:50 |
| ayush3504 | mithro: it's a part of schematic right? | 06:50 |
| mithro | yes, but we'll get back to that in a second | 06:51 |
| mithro | ayush3504: I'm going to disappear in about 40ish minutes | 06:53 |
| ayush3504 | mithro: oh okay | 06:54 |
| ayush3504 | mithro: any info about the IR receiver? | 06:57 |
| mithro | ayush3504: the IR receiver is really just GPIO with IR LED / Receiver connected to two pins right? | 07:00 |
| ayush3504 | mithro: yes, but why do you need IR LED? | 07:01 |
| mithro | ayush3504: for remotes possibly, or maybe controlling TV / displays or other things | 07:02 |
| ayush3504 | mithro: for that well be needing ir receivers right, not leds | 07:03 |
| mithro | IR LED is for sending, IR receiver is for receiving, right? | 07:03 |
| ayush3504 | mithro: yep, so what will we send? | 07:04 |
| mithro | --> maybe controlling TV / displays or other things (pretending to be a remote) | 07:04 |
| ayush3504 | mithro: HDMI2USB? | 07:04 |
| mithro | ayush3504: say the HDMI2USB is connected to a cable box | 07:04 |
| mithro | ayush3504: IR would be useful to cause the cable box to change channel | 07:05 |
| ayush3504 | mithro: oh ok, and is it worth having a separate dboard for IR? coz we can do it with gpio? | 07:05 |
| mithro | ayush3504: maybe not | 07:06 |
| ayush3504 | mithro: should i rule out IR then? | 07:08 |
| mithro | ayush3504: I think it would still be useful to have, as we have it on the production board | 07:09 |
| ayush3504 | mithro: the only practical difference i see is using individual wires instead of a trs connector (for receivier) | 07:10 |
| mithro | and IR receiver generally needs an amplifier (unless it's built into the IR receiver) | 07:10 |
| ayush3504 | it;s built into it | 07:10 |
| mithro | okay | 07:11 |
| ayush3504 | it's three pins, Vs, Gnd, Dout | 07:11 |
| mithro | it could be a very simple daughter board :) | 07:11 |
| mithro | the more interesting part is how it mechanically would connect to a faceplate | 07:12 |
| ayush3504 | mithro: do you plan to integrate the IR receiver on the dboard itself? | 07:12 |
| mithro | ayush3504: ? | 07:12 |
| ayush3504 | mithro: i'm assuming that the IR dboard will have connectors and the LED, Receiver will be connected through some cable? | 07:13 |
| mithro | ayush3504: I was assuming they would be mounted on the PCB | 07:14 |
| ayush3504 | mithro: IR receivers on market are that way | 07:14 |
| ayush3504 | mithro: http://p.globalsources.com/IMAGES/PDT/B1031211991/IR-Receiver-Cable.jpg | 07:15 |
| mithro | ayush3504: that is another option, then the PCB would need a 2.5mm header | 07:16 |
| ayush3504 | mithro: no they use 3.5mm trs jack, and that's pretty standard | 07:16 |
| mithro | ayush3504: sorry, hear 3.5mm jack | 07:17 |
| ayush3504 | mithro: a 2.54 mm screw header could be used for the LED, since there's no standard connector | 07:17 |
| mithro | ayush3504: maybe | 07:18 |
| mithro | ayush3504: so you still need to fill in all this information into the spreadsheet | 07:18 |
| mithro | ayush3504: you've also not mentioned how many serial ports we can get with this current model | 07:18 |
| ayush3504 | mithro: and for the dboards with screw header, we would probably want them to be hanging a bit outside the case outline so that we can make connections without opening the case. | 07:19 |
| mithro | ayush3504: agreed | 07:22 |
| mithro | ayush3504: do you think you have enough to be confident in designing the daughterboard template? | 07:22 |
| mithro | ayush3504: then you should be able to do a rough design for each daughterboard | 07:22 |
| ayush3504 | mithro: yes, i think so | 07:22 |
| mithro | ayush3504: then look at the mechanical design of a front face plate | 07:22 |
| ayush3504 | mithro: front face plate? isn't that the back plate? | 07:23 |
| mithro | ayush3504: you need to populate all the spreadsheets with mechanical information so we can refer back to it at a later date | 07:23 |
| ayush3504 | mithro: will do | 07:24 |
| mithro | ayush3504: take a look at -> https://docs.google.com/drawings/d/1_R3jtlCrZd9fILbPU8QGs2s61_4jhVgljF7P4RS27_U/edit | 07:26 |
| tpb | Title: Serial expansion board sketch - Google Zeichnungen (at docs.google.com) | 07:26 |
| ayush3504 | mithro: and what's the backview? | 07:29 |
| mithro | ayush3504: your board doesn't go all the way to the back | 07:30 |
| mithro | I'm about to head off | 07:30 |
| mithro | any last questions? | 07:30 |
| ayush3504 | mithro: umm, i'm still a bit confused about this | 07:31 |
| ayush3504 | mithro: what's the front and back once again? | 07:31 |
| ayush3504 | mithro: please draw a line parallel to the side that you consider "front" | 07:33 |
| mithro | ayush3504: I labeled the with arrows | 07:34 |
| mithro | S/the/them | 07:35 |
| ayush3504 | mithro: it looks like the right edge is the front, my board isn't on that side? | 07:35 |
| ayush3504 | mithro: right edge wrt Top view | 07:36 |
| *** mparuszewski has quit IRC | 07:51 | |
| *** Niharika has left #timvideos | 08:44 | |
| *** Niharika has quit IRC | 08:44 | |
| *** tija has joined #timvideos | 08:54 | |
| *** mparuszewski has joined #timvideos | 09:31 | |
| *** rohitksingh has joined #timvideos | 09:53 | |
| *** rohitksingh has quit IRC | 10:28 | |
| *** techdragon has quit IRC | 11:15 | |
| *** Joelw has quit IRC | 11:15 | |
| *** techdragon has joined #timvideos | 11:17 | |
| *** Joelw has joined #timvideos | 11:17 | |
| mithro | ayush3504: I'm just heading to bed any quick questions? | 11:45 |
| mithro | Did you figure out the front / back? | 11:45 |
| mithro | Well I'm going to sleep now. Gnight everyone. | 12:03 |
| *** thaytan_ is now known as thaytan | 12:28 | |
| *** ChanServ sets mode: +v thaytan | 12:28 | |
| *** FeltonChris has joined #timvideos | 12:59 | |
| *** FeltonChris has quit IRC | 13:00 | |
| *** FeltonChris has joined #timvideos | 13:00 | |
| *** tija has quit IRC | 13:16 | |
| *** mparuszewski has quit IRC | 13:31 | |
| *** Niharika has joined #timvideos | 13:38 | |
| *** mparuszewski has joined #timvideos | 13:48 | |
| *** hyades has joined #timvideos | 14:06 | |
| *** rohitksingh has joined #timvideos | 14:11 | |
| *** slomo has joined #timvideos | 15:53 | |
| *** rohitksingh has quit IRC | 15:58 | |
| *** Niharika has quit IRC | 16:05 | |
| *** rohitksingh has joined #timvideos | 18:13 | |
| *** hyades has quit IRC | 19:39 | |
| mithro | mparuszewski: ping? | 20:35 |
| mparuszewski | mithro: pong :) | 20:36 |
| mithro | mparuszewski: great, give me 5 minutes then we can talk | 20:38 |
| mparuszewski | OK, I also jeed 5 minutes. :) | 20:39 |
| mparuszewski | I am ready. :) | 20:47 |
| mithro | mparuszewski: I'm just walking into work well be back in 15 minutes | 21:02 |
| mithro | mparuszewski: poke? | 21:18 |
| mparuszewski | Ready to talk :) | 21:19 |
| mithro | mparuszewski: okay cool | 21:20 |
| mithro | mparuszewski: so I wanted to chat with you to understand your progress so far and to discuss some aspects of your project further (and help give you some guidelines to make the correct choices) | 21:21 |
| mparuszewski | mithro: ok, great. | 21:22 |
| mparuszewski | What would you like to know? :) Currently I am working on People on Gettin Started site, I've integrated it with GitHub, some of information are downloaded from GitHub API on client side. | 21:24 |
| mparuszewski | Just like in Issues | 21:25 |
| mithro | mparuszewski: first thing, how close are we to being able to deploy your version of the new site? | 21:26 |
| mparuszewski | In my opinion we can do that even now, my version has same content as current deployed on code.timvideos.us, works correctly and has all functionalities | 21:27 |
| mparuszewski | Today I've tested GitHub edit interface and works just like prose.io and dosen't need any servers or authentication and configuration, works out of the box. | 21:32 |
| mithro | mparuszewski: I was going to ask about the edit workflow | 21:32 |
| mithro | mparuszewski: how does the embedding work? | 21:33 |
| mparuszewski | Are you asking about embedding iframe on website? | 21:35 |
| mparuszewski | I am not sure if I understand :) | 21:35 |
| mithro | mparuszewski: I go to code.timvideos.us and want to edit a web page | 21:36 |
| mithro | mparuszewski: what happens now? | 21:36 |
| mithro | mparuszewski: having a "nice" edit experience is one part of your project, right? | 21:38 |
| mparuszewski | mithro: Yes, on new website you are able to edit website only via GitHub edit interface or Prose.io, if we want to have current edit experience with wiki it will need changes in design | 21:39 |
| mparuszewski | because every page was splitted into smaller parts (that are in _includes folder) | 21:40 |
| mithro | mparuszewski: so what does that look like? | 21:40 |
| mithro | editing via Prose.io / Github Edit interface is fine, but the person shouldn't need to know anything about those tools | 21:41 |
| mparuszewski | Currently if you want to edit website you need to go to GitHub edit interface or Prose.io, select the file and edit it. But now I understand the problem | 21:42 |
| mparuszewski | Person shouldn't think about file which he want to edit, I need to add Edit links on website to make it easy | 21:43 |
| mithro | mparuszewski: yeah | 21:44 |
| mithro | mparuszewski: ideally the edit link should pop-up a model window inside the website | 21:44 |
| mithro | mparuszewski: so you don't even leave the website | 21:44 |
| mithro | mparuszewski: it would be nice if we could theme / control the edit interface too - which is why I think prose.io is probably the right solution here | 21:45 |
| mithro | mparuszewski: editors might also be non-technical | 21:45 |
| mparuszewski | Ok, I will do that, I will display link on hover on element (panel is the element that user can edit) | 21:45 |
| mithro | mparuszewski: but not sure if you can embed the github edit interface? | 21:46 |
| mparuszewski | Prose has definitely better preview options, GitHub edit only displays current markdown document | 21:48 |
| mparuszewski | and its preview | 21:49 |
| mparuszewski | so yeah, prose.io will be better, but I am not sure if it can be configured to work with 'includes', because these are small part and doesn't has layout | 21:50 |
| mparuszewski | they are included into larger pages | 21:50 |
| *** lns has joined #timvideos | 21:50 | |
| CarlFK | lns: hi | 21:50 |
| lns | CarlFK, what's up :) | 21:50 |
| mparuszewski | mithro: So maybe I will need to change design a little bit. | 21:51 |
| CarlFK | I dvswitch is great, but.. | 21:51 |
| CarlFK | er. lns: dvsw.. but... | 21:51 |
| CarlFK | and I am perhaps one one of the most active users (I use it at least once a month, most others use it one event per year | 21:52 |
| mithro | mparuszewski: can you explain the includes better? | 21:53 |
| CarlFK | lns: anyway, I consider dvswitch to be.. legacy ;) | 21:53 |
| CarlFK | lns: it is still being used in production because a replacement hasn't been proven to work (there are a few candidates, but no one has taken the time/risk to use them) | 21:55 |
| CarlFK | and this #chan is way more active than #dvswitch, and given we still use it, you will likely get more from here than #dvs | 21:55 |
| lns | CarlFK, does "Tim's Videos" stream to Icecast? | 21:56 |
| mparuszewski | mithro: yes. I wanted to have nice design so I needed to split every page into smaller parts. For example, current page 'Summer of code' I split into 8 parts (http://pinoss.github.io/summer-of-code/, you can see 8 panels/boxes with content). Every panel has content loaded from '_includes' folder | 21:56 |
| mparuszewski | in Jekyll, those small parts are just markdowns and are generated into html | 21:57 |
| CarlFK | lns: icecast has been replaced with something better https://github.com/timvideos/streaming-system | 21:59 |
| tpb | Title: timvideos/streaming-system · GitHub (at github.com) | 21:59 |
| CarlFK | which has been used in production | 21:59 |
| CarlFK | more than a few times. better than icecast in a few ways: mutiple formats (ogv, webm, h2whatever...) and there is a web site that makes a nice experience for the viewer: like summary of tracks (pycon had 6 tracks) | 22:01 |
| mithro | mparuszewski: okay, this design kind of makes sense, but I don't think the structure is correct | 22:01 |
| CarlFK | and an irc client setup for each track, twitter falls... stu like that | 22:02 |
| CarlFK | brb | 22:02 |
| mithro | mparuszewski: can we make includes page level specific rather than having a global site include? | 22:02 |
| mithro | mparuszewski: IE we have a Summer-Of-Code.md and a "Summer-Of-Code" directory which has the include bits inside it for the Summer-Of-Code.md ? | 22:04 |
| mithro | mparuszewski: you still there? | 22:06 |
| mithro | mparuszewski: still got lots more to talk about :P | 22:09 |
| CarlFK | mithro: can you whip up some docs for running pusher.py? (like an example of setting up 1 track) | 22:23 |
| mithro | CarlFK: setup config.json, run pusher.py | 22:25 |
| CarlFK | setup config.json .... um.... | 22:26 |
| mithro | if you only want to push configs to the encoders use --no-collectors | 22:26 |
| mithro | this file -> https://github.com/timvideos/streaming-system/blob/master/config.json | 22:27 |
| tpb | Title: streaming-system/config.json at master · timvideos/streaming-system · GitHub (at github.com) | 22:27 |
| CarlFK | is that setup? | 22:27 |
| CarlFK | I am hoping I need to give hostname/ip of collector and encoder, and everyting else can default to "test" or "main track" or something | 22:28 |
| mithro | CarlFK: everything fulls the information from that file | 22:29 |
| mithro | s/fulls/pulls/ | 22:29 |
| mithro | you set the IP address or DNS names in the values | 22:29 |
| mithro | "flumotion-mixer": false, | 22:29 |
| mithro | "flumotion-encoder": false, | 22:29 |
| mithro | "flumotion-collector": false, | 22:29 |
| mithro | see further example in https://github.com/timvideos/streaming-system/blob/master/config.private.json.example | 22:30 |
| CarlFK | ah, that's what that means | 22:30 |
| tpb | Title: streaming-system/config.private.json.example at master · timvideos/streaming-system · GitHub (at github.com) | 22:30 |
| mithro | mixer == DVSwitch mixer thing | 22:31 |
| mithro | encoder == flumotion encoder machine running on EC2 | 22:31 |
| mithro | collector == flumotion collection machine running in your venue | 22:31 |
| *** rohitksingh1 has joined #timvideos | 22:32 | |
| *** rohitksingh is now known as Guest55815 | 22:32 | |
| *** rohitksingh1 is now known as rohitksingh | 22:32 | |
| CarlFK | that isn't obvious | 22:32 |
| CarlFK | nor am I sure where to document it | 22:32 |
| CarlFK | other than my dump of notes.txt wich is pretty bad | 22:33 |
| mithro | CarlFK: yeah the "flumotion-mixer" is probably a bad name and should be fixed | 22:34 |
| mithro | but the collector / encoder naming scheme is used throughout the system | 22:34 |
| CarlFK | it also isn't clear what kind of value goes there | 22:34 |
| mithro | CarlFK: see second diagram at https://github.com/timvideos/streaming-system | 22:35 |
| tpb | Title: timvideos/streaming-system · GitHub (at github.com) | 22:35 |
| CarlFK | that doesn't at tell me how to run pusher | 22:35 |
| mithro | CarlFK: you do "python pusher.py" and it pushes the configs based on your config.json file | 22:36 |
| *** rohitksingh has quit IRC | 22:37 | |
| *** rohitksingh has joined #timvideos | 22:38 | |
| CarlFK | change :false to :1.2.3.4 #ip or hostname of collector | 22:38 |
| mithro | It needs to stay false otherwise the value is not skipped. The config.private.json.example is your guide | 22:39 |
| CarlFK | that's not a good guide | 22:39 |
| CarlFK | or at least something could be done better | 22:39 |
| CarlFK | they are good examples, but it doesn't work as a guide that walks someone though the things that need to be done | 22:41 |
| CarlFK | "channel": "#timvideos", - someone may want to change it, but it doesn't need to be | 22:41 |
| CarlFK | which is the case for all the settings excpet the 3 you mentioned above | 22:42 |
| *** rohitksingh has quit IRC | 22:43 | |
| CarlFK | I'll try to set it up in an hour or so and take notest | 22:43 |
| CarlFK | notes | 22:43 |
| mithro | CarlFK: true, we need a "Setting Up" section | 22:48 |
| CarlFK | we have all the materials to build a house, but no blueprints. | 22:48 |
| mithro | CarlFK: patches welcome | 23:06 |
| CarlFK | there isn't anything to patch :p | 23:06 |
| mithro | CarlFK: sure there is, documentation can be patched | 23:07 |
| mithro | CarlFK: adding new files is patching too | 23:07 |
| CarlFK | but yeah, I am trying - but I keep getting so lost my scribble_notes.txt I don't even have faith in | 23:07 |
| mithro | CarlFK: dump them into a file in a pull request and I'll correct them if they are wrong | 23:08 |
| CarlFK | oh goodnesss.. but ok | 23:08 |
| CarlFK | bbl | 23:09 |
| *** CarlFK has quit IRC | 23:09 | |
| *** FeltonChris has quit IRC | 23:29 | |
| mithro | ayush3504: ping? | 23:37 |
| mithro | mparuszewski: I assume you fell asleep? | 23:37 |
| *** lns has left #timvideos | 23:40 | |
Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!
