Bonkers

I really appreciate the option you've given, but sadly I've a few other demands on my time right now - so I'll probably wait for the formal release, and pick it up next Thursday or so. I've also recently bought a I2C analyser, so I'm hoping to debug the HW I2C better - but it's not a huge priority since SW I2C is working fine. I'll start a new post on that. best regds

Glad you're in agreement, I don't really understand why Comp.Sci isn't taught like all other subjects, going from the particular, with concrete examples, to the general. Computers are not difficult if you start with small tasks in assembler. Who else builds a house from the roof down? Latest build? - Yes please :)

Sorry, that just looked good enough to post, to close the point. Even the prime founders of computer science rejected the unnecessary complexity and obfuscation imposed upon it. I'm hoping that the forum here is of a similar mind, and recognise that simplicity is not unsophistication. That's why we like BASIC, it's perfectly good enough and it works - with no need to learn geeky syntax. What's wrong with "For I = 1 to 10 ... Next I " versus "For I < 11, I++" - and a critical lone apostrophe somewhere...

Brilliant :) my thoughts? - we're on different time zones so it's a bit like postal chess. I will test the sourcefile compiler constant shortly, it's a classic substitution move, from a thing that can go wrong, to a thing that can't. Nice play. On formatting, bear with me, I should master it. Regarding the #include tree: my interest is in being able to drill down into what the compiler does, and where it gets it from - principally so that there is the possibility of further analysis if it is not...

So sorry for the delay in responding, I was expecting an email alert but failed to tick the "subscribe to this topic" box. You've cracked it, I just needed to put the #define in quotes, that was all ! > #define Version V26g ; doesn't work, undeclared variable V26g #define Version "V26g" ; with quotes ! - works perfectly, compiles... I've also taken the trouble to find the "formatting help" tab on the left - many mysteries solved - but not quite working yet - the ">" should put my code into blockquotes,...

I normally use a first-line comment to keep track of code version, like "; logger code version V26b " Later, there is a print instruction to embed it in my log file, I'm using OpenLog which takes ascii input. This is simply a manual duplication - i.e. " Ser1Print "this is version V26b" - but it means I need to update both and I often forget. Thirdly of course there is the filename, which has the version as a suffix - like "logger3 V26b.gcb" - I'd like to #define "version" as my version number - like:...

Thanks Gigi, you are correct in identifying the crystal capacitive loading as the parameter that needs to be adjusted. I've not seen parallel capacitance mentioned before, and I'm not sure it would work - normally it is two capacitors to ground that need to be adjusted. This can't be done properly with any old sample crystal - the crystal itself might be 5ppm "sharp" - i.e. within tolerance but not "bang-on". If you adjust the capacitors for this one, you will bias the 32kHz frequency to one side,...

I'm glad you agree, we see a similar confused landscape. I seek to understand what PPS defines and what it leaves to the user-program (or compiler). The PIC 18F05/Q40 says the following, on P394 of datasheet: Important: The pin locations for SDA and SCL are remappable through the Peripheral Pin Select (PPS) registers. If new pin locations for SDA and SCL are desired, user software must configure the INLVLx, SLRCONx, ODCONx, and TRISx registers for each new pin location. The RxyI2C registers cannot...