next topic »

[Reply #60 on:]

Even more user friendly:

http://labs.teague.com/?p=947

[Reply #61 on:]

Has anyone heard any news since the makers faire, or the possible specs released in September?

I'm stinging to get the 72Mhz OLIMEXINO-STM32 to let my library run free, but my preference would be the due.

Also, are there any specific technical documents for the cpu architecture or would everything be crammed into the datasheet.
What I mean is, are the things like data type sizes related to general gcc 32-bit sizes, or is it specific to the cpu? ( only ever had 32-bit windows n linux, and I think it is a cpu specific thing. )

[Reply #62 on:]

Has anyone heard any news since the makers faire, or the possible specs released in September?

Not as far as I know, there are supposed to be some alpha/beta testers with hands on hardware but the information flow from Arduino Inc is essentially non-existent.

I think a few people are eyeing off other 32-bit boards and may jump ship if info is not forthcoming soon.

I've just been working from the SAM data sheet, I don't understand your question about 32-bit sizes.

______
Rob

[Reply #63 on:]

cheers, the testers must have vowed to secrecy or something
I was wondering if the size of data types is the same on all 32-bit systems or is it specific to the CPU ( bool 16-bits, float 32-bits... ).

I found the datasheet for the processor, so I will have a squiz in that soon.

[Reply #64 on:]

cheers, the testers must have vowed to secrecy or something

The Arduino team has done a very good job staying very silent about this. My theory is that they're doing some of this under Atmel NDA.

[Reply #65 on:]

The more I see the Project Help section here, the more I am sure that something bigger/faster than UNO and MEGA is needed to cover the more ambitious efforts.

[Reply #66 on:]

  Something to think about, if we get one 32-bit Arm chip going strong maybe we will then be able to use many others. Think about names such as, Due-tiny, Due-mega, Due-alot-more lol.

[Reply #67 on:]

size of data types is the same on all 32-bit systems or is it specific to the CPU ( bool 16-bits, float 32-bits... ).

Some are, for example int cannot be trusted, that's why you should use uint16_t, uint32_t etc as they are supposed to be portable.

My theory is that they're doing some of this under Atmel NDA.

Quite possible, I just wish there was some more info, for example will the Due support 5v IO? That and many other things wouldn't be under an NDA surely.

And what has been released is just an erroneous dump of the SAM3U data sheet, for example the press release says 16 12-bit analogue inputs, that's not possible on the SAM3U. From that same release

Instead of just releasing the finished platform we are opening the process to the community early on.

Did I miss something? This forum is the community and I've not seen single thing here.

______
Rob

[Reply #68 on:]

I also find the lack of information disturbing from an "open source" company/organization.

[Reply #69 on:]

Solid state rectifiers are the only REAL rectifiers.

???  I can probably lay my hands on a 5Y3 here without a huge amount of trouble

[Reply #70 on:]

Quite possible, I just wish there was some more info, for example will the Due support 5v IO? That and many other things wouldn't be under an NDA surely.

I think that question has been pretty well answered with the UNO R3 board which has a new pin on the shield power connector wired to +5vdc called IOREF. A Due board will have 3.3vdc on that same pin. So it will be left to the shield to detect the Vcc voltage level on that pin and either enable or disable I/O pin voltage converters. So the Due won't directly support 5vdc I/O. At least that is what I got out of the few hints given out. Now it's probably the case that some I/O pins on the SAM3U chip on the Due are '5 volt tolerant', not sure there will be enough of them to map to all the standard arduino pin numbers? That will determine if the Due will be able to function will existing shield boards out there or not, I suspect not, but us mere mortals don't know that to date.

Lefty

[Reply #71 on:]

Solid state rectifiers are the only REAL rectifiers.

???  I can probably lay my hands on a 5Y3 here without a huge amount of trouble

I'd rather you look for an old trusty mercury vapor tube rectifier, 866 was it? It's what made real radios glow in the dark.

Lefty

[Reply #72 on:]

Solid state rectifiers are the only REAL rectifiers.

???  I can probably lay my hands on a 5Y3 here without a huge amount of trouble

You'd burn your hand though 
But really. With tube rectifiers, they run hot, waste power and fail more often then any other type of tubes. I usually just build a diode replacement  when I encounter tube rectifiers.

[Reply #73 on:]

But really. With tube rectifiers, they run hot, waste power and fail more often then any other type of tubes. I usually just build a diode replacement  when I encounter tube rectifiers.

True that. Are there any special considerations when substituting solid-state rectifiers for a vacuum tube? I mean other than the obvious voltage and current specs. Was going to try it years ago on a ancient surface grinder that had some pretty scary tubes providing DC to the magnetic chuck, but never quite got around to it.

[Reply #74 on:]

But really. With tube rectifiers, they run hot, waste power and fail more often then any other type of tubes. I usually just build a diode replacement  when I encounter tube rectifiers.

True that. Are there any special considerations when substituting solid-state rectifiers for a vacuum tube? I mean other than the obvious voltage and current specs. Was going to try it years ago on a ancient surface grinder that had some pretty scary tubes providing DC to the magnetic chuck, but never quite got around to it.

The output voltage will be higher because the efficiency of the diodes.
For example, a radio with 280v on the plate with a rectifier tube has 310v on the plate with SS rectifiers.
Hasn't blown up yet though