Back
[00:54:44] <Jartza> Casper: unfortunately, it's all about the money
[00:54:57] <Casper> not just money
[00:55:16] <Jartza> in the end, it is
[00:55:28] <Casper> often there is lots of stupid ol'geizer decision that should have retired...
[00:55:41] <Jartza> To make the merger a financial success, Sanghi aims to find about $170 million a year in so-called synergies—cost cuts or profit improvements—rising to $200 million in four years.
[00:55:53] <Jartza> Microchip had operating profits that were 29.5% of sales in its December quarter compared to 9.4% for Atmel.
[00:55:58] <Jartza> Atmel is the “worst performing company we ever bought,” Sanghi said.
[00:56:09] <Jartza> “This company is atrophying…it’s in trouble and a lot of improvements need to be made to bring it up to the Microchip level in technology, management and sales,” Sanghi said.
[00:56:11] <Casper> buy a compagny, kill it, don't even look at their know how...
[00:57:09] <Casper> microchip/atmel, kill the atmel brand, keep their knowledge and products, in part, piece or fully...
[00:57:20] <Jartza> in the end, the numbers are what investors are interested in
[00:57:50] <Casper> like... I don't know if it is still the same, but pic16 was 4 cycles/instruction, avr is mostly 1, merge the 2
[00:58:32] <Jartza> “Look at who has grown better—Atmel or Microchip. They were 2-3 times our size 20 years ago, and now we are twice their size and our profits are much larger,” he added.
[00:59:25] <Jartza> so the CEO at least loves microchip and seems to dislike atmel
[00:59:51] <Casper> atmel seemed to be badly managed anyway, so a restructuration will be needed
[01:00:11] <Casper> one of the issue with atmel I think is that they butchered some of their products, like the tiny85
[01:00:28] <Casper> man... they really fucked up with that one imo
[01:01:40] <_ami_> I think its abt the ego also. they never started atmel products so might kill them over the period.
[01:03:29] <Casper> like the t85... why can't it do async serial?!? why don't you have that "count to this value" in timer (forgot the register name)... there was also a few other annoyance like that... it make using it quite hard for many projects, even if it would be perfect if it wasn't butchered
[01:06:21] <Casper> ... ah fun... mercury spill....
[01:06:35] <Casper> was bagging old ccfl to bring it to be recycled...
[01:06:44] <Casper> ... bag broke
[01:08:35] <inflex> oops
[01:09:08] <Casper> yeah
[01:09:13] <Casper> 2 fell on the concrete
[01:09:25] <Casper> of course, the biggest one broke, not the small one...
[01:10:06] <inflex> btw, I agree, Atmel had a good product... but they really botched the global delivery for too long, and then they started fragmenting too many products trying to cover too many bases
[01:11:10] <inflex> xmega seemed to also get lost
[01:11:29] <inflex> ( and STM32 seems to have eaten that pie )
[01:12:20] <_ami_> CEO Steve Sanghi turned microchip into a successful company.:
http://www.bizjournals.com/phoenix/blog/techflash/2014/05/microchip-technology-ceo-steve-sanghi-on-turning-a.html
[01:12:35] <_ami_> i think he did a good job
[01:15:17] <Casper> and way too many avr8 ... and too many version of them... normal/picopower, standard/commercial/millitary/extended temp range, low/normal voltage... add that to the different form factors...
[01:16:28] <Jartza> Casper: what do you mean by "count to this value"?
[01:18:40] <Casper> Jartza: instead of going 0-255 it can count to 0-x
[01:19:15] <Jartza> sure t85 does that
[01:19:36] <Casper> tell me how, because the datasheet make it say that there is no such function
[01:19:53] <Casper> all I found is 0-max and max is fixed to 255
[01:23:40] <inflex> Casper, ja, too many variants.
[01:23:49] <Jartza> well, can't remember all t85 registers, but there's compare value register for timers and you can have it in clear timer on compare match mode
[01:24:25] <Casper> afaik, there is no compare match
[01:25:01] <Jartza> yes there is
[01:25:20] <Jartza> you can check from my octapentaveega-code, if you want
[01:25:48] <Jartza> I can't check right now because I'm with cellphone, but it uses timers that count from 0 to 159 :)
[01:25:52] <Jartza> that much I do remember
[01:26:10] <Jartza> or was it 158. anyway
[01:26:23] <Jartza> after which, counter continues from 0
[01:26:24] <Casper> hmmm willl need to check the others
[01:26:47] <Casper> but compare does exist, just not top settable...
[01:26:54] <Casper> which can be an issue for pwm
[01:27:13] <Casper> anyway, 2am
[01:27:21] <Casper> time to take pills and go to bed
[01:27:23] <Casper> headache
[01:30:05] <Jartza> compare has top settable :)
[01:30:53] <Jartza> but I agree, the timer works differently than almost any other avr timer
[01:31:24] <Jartza> so in a sense it's borked
[01:31:49] <Casper> I'm pretty sure that the mega8 have the compare + top
[01:32:44] <Jartza> many other avr timers have more registers, in t85 they are strangely combined into modes
[01:33:31] <Casper> when I bought them, I was like: wow this is the perfect chip for this project! ... now I think I'll scrap it
[01:34:16] <Casper> and I really should have went for a bigger chip, so I could use a crystal, so communication would have been dead easy
[01:54:22] <Jartza> attiny88 is cheaper :)
[01:59:04] <inflex> I've got a bunch of Tiny48's, I quite like them, a bit cheaper than the M88 but still quite functional
[03:49:31] <_ami_> inflex: attiny48 internal oscillator can run up to 16.5 MHz like t85s?
[03:50:44] <inflex> _ami_, genuinely not sure.... I think it's 20MHz rated
[03:51:12] <_ami_> inflex: internal RC oscillator?
[03:51:54] <inflex> oh internal probably just 8
[03:52:06] <_ami_> ok
[03:52:42] <_ami_> just checked the DS, it can only run up to 12Mhz with crystal
[03:52:48] <inflex> np
[03:58:56] <Jartza> I almost bought attiny48s, but they were more expensive than attiny88
[03:59:13] <Jartza> which is same chip, but double the ram/flash
[04:07:25] <inflex> ah okay, was cheaper here, but yes, if you can get the 88 cheaper, definitely
[04:07:35] <inflex> same here though with the t10 vs t5, the 10 is cheaper
[04:09:14] <LeoNerd> volume
[04:13:10] <Jartza> I have a lot of t5 chips
[04:13:13] <Jartza> got them free
[04:13:36] <Jartza> so I did what every sensible human would do with them, I drive 8-color VGA out from them.
[04:14:21] <Jartza> https://www.youtube.com/watch?v=g0IYBAw0j0Y
[04:14:23] <Jartza> like this
[04:14:47] <LeoNerd> You say "every"...
[04:14:51] <Jartza> and this
https://www.youtube.com/watch?v=VECIEO941d4
[04:14:56] <Jartza> LeoNerd: ;)
[04:15:04] <Jartza> LeoNerd: I also said "sensible"
[05:02:07] <Jartza> http://nibblestew.blogspot.fi/2016/06/running-cobol-on-arduino-using-meson.html
[05:02:18] <Jartza> (Jussi is my colleague)
[06:04:02] <Apicalis> lol
[06:04:05] <iwancoppa> well
[06:04:08] <iwancoppa> Hello #avr
[06:04:12] <iwancoppa> some #Arduino refugees have just arrived
[06:04:16] <Apicalis> xD
[06:04:38] <iwancoppa> Seeking wisdom on the subject of atmega32u4 interrupts
[06:04:39] <Apicalis> Holy people from the AVR cathedral. Hear my prayers ^^
[06:05:41] <Lambda-Aurigae> for starters, have you read the datasheet?
[06:06:22] <iwancoppa> I've read the relevant sections, I believe
[06:06:29] <Lambda-Aurigae> interrupts are just that, interrupts. something happens and interrupts the current flow of the program and jumps to a routine to handle the interrupt condition.
[06:06:48] <iwancoppa> We're trying to modify a library, so it uses INT0 instead of PCINT5
[06:07:10] <Apicalis> I will tell you how far we have gotten Lambda-Aurigae. I am trying to alter a library that works perfectly fine as it is. Problem is , i already have a PCB where i can't alter the wiring so i have to adapt the code to use the INT0 instead of the PCINT5. This is the part where it appears to be defined
[06:07:10] <Apicalis> https://github.com/trilu2000/NewAskSin/blob/75d3209f34f6ab559c0b6d1d7cbe09c53da2cd61/examples/HM_LC_SW1_BA_PCB/hardware.h#L62
[06:07:23] <Lambda-Aurigae> so you will need to understand the two types of interrupts and how to configure them.
[06:07:36] <iwancoppa> Yeah.
[06:07:51] <Lambda-Aurigae> ok, one header file does not a library make.
[06:08:12] <Lambda-Aurigae> a bunch of defines and no actual code.
[06:08:23] <iwancoppa> That header file is where we believe the interrupt setting register and bits are defined
[06:08:29] <iwancoppa> (This library is a horrid mess)
[06:08:48] <iwancoppa> Correct me if I'm wrong, but PCINT5 should use the PCINT0_vect vector?
[06:08:49] <Apicalis> This is the altering we so far did
http://pastebin.com/gScit0fD to the interrupt definition without success
[06:09:00] <Lambda-Aurigae> a bunch of stuff is defined there but nothing is configured, assigned, etc.
[06:09:31] <Lambda-Aurigae> those defines don't actually DO anything.
[06:09:36] <Apicalis> Can u tell us how the line should look like that's currently defining the vector so we can look for it and alter it to the matching one for INT0
[06:09:38] <Lambda-Aurigae> they are just defines...aliases...
[06:10:10] <Lambda-Aurigae> I don't know if this u person can. I don't know them.
[06:10:15] <iwancoppa> Lambda-Aurigae: Those defines are setting bits somewhere else in the code
[06:10:19] <iwancoppa> CC_GDO0_PCICR |= _BV(CC_GDO0_PCIE); etc
[06:10:56] <Lambda-Aurigae> and herein lies the problem...we don't have the code to see what it is doing with those defines.
[06:10:56] <Apicalis> Lambda-Aurigae, we know that of course. The thing is on other better written librarys you can alter similar definitions to switch to other Interrupts or IN/Outputs
[06:12:18] <Lambda-Aurigae> but configuring the INT0 instead of configuring the PCINT5 is not the same as switching from PORTA to PORTB
[06:12:25] <iwancoppa> I'm confident in declaring that those defines are being used to set pin direction, and interrupt configuration bits. That's not the issue we've got
[06:12:26] <iwancoppa> Yeah.
[06:12:31] <Lambda-Aurigae> they are configured differently.
[06:12:57] <Apicalis> That was our thought and the reason why we got here. Because so far we couldnt figure it out ourselves
[06:13:17] <Apicalis> This is the only thing coming close we could find to the vector definition
https://github.com/trilu2000/NewAskSin/blob/75d3209f34f6ab559c0b6d1d7cbe09c53da2cd61/examples/HM_LC_Dim1PWM_CV/hardware.cpp-org#L120
[06:13:22] <Lambda-Aurigae> for me to tell you how to change it, I would need to read through your code and figure out how PCINT5 is configured and come up with a configuration for the INT0 to match.
[06:14:01] <Lambda-Aurigae> that is the interrupt vector itself...where the program jumps to when the interrupt happens.
[06:14:15] <iwancoppa> Yeah. What's confusing me
[06:14:18] <Lambda-Aurigae> not the configuration section where it sets up the interrupt features.
[06:14:27] <iwancoppa> is that there's PCINT0, PCINT1, etc
[06:14:43] <iwancoppa> The datasheet's vector table only lists PCINT0
[06:15:41] <iwancoppa> As far as I know, all PCINT interrupts point to the same vector, namely PCINT0_vect
[06:15:46] <Lambda-Aurigae> let me download the datasheet and read it.
[06:15:57] <Apicalis> This is the datasheet we are using
[06:15:58] <Apicalis> http://www.atmel.com/Images/Atmel-7766-8-bit-AVR-ATmega16U4-32U4_Datasheet.pdf#M7.9.72181.SHNP..Section.Head.New.Page.Interrupts
[06:16:01] <iwancoppa> So I figured that we could find PCINT0_vect, and replace it with INT0_vect
[06:16:15] <Lambda-Aurigae> that's a start
[06:16:24] <Lambda-Aurigae> then you have to configure the INT0 hardware.
[06:16:30] <iwancoppa> Yeah
[06:16:36] <iwancoppa> We'd need to add defines for EICRA1 and the relevant bits
[06:16:45] <iwancoppa> And then insert the bit-shifts into the library alongside the other bit shifts
[06:17:20] <Apicalis> i think it was EICRA bit 0 not 1
[06:19:22] <iwancoppa> EICRA ISC00 needs to be set to make INT0 behave like a PCINT
[06:19:46] <iwancoppa> ISC00 set and ISC01 unset will generate an interrupt on a rising OR falling edge
[06:19:53] <iwancoppa> which is the behaviour of a PCINT iirc
[06:20:02] <iwancoppa> PinChange INT
[06:24:54] <Lambda-Aurigae> read section 11 of the datasheet. It describes in detail the configuration for both the PCINT0 and INT0 registers.
[06:26:11] <Lambda-Aurigae> there are different configurations for the two types. you don't have an enable mask for the INTx because each is configured independently.
[06:27:12] <Lambda-Aurigae> there is only 1 interrupt routine for PCINT...all of the PCINTx pins generate the same interrupt.
[06:29:15] <Apicalis> And then the mask "filters" which one should be triggered right?
[06:29:29] <Apicalis> that would suggest there would be actually less configuration necessary if i understand correctly
[06:30:28] <Lambda-Aurigae> that code you posted with the multiple vectors won't work for the atmega32u4 as it only has PCINT0 vector.
[06:30:38] <Lambda-Aurigae> different configuration.
[06:30:53] <Lambda-Aurigae> as the INT0 has no filter mask but it has other configuration.
[06:30:57] <iwancoppa> Great, I'm not going crazy. Good to know
[06:31:11] <Lambda-Aurigae> the atmega1284p has PCINT0,1,2,3
[06:31:24] <Lambda-Aurigae> which is NOT the same as the PCINTx definitions for the individual pins...
[06:31:34] <Apicalis> Yeah the problem is that bad written library ... but also that i am not better at writing librarys currently. I have to take a look again what this example actually calls up from the library
[06:31:35] <Lambda-Aurigae> they should have named them differently.
[06:31:59] <iwancoppa> So at the moment, we first need to work out what the hell is going on in this bloody library
[06:32:09] <Lambda-Aurigae> yeah, and I have to eat breakfast.
[06:32:22] <Lambda-Aurigae> I've spent too much time reading this as it is...have to get ready for work.
[06:32:43] <iwancoppa> Thanks for the help!
[06:32:46] <Apicalis> thank you for your help so far
[06:33:48] <iwancoppa> Apicalis: You're not using anything in the examples folder, correct?
[06:34:23] <Apicalis> I am actually using this exact example
https://github.com/trilu2000/NewAskSin/blob/75d3209f34f6ab559c0b6d1d7cbe09c53da2cd61/examples/HM_LC_SW1_BA_PCB/HM_LC_SW1_BA_PCB.ino
[06:34:57] <Apicalis> It calls up AS.h and register.h let me take a look
[06:35:04] <iwancoppa> Ugh.
[06:35:19] <iwancoppa> Hate to be a pain, but I think it's time you ditched this library and wrote your own code to drive this
[06:35:25] <Apicalis> OH MY GOD AS calls up EVERYTHING
[06:35:34] <Apicalis> i gonna die
[06:35:34] <iwancoppa> In a couple of places it's using PCINT specific functions
[06:35:43] <iwancoppa> which makes sense since PCINT behaves differently to hardware interrupts
[06:36:01] <iwancoppa> It also means that by the time you've re-written it to work with INTs, you may as well have just written the thing from scratch
[06:36:12] <iwancoppa> since this library is a fucking minefield of spaghetti code
[06:36:17] <Lambda-Aurigae> PCINT is a hardware interrupt that triggers on one or more pins in the same port.
[06:36:26] <Lambda-Aurigae> INTx triggers on one specific pin only.
[06:36:45] <Lambda-Aurigae> you can have 1 to 8 pins trigger the same PCINT interrupt.
[06:36:50] <iwancoppa> Yep
[06:36:52] <Apicalis> It sure is but it's not like i just set the frequency of the chip and stuff like this, this library also decodes the signal since it's a special protocl for Homematic smart home devices
[06:37:04] <iwancoppa> and I believe there are some functions to work out which pin triggered the interrupt
[06:37:48] <Apicalis> I would love to write my own library but at this point for this complexity it's out of question ot be honest. This would take up a month at least and i actually have days
[06:38:09] <Tom_itx> on pcint you mask the pins in the interrupt to determine which pin it was
[06:39:00] <iwancoppa> days? eek.
[06:39:14] <iwancoppa> At this point I'd be desperately trying to contact the dude who write the library
[06:39:24] <Apicalis> This is what i am currently doing xD
[06:39:27] <Lambda-Aurigae> or find another.
[06:39:49] <Lambda-Aurigae> trying to run before learning to crawl.
[06:39:53] <Apicalis> There is only one other and that's the previous worse on from the same guy
[06:40:08] <Lambda-Aurigae> what are you trying to control?
[06:40:12] <Lambda-Aurigae> what is this for?
[06:40:36] <Apicalis> It's a CC1101 868Mhz Radio Module that has to be able to handle the Homematic Protocol for smart home devices/servers
[06:40:45] <iwancoppa> Run before crawling is exactly correct. I usually try and avoid such things
[06:41:29] <Tom_itx> is INT0 on the pin you want to use?
[06:41:39] <Tom_itx> it only fires on one pin
[06:41:50] <Apicalis> INT0 is the pin i want to use and it's currently configured to the PORTB5 PCINT5
[06:42:09] <Apicalis> So i want to switch from PCINT5 to INT0
[06:42:12] <Tom_itx> what did PCINT5 do to offend you?
[06:42:21] <iwancoppa> the PCB is doing the offending
[06:42:25] <Apicalis> yes
[06:42:51] <iwancoppa> to be fair, there is a solution to this that's rather ugly
[06:42:55] <Tom_itx> seems the PCB is what you should attack then
[06:42:58] <iwancoppa> If you're feeling good at soldering, desolder the chip
[06:43:11] <iwancoppa> slap it on a QFP breakout
[06:43:16] <Lambda-Aurigae> and jumping from arduino to writing this kind of lib is like jumping from using legos to build a model house to building a model airplane from scratch from balsa wood and glue.
[06:43:31] <iwancoppa> and then solder the individual pads to the pins on the breakout etc
[06:44:05] <Apicalis> i know the issues and i know the difference betweend these things but the problem is i have this PCB designed for another chip so the portb5 is no accessable
[06:44:09] <Lambda-Aurigae> just desolder the offending pins, bend them up, and rewire with some air wire runs.
[06:44:13] <iwancoppa> ^
[06:44:26] <Apicalis> its a QFN package, there are no pins to be bent
[06:44:48] <Apicalis> https://img.conrad.de/medias/global/ce/2000_2999/2900/2970/2979/1266711_BB_00_FB.EPS_1000.jpg
[06:44:55] <iwancoppa> Is it possible to admit failure on this project and take the time to get a PCB with the correct design?
[06:45:07] <Lambda-Aurigae> I know what a qfn is.
[06:45:12] <Tom_itx> http://tom-itx.no-ip.biz:81/~webpage/boards/atmega32u4/atmega32u4_1.jpg
[06:45:13] <Tom_itx> so do i
[06:45:40] <Tom_itx> that was hand soldered btw
[06:45:43] <inflex> lo there Tom_itx
[06:45:43] <Apicalis> I could shit out the PCB design within 30 minutes. The thing is that it would take too much money which i currently don't have to produce it within 1-2 weeks
[06:45:51] <Tom_itx> damn tootin!
[06:46:16] <Tom_itx> hope you wipe afterward
[06:46:21] * LeoNerd trying to get more into the "I'll design custom PCBs for people" business <.<
[06:46:35] <iwancoppa> Do you have a budget figure, or would you rather not spend anything if possible
[06:46:38] <inflex> oh hell no LeoNerd
[06:46:40] <_ami_> http://www.usb.org/developers/hidpage/HID1_11.pdf --> its sooo long :P
[06:46:41] <Tom_itx> LeoNerd, do it
[06:46:44] <Tom_itx> :D
[06:46:45] <inflex> heh
[06:46:50] <inflex> you're cruel Tom_itx
[06:46:57] <Tom_itx> haha
[06:47:02] <iwancoppa> If the board's less than 10x10cm, you can get it fabbed decently cheap by dirtypcbs
[06:47:04] <Tom_itx> good learning experience for him
[06:47:14] <inflex> true
[06:47:15] <Lambda-Aurigae> iwancoppa, but takes forever to get them.
[06:47:29] <LeoNerd> I dislike dirty for anything I'd sell. .their silkscreen printer is horrible
[06:47:34] <iwancoppa> Eh, it took about a week with DHL air mail for me
[06:47:36] <LeoNerd> oshpark have far nicer silkscreen
[06:47:41] <Apicalis> This is my PCB Tom_itx also hand soldered
http://picpaste.de/pics/20160628_140444-TMb69psA.1467199235.jpg
[06:47:49] <Tom_itx> yeah but i hate purple
[06:47:55] <LeoNerd> Granted you pay more for oshpark, but you certainly get what you pay for
[06:48:41] <Apicalis> But anyway, other PCB manufacturers might be interesting. What would be the fastest price/quality dealer you would recommend that ships to germany?
[06:48:58] <Lambda-Aurigae> hackvana
[06:49:08] <Tom_itx> yeah mitch is ok
[06:50:39] <iwancoppa> http://i.imgur.com/hq0LzQO.jpg
[06:51:13] <Lambda-Aurigae> so, going to the 32u4 to add usb to the project?
[06:51:18] <iwancoppa> That's from dirtyPCBs, got here a few days ago. Jack's desoldered because I stuffed up and put the jack in the wrong way
[06:52:17] <Apicalis> Yes Lambdra
[06:52:46] <Lambda-Aurigae> and you have the usb portion of the code added already?
[06:53:59] <Apicalis> No
[06:54:05] <Lambda-Aurigae> uhuo.
[06:54:17] <Lambda-Aurigae> because that is going to completely hork everything else around.
[06:54:39] <Lambda-Aurigae> better off adding an external usb interface I would think.
[06:55:09] <Lambda-Aurigae> if you don't understand the interrupt system enough to switch between pcint and int, the usb interrupts are going to totally throw you for a loop.
[06:55:12] <LeoNerd> If you're "just" adding USB-CDC you probably want to use one of the prebuilt bridges
[06:55:34] <iwancoppa> Lambda-Aurigae: While you're here; Atmel sample center seems convinced that they have no AVRs of any type available for samples. Do they not do samples anymore?
[06:55:54] <Lambda-Aurigae> not to mention having to contend with interrupts that happen during usb stuff
[06:56:11] <Lambda-Aurigae> iwancoppa, I haven't ordered any atmel samples in about 3 years. last time I did I had no problems.
[06:56:15] <iwancoppa> I tried to request samples for an AT90PWM3B initially. After that, I tried the rest of the AT90PWM range, then a few tinys, then a few megas, and they all gave the same 'no samples available'
[06:56:23] <Lambda-Aurigae> with the buyout by microchip, things are likely in flux.
[06:56:25] <Apicalis> To explain my situation. I already got a working product, softwarewise still in a prototyping state. It was meant to be a transmitter connected to a Gateway (868Mhz to ethernet). That setup works perfectly fine and can be connected to smart home servers. BUT it would be even more interesting for INvestors if the Transmitter itself could be directly included into Smart home Servers. That's why i
[06:56:25] <Apicalis> switched to the other Transceiver module. The USB Controller will be replaced in the future on the Transmitter since it's not needed. I just chose it to have one controller on both boards and not to switch inbetween the coding
[06:56:51] <iwancoppa> I have the feeling they're not doing samples anymore because of idiots abusing the system to get a 'free arduino', although it could be buyout related too
[06:57:16] <Apicalis> Also the USB Functionality will also be abandoned on the receiver too in the future since it's no longer needed and the settings will be done via Ethernet (webui)
[06:57:22] <Lambda-Aurigae> iwancoppa, find out who your local atmel rep is and call them.
[06:58:07] <Lambda-Aurigae> I used to have lunch with mine every 3 or 4 months or so.
[06:58:15] <Lambda-Aurigae> she was cute and brought me lots of toys I didn't ask for.
[06:58:15] <iwancoppa> Apicalis: Hold up. Is this a commercial product?
[06:58:26] <iwancoppa> If it is, you can't use this library - license is strictly non-commercial.
[06:58:29] <Apicalis> It will be in the future and i will develop my own library etc.
[06:58:36] <iwancoppa> Rightio.
[06:58:44] <Apicalis> Don't worry about that
[06:59:35] <Lambda-Aurigae> I still say the better bet would be go back to the original chip and add a usb daughter board or adapter.
[07:00:28] <Lambda-Aurigae> or get/pay someone to rewrite the library for you.
[07:01:46] <iwancoppa> Either I'm doing something very wrong, or Atmel doesn't have anything in the way of sales representatives in Australia
[07:01:51] <Apicalis> USB is absolutely not the problem here and as i said won't be used in the future. Like i said, i used this exact chip for the RFM69CW Module without any problems. Also using Interrupts and Slave select without issues. I just have to: either alter the PCB or alter the library. PCB would be of course the easiest but the most expensive solution
[07:06:12] <Lambda-Aurigae> then get someone to rewrite the library for you.
[07:06:33] <Apicalis> That sounds even more expensive xD
[07:06:42] <Lambda-Aurigae> or, read and learn and rewrite it yourself...read the datasheet and the avr-libc section on interrupts.
[07:07:10] <Lambda-Aurigae> because it's not something someone in here can say "change line 30 to say this and line 60 to say that"
[07:07:31] <Lambda-Aurigae> it's not a major change but it's more than just a couple of lines.
[07:12:33] <Apicalis> Yeah that's what i already thought but i was hoping that somone could name all the commands that need to be done for the PCINT5 and INT0 configuration so i could use the search function to at least find the and figure out how to properly replace it
[07:12:50] <Lambda-Aurigae> it's all in section 11 of the datasheet.
[07:12:59] <Lambda-Aurigae> at least, for the configuration part.
[07:13:16] <Lambda-Aurigae> then read the section of the avr-libc manual on interrupts.
[07:15:19] <Apicalis> ty for the hints
[07:16:41] <iwancoppa> I think I've killed Atmel.com. Can't load the page anymore
[07:19:42] <Lambda-Aurigae> it died for me earlier.
[07:19:53] <tkoskine> Atmel.com has been slow for me also today (works now though...). Maybe Microchip is trying to give us a hint. ;)[1~
[07:19:59] <Lambda-Aurigae> Apicalis, how many external interrupt pins are actually used?
[07:20:02] <megal0maniac> Works for me
[07:20:09] <_ami_> works for me too
[07:20:21] <Lambda-Aurigae> I got an email from atmel yesterday that was mostly microchip stuff.
[07:20:30] <iwancoppa> Lucky, you lot
[07:20:41] <iwancoppa> Would any of you happen to have the email for the samples department, or sales?
[07:21:20] <Apicalis> Lambda-Aurigae the receiver has only the CC1101 Radio module attached so it actually only uses the SPI + SS + Interrupt. That's why i will later switch to a cheaper less powerfull controller on the transmitter side.
[07:21:28] <Apicalis> I mean transmitter not receiver
[07:21:50] <Lambda-Aurigae> iwancoppa, where are you?
[07:21:57] <iwancoppa> Australia
[07:22:26] <Apicalis> That country south from germany? ^^
[07:22:56] <Lambda-Aurigae> singapore is your nearest sales rep
[07:23:43] <iwancoppa> Eek. Got an email?
[07:23:51] <Lambda-Aurigae> just posted a PM to you.
[07:24:28] <Lambda-Aurigae> there's also customerservice@atmel.com
[07:25:11] <iwancoppa> Alrighty, thanks
[07:25:14] <Lambda-Aurigae> and, now I gots to head off to worky.
[07:25:26] <Lambda-Aurigae> chaos, panic, disorder,,,,my job here is done!
[07:31:57] <iwancoppa> Alright, email fired off to customer service. Let's see where this goes
[08:02:49] <GeneralStupid> Hi, can anyone help me with my makefile and the ASF?
[08:03:01] <GeneralStupid> I would really like to see an example or something
[08:56:21] <GeneralStupid> ok, Make tells me he couldnt find ..src/ASF/xmega/drivers/cpu/ccp.s but its there and the path looks ok
[09:02:32] <LeoNerd> Bah... So who was it round here who suggested I ought to use the CH340 chips? I want to blame them - it's all your fault.
[09:02:53] <LeoNerd> Couldn't find any UK sellers from the usuals (Farnell, Mouser, etc..) so I ordered some random stuff off eBay. A month ago. Still not turned up yet :(
[09:04:57] <bss36504> Is the CH340 just a PIC programmed as a USB-UART? I dont think olimex makes silicon...
[09:05:09] <LeoNerd> I don't know
[09:05:22] <LeoNerd> It's a 20 pin TSSOP
[09:05:36] <LeoNerd> We could compare the pinouts to see if the USB and XTAL pins match up to known PICs
[10:33:01] <_ami_> any good usb packets sniffer application on linux?
[10:33:08] <LeoNerd> I imagine sigrok can do it
[10:33:16] <LeoNerd> Given suitable hardware
[10:50:30] <bss36504> There's a company called TotalPhase that makes a USB sniffer. I used their USB to SPI adapter on numerous occasions. Hardware and Software are solid, even if it's a little expensive.
[10:51:59] <_ami_> thanks, i shall check.
[10:52:39] <_ami_> so they make all type of sniffers.
[10:52:43] <_ami_> types*
[10:53:18] <_ami_> 500$ :O
[10:53:23] <_ami_> for usb sniffer
[10:53:54] <bss36504> Like I said, expensive haha
[10:54:18] <bss36504> But, if you ever need a 50MHz USB-SPI adapter, I think they are the only one.
[10:54:45] <bss36504> We could do almost full speed testing with the serial memory we were making.
[11:24:46] <curlyears> *wow* things have inproved in the AVR world, I see
[11:25:18] <_ami_> curlyears: ? :)
[11:25:34] <_ami_> are you coming back to AVR world after few years?
[11:25:37] <curlyears> 2 years ago, I couldn't get enough people to particip[ate in an AVR specific channel to keep one goin. Nice to see that's changed. Dare I question how much the arduino phenomenon has influeced this?
[11:26:20] <curlyears> _ami_ I don't know that I'm coming back, I have pretty much moved on the the Raspberry Pi, but I am still interested in AVR uses and applications
[11:26:40] <_ami_> probably yes. I used arduino first and got bored in short amount of time :)
[11:27:13] <curlyears> and, if you're not familiar with it alread, check out http//:www.nanopi.org
[11:27:14] <_ami_> you can say arduino introduces AVR to me. this might be a generic case with others too?
[11:27:27] <curlyears> ://, *duh*
[11:27:36] <curlyears> and, if you're not familiar with it alread, check out
http://www.nanopi.org
[11:27:42] <curlyears> there we go
[11:28:01] <curlyears> might well be, yes
[11:35:55] <skz81> Dare I question how much the arduino phenomenon has influeced this? >> I started to play with an arduino, that's right !
[11:40:04] <_ami_> curlyears: rpi is just like another PC :) not much difference to me :) i hv been working on UIFW/Graphics stuffs for last 9 years.
[11:40:17] <Strangework> I started with an Arduino as well. For all the criticism it receives, one has to concede that it is a very accessible introduction to microcontrollers and hobbyist electronics.
[11:40:55] <_ami_> i wanted to taste the lower hardware stuffs so that i can start writing linux drivers. it was the initial motivation for me to start hacking electronics.
[11:41:50] <_ami_> my avr journey is little short. started in April this year
[11:43:27] <_ami_> very nice people here who helps others so i am enjoying avr programming.
[11:43:45] <liwakura> i also have to throw my part in, i also got to AVR by getting some Arduino Hardware
[11:44:20] <_ami_> there you go! :)
[11:44:28] <liwakura> _ami_: for your interest, i also started last March
[11:44:35] <liwakura> and i went here and asked alot of question
[11:44:40] <_ami_> nice! :)
[11:44:53] <liwakura> and in 40% of cases, "Its in the Datasheet on Page X" was the answer
[11:45:00] <_ami_> yup
[11:45:56] <_ami_> reading AVR datasheet is an art! you hv to get good at it to find your answers :)
[11:46:06] <_ami_> this is my learning too!
[11:46:21] <Strangework> I'm very pleased with how descriptive the AVR datasheets are. I haven't had much experience dealing with datasheets from other electronics manufacturers, though I find AVR sheets to be very explicit
[11:46:47] <Strangework> Having all that information in one place makes study and practice that much more approachable!
[11:47:49] * _ami_ makes notes of avr stuffs in a notebook! :)
[11:48:41] <_ami_> that notebook is about to get full.. only few blank pages are left!
[11:49:26] <Strangework> What, exactly, do you record in your notebook? :o
[11:50:27] <_ami_> my work cycle is "Learn X" ==> experiment with it ==> if get stuck -> do google -> still stuck -> ask here -> implement it again" ==> when i am done with topic X => i make a note of this journey on the notebook :)
[11:50:42] <Strangework> That's a great workflow! :D
[11:51:12] <Strangework> Mine's too freeform - it gets in the way of productivity. Maybe I'll give your method a shot!
[11:51:30] <_ami_> try it! it worked for me all the time.
[11:52:04] <_ami_> may be one day, i publish it as "The Are of AVR programming" book :)
[11:52:12] <_ami_> Art*
[11:57:14] <bss36504> Dont wait too long or you'll have to write "The Art of PIC Programming"
[11:57:32] <LeoNerd> Maybe it's written by pirates; "The ARrrrrr of AVR Programming"?
[12:00:36] <curlyears> Atmel's datasheets are amonst the best in the industry
[12:00:37] <Strangework> bss36504 - why do you say that? Microchip/Atmel acquisition? :P
[12:00:38] <_ami_> bss36504: :/ yeah, :(
[12:00:54] <_ami_> LeoNerd: :)
[12:01:10] <liwakura> mine is the 7-2-4-2 rule
[12:01:42] <liwakura> i do nothing for 7 days
[12:02:00] <curlyears> _ami_ Microchip has been trying to acquire Atmel for over 10 yeards
[12:02:04] <liwakura> then do the work of 2 days in 4 hours at 2 AM
[12:04:03] <Strangework> curlyears, a merger had already been completed a few months ago!
[12:04:35] <curlyears> Strangework: really. DAMN IT. Another truly great manufacturer down the drain
[12:05:35] <Strangework> We'll see what it means for hobbyists. I can't see Microchip having a good reason to squelch the AVR arch - I expect things to be okay :))
[12:05:58] <twnqx> AVR is going downhill for ages
[12:06:09] <twnqx> or did you not notice the price hikes
[12:06:32] <twnqx> making chips 10x as expensive as their arm competition while remaining at a tenth of the power
[12:06:58] <twnqx> now shipiing chips without bootloader because it's too much effort to preprogram them
[12:08:15] <curlyears> twnqx: since when did Atmel ever ship processors with a boot loaded programmed in? Never did to my knnowledge, and I used the for 10 years, only stopped about 4 years ago
[12:08:29] <curlyears> Atmel's datasheets are amonst the best in the industry
[12:08:32] <bss36504> I only knew of the USB ones having any kind of bootloader
[12:08:32] <twnqx> 16/32u2/4 did
[12:08:43] <curlyears> bss36504: right
[12:19:32] <_ami_> in v-usb, hid & custom class can't be mixed?
[12:20:06] <_ami_> e.g. i want to send a custom message to hid mouse so that it moves in left direction a bit.
[12:20:07] <LeoNerd> I don't know why you persist in asking questions, in here, about V-USB
[12:20:20] <_ami_> i am obsessed with it! ;)
[12:20:22] <LeoNerd> We've already stated many times we don't like it, we suggest not using it. You therefore won't find many people who could answer
[12:20:30] <_ami_> ok :)
[12:20:53] <bss36504> I missed the lead up to this; why on earth would you use v-usb in 2016?
[12:22:43] * _ami_ plans to change his nick name to v-usb D:
[12:22:50] <bss36504> oh jeez
[12:23:10] <bss36504> but really, why? Are you trying to shoehorn an Attiny into a USB application?
[12:23:19] <_ami_> yeah
[12:23:20] <LeoNerd> I think the answer is "yes"
[12:23:21] <LeoNerd> :(
[12:23:36] <bss36504> http://i.imgur.com/TnQRX6v.gif
[12:23:54] <_ami_> lol
[12:23:58] <bss36504> lol indeed
[12:24:49] <_ami_> v-usb is the coolest thing i hv seen yet ! :D
[12:25:19] <LeoNerd> I can imagine if you hadn't really seen anything, you could believe that
[12:26:16] <bss36504> f*cking savage, LeoNerd lol
[12:26:32] <bss36504> _ami_: you should just use a U2/U4
[12:26:34] <LeoNerd> People who've only ever seen moonlight at night think candles are pretty cool
[12:26:37] <bss36504> or an arm
[12:26:39] <LeoNerd> Just wait til they see halogen lights
[12:26:54] <_ami_> :)
[12:27:16] <_ami_> bss36504: cp2102 chips are yet to arrive at my doorsteps
[12:27:33] <LeoNerd> I've gone off the 2102 lately. It doesn't appear to handle BREAK at all :(
[12:27:56] <LeoNerd> FT232 fine. PL2303 fine. CH340 fine
[12:28:05] <LeoNerd> CP2102 - doesn't want to know.
[12:28:48] <LeoNerd> I don't know if that's because the chip itself doesn't suport it, or the chip does but the Linux driver doesn't recognise it. But since the Linux driver was written /by/ Silabs and nobody seems to have any semblence of documentation at all, those two cases are basically indistinguishable
[12:29:18] <_ami_> hrm, u could report this to SL?
[12:29:23] <LeoNerd> Hah
[12:29:31] <LeoNerd> If you can find me a technical contact to talk to, sure
[12:29:40] <LeoNerd> BTW I don't speak Chinese
[12:30:10] <_ami_> they are very nice in providing samples
[12:30:26] <_ami_> so i think they should reply to your queries
[12:30:32] <LeoNerd> Sales != Technical
[12:30:39] <_ami_> aha
[12:30:43] <_ami_> :/
[12:30:45] <LeoNerd> I emailed *the* author of the current Linux driver
[12:30:47] <LeoNerd> A month ago. No reply
[12:31:12] <_ami_> paid programmers are the worst!
[12:31:13] <_ami_> :/
[12:31:42] <LeoNerd> They really are, though. I've spent 15 years being both an opensource hobbiest and a commerically paid programmer
[12:31:45] <_ami_> a open source enthuasist would have fixed it., since he was paid to write those linux drivers.. he won't bother
[12:31:53] <LeoNerd> Hands-down without question all my best work was the stuff I *chose* to do in my spare time
[12:32:08] <_ami_> indeed!
[12:33:07] <LeoNerd> Anyway, since there's three other kinds of chip available, I can just use one of those and ignore the CP2102
[12:33:47] <LeoNerd> In related news: Where's my CH340s??!
[12:33:48] <_ami_> LeoNerd: can you report this to linux kernel ML?
[12:33:51] <LeoNerd> Hah
[12:33:52] <LeoNerd> hahah..
[12:34:06] <LeoNerd> I have point-blank given up trying to hold any kind of discussion with a group that big
[12:34:11] <LeoNerd> It *never* turns out to be useful
[12:34:18] <_ami_> oh, okay.
[12:34:50] <LeoNerd> Unless you are literally just providing a patch of code, there's just no point talking there
[12:34:55] <_ami_> if i compare this with EFL opensource group. we are pretty responsive. we fix bugs if some one reports on phab or ML
[12:34:57] <LeoNerd> It will get drowned in silence
[12:35:34] <_ami_> although we encourage them to post issues on Phab.
[12:35:48] <_ami_> https://phab.enlightenment.org/
[12:36:15] <LeoNerd> To be honest, I don't really like any sort of project where the number of people in charge does not equal 1
[12:38:44] <_ami_> time to sleep
[12:38:48] <_ami_> nn
[13:11:44] <ferdna> any comments on eagle being purchase by autocad =|
[13:15:07] <twnqx> "couldn't autocad afford anything better"
[13:15:55] <Thrashbarg> heh...
[13:17:48] <twnqx> autodesk, i should say
[13:22:50] <Strangework> lol
[13:34:34] <LeoNerd> Ooh, this is rather cute. BMP280 is a pressure/temp. sensor that operates as either SPI or I²C slave... but it doesn't need a separate configuration pin to choose which. It simply samples the SS line on powerup. If it's high -> SPI. If it's low -> I²C
[13:36:11] <ferdna> twnqx, yeah autodesk... lol... my bad...
[13:36:22] <ferdna> so will everyone move to kicad?
[13:36:33] <twnqx> i doubt there will be much change to begin with
[13:37:33] * twnqx is still an Eagle Pro license holder
[13:37:49] <twnqx> though yeah, gonna take a look at kicad for my next project :P
[13:38:06] <twnqx> need some advanced features for impedance control and length matching
[13:38:19] <twnqx> all those 5-6gbit/s serial links :X
[13:40:24] <aandrew> twnqx: as am I, for v6
[13:40:35] <twnqx> purchased at 4, still current at 7.6
[13:40:45] <twnqx> definitely going to check out kicad before 8
[13:40:59] <aandrew> twnqx: heh same here, except I stopped at 6. wasn't going ot pay for pretty icons
[13:41:06] <aandrew> I moved on to altium
[13:41:10] <twnqx> uhhh
[13:41:19] <twnqx> a friend of mine does nothing but complain about it
[13:41:30] <twnqx> (if he's forced to use it)
[13:41:58] <twnqx> but he also complains about eagle and how bad it is
[13:42:40] <twnqx> i'd really love to see experienced users of the various softwrae duke it out with a given project :P
[13:42:50] <aandrew> heh
[13:42:55] <aandrew> I loved eagle, I really did
[13:43:07] <twnqx> eagle has tons of things i like
[13:43:11] <twnqx> and tons of things i hate
[13:43:17] <twnqx> part numbering e.g. is... bad
[13:43:20] <aandrew> it just failed to grow up. I think that when element14/newark bought it they had no idea what to do with it, so it languished
[13:43:48] <twnqx> and the fact that it took them until 7 to get arbitrary smd pads
[13:44:04] <twnqx> the component library system is a nightmare at best
[13:44:13] <twnqx> yes, it got better with the xml format
[13:44:27] <twnqx> because now you can use a text editor to be faster then with the graphical editor
[13:44:33] <twnqx> than*
[13:45:25] <aandrew> yes, but the XML used is a little wonky. you ahve to change in two places things that should only have to be changed in one place (net connections in particular)
[13:45:34] <twnqx> yes.
[13:46:06] <aandrew> their meander implementation is the brainchild of a team working in complete bongsmoke
[13:46:41] <twnqx> their inability to use custom fonts
[13:47:19] <aandrew> that one didn't bother me so much, but little things like net labels being RIGHT ON THE LINE and needing to be manually nudged up to be legible...
[13:47:46] <aandrew> dunno. it'll always have a place in my heart but I will charge a premium if I have to use it
[13:59:35] <bss36504> I really only know eagle. I tried kicad a little bit and the interface almost gave me a brain aneurysm
[14:00:08] <bss36504> I'd love to use altium or really any of the top tier tools, but I dont have tens of thousands of dollars that i dont want anymore
[14:00:42] <bss36504> Considering buying an eagle license since the features vs. price is good for me.
[14:01:00] <bss36504> I've kind of just grown used to the annoying bits.
[14:03:27] <bss36504> It's interesting that Autodesk would buy eagle...Most of AD's stuff is, IMO, very polished and high quality. Seems like even if they reskinned eagle, it wouldnt even come close to the same level of quality. However, if I can get a free education license of eagle like you can with other AD products, I wont complain.
[14:17:09] <ferdna> the only problem with this.. is that they are going to make it windows only...
[14:17:14] <ferdna> probably*
[14:17:20] <ferdna> i am a linux user
[14:21:30] <inkjetunito> i don't quite understand the kicad hype
[14:21:41] <aandrew> bss36504: if you're a student you can get a full version of altium for noncommercial use for $100/y
[14:22:21] <bss36504> Is that so...
[14:22:26] <aandrew> kicad looks very, very promising and is used for complex designs *today*. it's funded in part by CERN, and is OSS. That is the hype.
[14:22:27] <bss36504> The more you know.
[14:23:08] <bss36504> I watched the video of the fancy place and route tools from CERN which is actually what made me download it. Didnt even get that far though.
[14:23:43] <bss36504> It's like the interface was designed by people who never used an EDA suite of any kind before.
[14:34:10] <LeoNerd> Tonight's plan: interrupt-driven soft UART for tiny85 to run on calibrated internal RC osc
[14:34:29] <LeoNerd> With any luck I plan to 3x sample the bits, like the hardware USART modules do
[15:01:08] <aandrew> LeoNerd: interesting
[15:01:27] <aandrew> I am actually potentially rewriting an HDL serial port for higher reliability
[15:11:54] <LeoNerd> I'm only doing 9600baud, for telemetry control, so I can afford some oversample
[15:12:13] <LeoNerd> I'll probably run an 8x timer and sample on.. oh. hang on. I don't have to use powers of 2
[15:12:34] <LeoNerd> I could run at 6x times and sample on 2/3/4
[15:12:52] <aandrew> heh so that throws you for a loop too I see
[15:13:24] <LeoNerd> Mm?
[15:13:32] <aandrew> you get so used to thinking in powers of two that you forget that sometimes you can get away with non-2^ numbers without suddenly costing a million cycles
[15:13:37] <LeoNerd> Yah :)
[15:13:54] <LeoNerd> My baud-to-clocktick calculation is done at compiletime in a macro, so that doesn't matter
[15:13:54] <aandrew> I remember implementing a /3 on PIC16
[15:14:02] <aandrew> discovered taylor series
[15:14:07] <aandrew> worked out really nicely
[15:14:23] <LeoNerd> Compiletime-constant division factors are easy though
[15:14:28] <aandrew> yes
[15:14:41] <aandrew> becuase you have "big iron" figuring out the value and plonking it into the code directly
[15:14:51] <LeoNerd> The divide-by-10 is good. I like that
[15:16:16] <bss36504> I sometimes wish you could do more advanced math and meta-programming with the preprocessor. It would be super helpful in certain situations.
[15:17:40] <LeoNerd> Having a more powerful compiletime in C would be nice. But.. meh :/
[15:17:43] <LeoNerd> That way lies Lisp
[15:18:25] <LeoNerd> Rightthen.. where'd I put my tiny85?
[15:18:32] <bss36504> I agree, totally not necessary. but it would be handy
[17:02:31] <GeneralStupid> hi guys
[17:02:54] <GeneralStupid> my compiler does not find the "avr/io.h" but i have the mmcu switch
[17:14:48] <GeneralStupid> Fuck :D i had to install avr-libc :D
[17:18:06] <LeoNerd> Yup
[17:18:36] <GeneralStupid> i guess its more reliable now then with atmel studio...
[17:20:34] <GeneralStupid> we are no atmel experts :D ( wen never use 8 bit stuff, normally ) so atmel stuido looks right. But two full payed engineer days for fixing it is nothing we can explain to our boss
[18:11:29] <Casper> GeneralStupid: hehe but yeah sometime it's a small issue that eat tons of time
[19:22:13] <rue_bed> whats the smallest mega the 328?
[19:22:17] <rue_bed> pincount wise
[19:29:35] <iwancoppa> rue_bed: AT90PWM* series come in 24 SOIC
[19:30:16] <iwancoppa> apparently some are in 20 pin SOIC too
[19:33:00] <rue_bed> oh dip, but low pin count
[19:33:18] <rue_bed> I need a uart, and 3 sets of bitbanged serial
[19:37:17] <iwancoppa> Attiny441 is 14 pins, and has a hardware uart
[19:38:19] <Lambda-Aurigae> atmega88/168/328 is the smallest physical atmega in dip package as I recall.
[19:40:15] <iwancoppa> Not sure if you're going to easily find a small dip atmega/attiny - what's the issue with soic?
[19:41:53] <rue_bed> hmmm
[19:42:10] <rue_bed> tiny441 has an async uart built in?
[19:44:11] <Lambda-Aurigae> two of them.
[19:44:20] <Lambda-Aurigae> two full duples usart with start frame detection.
[19:44:33] <Lambda-Aurigae> soic
[19:44:39] <Lambda-Aurigae> 14 pin soic
[19:44:44] <Lambda-Aurigae> no pdip
[19:46:15] <Lambda-Aurigae> attiny26 has a UART in a pdip-20
[19:47:09] <rue_bed> not sync uarts, async
[19:47:32] <rue_bed> the attiny26 uart is sync, useless for pc serial
[20:10:45] <iwancoppa> rue_bed: correct me if I'm wrong, but any AVR USART is configurable as a UART
[21:01:45] <rue_house> not easily as an asynchronous uart
[21:01:51] <rue_house> async has start and stop bits
[21:06:08] <rue_bed> and no clock line
[21:07:23] <cehteh> its possible to define an external clock for the usart
[21:18:08] <rue_bed> having it do async framing would be a pain tho
[21:33:46] <iwancoppa> rue_bed: I'm pretty sure the USART on the 441/841 supports hardware asynchronous transmission as well as synchronous
[23:47:26] <_ami_> my pkg from Silicon labs is stuck at custom. their object is the difference in invoice and actual bill. :/
[23:47:32] <_ami_> WTF!
[23:47:44] <_ami_> objection*
[23:48:23] <_ami_> few items price are marked as 0$
[23:48:47] <_ami_> it is 0$ because its sample only.
[23:48:54] <iwancoppa> fucking hell
[23:49:06] <Casper> this is also why they put less and less the real bill inside the package anymore
[23:49:06] <iwancoppa> Customs is the true nanny state department
[23:49:19] <_ami_> weird custom rules. is this happen with anybody else?
[23:50:09] <_ami_> i requested SL to provide me new invoice with mention "Sample only"
[23:50:21] <_ami_> waiting for their reply.
[23:50:51] <_ami_> total cost of the samples are just 6$
[23:52:02] <_ami_> i wonder VIPs here are allowed to roam whole world with loads of cash and people who actually try to do some good by doing R&D in house are questioned.
[23:52:19] <iwancoppa> Well, atleast you're getting samples. Grr atmel grr
[23:52:32] <_ami_> custom makes exception for VIPs but not for common people.
[23:52:38] <_ami_> iwancoppa: i still did not get it.
[23:52:46] <_ami_> i need to do some paper work.
[23:53:08] <_ami_> according to shipment company DHL, they require original priced bill
[23:53:57] <_ami_> iwancoppa: i did not ask for samples only. i bought few items also from SL.
[23:54:54] <_ami_> Casper: the Aliexpress seller do this trick all the time just to avoid custom :)
[23:55:15] <Casper> yes, like in canada, <20$CAD = no custom no tax
[23:55:16] <_ami_> they mark shipment as GIFT also :)
[23:55:46] <Casper> >=20$CAD = 15% tax + random custom fee
[23:55:58] <_ami_> Casper: 30$ for us (India)
[23:56:56] <iwancoppa> Eek
[23:57:06] <iwancoppa> Easiest option is to probably go down to the customs office with a box of donuts :P
[23:57:20] <_ami_> haha :)
