PBP projects for R/C models

[Kenjones1935]

Trial and error tells me that the only way to reconnect hyperterminal via C4 (the USB) to my BITWhacker after physically dislocating the connector is to be holding down the RESET switch while inserting the USB connector.

Anybody see that written down anywhere?

Thank you both for the leads to documentation of this thread.

Ken

[ScaleRobotics]

Trial and error tells me that the only way to reconnect hyperterminal via C4 (the USB) to my BITWhacker after physically dislocating the connector is to be holding down the RESET switch while inserting the USB connector.

Anybody see that written down anywhere?

It is sort of documented.....

I think this is an effect of having the bootloader resident on the device. You "should" be able to either have the bootloader resident, with StickOS in the program memory (sort of underneath it). Or, to get rid of the "feature" you found, program over the whole thing, using your Pickit2 with the StickOS with the shorter name (not meant for bootloaders). Though I am a little hesitant to have you do that to the working device. Better off trying this on the non-working one, and see if we can revive it.

I think, then you would have it immediately recognized when you plug it in to a port, without pressing a button.

When I say sort of documented, it is at the bottom of the UBW32 page here: http://www.schmalzhaus.com/UBW32/doc...mentation.html Does this explain what you have found?

In my search, I also found a page that has the pinouts for the device in a readable format. http://www.schmalzhaus.com/UBW32/doc...easeNotes.html

As for your question about the other off topic thread: We had a member graciously volunteer to build some StickOS devices. But it is a fair amount of work, and somewhere between the commitments of family, work, (and I think even moving), it has been understandably delayed a bit. So we are all living vicariously through you right now. (Although I do have a piece of hardware that I can get a command line interface with StickOS, just not via USB.) There is also a StickOS simulator for PC's lcated here: http://www.cpustick.com/downloads/StickOS.v1.80.exe But the simulator would have different pin names than your hardware.

And as for cheaper, the Eagle board files for the UBW32 are available at Sparkfun's site. Although you sound a bit skeptical (as was I) about soldering a device like that, most others seem to find it very doable, to hand solder these devices (and the rest use toaster ovens). Doing this, with a fair number of boards, would make it much cheaper than the $40 a pop. For soldering tips, check's out nicmus's response here, and Dave's post just after it: http://www.picbasic.co.uk/forum/show...2872#post92872

[Kenjones1935]

Thank you rmteo,

I enticed MikroBasic Pro to compile its 1st_project 'blink the LED's' Basic code . I then got PICKit2 to download the resulting .hex file. The only mistake was that MikroBasic assumed the LEDs are attached to PORTC. On the PICKit2 card they are attached to PORTD. After that minor adjustment. It works.

KEn!

[Kenjones1935]

Way back I thought a good middle school project would be
to race by R/Cing the car out a door, wait for it to find its way autonomously back through another door (This second door would have a naked 150W bulb at its threshold.), then repeat the cycle some number of times. The R/C - autonomous toggle to be controlled by powering ON and OFF the radio transmitter. If the transmitter's power is ON, the PIC detects activity from the radio receiver and switches control over to the original system.

Advantages of that idea are:
1. No need for proportional controls. A toy level car will do.
2. Photo cells are much less expensive than sonar sensors.

A problem is that the kit requires six DPDT coil driven relays: two for PIC generated steering, two for PIC generated wheel control and two for toggling between PIC control and R/C control. These are inexpensive, but add complexity in kit construction.

This car could also do the swarm-after-teacher who's carrying a naked bright light game. I've been changing my focus from teach-the-student to teach-the-teacher. What do you think? The RC system itself is full of "How things work" answers.

Your thoughts?

Ken

[Kenjones1935]

Wednesday morning I'm going out of town for at least a week. I will not make any robocar progress.

I have one BITWhacker that operates per the documentation. It establishes connection thru the USB and behaves by flashing its lights per "http://www.schmalzhaus.com/UBW32/doc...mentation.html".

The other one has HIDbootloader successfully loaded via PICkit2. It will not make USB contact, it does turn on its LED's, but does not flash them. This too seems to match the above LINK's statements. I have no idea how to get this one back to standard.

My next step is to build that toy level car with the trio of photo cells. Will I need pots to tune each one? I hope not.

Ken

[mackrackit]

POTs would be best to fine tune things but if you are in a very dimly lite room and have a very bright light then you might be able to preset the sensors with fixed resistors.

[Kenjones1935]

My problem loading the BITWhacker PIC32 from PICkit 2 is that it is not capable of doing so. MPLAB tells me that I need PM3, REAL ICE, ICD2, ICD3, or PICkit3.

MichaelS referring to PICkit3 said in a September 2010 entry:

# The application supports all devices supported in MPLAB 8.56 except PIC32. This is not to say it has been tested on all devices. If you have any problems programming any devices, please leave a note here or send me a PM.
# PIC32 support is coming very soon. I have stable support working in my current development builds.

See you in a week or so.
Ken

[ScaleRobotics]

My problem loading the BITWhacker PIC32 from PICkit 2 is that it is not capable of doing so. MPLAB tells me that I need PM3, REAL ICE, ICD2, ICD3, or PICkit3.

MichaelS referring to PICkit3 said in a September 2010 entry:

Yes, MPLAB doesn't like the Pickit2 for use with PIC32, but who needs Mplab to load the Bitwhacker? All you need is the Pickit2 programmer IDE. I get the message saying "Programming Successful", and the command line interface I get after doing so. The Pickit2 is perfectly capable of programming PIC32 chips. Otherwise, it would not have a drop down menu including them. I don't quite know why MPLAB is forcing the use of other programmers, but you don't really have to worry about it.

[ScaleRobotics]

Here are some that were referenced in the thread. None of them use your chip though, so some modifications would need to be made, or changes to a new chip.

A 12F683 design (would require a fair amount of changes to work on your chip)
http://www.picbasic.co.uk/forum/show...4998#post84998

This one could not be modified for your chip, and would require a 18F2431, or 4431.
http://www.picbasic.co.uk/forum/show...1961#post91961 (cleaner code than above)

And the one rmteo pointed out, which would require an 18 series chip: http://www.picbasic.co.uk/forum/cont...e-Servo-Driver (Darrels, so you can't really go wrong)

Once you decide which way you would like to go, I am sure we can help you get it going.

[Kenjones1935]

My video shows my kit uses a 0.1" centers solderless prototype board. If I am to change PICs I would like something compatible.
I tried the 32BITWhacker board of 32MX460. I was disappointed because I could not program it using the PICKIT2 system. Maybe if I purchase a PICKIT3.....(It is programmable via its USB port. That requires I completely change my coding system and learn yet another variation of BASIC or C)

What Microchip PIC do you all suggest that has a Dual Inline (DIP) configuration and is easily programmable?

Ken