|
Astoundingly good demo
Hi mister_e & all who have contributed. I am quite new to PBP and this is my first post to this list. I just found this demo a week ago, read the thread, ordered the parts, assembled a proto board on Saturday and - (insert Windows USB Device da-dink! sound) it worked FLAWLESSLY, the first time. I am either lucky standing on the shoulders of giants - but oh, my, what a good feeling.
I have been tinkering incessantly since then.
Thank you for giving me super powers.
|
Take my advice...Give out while you still can...Originally Posted by semiuniversal
I have lost countless hours of sleep playing with USB and that demo, spent untold amounts of money, not to mention ticked off the wife numerous times...
Seriously though...Good game...
I wish other Noobs would take that as an example...especially the part about 'reading the thread'....
|
Using USBDemo with LONG variable (PBPL)
NOTE: If your going to use LONG variables, you MUST copy the PIC18Xxxxx.BAL file in your source directory as well, unless you'll receive some compilation errors.
The .BAL file is located in \PBP\USB18 directory.
If you're using PIC18F4550, you MUST copy the 18F4550.BAL file in your source code directory.
@Darrel.. is this possible to paste it in the first post as well as the other source code (or link) for the other PICs (post 99 http://www.picbasic.co.uk/forum/show...8&postcount=99) ?
Last edited by mister_e; - 4th April 2008 at 19:21.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
Done!
DT
|
$20 says a dozen people miss the 18Fxxxx.BAL note...Done!
|
Couple of Questions
Ok so first of THANK YOU to everyone.
I'm much further than I was a year ago already...which is a device windows enumerates....
Now for the problem
So i have a 2550. I commented out the old .inc file lines updated the ASM line to reflect the proper PBP version i have, implemented the corrected Fuse settings for the 20mhz crystal. and When I plug up the device to Windows I get "USBDemo" then it changes to two different things Hid compliant device and USB Human Interface Device. Then The HID compliant one disappears...then the USB Human Interface Device Gets an ! over it...
If i run the USB demo VB program the Device Manager Updates and sometimes It will remove teh USB device all together...or sometimes just change to a USB Unknown Device.
WTF?!
Earlier I plugged it in and the DEMO vb Recognized it and displayed the RX data for like...20 loops....then then everything stopped. it didnt recognize the usb device anymore as the Mister_E USBdemo that the program previously displayed...
Other than the ASM changes, "DEFINE OSC 20" and fuse changes ....i haven't changed anything software side. Hardware I have a .33uf because well...the store had a .47uf in 300volts size..and that was to large for the board..and kinda ridiculous. PBP version is 2.46
Is there a setting in MELABS programmer for the internal pull ups? I saw there was on in the code..but maybe it was being overwritten?
I've been toying for 3 days now...re reading the thread and looking at others...
Also...I dont have a .BAL file...*.bal search turned up nothing.. GR....
Anyone?
Last edited by UnaKRon; - 7th June 2008 at 02:53.
|
Which are rather large changes considering you have to have the right freq for the USB to run right in the first place.
Don't know if it'll fix your problem or not, but there is a 2.46 patch, and a few updates for $25 that gets you up to PBP 2.50A. A few fixes for USB and PIC18F types. Might help, might not.PBP version is 2.46
Internal pullups on Port B are described in the datasheet for the particular PIC.Is there a setting in MELABS programmer for the internal pull ups?
And you won't unless you're using PBP 2.50A.Also...I dont have a .BAL file...*.bal search turned up nothing.. GR....
Members who have read this thread : 1You do not have permission to view the list of names.
Posting Permissions
Bookmarks