Oops, my bad. I recommend trying to find ways to shrink your program. I've done the majority of my nixie clock programming on the ATTiny2313, which is a 2k chip, so I know it isn't easy.. Print out your code, post it to this group, I guarantee that there is a lot of space that could be freed up. In my clocks, the trick was in remembering to only keep the data in one place. Everything else in the program references that data or modifies it, but never copies it. Every byte matters. For example, if you have a variable which is a simple True/False flag, that is only one BIT of information. You don't need to define a Byte or 2 or 4 to cover that amount of information.
-Adam On Sun, Jul 24, 2011 at 2:39 PM, Shane Ellis <[email protected]> wrote: > No no no, the memory is much larger, the program I wrote is probably very > primitive, and large. I overran the available memory BY 408 bytes. Picaxe > is good for me, because I don't know another language, and don't really have > time to devote to learning. BASIC does present coding challenges, but I > like the problem solving aspect presented there. > > @Dennis, I'm hoping the Picaxe manuals will cover the eeprom connection, as > an easy memory addition. I looked and for some reason, I have a couple > 24LC256 in my "programming stuff" box, after the youngins go to bed, I'll > figure out how to set this up. I should probably try to shrink my program > as well... > > Shane > > On Sun, Jul 24, 2011 at 3:14 PM, Adam Jacobs <[email protected]> wrote: > >> Holy smokes. Are you serious? The maximum onboard program memory on the >> picaxe is 408 bytes? >> >> .. I don't mean to sound like a religious fanatic, but exactly what is the >> advantage of this platform? I understand that people like to use them to >> program their clocks in basic.. but it seems like you're losing all of that >> "ease of learning" if it means needing to understand how to interface in an >> i2C EEPROM. Am I missing something? >> >> If it was me, I would take this opportunity to switch platforms to the >> arduino. >> >> -Adam >> >> >> On Sun, Jul 24, 2011 at 11:53 AM, Mimewar <[email protected]> wrote: >> >>> It's funny, in the "if it's not one thing, it's another" kind of way. >>> >>> I got two tubes running (0-99), then three(0-999) I get to four, all >>> is well, then I write my entire clock code( no seconds yet), go to >>> program the picaxe, and BAM, program is too large by 408 bytes. >>> So now, I get to (have to) get familiar with Eeproms. >>> >>> On the plus side, I removed a chunk of code ( time after 9:00), and it >>> runs just fine with the four tubes. First time I have ever had four >>> tubes running, and working. >>> >>> Eeproms, here I come. >>> >>> Shane >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "neonixie-l" group. >>> To post to this group, send an email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/neonixie-l?hl=en-GB. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "neonixie-l" group. >> To post to this group, send an email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/neonixie-l?hl=en-GB. >> > > -- > You received this message because you are subscribed to the Google Groups > "neonixie-l" group. > To post to this group, send an email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/neonixie-l?hl=en-GB. > -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To post to this group, send an email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/neonixie-l?hl=en-GB.
