As the title says.
I know this is probably a silly question...but I can't find the answer, sorry.
Also, the task is running for over 3 hours and the bar still shows 0.00%!
What should I do now?

As the title says.
I know this is probably a silly question...but I can't find the answer, sorry.
Also, the task is running for over 3 hours and the bar still shows 0.00%!
What should I do now?

Let me ask a question here.

The thing takes 12 volts?

How much power is needed, ie mA. Your computer power supply in many instances has extra 12V plugs on it. It might once I get one to look at, be very easy to plug this thing right into your power supp if it's not taking too much juice.

Aaron

Let me ask a question here.

The thing takes 12 volts?

How much power is needed, ie mA. Your computer power supply in many instances has extra 12V plugs on it. It might once I get one to look at, be very easy to plug this thing right into your power supp if it's not taking too much juice.

Aaron

Let me ask a question here.

The thing takes 12 volts?

How much power is needed, ie mA. Your computer power supply in many instances has extra 12V plugs on it. It might once I get one to look at, be very easy to plug this thing right into your power supp if it's not taking too much juice.

Aaron

Let me ask a question here.

The thing takes 12 volts?

How much power is needed, ie mA. Your computer power supply in many instances has extra 12V plugs on it. It might once I get one to look at, be very easy to plug this thing right into your power supp if it's not taking too much juice.

Aaron

You could probably do that but you still have to have the USB cable attached because the onboard microprocessor dumps it's data to the PC through the USB cable. May as well just power it via USB and use only 1 cable instead of 2.

If you're going to add batteries then how about some RAM too? The Attiny4313 has only 128B SRAM which is not enough to cache much data. With a battery and some additional RAM the sensor could operate even when disconnected from phone/tablet/laptop or when the PC is powered off. You could have a jumper/switch that would switch between frequent sample mode and infrequent sample mode to conserve RAM. In infrequent sample mode the processor would switch to low power mode and the LCD would be powered off to conserve battery.

How about an onboard battery charger so a rechargeable battery can be used?

Have 2 models: a cheap one to sit beside a PC constantly and a more expensive portable model with battery, more RAM and charger.

Here it says 128B SRAM.

Maybe you need ATtiny 88 with 8 KB flash memory. It might not have enough data lines for the LCD but you can use a serial LCD or use only 4 data lines for the LCD if it is parallel interface by strobing the low bits first and the high bits second. But why have an LCD when you can display the current reading on the PC/tablet/phone screen?

Bluetooth would be a good idea for a portable model of the sensor. GPS is good too. But if the sensor is used with a tablet/phone then maybe the sensor will be disconnected for many hours, for example when you leave home and take your phone/tablet with you but not the sensor. For those times it would be good to have storage RAM to save the readings for when the phone/tablet returns. I don't know how much RAM would be required because I don't know how much data is in 1 sample but you could switch the sample rate to low rate when disconnected from the phone/tablet.

Of course every chip adds to the cost but you saw how fast the first batch was taken. I think people who have tablets and phones would be willing to pay more for a sensor with Bluetooth, a battery and some RAM to cache data.

Poor Szopler, maybe he will complain about the extra soldering ;-)

How about have the user just plug in a USB thumb drive, those are fairly cheap and relatively low power.

Cheap and low power yes but then they would need to include code for mounting a drive and for filesystem I/O. The ATTiny 4313 microprocessor has only 4 KB for program code. If they used a USB drive they would be obligated to include a Bluetooth port too to dump the data on the USB stick or include a second USB port or provide a program to run on the laptop/phone that would download the data from the USB stick (if the device has a USB connector that size, it may not) and feed it to their BOINC app. That all adds to the code space required. And you have to conserve interrupt lines too.

An onboard memory cache would eliminate the need for another USB port or Bluetooth and filesystem overhead. And it would be cheaper than a USB stick and wouldn't require an interrupt.