kyak changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
Nik05 has quit [Ping timeout: 264 seconds]
Nik05 has joined #qi-hardware
fengling has joined #qi-hardware
archang has quit [Remote host closed the connection]
archang has joined #qi-hardware
fengling has quit [Ping timeout: 245 seconds]
wpwrak has joined #qi-hardware
<wpwrak> welcome back, world ! :)
archang has quit [Remote host closed the connection]
Nik05 has quit [Remote host closed the connection]
Nik05 has joined #qi-hardware
fengling has joined #qi-hardware
atommann has joined #qi-hardware
rjeffries has joined #qi-hardware
fengling has quit [Quit: WeeChat 1.2]
archang has joined #qi-hardware
<wpwrak> (pronunciation of "wpwrak") i'd just pronounce it as if it was a regular german word. sounds bumpy and ugly, but given that it's mainly optimized for uniqueness, that ought to be fine :)
atommann has quit [Quit: Leaving]
<DocScrutinizer05> err I fail to speak "wpwrak"
<DocScrutinizer05> 4 consonants :-o
<DocScrutinizer05> "wepewrak" would work
<wpwrak> yeah, it's an effort to make it to he bonus vowel ;-)
<DocScrutinizer05> even wepwrak
<wpwrak> maybe think of "wpwrak" as a stifled burp ;)
<DocScrutinizer05> "wp" is unspeakable
<wpwrak> think "whip" and delete the "i" :)
rjeffries has quit [Ping timeout: 245 seconds]
<DocScrutinizer05> maybe provide a audio for the pronunciation
<DocScrutinizer05> on an unrelated topic I think I cought a slight cold in the night of tuesday to wednesday. which comes in handy for finishing the whole camp infra etc
<wpwrak> indeed :) i'm kinda surprised i didn't get one of my own
xiangfu has joined #qi-hardware
<nicksydney> something cool to build http://imgur.com/a/DyQZL
<DocScrutinizer05> xiangfu: HI!
<DocScrutinizer05> hi! (sorry capslock)
ccnnjj has quit [Ping timeout: 244 seconds]
fengling has joined #qi-hardware
<xiangfu> DocScrutinizer05: Hi
pcercuei has joined #qi-hardware
xiangfu has quit [Ping timeout: 246 seconds]
jwhitmore has joined #qi-hardware
fengling has quit [Ping timeout: 245 seconds]
archang has quit [Ping timeout: 255 seconds]
fengling has joined #qi-hardware
fengling has quit [Quit: WeeChat 1.2]
wolfspraul has joined #qi-hardware
jwhitmore has quit [Ping timeout: 250 seconds]
ccnnjj has joined #qi-hardware
jwhitmore has joined #qi-hardware
FDCX has quit [Ping timeout: 260 seconds]
FDCX has joined #qi-hardware
kanzure has quit [Ping timeout: 244 seconds]
kanzure has joined #qi-hardware
ccnnjj has quit [Ping timeout: 244 seconds]
FDCX has quit [Ping timeout: 245 seconds]
FDCX has joined #qi-hardware
ccnnjj has joined #qi-hardware
jwhitmore has quit [Ping timeout: 240 seconds]
<larsc> eintopf: so, you want a adf7242?
pcercuei has quit [Ping timeout: 256 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
pcercuei has joined #qi-hardware
<eintopf> larsc: I got a offer that somebody will give me a adf7242, but I am also happy to maintain at86rf2xx and to work with mrf24jFOOBAR
<eintopf> and of course work with atusb
<eintopf> not important, I will keep to work with at86rf2xx, mrf24jFOOBAR and atusb. It's still hard to keep everything up-to-date to the recent mainline state
<eintopf> so they have the latest greatest features
<eintopf> here my work for the mrfj24FOOBAR
<eintopf> I say foobar because I can't remember the last numbers
<eintopf> mrf24j40 ist the transceiver
<eintopf> but there exists mrf24j40ma and mrf24j40mc, etc some different boards
<eintopf> with amplifier or not
<larsc> eintopf: that somebody is boss, your adf7242 is on my desk, I'll ship it on monday
<larsc> is my boss
<eintopf> and why do you know my name >:-|
<larsc> I expected it to be you
<eintopf> does your company like to have the driver mainline?
<larsc> sure
<larsc> that was always the paln
<eintopf> yea but mainline is also not quite now, it's better than when the project was linux-zigbee
<eintopf> depends many people (inclusive myslef) have more effort to implement 6lowpan
<eintopf> the address family 802.15.4 is still somewhat broken at some places
<eintopf> but we working on this
<eintopf> the project grabs now some frameworks from wireless
<eintopf> larsc: how easily is it to connect some wires on the transceiver?
<eintopf> does it has some female connecters
<eintopf> connectors
<eintopf> I don't want to solder here much
<eintopf> and I am very bad in soldering
<larsc> it's a male header
<larsc> what baseboard do you want to use?
<eintopf> I have some beaglebones here and raspberry pi's
<eintopf> and I have wires
<larsc> we tested it ith the pi
<eintopf> in diffent colors male<->male, female<->male
<larsc> you'll need 7 wires. 4 for SPI, a interrupt and VCC and GND
<eintopf> VCC is 3.3?
<larsc> yes
<eintopf> and when I have other questions to things what the datasheet doesn't say anything. I can ask you?
<larsc> sure
<eintopf> this looks beautiful
<eintopf> the most people @linux-wpan use these transceivers http://openlabs.co/store/Raspberry-Pi-802.15.4-radio
<eintopf> I think the price is 1 cent cheaper each day
<eintopf> and currently I think this man need to produce many of them because - https://lists.riot-os.org/pipermail/devel/2015-August/002858.html
<eintopf> but the price is okay
<eintopf> I heard the eval board of adf7242 cost much
* eintopf never looked what it costs
<eintopf> larsc: does the adf7242 have one frame buffer only?
<eintopf> or seperate rx/tx buffer?
* eintopf need to look
<larsc> no idea to be honest
<eintopf> a separate
<eintopf> that's good
<eintopf> the at86rf2xx have one only, I expierence improvements at mrf24j40
<eintopf> mrf24j40 has also separate rx/tx buffer
<eintopf> ah cca mode 1 only
<eintopf> okay
<eintopf> yea, datasheets looks okay
<eintopf> I am sure I have question when I look again into it
<eintopf> larsc: and can I have the source for the firmware? :-)
<eintopf> no, little joke :(
<larsc> probably not
<larsc> I don't have it either
<larsc> we are unworthy software developers ;)
<eintopf> mhh, where are the register settings for the address filter
<eintopf> maybe I should lookup it in the current driver
<eintopf> doesn't described inside the datasheet but driver use 0x116
<eintopf> base address 0x116 for the extended address
wolfspraul has quit [Quit: leaving]
<eintopf> I think I have not the _real_ for internal use datasheet ;-)
<eintopf> yes
<eintopf> #define REG_IEEE_ADDR_0 0x116
<eintopf> this isn't described in my version of datasheet
<eintopf> Rev. 0
<larsc> All I have is what is on the public website
<pcercuei> it's a fake register IIRC
<pcercuei> handled by the firmware
<eintopf> hmpf
<eintopf> so the datasheet doesn't represent the current available firmware?
<pcercuei> 0x116 is for the 64-bit address
<eintopf> ahh here is the right document
<pcercuei> yeah. I don't know where that info actually comes from.
<eintopf> register map extensions
<eintopf> okay
<eintopf> I will put that to my materials
<pcercuei> ah, great
<pcercuei> also, I'm pretty sure that the chip can work without any firmware
<pcercuei> (and then the advanced features are not available)
<eintopf> address filtering is also only a optional feature
<eintopf> to reduce workload
<eintopf> I think I will have more question when I work on it :/
<eintopf> also question is for me if the transceiver automatically detects if acknowledge request bit is set and waiting after transmit for an ack
<eintopf> or I need to go into some special state or do I need set some register bit for that
<eintopf> a great
<eintopf> the transceiver will do that automatically
<eintopf> If it is set, then an acknowledgment
<eintopf> frame is expected following the transmission.
infobot has quit [Ping timeout: 250 seconds]
pcercuei has quit [Quit: dodo]