Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TimV

  • Rank
  1. Hi Dave: I am up and coding. The #pragma worked once I took out the spaces between the &'s. What can I say? I picked up some documentation for C from the Microchip site and that's how it was written. All my Dim's pass as do all the data variables using 0x to denote hex. I am now working on the output routine for the 7219 Thanks for your help. No doubt I will be posting again soon. Tim
  2. Hi Dave: I shall try that when I get home. Since the Max_7219 uses a 16 bit word, could I not just combine the address and data that I want to send and pass the whole thing? It would end up being 0AFF in this case. Would it be better to send that, or break it into two bytes as I currently do? Thanks Tim
  3. Hi Dave: I changed all my $ hex symbols to &, but after saving the file, the compiler exits on #pragma DATA _CONFIG, _WDT_OFF & _HS_OSC & _LVP_OFF & _CP_OFF & _PWRTE_OFF with exit code 1 as it did before. It clears with the line commented out. In the samples that I was reading, the comments were all in green. In the editor settings on my installation, both line comment and comment are set to show green as the foreground as well. They are showing in the same brown that is used for character in all locations where I have comments. The #pragma line abov
  4. Thanks Dave I tried this in my code earlier and it failed but I might have had the #include statement in at the same time. I just tried it and the compiler did not object. Thanks Does this mean "&" denotes a hex value? Is there a similar special symbol for binary and decimal? Thanks Tim
  5. Hi Dave: Thanks for the response. Ok.....Not what I was hoping for, but I am up for a challenge. For reference, Pulsout is simply a command in the PicAxe library that lets you pick a pin and send a single pulse (high) out that pin for things like clocking. If you have a couple of minutes, maybe you wouldn't mind helping me get started. In studying the sample code for the I2C, I can see how it is being done in BoostBasic so I'm not all that worried. (Pulsout) In the C code examples, I notice #include and #pragma to set up config bits, etc. The BoostBasic samples do not have
  6. Hi: Is the help file in the Basic compiler the extent of the documentation for BoostBasic? I am not all that familiar with Visual Basic and I see no references to keywords that I am familiar with such as Gosub / Return, Pulsout, Peek, Poke, Lookup, etc. I am migrating from the PicAxe which has a 100+ page manual dedicated to keywords with syntax and usage laid out fairly well. I have read through the examples on the main web site and while I think I can get my head around how things are being done I'm wondering if there might be other resource material that might help. Th
  7. Sorry for the previous post. I found the answer in the manual. Should have read it through first. Tim
  8. Hi All: I have been using the PicAxe product and would like to switch to SourceBoost as it seems more full featured and looks like it will give me full control of all of the ports on the Microchip controllers. I loaded a program which runs on one of my PicAxe chips into SourceBoost and selected "Build All" I had hoped that I would get a list of errors which I could use to convert the code/ instructions. Unfortunately I can't do CTRL+C to grab the error message, but it says thermometer.bas(7): error: failure Exit code was 1. Removing target: _.obj Failed to locate output file '
  • Create New...