Recent content by bpowell

Interesting project! Thanks for the detail!

I can't wrap my head around your application ... can you explain what the LDR is doing, and why you're reading it with different ADC's?

Using a 10k resistor and a 100uf CAP, I get a 2-second charge time from 0 - 4V ... so, theoretically, using a ST input, you shouldn't get a HIGH for about 2 seconds after the switch is pressed and held ... you'd want another resistor (1k or so) to discharge the cap when the button isn't pressed.

Maybe a for-loop? When the button is pressed initially, the loop starts ... every 100ms, the loop checks to see if the button is still low ... if so, the loop continues, if not, the loop exits with "Unpressed" ... after 20 loops, you'll know the button was held for a solid 2 seconds....and you...

Is there a separate downloader app? I spend 90% of my computer time on a chromebook ... When I want to tinker with PICAXE code, I remote into a server which has the PE6 installed .... I can write, simulate, and check code ... but if I want to actually program a PICAXE, I need to get to a full...

How is the code downloaded to the PICAXE? Is there an application for ChromeOS that handles this? Chrome extension? Thanks!

It sounds like you need a pull-down resistor on Pin 3 .... you could hook a 10kOhm resistor to pin 3, and that would give it a known state (low) then, you have your switch which is connected on one end to vcc, and the other end to Pin 3 (preferably through a 1k resistor). Also, be sure to have...

Perhaps that's because PE7 is about to drop with C and full ASM support? :) (Man, I am on FIRE with these rumors...)

As far as I know; RevEd never had the SMT chips custom engraved from Microchip ... only the DIPs. So SMT chips will have the actual microchip part number on 'em. On top of that, during the parts shortage, RevEd did sell some PICAXE chips in DIP format that didn't have custom etching (But had the...

Check here ... https://picaxe.com/what-is-picaxe/picaxe-chip-labels/

Sending 128 Bytes from PC @ 230400 bps = 5ms Sending 128 Bytes to EEPROM @ 400khz = ~ 2.8ms + 5ms "write time" I'm overlapping to some extent the PC send with the write-time ... so I'm very happy with 8.3 seconds for 512kB! I tried to rework the PICAXE program to use background receive and try...

So ... I don't know if it's OCD, or what ... but I've been wondering how to speed this process up! Grabbed my 20x2 proto-board, and threw a 512k eeprom on it ... (all I had) and started tinkering. Using HSERIN at 115200 (or 230,400 ... doesn't make a material difference) and removing the...

It would be quite a lift I'd imagine ... the Q-series chips have a lot of changes "under the hood" that Reved would need to deal with ... how I2C is implemented, different SFRs, etc. It would be a job for sure, but would be cool!

Wait!! There's a 32-bit PICAXE releasing soon?! (And the rumors have started!)

I haven't dug into it much; but I believe "Dual SPI" and QSPI are actually half-duplex...In dual-mode, the MISO and MOSI both become outputs, and clock odd and even bits .... so the receiver can get 2 bits per clock cycle...in QSPI, 2 more lines are used....so 4-bits per clock cycle.