Search results

I think it might have been an EE-08 but not exactly sure. It was probably pre 1970, had the green bowl for holding the light bulb, a couple of old fashioned pointer-knobs for pots, crystal earpiece, no speakers, if I remember right.

Many thanks for all the kind words and it's been a pleasure for me too. It definitely isn't going to be a 'numbed with boredom' future for me; I'm not sure how it could be with a love of electronics, programming and hacking. I have a lot thank to that Philips EE peg board for. And I guess I hit...

Time for a reboot. So just a heads-up that beyond this week I will be enjoying an early retirement and putting my feet up, so don't be surprised when my status shows as "ex-staff" or whatever the forum software offers up. I'm not unplugging the soldering iron, will still be continuing with...

You can do it by just using a variable to count elapsed time ... w0 = 0 Do Pause 1 w0 = w0 + 1 If BTN_PIN = 0 Then w0 = 0 End If Loop Until w0 >= 2000 How best to do it, how to structure it as a loop with button handling within it, will depend on what else the code needs to be...

There will always be potential for jitter; if a pot is sitting on the boundary of being say 9 and 10 just a single bit change from noise will have it switching between the two. Other than at the boundaries there shouldn't be any jitter. Adding a capacitor on the input will help reduce jitter...

That's an interesting project. I was a little confused by "fan" having not heard of it but seeing it's a dual 'fan" and "spinning bar with LED's on", creating a Persistence of Vision display, it all made sense.

That is my understanding but I haven't tried it. The emulation is said to be quite impressive, and doesn't simply take each instruction at a time and emulate what it should do, but uses Just In Time (JIT) compilation tricks to turn X86/X64 instructions and routines into ARM equivalents which run...

Using the wrong divisor does seem to have been the issue. If you want 20 LED steps it's - 0 to 255 0 to 19 = -------- N So your 'N' to divide by will be 255/19, or 1023/19 if using READADC10. Because 'N' has to be an integer for a PICAXE it does mean that you can end up...

It seems to me there are only 705 unique descending digit numbers and - 1 loop = 20 ***** 2 loops = 34 ********* 3 loops = 140 *********************************** 4 loops = 129 ******************************** 5 loops = 113 **************************** 6 loops = 153...

Seems Wikipedia is right, testing all valid numbers ... 1 loop = 384 ******** 2 loops = 576 ************ 3 loops = 2400 ************************************************ 4 loops = 1272 ************************* 5 loops = 1518 ****************************** 6 loops = 1656...

Sorry; I had missed that as an option and it is a very neat trick. Given 'a XOR b' will give a zero result when both are the same I was wondering if something like 'a XOR b XOR c XOR d' would work, but it doesn't., only works for pairs. But I did get to this ... x = a ^ b x = b ^ c | x x = c ^...

That is something I had never heard of before and very interesting. The challenges do seem to be input, checking the digits aren't all the same, and particularly sorting. For checking the digits aren't all the same one can either split into digits then compare them against each other, or check...

If just jumping to 45' 90' and 180' angles you should be able to specify those using just SERVO command, setting the 'Position' to the appropriate values. You would only need to use a variable if you were wanting to move the servo more slowly between one position and another. The variable would...

The qualifiers define what must be at the start of the message, not the variables themselves. If your message is - X=12,Y=34,Z=56<CR><LF> You should be able to capture that using - serin B.3,T9600_8,("X"), #b8, #b10, #b12 If that doesn't work then if you can tell us what your message looks...

Yes, and in this case I would suggest a separate PICAXE controlling the spoiler is the perfect solution. It can run as slow or as fast as it likes with the only issue perhaps being the latency to adjusting the spoiler. Being independent all manner of tricks can be applied to reduce latency...

Why do you need multiple PULSIN to determine the frequency ? Just one should give a pretty good indication of what the input frequency is.

Not surprisingly if using something like- setoutputs: pinB.0 = bit7 pinB.1 = bit6 pinB.2 = bit5 pinB.3 = bit4 pinB.4 = bit3 pinB.5 = bit2 pinC.1 = bit1 pinC.0 = bit0 return There will be a delay between setting each individual bit of output. Things can be...

That seems to be in the right ballpark. A page write will take something like 10ms which I would guess is where most of the time is; 512 x 0.01 = 5.12 seconds and the remainder, about 3.2 seconds, being in serial, processing and passing data to the chip, overhead. The best you can do is shave...

We all have to start from the ground up and 'start simple' is the best advice I have. I always favour 'flash a led', 'turn it on when a button is pushed', then build up to a traffic light. That brings in most of the fundamentals which will serve well in more advanced projects. Most people on...

I have found that it's mainly the pulse width which is important, that the frame time or repeat rate is much less critical but YMMV.