So i'm just about to the point of pulling my hair out... I have the USB IR Toy V1a, and i hook it up to my computer. I point the driver install file to the firmware v11 driver directory and it installs as com2. I updated to that version of firmware. I can't get it to do anything with BP_LogicAnalyzer.exe and winLIRC IRGraph shows tons of ir being received, as does the "I" LED flash repeatedly (when i'm not using a remote control). I built the through hole version and it seems to work fine (for my limited knowledge of the logicanalyzer software). The irgraph with LIRC shows what i would expect to see and i don't see a constant stream of IR coming in, just when i use the remote. Any clue what may be going on?
Wow, thanks for your thoughts on the subject. Helps me understand much more than i have until now. I'll get a PICKit of some flavor (2 or 3) ordered right away :)
ok... i was just worried that the pickit was somehow "crippled" versus the ICD. I guess i'm just not sure what the difference in use between the two are.
Ian, is the main difference between the pickit and ICD that the ICD allows more debugging? For the occasional user would the pickit be sufficient, or are there basic things that would make the ICD a worthwhile investment?
I have the through hole version of the IRToy, and was wondering if it's possible to program it via the Bus Pirate. I've never really dealt with programming a PIC before, and not sure how to proceed. I tried looking through the forum, but maybe i'm just looking in the wrong places. From what i understand the BP's PIC Programming Adapter is just for if you need a higher voltage supply, or is that required for programming all PICs?
Is there plans to implement RSS feeds like the old board has? Maybe i'm just overlooking it, but i'm not seeing it. I liked the fact that i can keep up with the goings on by just subscribing to the whole forum and read it in RSS reader.
Ok... so i got it working. For some reason, device manager thought it was a "Broadcom Bluetooth 3.0 USB with AMP". I just downloaded the FTDI driver, told it to upgrade the driver for "Broadcom Bluetooth 3.0 USB with AMP" and pointed it to the right driver, and that straightened out the bluetooth issue. It still wasn't working... Then i saw it under other devices... USB Serial Port with no driver installed... pointed it to that directory again for its drivers, and i can access it just fine. Hope that helps someone out.
I'm going to investigate to see what the issue is, but wondering if any of you have ran into similar issues. I got a new laptop, and as soon as i connect the BP, it kills my bluetooth (internal DW375 bluetooth module on a Dell Latitude E6510). I disconnect the BP and bluetooth is still dead. I have to reboot, and it works fine until i plug the BP in again. I know the BP is good because i have used it on my old laptop several times.
If i find something, i'll post the solution in case anyone else can be helped by it.
[quote author="rsdio"] One important aspect is that I think you're rarely going to find a channel that has unchanging video.[/quote]
To make sure i understand, are you saying that the video characteristics imply that even if the picture is frozen (i.e. the receiver has locked up), due to the fact that the picture is being modulated, then demodulated on the other end to composite video, and it appears visually that it is constantly showing the same video, that there will probably still be changes in intensity, color phase, etc? I'm trying to test for that scenario of picture being there but frozen, and the scenario where you just have a completely black screen.
I'm trying to figure out how to do something, and thought you guys may be able to lend some suggestions. I'm trying to make a device that can be connected to the video out of a cable box and scroll through the channels, and have a video input where it could analyze the video to determine if the video is chaning. It doesn't need to be high resolution, just determine if the video changes more than X% threshold over Y amount of time. I found an arduino shileld that may work, but the parts are a little higher than i thought (i think because of the sampling rate that they support). The schematic for that shield is at http://homepage.mac.com/dave_chatting/a ... ircuit.png
Does anyone have knowledge of NTSC video that can tell me if that's the best way to go, or could suggest a better/easier/cheaper way to do it? It's essentially a "channel checker" box that verifies that all channels are good, and when it determines there is a bad channel, it does some sort of digital action. It is fine if it has to set on the channel for 5, 10, even 30 or 60 seconds to get enough samples to determine if the video is chaning (which i am assuming means that the channel is good) or not.
Cool, thanks! I looked for an example but couldnt' find it. I also determined my issue (dumb mistake). I had a 74HC165 instead of 74HC595 (my drawer was labeled right, but had the wrong component in it.
Interfacing to the 595 was the first true thing i've done with the BP, even though i have had it for months and months. I just haven't had a chance to play with it. I can't wait to see what other kind of stuff i'll end up doing with it. Now i'll have to investigate that SPI sniffing info again so I can examine the traffic between arduino and the chip since it works now. In regards to my previous post, do i just not use the clock from the BP since clock is being sent from the master to the slave and it's sitting in between, or how does that work?
I also have the OLS if that's better at sniffing the traffic (if it can sniff SPI)
Ok, i'll admit i tried to look through the documentation and forums, but what info i found was a bit over my head. This is my first venture into SPI (or much bus work at all). I'm trying to determine whether my project between an arduino and a 74HC595 is not working because of the arduino or because of the 74HC595. I have followed their examples and using their schematic and code (tried a few examples and double checked my work) but nothing seems to work. I'm trying to send data to the 74HC595 to tell it to turn on whichever output pins between 0 and 7 to light LEDs. This is just to play around with to understand the chip. The examples i'm using are using software serial and have arduino connections for 5VDC, GND, Clock, Serial out, and Latch which connect to the 74HC595 pins Vcc, GND, SH_CP, DS, and ST_CP respectivley. I assume i connect BP GND to GND and BP MISO to Serial out/DS, but i'm not sure whether i connect clock to clock/SH_CP, or leave it disconnected. The connections drawing at http://dangerousprototypes.com/docs/SPI indicate that it is for BP Clock OUT, so that's why i'm confused if i need it since the arduino is providing clock.
Would it be easier to connect inline to sniff this scenario and determine what bits are being passed, or easier to be a slave to the arduino and see what is being sent, then be a master to the 74HC595 and try and pass it bits?
I hope i have explained this well. Let me know if i'm just missing some basic concepts, or how you would suggest i proceed.
