Well whats next?! I absolutely love your development tools; eg:
Of course the Bus pirate-> gives us communication help and development OLS & Logic Shrimp-> gives us the abillity to analyser our software Bus Blaster-> JTAG development FPGA Breakouts-> FPGA development Multiple other breakouts-> rapid development with the help of pre-built circuits Super Robby-> Multi-tool Dangerous DSO -> why dont you sell these yet? and more..
I would love to see more projects like these. I think you guys do a great job with these projects and they are extremely usfull in my day to day electronics 'tinkering'. But whats left? What other tools can you build that doesn't already fall under one of the others?
Heres my ideas: 1) Finish the D-DSO and start selling them. I need a cheap o-scope. 2) Super Robby. I would like to see you create an electronics multi-tool like the super probe of your own. I can think of 100s of tiny tools for this thing, beyond the basic. Like a simple LED tester, transistor tester, crystal tester, be able to poke it into my breadboard and monitor the power supply during certain tasks, and more... 3) Power supply. perhaps controllable via terminal. that would be sweet. 4) Function generator. This is the only 'major' tool you guys have not dipped into yet. I would love to see an add-on to the OLS thats a function generator (where the unbuffered ports are). And be able to generate signals setup in the terminal. And best of all, be able to play back saved capture files with a press of a button. That would rock. Is that possible? Is there spare pins going to that section that could be utilized to do such a thing? 5) I would like to see the bus pirates pic programmer add-on board completed.
Some other, off the wall, ideas: *-? I would like to see an OLED LCD that is a terminal. I think it would be sweet to, for example, connect an LCD to the bus pirate and be able to put te bus pirate into listen/monitor mode and be able to see the results from the LCD instead of a PC. Then I could do whatever on the PC while still watching my circuit.
Other users, please contribute. What would you like to see dangerous prototypes build next? I am very curios to see what everyone would like to see built. And I always like hearing ideas that I may be able to build myself. I always find the hardest part of electronics, is deciding what to build next.
On a side note. I think you should switch from RED pcbs to Orange. I think the Orange looks better (the traces look awesome) and red is used by everyone these days. If you made Orange PCBs it would stand out a bite more as DP products.
I dont have a box like that; but I do have 5-6 analog digital IC boxes. There plastic with a push through foam on the bottom and then a soft foam on top of that to hold everything in place. I could put all the IC's into those and then drop them into some at-bags. And there pretty nice size. I would estimate about 4/5's the width of your box and 3/4 the height. Other then them being plastic see through its basicly the same as yours.
Also. I have a few silica dryer packages which include this peice of paper that changes colors if the silica is getting old or the ICs are getting to moist. It might be smart to throw a few of those in with the ICs (some open and some still closed, so if the next guy gets it and sees the paper starting to turn red, then open a new silca pack and replace the old ones.. so the ICs stay good during shipment.) There specifically made for traveling ICs. I could part with a few of those; enough to last quite a few trips around the states/world.
Do you already know what that fuse is set to by chance? Lets say the FWDTEN is 1 (always on) How do you go about changing the WDT timer value? Is that also via fuses or in software? What about setting the timeout value?
yeah this would be sweet. I have a couple things I could part with perhaps anouther use could use. including:
EDIT: deleted the stuff i listed. Supposed to be secret :)
im in!
What types of parts are we talkin here? If its chips I have tons of chips; all sorts of differnt functions. If its modules; I have a few modules XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (edited) Whatever it be; I would totally stock that box with a few extra goodies for the next guy (without overflowing it of course).
someone want to send me some dac related goods? I will send you back a surprise (I promise it will be of equal or better price :) I normally dont do much with analog, except maybe an ADC now and again. I would like to try my hand at some analog circuits but have no parts nor the knowledge of whats good. So if someone sends me a 'goodie bag' of DAC related parts i might need. I will send back some neat toys.
In your code it looks like you are setting RCON to enable WDT. but what about FWDTEN? Is that similar as in changing a bit? unsetting it I guess. Perhaps you need to set both? Set RCON and clear FWDTEN?
that snippet sounds like you have two options:
1) Set FWDTEN and have wdt on all the time. Or 2) Clear FWDTEN and then you are able to set WDT with RCON
Yoga, if you see the schematic @ http://dangerousprototypes.com/docs/ima ... e-v3.5.png there is the CTS and RTS lines (+ tx rx) from pic to the ftdi chip, those are the 4 lines. Those are the request to send and clear to send signals.
I hope I dont get destroyed for asking this but its worth while. You are getting an incorrect device error; and you built a BP from a blank PCB correct. Did you purchase the correct pic?
I am a bit confused. What is the 'demon' core exactly? From reading about it; it seems like a seconday firmware i could put on my OLS. Is that correct? if it is; which is better the one provided by gadget factory (the one I have installed on the OLS) or the Demon core?
So the schematic is wrong, it looks like the AVR pin is going to the base with a 10k resistor (good). b
but it still isnt right; the pad is connected to the collector? and its emitter to +5v? perhaps its just a rare transistor, i dont know :) its labeled t06 40.
Everything i have found on it says its incorrect if the duty of the part was indeed to run leds. the way its hooked up it looks like the powering the device or somthing... i dont know..
maybe i will take out the transistor, connect an LED in its place so when the pin is low the LED is connected +5v through the resistor ( will leave at 10k) and perhaps run a second line to the pad. Then I can have one pad that when in use lights up; which would be sweet.
The top right pads, the top 3 are IR-/+/d for a remote. I will keep that but overtake everything else for a different project. One friend asked if I could make him a simple fan controller for his new pc. maybe i will use this. the attiny45 in it has a temp sensor but i might take 2 DS18b20's so it has multiple sensor areas. The fans themselves have small on/off switch which I will take over; this way I dont need to make a circuit to power the fans. I will just use a transistor to emulate it being switched or something. Then I will use the on-board serial to talk to a serial enabled LCD backpack to output the temp, then perhaps just use the extra pins for override buttons.
Im not a pic guy (yet, i will learn) but i know with the AVR series microcontrollers to enable watchdog on certain AVRs a programming fuse must be set. I just did a quick google search of 24f wdt fuse and came up with:
Quote
Inside the PIC there are things called ‘Fuses’. These are not the same as the fuses you would find in a mains plug, but electronic switches which are ‘blown’ by the programmer. Now, one of these fuses has to be ‘blown’ in order for the WDT to operate. There are two ways of doing this. One way is to write a couple of lines at the beginning of your program to tell the PIC programming software to enable or disable certain fuses. The other way is to tell the PIC programming software manually which fuses to enable.
You said it can be enabled in software; is that what you meant? it looks like:
[ASM] OPT equ 81h
Again, i am not familure with the PIC instruction set. so if im way off, dont abuse me :) just perhaps a reminder maybe?
Some other user asked about catching UART data with the bus pirate then playing it back some other time. So out of no projects at the moment; I decided it might be neat to do that with the OLS capture file.
If I could feed an MCU the capture results and have it emulate it down to the .US. I would be satisfied. but when I opened one of my capture files I was surprised that it wasnt as simple as i thought the capture file would be. I thought it would simple have 1:<time> for it going high or 0:<time> for it going low. but it looks like:
looks like you would expect but. at 0 the line whent low (ok maybe 1 to 0 @ 0) but then the line goes back high at 638.550 US not 235720 whatever. So I played with the numbers for a while but couldnt figure out.
The circuit was a simple TSOP382 IR rec. Naturally high.
Alright. Its still doing it. its a bit differnt this time around; its still zoomed in. but showing the lines. but at first glance it looks like it captured nothing, even though on a trigger.. then you zoom out and see the wave.
I have goto meeting on my machine, if you are interested in seeing it just let me know.
One other thing i noted, is in 94 i can just open it up, hit capture and hit ok and its the same settings as before so I can jump right into it. In 95 I always have to start by selecting 'device-> ols' and then go into the capture settings, fix them, and then go to capturing.
