BasicMicro - Forums

I've used the ADIN command many times over the years with the older version of MBasic.
Now I can't seem to get it to compile tried and true code.
Here is the code:
; ad test

volts var word

Main

Adin a0,2,%10000000,volts

goto main

When I compile, I get [token 2]: expected variable

Nathan, did ADIN get goofed up in the new version??
I've tried to compile this for both the 877a and the 887.

Help!

Pete

5.3.1.6 uses the new simplified ADIN command. Syntax is adin pin,variable

No clock settings and no ad_setup setting.

_________________
Nathan Scherdin
Basic Micro - Robotic Technology Evolved

Thank you, Nathan. Is there a list of commands that changed or were added? I wasted an hour or so trying to get ADIN to work.
Your loyal MBasic user,
Pete

The MBasic 5.3.1.6 is considered beta so there isn't any documentation on the changes specific to MBasic. Many of the changes are what you see in the Atom and AtomPro manual(the current one, not so much the new beta manual). If you run into anything and want help the quickest solution is to post it. I'm in here a couple times every day most days.

_________________
Nathan Scherdin
Basic Micro - Robotic Technology Evolved

Hi Nathan
Ok I got the new ADIN to work on RA0 (pin 2 on the 16F887): adin A0,volts

I expected that ADIN A1,volts would read RA1. It reads RA2 instead (pin 4)

ADIN A2 reads RA5 (pin7)

ADIN A3 reads RE1 (pin 9)

Is there some kind of mapping that I don't know?
I really want to use RE0 and RE1 as my two analog inputs. How do I do this?

Thanks
Pete

It should just be AX0 = AN0,AX1 = AN1, AX2 = AN3. AX3 = AN4. But it's been a while since I've used ADIN with MBasic.

_________________
Nathan Scherdin
Basic Micro - Robotic Technology Evolved

Hi Nathan
ADIN AX0,volts reads AN0
ADIN AX1,volts reads AN0 (not AN1)
ADIN AX2,volts reads AN0 (not AN2)
ADIN AX3,volts reads AN0 (not AN3)
ADIN AX4,volts has an unexpected token type error at compile
Same error for all numbers above 3

Any thoughts?
Pete

He's right. Using the "AX" numbers produces four identical value reports.
Still investigating.
kenjj

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/

Give up now. I started out to map the ADC inputs and got totally unexpected results. The code looks like:

i started with A0, A1, A2 and A3. The printout reports the #, followed by the resulting ADC reading. You just match up the # (0-3) with the specified pin number to do the map. The early results showed some pins, like A0 and B0, reported to the other three pins! I don't have a connection from the headers to pins A6 and A7, so can't say where they go.
The results were strange:

Somewhere in the pin definitions for this chip, the ADC pins got totally messed with.
Feel free to finish the map.
At least you know how to specify E0 and E1 for ADC: use B1 and B0! I think. E1 also appears on A3. I haven't checked the data sheet for the 16F887, these may have no connection to the real world?!
Later.

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/

PS, the BASICAtom28 and -40 are 16F886 and -887 chips and operate at 20 MHz. Studio is available for free to program these from, but of course you have to pay for each IC to program. Discounts are available for quantity purchases. If you went to the -887 to get cheaper parts, you lose here.
Documentation is available in Studio, but is specifically written for the Pro modules. The new forum manual is all inclusive, but incomplete. At least MOST of the syntax is the same between chips, but not entirely, and internal timings and variable sizes have changed in many places. That is, there is a learning curve.

You might want to consider going to another compiler/IDE. Some are free. Most of the established ones are >>$100. I know. I have three or four sitting on my PC. They are all limited in some way. They are all a pain to work with, for various reasons, compared to MB Pro.
I just purchased the Proton Development System (PDS) for $165. It has a lot of fire power, a long list of devices and features. My principal reason for buying it is that it supports the 18F25K22, which I call "super chip". Get the data sheet, it will knock your socks off.
PDS is damn near 180 degrees out from MBASIC. PDS is like shark fishing in shallow water with a boat hook. Yes, the final catch is amazing to behold, and there's lots to feed on, but getting there is a long, hard and brutal @#$! effort.
Take care.

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/

Any analog pins that are floating near by another driven analog pin will tend to have a value close to that one driven analog pin. I beleive there is some coupling inside the PICmicro processor. As long as all the analog pins you are using have driven analog signals on them there shouldn't be a problem.

When testing which pin is analog make sure all the other analog pins are grounded. Otherwise you may see the analog signal on any of them as well. This is just inductive coupling(external or internal to the processor I don't know).

_________________
Nathan Scherdin
Basic Micro - Robotic Technology Evolved

Yes, internal coupling is a BIG factor. To eliminate this situation I eventually did the tests on a development board because it allowed me to pullup (5V) every pin. So no matter what real ADC pin I read, it read close to 1023, the ADC's highest reportable value. I then went and grounded the pin of interest, in which case it went to 0. After discovering several pins reported bogus values (as Nathan says above), I used FOR-NEXT loops to read JUST the supported pins, which led to faster reports and good values.
Later.

_________________
kenjj
http://blog.basicmicro.com/
http://kjennejohn.wordpress.com/