[komi]

Quote:

Originally Posted by amb /img/forum/go_quote.gif Here is the LCDuino-1 BOM.

Put me on the list for proto boards please ...

 

[GeWa]

I'm also kinda interested in one of those.

Regards

 

[Grahame]

Quote:

Originally Posted by linuxworks /img/forum/go_quote.gif that reminds me, one possible thing to do with 'gathered information' is to send it to a pc, somewhere. suppose you wanted to get a graph of simultaneous (ie, time matched) sensor readings of rail voltage, bias voltage, heatsink temperature, powerOn-time and maybe even volume level. those are a bunch of collected 'data points'. the ard can't keep all that locally (for long) and so if you are into data collection or need to watch things for debugging, you want that up on some host or pc. a wireless link is kind of neat there are these xbee modules that have arduino drivers. you can create a pt-pt tunnel between arduinos and other arduinos or even pc's. if one endpoint is the pc, then it can store the logged data. import into a spreadsheet and go nuts

On the "enterprise class monitoring" side of things, I hope there is the ability to have some meta data, so that these things, the sensors/actuators can become self describing.

e.g. query for attributes that give, say, name, type, range?, and operations/methods - something like the java bean api, for example.

That way you could have a generic web/java/c# app for *any* device that implemented the API/Protocol, and as you add new capabilities to the device, the client app could recognize them, *with no additional work required*

You can still write custom apps using the API to some up with a "pretty" remote UI for the device (from an iPhone, nokia770 or other browser, say),

Sample attributes to display on historical trend graphs. Alert on out of band/range values. etc etc

All this can be done external to the device, as long as there is some generic way of getting the data out of the device, on request ( getValue(AttributeName) , say) , or setting an attribute value, or performing an operation remotely.

What say you?

This is the sort of thing I'd be interested in, and would be willing to help with.

*edit* - *Aha!*

Define the API/Protocol, then you can write adapters to the component model of you choice ...

e.g. write an adapter (only needs to be done once) to make the device appear as a JMX/java bean, then you can monitor/control it by jconsole out of the box, or plug it into any bean aware framework ...

Same approach works for any other component based framework ..., JMX, SNMP, etc

REST based web interface, etc etc

 

[linuxworks]

next he'll be asking for SNMP support.

 

[Beefy]

POP3/SMTP. I want my DAC to be able to send and receive emails.

 

[Grahame]

Quote:

Originally Posted by Beefy /img/forum/go_quote.gif POP3/SMTP. I want my DAC to be able to send and receive emails.

*Oh No* given the availability of the right email / sms gateway, your DAC could auto twitter to what you are listening to, at what volume level.

*Edit* or just use the twitter API ...

*Help*. I've just created a monster!

 

[jtostenr]

This is really cool stuff. Gonna have to rethink my Beta 22 project.....

Good thing it's going at a snail's pace

I love the idea of being able to monitor critical voltages, temps, etc. and setting up alarms and logging the data. I wonder though, could you monitor things like the bias without affecting it, and potentially the sound quality? I love this stuff, but sound quality remains my top priority.

Jeff

 

[linuxworks]

HOW the measurement is done - that's probably not my expertise. I can suggest some a/d chips but I'm not sure how to make the measurements and not be 'kosher' with audiophiles due to measurement wires running from test points to data collection points.

then there's the muxing issue; assuming you have 1 voltage a/d you can poll, you'll still have to connect it (probably 2 points but maybe all can be wrt ground) to each place via some 'roving relay' contact or something.

it would not be affordable to have precision a/d chips for each and every measurement point!

there are only 4 spare a/d (10bit, 0-5v) channels on the arduino so you run out of those, fast, too.

so, if the muxing can be done so that you can select, via some 2 or 3 bit address, which point you are going to measure, then yes, it can watch many bias points and stuff like that.

maybe an analog cmos switch would be enough just to allow sampling of key voltage test points?

needs more research. but I do think its a desireable feature, someday, to be able to monitor lots of key internal values. maybe even servo logic to keep them in check, as well!

 

[jtostenr]

It would be great to have a switchable input attenuator as an option as well, just in case you didn't have enough suggestions yet

I.E. - http://www.head-fi.org/forums/f6/rol...9/index58.html

Jeff

 

[linuxworks]

not only switchable input atten but on amps that allow it, switchable GAIN settings.

the m3 and PPA series can be gain-programmed with just a simple R per channel. locate some relays near those points and its simple enough. uln2003 style chip to drive the relays or just use transistors.

 

[jtostenr]

You can even add a touchscreen interface to the front of your amp -

Liquidware : TouchShield Slide

Seems like there a thousands of different applications for this platform. I can't wait to see the finished product.

So when are you guys going to start taking pre-orders?

Jeff

 

[mattcalf]

Quote:

Originally Posted by jtostenr /img/forum/go_quote.gif You can even add a touchscreen interface to the front of your amp - Liquidware : TouchShield Slide Seems like there a thousands of different applications for this platform. I can't wait to see the finished product. So when are you guys going to start taking pre-orders? Jeff

That is so ridiculously badass!

Pardon my language.

 

[linuxworks]

Quote:

Originally Posted by jtostenr /img/forum/go_quote.gif You can even add a touchscreen interface to the front of your amp -

better yet, why have it on the front panel; put that cool touch pad thing on a handheld (diy) remote and link them with RF.

do-able, in theory.

 

[DoYouRight]

that is calling me must snag a touchscreen for myself.

 

[aloksatoor]

Liquidware : InputShield.... using a joystick mounted on the front panel to power on and cntrl the input relays and the volume pots (or a rudimentary UI).... would mean a minimalist front panel with only a control stick and a headphone out n lcd