Thread: Anyone currently working with 18f2550

have you done any coms with it, I ported the f88 code to it, only needed port register changes.

Anyhow, powered it up, all looked fine, plugged it onto the mobile phone, nothing from phone.

Plugged it into a serial/usb dongle, garbage.........

I dont have much of an answer for this as I'm using picbasic, its hard to get the commands wrong.........

Noticed it seems to run a little fast, got a 16mhz on it and a 'def osc 16' in the code so I'm puzzled.

I have noticed some programmer allows you set a divider in the fuses, makes me wonder if thats a clue.

Fixed it, I have to set the fuses/config in the programmer software, it defaults to stupid pll /3 and osc/5

setting them to none and /4 works and I get good serial data again.

I suppose if I go with the internal clock then I'll have to set it to /2, but I dont know how stable that will be, early pics when on internal would drift a bit

I mistyped this in a program ( I quickly wanted to blink an LED on portA)

high porta.1
pause 500
high porta.0
pause 500
high porta.1
pause 500
high porta.0
pause 500
high porta.1
pause 500
high porta.0
pause 500

See the problem, they all should be portA.0, so in theory the LED on PortA.1 should light, slight pause, then the LED on PortA.0 should light.

Ha, no it doesnt, well OK it does BUT the first led (on PortA.1) goes out, and instead of 2 leds being on, I get alternating leds ????

Ie

01
10
01
10

I expected

01
11
11
11

?? eh ??

thats really strange. I dont see how it's flashing back and forth with that code. Unless they are too high of a MA LED and it's overloading the port and shutting down.

(mA)

No if I 'for n=0 to 64' I can have them all as normal.

I just downlaoded a simulator and cut and pasted the code into it and get 2 leds on, as sanity says you should.

I actually use porta.0 as door lock signal, and porta.1 as unlock so I dont want errors like this !

I have posted on the picbasic forum, hell its their software, but it works fine on the f88.

I may have an analog setting wrong or something, that adcon, cmcon and other 'con' keywords always seem to cause me bother.

fixed it for now with 'alldigital'

so it must have been a 'con' keyword wrong.

ah yeah, always seems i'm having to tweak adcon or cmcon to get things working right.

good to hear you figured it out