PBP projects for R/C models

[Byte_Butcher]

Yep, the "D" package is SOIC (Small Outline Package)

You would want the "N" package for DIP. According to the TI data sheet, the "J" package is obsolete.

Don't feel bad, You ain't the first one to order parts in the "wrong" package.
I've got a few 16F727's sitting here that I meant to order in a nice compact 44-tqfp package and instead I ended up with these HUGE 40 pin DIP's. Cripes, they're bigger than the whole circuit board they're supposed to go on!



steve

[Kenjones1935]

The hobby car using HPWM seems to behave correctly.

I need to calibrate the wheel torques associated with the various PWM pulse sizes. The steering servo seems slow. I know it can work well because it did so with the radio receiver in charge.

My proto is too fragile to run the car on the floor. I have it up on a stand making the wheels free. It runs on its own 7.2V battery unattached to the USB port. I can make it think there are walls near by using an oak cutting board to fool the proximity detectors.

Once this thing makes sense I will post a video.

Ken

[Kenjones1935]

Suddenly and without warning my PICkit2 programmer is not doing its job. See this picture. Any ideas? I can get rid of the Code Protect by erasing. Then it comes back. The memory error just starts happening...



NUTS! Or am I repeating myself.

Ken

[mackrackit]

Maybe it got turned on here?

[Kenjones1935]

Ladies and Gentlemen:

My project and I have a problem. PULSIN is putting zero into its target register even though my PICkit 2 LOGIC TOOL sees a reasonable pulse. See picture, below.

It is happening on the inputs from both SRF05 proximity detectors. My code, below, looks for zero and blinks some LED's if it sees a zero. They blink on the very first proximity tests.

Any suggestions? Is my code incorrect? Are there vulnerabilities or idiosyncrasies of which I should be aware?

symbol trigright = PORTB.0 ' Define output pin for Trigger pulse
symbol trigfront = PORTB.1 ' Define output pin for Trigger pulse

symbol echoright = PORTB.2 ' Define input pin for Echo pulse
symbol echofront = PORTB.3 ' Define input pin for Echo pulse

puls:
GOSUB blinkloop0
DEFINE PULSIN_MAX 65535
pulsout trigright,2 ' produce 20uS trigger pulse (must be minimum of 10uS)
pulsin echoright,1,rangeright ' measures the range in 10uS steps

pulsf:

pulsout trigfront,2 ' produce 20uS trigger pulse (must be minimum of 10uS)
pulsin echofront,1,rangefront ' measures the range in 10uS steps
pause 10 ' recharge period after ranging completes

'*****test for zeros******
IF rangeright = 0 then
gosub blinkloop45
endif
if rangefront = 0 then
gosub blinkloop67
endif
return

[mackrackit]

What I see of your code and your description I will guess the code never loops back for a second check.

[Kenjones1935]

That was just a segment of the whole wall racer code.

Here is a short piece written to test the hypothesis that the registers never get set. The blinkloop subroutines are simple blink ten times loops. And, yes, the blinker blink to their little hearts delight.

[QUOTE:]
symbol trigright = PORTB.0 ' Define output pin for Trigger pulse
symbol trigfront = PORTB.1 ' Define output pin for Trigger pulse

symbol echoright = PORTB.2 ' Define input pin for Echo pulse
symbol echofront = PORTB.3 ' Define input pin for Echo pulse

rangeright var word
rangefront var word
CNT VAR BYTE

main:
GOSUB blinkloop01
DEFINE PULSIN_MAX 65535
pulsout trigright,2
pulsin echoright,1,rangeright

pulsout trigfront,2
pulsin echofront,1,rangefront
pause 10 ' recharge period after ranging completes

'*****test for zeros******
IF rangeright = 0 then
gosub blinkloop45
endif
if rangefront = 0 then
gosub blinkloop67
endif
goto main: [QUOTE:]