I managed to get it working on the 2313, and also managed to fix some bugs that prevented output 0 being used as PWM (these have now been fixed in the latest Arduino 1.0 version of SoftPWM I noticed the other day)

Can't remember what I did now - I'll have to re-familiarise myself with teh code again....

I did find that the structures consume a huge amount of RAM - I could only get 8 outputs PWMing and more and really strange things start happening....

Doh! I knew there's be a simple option

Thanks!

I'm trying to put a 3mm hole in my board for a locating peg, but I can't seem to get just a hole. if I use MOUNT-HOLE3.0 it also places a huge pad and keepout around the hole. I just want the hole. Is there some other library part that is just the hole with no outside pad, or do I have to create one myself?

Cheers in advance!

I'm using the Aurduino-Tiny 2313 core.

Made a bit of progress... First realised it was still running at 1Mhz. Burnt the 8MHz bootloader to set the fuses and verified correct speed with the standard blink.

Went back to the SoftPWM blink and it was flickering fast now rather than random blinking. I've since discovered that setting a very long delay between the on and off provides correct functionality i.e.

Code:

void loop()
{
  SoftPWMSet(5, 255);
  delay(50000);
  SoftPWMSet(5, 0);
  delay(50000);
}

From this I'm concluding that the timer the SoftPWM is now using is also the one the delay() function uses and that has now been changed such that the delay() function no longer provides a delay in ms. I can live with that and just make adjustments in my code. Are there any other side effects I should be aware of?

I'm looking to use this on the ATTINY2313 to PWM all the outputs. I created a new "TinySoftPWM.c/h" library and changed the failing references in blind hope thus

Code:

  TIFR = (1 << TOV0);          // clear interrupt flag
  TIMSK = (1 << OCIE0A);       // enable timer0 output compare match interrupt
  TCCR0B = (1 << CS01);         // start timer (ck/8 prescalar)
  TCCR0A = (1 << WGM01);        // CTC mode
  OCR0A = SOFTPWM_OCR;

And also changed ISR(TIMER2_COMPA_vect) to ISR(TIMER0_COMPA_vect).

The code now compiles, but behaves oddly once uploaded (TinyISP). I'm running using the internal 8MHz osc so would expect it to be a bit slower, but I seem to be getting some rather random blinking running the SoftPWM blink sketch.
No idea what to try next....

Thanks for the clarification  

I just updateded from v14 to v18 of the IDE - is there any way to get the last project to load automatically at startup?

New behaviour seems to be always create a new project. When loading the old one, you then get a new window. Annoying.

I couldn't see anything in the preferences to set this, but my last project is listed under last.sketch0.path

Also, is it possible to use tabs as tabs (not spaces)? Setting editor.tabs.expand=false generates nothing at all for the tab key  :-?

Cheers

Cheers.

Looking into the EEPROM library code, it's basically aliasing some core functions, so it was easier to use those directly  

I'm creating a small library from which I want to use the EEPROM library but I'm getting a compile error in my library on the include line
#include <EEPROM.h>

error: EEPROM.h: No such file or directory

I can use the EEPROM fine from my sketch with the same include.

Is this behaviour supported, or must all libraries be self contained?

Cheers

I was having the same problem in v14 but moving to v18 it worked as expected!

They look like audio leads from CD drives - usually a 3 or 4 pin .1" molex on each end....

Not the best by any means, but if you happened to have a boxfull to hand, why not...

Marvin Martian, why do you think you would need to reprogram the bootloader?

Because of what mungbean said earlier:

As I understand it, clock speed is hard-coded into the bootloader, so changing the crystal isn't enough to change the speed.  You would need to program a new bootloader in as well.

So I'm still confused as to whether this is or is not necessary  :-/

But without the capability to reprogram the bootloader that's going to be a bit awkward. Ho hum.

Cheers

I've got a stand alone battery prowered 328 project that runs off 3 AAs - it "works ok" but reading here is sounds like I'm on the edge of it running successfully at 16MHz.

I was considering dropping the crystal down to 8MHz to give me a wider power margin - Comms is not an issue as I'm programming the 328 in an Arduino then taking it out and dropping it in my PCB.

But it sounds like just changing the crystal won't work either and it will require a software tweak too - is that correct?

Cheers

You could probably do this with just a few standard ultrabright LEDs withough resorting to the high power route

Something like this will kick out 30 candelas for a few 10's of mA

http://www.rapidonline.com/sku/Electronic-Components/Optoelectronics/5mm-LEDs/5mm-Ultra-high-brightness-15-deg-LEDs/73421/55-2484

Of course you may end up with a directional light source. You don't say how long you need it to last, but you could probably drive a few of these for a day on 3 AAs

If your eyes are accustomed to a dim room these would definitely make you squint