Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #21464 > unrolled thread

waveform display in browser

Back to article view | Back to comp.arch.embedded

Contents

  waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 11:18 -0700
    Re: waveform display in browser Joerg <news@analogconsultants.com> - 2015-07-23 11:53 -0700
    Re: waveform display in browser Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2015-07-23 16:34 -0400
      Re: waveform display in browser rickman <gnuarm@gmail.com> - 2015-07-23 16:49 -0400
        Re: waveform display in browser Dimiter_Popoff <dp@tgi-sci.com> - 2015-07-24 00:13 +0300
          Re: waveform display in browser rickman <gnuarm@gmail.com> - 2015-07-23 17:39 -0400
          Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 14:50 -0700
            Re: waveform display in browser Dimiter_Popoff <dp@tgi-sci.com> - 2015-07-24 01:19 +0300
              Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 15:30 -0700
                Re: waveform display in browser rickman <gnuarm@gmail.com> - 2015-07-23 18:46 -0400
                Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-23 17:54 -0500
                  Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 16:22 -0700
                    Re: waveform display in browser Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2015-07-23 19:56 -0400
                      Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-24 14:55 -0500
                        Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-24 14:11 -0700
                          Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-24 17:00 -0500
                          Re: waveform display in browser Herbert Kleebauer <klee@unibwm.de> - 2015-07-25 09:04 +0200
                    Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-24 14:58 -0500
                      Re: waveform display in browser Grant Edwards <invalid@invalid.invalid> - 2015-07-24 20:15 +0000
                        Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-24 16:48 -0500
                          Re: waveform display in browser Grant Edwards <invalid@invalid.invalid> - 2015-07-24 22:08 +0000
                            Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-24 22:46 +1000
                              Re: waveform display in browser Grant Edwards <invalid@invalid.invalid> - 2015-07-25 14:32 +0000
                        Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-24 22:44 +0000
                          Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-24 23:31 +0000
                          Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-24 22:49 +1000
                            Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-25 09:28 +0000
                              Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-25 08:43 +1000
                                Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-25 22:27 +0000
                                  Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-25 20:57 +1000
                      Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-24 22:41 +0000
                        Re: waveform display in browser rickman <gnuarm@gmail.com> - 2015-07-24 22:03 -0400
                    Re: waveform display in browser Tim Wescott <seemywebsite@myfooter.really> - 2015-07-24 15:05 -0500
    Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-23 21:37 +0000
      Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 15:32 -0700
    Re: waveform display in browser Martin Riddle <martin_ridd@verizon.net> - 2015-07-23 20:24 -0400
      Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-23 21:08 -0700
        Re: waveform display in browser Martin Riddle <martin_ridd@verizon.net> - 2015-07-24 07:52 -0400
          Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-24 14:08 +0000
            Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-24 22:53 +1000
              Re: waveform display in browser Jasen Betts <jasen@xnet.co.nz> - 2015-07-25 09:46 +0000
                Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-25 08:46 +1000
    Re: waveform display in browser Clifford Heath <no.spam@please.net> - 2015-07-24 00:37 +1000
    Re: waveform display in browser Martin Brown <|||newspam|||@nezumi.demon.co.uk> - 2015-07-24 11:46 +0100
    Re: waveform display in browser YD <ydtechHAT@techie.com> - 2015-07-24 14:25 -0300
      Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-24 10:55 -0700
        Re: waveform display in browser rickman <gnuarm@gmail.com> - 2015-07-24 14:09 -0400
        Re: waveform display in browser Grant Edwards <invalid@invalid.invalid> - 2015-07-24 18:42 +0000
          Re: waveform display in browser YD <ydtechHAT@techie.com> - 2015-07-24 19:12 -0300
            Re: waveform display in browser Grant Edwards <invalid@invalid.invalid> - 2015-07-25 14:36 +0000
        Re: waveform display in browser Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2015-07-24 14:55 -0400
    Re: waveform display in browser John Larkin <jlarkin@highlandtechnology.com> - 2015-07-27 17:52 -0700
      Re: waveform display in browser Phil Hobbs <hobbs@electrooptical.net> - 2015-07-28 17:58 -0400
    Re: waveform display in browser "jurem" <51422@EmbeddedRelated> - 2015-07-28 09:49 -0500

Page 1 of 3  [1] 2 3  Next page →

#21464 — waveform display in browser

I'm designing a tachometer box and it will have a web page interface
as one way to talk to it. I thought it would be cool to include an ADC
so we could display waveforms, too. My software guys here are mostly
embedded types so we don't know a lot about Javascript and such. I did
a little searching and mostly found things for displaying audio
envelope cartoons; I want a real oscilloscope-looking thing, so users
can see what happens as they change gains and filtering and trigger
level settings. Dual trace would be nice, the analog waveform and
corresponding comparator outputs.

Has anybody done this? We'd consider getting outside help, either
advice or actual coding.

I assume our box will, through some port, deliver HTML, Javascript,
and maybe some zipped JS libraries to the browser. And the company
logo of course. The browser will send us text strings to parse if the
user wants to change parameters or such. We would also deliver blocks
of waveform data on request. That's my PHB perspective on things; I'm
just the hardware designer.


-- 

John Larkin         Highland Technology, Inc
picosecond timing   precision measurement 

jlarkin att highlandtechnology dott com
http://www.highlandtechnology.com

[toc] | [next] | [standalone]

#21465

On 2015-07-23 11:18 AM, John Larkin wrote:
>
>
> I'm designing a tachometer box and it will have a web page interface
> as one way to talk to it. I thought it would be cool to include an ADC
> so we could display waveforms, too. My software guys here are mostly
> embedded types so we don't know a lot about Javascript and such. I did
> a little searching and mostly found things for displaying audio
> envelope cartoons; I want a real oscilloscope-looking thing, so users
> can see what happens as they change gains and filtering and trigger
> level settings. Dual trace would be nice, the analog waveform and
> corresponding comparator outputs.
>
> Has anybody done this? We'd consider getting outside help, either
> advice or actual coding.
>
> I assume our box will, through some port, deliver HTML, Javascript,
> and maybe some zipped JS libraries to the browser. And the company
> logo of course. The browser will send us text strings to parse if the
> user wants to change parameters or such. We would also deliver blocks
> of waveform data on request. That's my PHB perspective on things; I'm
> just the hardware designer.
>

An easy method for non-programmer types is this:

http://azeotech.com/j/index.php

Comes in various flavors from free to full bore. A "Shazam!" reaction at 
a client happened when they found their company logo integrated into the 
control screen which was no more effort than copy-paste.

-- 
Regards, Joerg

http://www.analogconsultants.com/

[toc] | [prev] | [next] | [standalone]

#21468

On 7/23/2015 2:18 PM, John Larkin wrote:
>
>
> I'm designing a tachometer box and it will have a web page interface
> as one way to talk to it. I thought it would be cool to include an ADC
> so we could display waveforms, too. My software guys here are mostly
> embedded types so we don't know a lot about Javascript and such. I did
> a little searching and mostly found things for displaying audio
> envelope cartoons; I want a real oscilloscope-looking thing, so users
> can see what happens as they change gains and filtering and trigger
> level settings. Dual trace would be nice, the analog waveform and
> corresponding comparator outputs.
>
> Has anybody done this? We'd consider getting outside help, either
> advice or actual coding.
>
> I assume our box will, through some port, deliver HTML, Javascript,
> and maybe some zipped JS libraries to the browser. And the company
> logo of course. The browser will send us text strings to parse if the
> user wants to change parameters or such. We would also deliver blocks
> of waveform data on request. That's my PHB perspective on things; I'm
> just the hardware designer.
>
>
One approach is a CGI script that runs gnuplot under the covers.  IIRC 
quite a few folks do that.  (I'm a static HTML guy myself.)


Cheers

Phil Hobbs

-- 
Dr Philip C D Hobbs
Principal Consultant
ElectroOptical Innovations LLC
Optics, Electro-optics, Photonics, Analog Electronics

160 North State Road #203
Briarcliff Manor NY 10510

hobbs at electrooptical dot net
http://electrooptical.net

[toc] | [prev] | [next] | [standalone]

#21470

On 7/23/2015 4:34 PM, Phil Hobbs wrote:
> On 7/23/2015 2:18 PM, John Larkin wrote:
>>
>>
>> I'm designing a tachometer box and it will have a web page interface
>> as one way to talk to it. I thought it would be cool to include an ADC
>> so we could display waveforms, too. My software guys here are mostly
>> embedded types so we don't know a lot about Javascript and such. I did
>> a little searching and mostly found things for displaying audio
>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>> can see what happens as they change gains and filtering and trigger
>> level settings. Dual trace would be nice, the analog waveform and
>> corresponding comparator outputs.
>>
>> Has anybody done this? We'd consider getting outside help, either
>> advice or actual coding.
>>
>> I assume our box will, through some port, deliver HTML, Javascript,
>> and maybe some zipped JS libraries to the browser. And the company
>> logo of course. The browser will send us text strings to parse if the
>> user wants to change parameters or such. We would also deliver blocks
>> of waveform data on request. That's my PHB perspective on things; I'm
>> just the hardware designer.
>>
>>
> One approach is a CGI script that runs gnuplot under the covers.  IIRC
> quite a few folks do that.  (I'm a static HTML guy myself.)

Isn't there an actual oscilloscope display package under Linux?  It 
should be fairly straightforward to drive that from an internet 
connection.  I guess requiring the customer to installing such a package 
is not preferred.

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#21471

On 23.7.2015 г. 23:49, rickman wrote:
> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>
>>>
>>> I'm designing a tachometer box and it will have a web page interface
>>> as one way to talk to it. I thought it would be cool to include an ADC
>>> so we could display waveforms, too. My software guys here are mostly
>>> embedded types so we don't know a lot about Javascript and such. I did
>>> a little searching and mostly found things for displaying audio
>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>> can see what happens as they change gains and filtering and trigger
>>> level settings. Dual trace would be nice, the analog waveform and
>>> corresponding comparator outputs.
>>>
>>> Has anybody done this? We'd consider getting outside help, either
>>> advice or actual coding.
>>>
>>> I assume our box will, through some port, deliver HTML, Javascript,
>>> and maybe some zipped JS libraries to the browser. And the company
>>> logo of course. The browser will send us text strings to parse if the
>>> user wants to change parameters or such. We would also deliver blocks
>>> of waveform data on request. That's my PHB perspective on things; I'm
>>> just the hardware designer.
>>>
>>>
>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>> quite a few folks do that.  (I'm a static HTML guy myself.)
>
> Isn't there an actual oscilloscope display package under Linux?  It
> should be fairly straightforward to drive that from an internet
> connection.  I guess requiring the customer to installing such a package
> is not preferred.
>

He is after a browser plugin - something like VNC, the way I do it
on our spectrometers (I do not use a plugin but I could if I wanted to).

However this implies a fullblown RFB connection to a stand alone
system having its display and GUI locally (within his oscilloscope
thing) which is far from being trivial.

Dimiter

------------------------------------------------------
Dimiter Popoff, TGI             http://www.tgi-sci.com
------------------------------------------------------
http://www.flickr.com/photos/didi_tgi/

[toc] | [prev] | [next] | [standalone]

#21472

On 7/23/2015 5:13 PM, Dimiter_Popoff wrote:
> On 23.7.2015 г. 23:49, rickman wrote:
>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>
>>>>
>>>> I'm designing a tachometer box and it will have a web page interface
>>>> as one way to talk to it. I thought it would be cool to include an ADC
>>>> so we could display waveforms, too. My software guys here are mostly
>>>> embedded types so we don't know a lot about Javascript and such. I did
>>>> a little searching and mostly found things for displaying audio
>>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>>> can see what happens as they change gains and filtering and trigger
>>>> level settings. Dual trace would be nice, the analog waveform and
>>>> corresponding comparator outputs.
>>>>
>>>> Has anybody done this? We'd consider getting outside help, either
>>>> advice or actual coding.
>>>>
>>>> I assume our box will, through some port, deliver HTML, Javascript,
>>>> and maybe some zipped JS libraries to the browser. And the company
>>>> logo of course. The browser will send us text strings to parse if the
>>>> user wants to change parameters or such. We would also deliver blocks
>>>> of waveform data on request. That's my PHB perspective on things; I'm
>>>> just the hardware designer.
>>>>
>>>>
>>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>>> quite a few folks do that.  (I'm a static HTML guy myself.)
>>
>> Isn't there an actual oscilloscope display package under Linux?  It
>> should be fairly straightforward to drive that from an internet
>> connection.  I guess requiring the customer to installing such a package
>> is not preferred.
>>
>
> He is after a browser plugin - something like VNC, the way I do it
> on our spectrometers (I do not use a plugin but I could if I wanted to).
>
> However this implies a fullblown RFB connection to a stand alone
> system having its display and GUI locally (within his oscilloscope
> thing) which is far from being trivial.

Yeah, I get what he is after, but there is more than one way to skin a 
cat.  Another would be to allow a remote desktop connection.  Then no 
software of any kind is needed for the client other than the RDP app. 
Still more work on the client end but installing a canned app isn't that 
hard.  Browser based apps can be work to get running on multiple 
browsers and keep running with browser updates.  A friend is in that 
line of work and there is *soooooo* much work keeping all the different 
versions working.

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#21473

On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
wrote:

>On 23.7.2015 ?. 23:49, rickman wrote:
>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>
>>>>
>>>> I'm designing a tachometer box and it will have a web page interface
>>>> as one way to talk to it. I thought it would be cool to include an ADC
>>>> so we could display waveforms, too. My software guys here are mostly
>>>> embedded types so we don't know a lot about Javascript and such. I did
>>>> a little searching and mostly found things for displaying audio
>>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>>> can see what happens as they change gains and filtering and trigger
>>>> level settings. Dual trace would be nice, the analog waveform and
>>>> corresponding comparator outputs.
>>>>
>>>> Has anybody done this? We'd consider getting outside help, either
>>>> advice or actual coding.
>>>>
>>>> I assume our box will, through some port, deliver HTML, Javascript,
>>>> and maybe some zipped JS libraries to the browser. And the company
>>>> logo of course. The browser will send us text strings to parse if the
>>>> user wants to change parameters or such. We would also deliver blocks
>>>> of waveform data on request. That's my PHB perspective on things; I'm
>>>> just the hardware designer.
>>>>
>>>>
>>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>>> quite a few folks do that.  (I'm a static HTML guy myself.)
>>
>> Isn't there an actual oscilloscope display package under Linux?  It
>> should be fairly straightforward to drive that from an internet
>> connection.  I guess requiring the customer to installing such a package
>> is not preferred.
>>
>
>He is after a browser plugin - something like VNC, the way I do it
>on our spectrometers (I do not use a plugin but I could if I wanted to).

Actually, I don't want a plugin, just a way for the browser to display
a waveform, using some javascript. We can store any reasonable zipped
javascript libraries in our gadget and deliver them to the browser.


>
>However this implies a fullblown RFB connection to a stand alone
>system having its display and GUI locally (within his oscilloscope
>thing) which is far from being trivial.

The tach box will have no display or GUI, and in fact no official OS.


-- 

John Larkin         Highland Technology, Inc
picosecond timing   precision measurement 

jlarkin att highlandtechnology dott com
http://www.highlandtechnology.com

[toc] | [prev] | [next] | [standalone]

#21476

On 24.7.2015 г. 00:50, John Larkin wrote:
> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
> wrote:
>
>> On 23.7.2015 ?. 23:49, rickman wrote:
>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>
>>>>>
>>>>> I'm designing a tachometer box and it will have a web page interface
>>>>> as one way to talk to it. I thought it would be cool to include an ADC
>>>>> so we could display waveforms, too. My software guys here are mostly
>>>>> embedded types so we don't know a lot about Javascript and such. I did
>>>>> a little searching and mostly found things for displaying audio
>>>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>>>> can see what happens as they change gains and filtering and trigger
>>>>> level settings. Dual trace would be nice, the analog waveform and
>>>>> corresponding comparator outputs.
>>>>>
>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>> advice or actual coding.
>>>>>
>>>>> I assume our box will, through some port, deliver HTML, Javascript,
>>>>> and maybe some zipped JS libraries to the browser. And the company
>>>>> logo of course. The browser will send us text strings to parse if the
>>>>> user wants to change parameters or such. We would also deliver blocks
>>>>> of waveform data on request. That's my PHB perspective on things; I'm
>>>>> just the hardware designer.
>>>>>
>>>>>
>>>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>>>> quite a few folks do that.  (I'm a static HTML guy myself.)
>>>
>>> Isn't there an actual oscilloscope display package under Linux?  It
>>> should be fairly straightforward to drive that from an internet
>>> connection.  I guess requiring the customer to installing such a package
>>> is not preferred.
>>>
>>
>> He is after a browser plugin - something like VNC, the way I do it
>> on our spectrometers (I do not use a plugin but I could if I wanted to).
>
> Actually, I don't want a plugin, just a way for the browser to display
> a waveform, using some javascript. We can store any reasonable zipped
> javascript libraries in our gadget and deliver them to the browser.

I am not sure I have seen that done for live graphics - then scaling,
perhaps autoranging etc., even if doable it would be a massive pain
to support with all browsers as they keep on evolving.
Your best bet might be to produce locally a .gif (or .png or
whatever) bitmap, maintain it live and persuade the browser to refresh
it regularly. Don't know how the latter is to be done though.

>>
>> However this implies a fullblown RFB connection to a stand alone
>> system having its display and GUI locally (within his oscilloscope
>> thing) which is far from being trivial.
>
> The tach box will have no display or GUI, and in fact no official OS.
>

Not having a display is not a problem, some of our spectrometers do
not have one, they just maintain the display bitmap in system
memory - which is viewed via RFB (VNC)(RDP which Rick suggested
is very similar, same thing really but over a non-public protocol).
Not having an OS - nor a VNC server nor the image to be
displayed - obviously makes this impractical in your case.

Dimiter

------------------------------------------------------
Dimiter Popoff, TGI             http://www.tgi-sci.com
------------------------------------------------------
http://www.flickr.com/photos/didi_tgi/

[toc] | [prev] | [next] | [standalone]

#21477

On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
wrote:

>On 24.7.2015 ?. 00:50, John Larkin wrote:
>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>> wrote:
>>
>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>
>>>>>>
>>>>>> I'm designing a tachometer box and it will have a web page interface
>>>>>> as one way to talk to it. I thought it would be cool to include an ADC
>>>>>> so we could display waveforms, too. My software guys here are mostly
>>>>>> embedded types so we don't know a lot about Javascript and such. I did
>>>>>> a little searching and mostly found things for displaying audio
>>>>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>>>>> can see what happens as they change gains and filtering and trigger
>>>>>> level settings. Dual trace would be nice, the analog waveform and
>>>>>> corresponding comparator outputs.
>>>>>>
>>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>>> advice or actual coding.
>>>>>>
>>>>>> I assume our box will, through some port, deliver HTML, Javascript,
>>>>>> and maybe some zipped JS libraries to the browser. And the company
>>>>>> logo of course. The browser will send us text strings to parse if the
>>>>>> user wants to change parameters or such. We would also deliver blocks
>>>>>> of waveform data on request. That's my PHB perspective on things; I'm
>>>>>> just the hardware designer.
>>>>>>
>>>>>>
>>>>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>>>>> quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>
>>>> Isn't there an actual oscilloscope display package under Linux?  It
>>>> should be fairly straightforward to drive that from an internet
>>>> connection.  I guess requiring the customer to installing such a package
>>>> is not preferred.
>>>>
>>>
>>> He is after a browser plugin - something like VNC, the way I do it
>>> on our spectrometers (I do not use a plugin but I could if I wanted to).
>>
>> Actually, I don't want a plugin, just a way for the browser to display
>> a waveform, using some javascript. We can store any reasonable zipped
>> javascript libraries in our gadget and deliver them to the browser.
>
>I am not sure I have seen that done for live graphics - then scaling,
>perhaps autoranging etc., even if doable it would be a massive pain
>to support with all browsers as they keep on evolving.
>Your best bet might be to produce locally a .gif (or .png or
>whatever) bitmap, maintain it live and persuade the browser to refresh
>it regularly. Don't know how the latter is to be done though.

We could do that in the FPGA! If nobody murders me for suggesting it.


-- 

John Larkin         Highland Technology, Inc
picosecond timing   precision measurement 

jlarkin att highlandtechnology dott com
http://www.highlandtechnology.com

[toc] | [prev] | [next] | [standalone]

#21479

On 7/23/2015 6:30 PM, John Larkin wrote:
> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
> wrote:
>
>> On 24.7.2015 ?. 00:50, John Larkin wrote:
>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>> wrote:
>>>
>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>
>>>>>>>
>>>>>>> I'm designing a tachometer box and it will have a web page interface
>>>>>>> as one way to talk to it. I thought it would be cool to include an ADC
>>>>>>> so we could display waveforms, too. My software guys here are mostly
>>>>>>> embedded types so we don't know a lot about Javascript and such. I did
>>>>>>> a little searching and mostly found things for displaying audio
>>>>>>> envelope cartoons; I want a real oscilloscope-looking thing, so users
>>>>>>> can see what happens as they change gains and filtering and trigger
>>>>>>> level settings. Dual trace would be nice, the analog waveform and
>>>>>>> corresponding comparator outputs.
>>>>>>>
>>>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>>>> advice or actual coding.
>>>>>>>
>>>>>>> I assume our box will, through some port, deliver HTML, Javascript,
>>>>>>> and maybe some zipped JS libraries to the browser. And the company
>>>>>>> logo of course. The browser will send us text strings to parse if the
>>>>>>> user wants to change parameters or such. We would also deliver blocks
>>>>>>> of waveform data on request. That's my PHB perspective on things; I'm
>>>>>>> just the hardware designer.
>>>>>>>
>>>>>>>
>>>>>> One approach is a CGI script that runs gnuplot under the covers.  IIRC
>>>>>> quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>
>>>>> Isn't there an actual oscilloscope display package under Linux?  It
>>>>> should be fairly straightforward to drive that from an internet
>>>>> connection.  I guess requiring the customer to installing such a package
>>>>> is not preferred.
>>>>>
>>>>
>>>> He is after a browser plugin - something like VNC, the way I do it
>>>> on our spectrometers (I do not use a plugin but I could if I wanted to).
>>>
>>> Actually, I don't want a plugin, just a way for the browser to display
>>> a waveform, using some javascript. We can store any reasonable zipped
>>> javascript libraries in our gadget and deliver them to the browser.
>>
>> I am not sure I have seen that done for live graphics - then scaling,
>> perhaps autoranging etc., even if doable it would be a massive pain
>> to support with all browsers as they keep on evolving.
>> Your best bet might be to produce locally a .gif (or .png or
>> whatever) bitmap, maintain it live and persuade the browser to refresh
>> it regularly. Don't know how the latter is to be done though.
>
> We could do that in the FPGA! If nobody murders me for suggesting it.

If a simple GIF image is good enough, I'm pretty sure you can imbed that 
in an HTML page that will auto refresh periodically.  How often does it 
need to update?

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#21480

On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:

> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
> wrote:
> 
>>On 24.7.2015 ?. 00:50, John Larkin wrote:
>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>> wrote:
>>>
>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>
>>>>>>>
>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>> interface as one way to talk to it. I thought it would be cool to
>>>>>>> include an ADC so we could display waveforms, too. My software
>>>>>>> guys here are mostly embedded types so we don't know a lot about
>>>>>>> Javascript and such. I did a little searching and mostly found
>>>>>>> things for displaying audio envelope cartoons; I want a real
>>>>>>> oscilloscope-looking thing, so users can see what happens as they
>>>>>>> change gains and filtering and trigger level settings. Dual trace
>>>>>>> would be nice, the analog waveform and corresponding comparator
>>>>>>> outputs.
>>>>>>>
>>>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>>>> advice or actual coding.
>>>>>>>
>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>> Javascript, and maybe some zipped JS libraries to the browser. And
>>>>>>> the company logo of course. The browser will send us text strings
>>>>>>> to parse if the user wants to change parameters or such. We would
>>>>>>> also deliver blocks of waveform data on request. That's my PHB
>>>>>>> perspective on things; I'm just the hardware designer.
>>>>>>>
>>>>>>>
>>>>>> One approach is a CGI script that runs gnuplot under the covers. 
>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>
>>>>> Isn't there an actual oscilloscope display package under Linux?  It
>>>>> should be fairly straightforward to drive that from an internet
>>>>> connection.  I guess requiring the customer to installing such a
>>>>> package is not preferred.
>>>>>
>>>>>
>>>> He is after a browser plugin - something like VNC, the way I do it on
>>>> our spectrometers (I do not use a plugin but I could if I wanted to).
>>>
>>> Actually, I don't want a plugin, just a way for the browser to display
>>> a waveform, using some javascript. We can store any reasonable zipped
>>> javascript libraries in our gadget and deliver them to the browser.
>>
>>I am not sure I have seen that done for live graphics - then scaling,
>>perhaps autoranging etc., even if doable it would be a massive pain to
>>support with all browsers as they keep on evolving.
>>Your best bet might be to produce locally a .gif (or .png or whatever)
>>bitmap, maintain it live and persuade the browser to refresh it
>>regularly. Don't know how the latter is to be done though.
> 
> We could do that in the FPGA! If nobody murders me for suggesting it.

I don't know how to persuade a browser to auto-refresh, but GIF format 
uses run-length limiting for compression.  That means that line drawings 
of few colors tend to be very small -- you'll use up way more bits on 
text than on the pictures.

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

[toc] | [prev] | [next] | [standalone]

#21481

On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
<seemywebsite@myfooter.really> wrote:

>On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>
>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>> wrote:
>> 
>>>On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>> wrote:
>>>>
>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>> interface as one way to talk to it. I thought it would be cool to
>>>>>>>> include an ADC so we could display waveforms, too. My software
>>>>>>>> guys here are mostly embedded types so we don't know a lot about
>>>>>>>> Javascript and such. I did a little searching and mostly found
>>>>>>>> things for displaying audio envelope cartoons; I want a real
>>>>>>>> oscilloscope-looking thing, so users can see what happens as they
>>>>>>>> change gains and filtering and trigger level settings. Dual trace
>>>>>>>> would be nice, the analog waveform and corresponding comparator
>>>>>>>> outputs.
>>>>>>>>
>>>>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>>>>> advice or actual coding.
>>>>>>>>
>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>> Javascript, and maybe some zipped JS libraries to the browser. And
>>>>>>>> the company logo of course. The browser will send us text strings
>>>>>>>> to parse if the user wants to change parameters or such. We would
>>>>>>>> also deliver blocks of waveform data on request. That's my PHB
>>>>>>>> perspective on things; I'm just the hardware designer.
>>>>>>>>
>>>>>>>>
>>>>>>> One approach is a CGI script that runs gnuplot under the covers. 
>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>>
>>>>>> Isn't there an actual oscilloscope display package under Linux?  It
>>>>>> should be fairly straightforward to drive that from an internet
>>>>>> connection.  I guess requiring the customer to installing such a
>>>>>> package is not preferred.
>>>>>>
>>>>>>
>>>>> He is after a browser plugin - something like VNC, the way I do it on
>>>>> our spectrometers (I do not use a plugin but I could if I wanted to).
>>>>
>>>> Actually, I don't want a plugin, just a way for the browser to display
>>>> a waveform, using some javascript. We can store any reasonable zipped
>>>> javascript libraries in our gadget and deliver them to the browser.
>>>
>>>I am not sure I have seen that done for live graphics - then scaling,
>>>perhaps autoranging etc., even if doable it would be a massive pain to
>>>support with all browsers as they keep on evolving.
>>>Your best bet might be to produce locally a .gif (or .png or whatever)
>>>bitmap, maintain it live and persuade the browser to refresh it
>>>regularly. Don't know how the latter is to be done though.
>> 
>> We could do that in the FPGA! If nobody murders me for suggesting it.
>
>I don't know how to persuade a browser to auto-refresh, but GIF format 
>uses run-length limiting for compression.  That means that line drawings 
>of few colors tend to be very small -- you'll use up way more bits on 
>text than on the pictures.

There is some simple HTML thing that makes a page reload periodically.
That's apparently easy to do.

A BMP would be easy to make inside the FPGA, but that would be slow to
load. Maybe the ARM could make a GIF or PNG. That would avoid all the
javascript nonsense. We'd just have to find the code somewhere.

This bmp is 556K bytes.

https://dl.dropboxusercontent.com/u/53724080/Circuits/Current_Limiters/LM317L_ilim.bmp

That wouldn't be really terrible to send once a second or so over 100
MBPS Ethernet. But my FPGA doesn't have enough RAM.


-- 

John Larkin         Highland Technology, Inc
picosecond timing   precision measurement 

jlarkin att highlandtechnology dott com
http://www.highlandtechnology.com

[toc] | [prev] | [next] | [standalone]

#21482

On 7/23/2015 7:22 PM, John Larkin wrote:
> On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
> <seemywebsite@myfooter.really> wrote:
>
>> On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>>
>>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>> wrote:
>>>
>>>> On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>> wrote:
>>>>>
>>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>>> interface as one way to talk to it. I thought it would be cool to
>>>>>>>>> include an ADC so we could display waveforms, too. My software
>>>>>>>>> guys here are mostly embedded types so we don't know a lot about
>>>>>>>>> Javascript and such. I did a little searching and mostly found
>>>>>>>>> things for displaying audio envelope cartoons; I want a real
>>>>>>>>> oscilloscope-looking thing, so users can see what happens as they
>>>>>>>>> change gains and filtering and trigger level settings. Dual trace
>>>>>>>>> would be nice, the analog waveform and corresponding comparator
>>>>>>>>> outputs.
>>>>>>>>>
>>>>>>>>> Has anybody done this? We'd consider getting outside help, either
>>>>>>>>> advice or actual coding.
>>>>>>>>>
>>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>>> Javascript, and maybe some zipped JS libraries to the browser. And
>>>>>>>>> the company logo of course. The browser will send us text strings
>>>>>>>>> to parse if the user wants to change parameters or such. We would
>>>>>>>>> also deliver blocks of waveform data on request. That's my PHB
>>>>>>>>> perspective on things; I'm just the hardware designer.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> One approach is a CGI script that runs gnuplot under the covers.
>>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>>>
>>>>>>> Isn't there an actual oscilloscope display package under Linux?  It
>>>>>>> should be fairly straightforward to drive that from an internet
>>>>>>> connection.  I guess requiring the customer to installing such a
>>>>>>> package is not preferred.
>>>>>>>
>>>>>>>
>>>>>> He is after a browser plugin - something like VNC, the way I do it on
>>>>>> our spectrometers (I do not use a plugin but I could if I wanted to).
>>>>>
>>>>> Actually, I don't want a plugin, just a way for the browser to display
>>>>> a waveform, using some javascript. We can store any reasonable zipped
>>>>> javascript libraries in our gadget and deliver them to the browser.
>>>>
>>>> I am not sure I have seen that done for live graphics - then scaling,
>>>> perhaps autoranging etc., even if doable it would be a massive pain to
>>>> support with all browsers as they keep on evolving.
>>>> Your best bet might be to produce locally a .gif (or .png or whatever)
>>>> bitmap, maintain it live and persuade the browser to refresh it
>>>> regularly. Don't know how the latter is to be done though.
>>>
>>> We could do that in the FPGA! If nobody murders me for suggesting it.
>>
>> I don't know how to persuade a browser to auto-refresh, but GIF format
>> uses run-length limiting for compression.  That means that line drawings
>> of few colors tend to be very small -- you'll use up way more bits on
>> text than on the pictures.
>
> There is some simple HTML thing that makes a page reload periodically.
> That's apparently easy to do.
>
> A BMP would be easy to make inside the FPGA, but that would be slow to
> load. Maybe the ARM could make a GIF or PNG. That would avoid all the
> javascript nonsense. We'd just have to find the code somewhere.
>
> This bmp is 556K bytes.
>
> https://dl.dropboxusercontent.com/u/53724080/Circuits/Current_Limiters/LM317L_ilim.bmp
>
> That wouldn't be really terrible to send once a second or so over 100
> MBPS Ethernet. But my FPGA doesn't have enough RAM.
>
>
Bumpfiles are simple, so that's a win.  I usually generate those in my 
code, then (in a script) call ImageMagick's 'convert' to make them into 
.jpg or .png or whatever.

Cheers

Phil [system("convert foo.bmp foo.png") covers a multitude of sins]Hobbs

-- 
Dr Philip C D Hobbs
Principal Consultant
ElectroOptical Innovations LLC
Optics, Electro-optics, Photonics, Analog Electronics

160 North State Road #203
Briarcliff Manor NY 10510

hobbs at electrooptical dot net
http://electrooptical.net

[toc] | [prev] | [next] | [standalone]

#21508

On Thu, 23 Jul 2015 19:56:41 -0400, Phil Hobbs wrote:

> On 7/23/2015 7:22 PM, John Larkin wrote:
>> On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
>> <seemywebsite@myfooter.really> wrote:
>>
>>> On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>>>
>>>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>> wrote:
>>>>
>>>>> On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>>> wrote:
>>>>>>
>>>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>>>> interface as one way to talk to it. I thought it would be cool
>>>>>>>>>> to include an ADC so we could display waveforms, too. My
>>>>>>>>>> software guys here are mostly embedded types so we don't know a
>>>>>>>>>> lot about Javascript and such. I did a little searching and
>>>>>>>>>> mostly found things for displaying audio envelope cartoons; I
>>>>>>>>>> want a real oscilloscope-looking thing, so users can see what
>>>>>>>>>> happens as they change gains and filtering and trigger level
>>>>>>>>>> settings. Dual trace would be nice, the analog waveform and
>>>>>>>>>> corresponding comparator outputs.
>>>>>>>>>>
>>>>>>>>>> Has anybody done this? We'd consider getting outside help,
>>>>>>>>>> either advice or actual coding.
>>>>>>>>>>
>>>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>>>> Javascript, and maybe some zipped JS libraries to the browser.
>>>>>>>>>> And the company logo of course. The browser will send us text
>>>>>>>>>> strings to parse if the user wants to change parameters or
>>>>>>>>>> such. We would also deliver blocks of waveform data on request.
>>>>>>>>>> That's my PHB perspective on things; I'm just the hardware
>>>>>>>>>> designer.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> One approach is a CGI script that runs gnuplot under the covers.
>>>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>>>>
>>>>>>>> Isn't there an actual oscilloscope display package under Linux? 
>>>>>>>> It should be fairly straightforward to drive that from an
>>>>>>>> internet connection.  I guess requiring the customer to
>>>>>>>> installing such a package is not preferred.
>>>>>>>>
>>>>>>>>
>>>>>>> He is after a browser plugin - something like VNC, the way I do it
>>>>>>> on our spectrometers (I do not use a plugin but I could if I
>>>>>>> wanted to).
>>>>>>
>>>>>> Actually, I don't want a plugin, just a way for the browser to
>>>>>> display a waveform, using some javascript. We can store any
>>>>>> reasonable zipped javascript libraries in our gadget and deliver
>>>>>> them to the browser.
>>>>>
>>>>> I am not sure I have seen that done for live graphics - then
>>>>> scaling, perhaps autoranging etc., even if doable it would be a
>>>>> massive pain to support with all browsers as they keep on evolving.
>>>>> Your best bet might be to produce locally a .gif (or .png or
>>>>> whatever)
>>>>> bitmap, maintain it live and persuade the browser to refresh it
>>>>> regularly. Don't know how the latter is to be done though.
>>>>
>>>> We could do that in the FPGA! If nobody murders me for suggesting it.
>>>
>>> I don't know how to persuade a browser to auto-refresh, but GIF format
>>> uses run-length limiting for compression.  That means that line
>>> drawings of few colors tend to be very small -- you'll use up way more
>>> bits on text than on the pictures.
>>
>> There is some simple HTML thing that makes a page reload periodically.
>> That's apparently easy to do.
>>
>> A BMP would be easy to make inside the FPGA, but that would be slow to
>> load. Maybe the ARM could make a GIF or PNG. That would avoid all the
>> javascript nonsense. We'd just have to find the code somewhere.
>>
>> This bmp is 556K bytes.
>>
>> https://dl.dropboxusercontent.com/u/53724080/Circuits/Current_Limiters/
LM317L_ilim.bmp
>>
>> That wouldn't be really terrible to send once a second or so over 100
>> MBPS Ethernet. But my FPGA doesn't have enough RAM.
>>
>>
> Bumpfiles are simple, so that's a win.  I usually generate those in my
> code, then (in a script) call ImageMagick's 'convert' to make them into
> .jpg or .png or whatever.
> 
> Cheers
> 
> Phil [system("convert foo.bmp foo.png") covers a multitude of sins]Hobbs

Kinda hard for John to do since he has no OS (if I remember this whole 
thread well enough).

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

[toc] | [prev] | [next] | [standalone]

#21513

On Fri, 24 Jul 2015 14:55:50 -0500, Tim Wescott
<seemywebsite@myfooter.really> wrote:

>On Thu, 23 Jul 2015 19:56:41 -0400, Phil Hobbs wrote:
>
>> On 7/23/2015 7:22 PM, John Larkin wrote:
>>> On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
>>> <seemywebsite@myfooter.really> wrote:
>>>
>>>> On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>>>>
>>>>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>> wrote:
>>>>>
>>>>>> On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>>>>> interface as one way to talk to it. I thought it would be cool
>>>>>>>>>>> to include an ADC so we could display waveforms, too. My
>>>>>>>>>>> software guys here are mostly embedded types so we don't know a
>>>>>>>>>>> lot about Javascript and such. I did a little searching and
>>>>>>>>>>> mostly found things for displaying audio envelope cartoons; I
>>>>>>>>>>> want a real oscilloscope-looking thing, so users can see what
>>>>>>>>>>> happens as they change gains and filtering and trigger level
>>>>>>>>>>> settings. Dual trace would be nice, the analog waveform and
>>>>>>>>>>> corresponding comparator outputs.
>>>>>>>>>>>
>>>>>>>>>>> Has anybody done this? We'd consider getting outside help,
>>>>>>>>>>> either advice or actual coding.
>>>>>>>>>>>
>>>>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>>>>> Javascript, and maybe some zipped JS libraries to the browser.
>>>>>>>>>>> And the company logo of course. The browser will send us text
>>>>>>>>>>> strings to parse if the user wants to change parameters or
>>>>>>>>>>> such. We would also deliver blocks of waveform data on request.
>>>>>>>>>>> That's my PHB perspective on things; I'm just the hardware
>>>>>>>>>>> designer.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> One approach is a CGI script that runs gnuplot under the covers.
>>>>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>>>>>
>>>>>>>>> Isn't there an actual oscilloscope display package under Linux? 
>>>>>>>>> It should be fairly straightforward to drive that from an
>>>>>>>>> internet connection.  I guess requiring the customer to
>>>>>>>>> installing such a package is not preferred.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> He is after a browser plugin - something like VNC, the way I do it
>>>>>>>> on our spectrometers (I do not use a plugin but I could if I
>>>>>>>> wanted to).
>>>>>>>
>>>>>>> Actually, I don't want a plugin, just a way for the browser to
>>>>>>> display a waveform, using some javascript. We can store any
>>>>>>> reasonable zipped javascript libraries in our gadget and deliver
>>>>>>> them to the browser.
>>>>>>
>>>>>> I am not sure I have seen that done for live graphics - then
>>>>>> scaling, perhaps autoranging etc., even if doable it would be a
>>>>>> massive pain to support with all browsers as they keep on evolving.
>>>>>> Your best bet might be to produce locally a .gif (or .png or
>>>>>> whatever)
>>>>>> bitmap, maintain it live and persuade the browser to refresh it
>>>>>> regularly. Don't know how the latter is to be done though.
>>>>>
>>>>> We could do that in the FPGA! If nobody murders me for suggesting it.
>>>>
>>>> I don't know how to persuade a browser to auto-refresh, but GIF format
>>>> uses run-length limiting for compression.  That means that line
>>>> drawings of few colors tend to be very small -- you'll use up way more
>>>> bits on text than on the pictures.
>>>
>>> There is some simple HTML thing that makes a page reload periodically.
>>> That's apparently easy to do.
>>>
>>> A BMP would be easy to make inside the FPGA, but that would be slow to
>>> load. Maybe the ARM could make a GIF or PNG. That would avoid all the
>>> javascript nonsense. We'd just have to find the code somewhere.
>>>
>>> This bmp is 556K bytes.
>>>
>>> https://dl.dropboxusercontent.com/u/53724080/Circuits/Current_Limiters/
>LM317L_ilim.bmp
>>>
>>> That wouldn't be really terrible to send once a second or so over 100
>>> MBPS Ethernet. But my FPGA doesn't have enough RAM.
>>>
>>>
>> Bumpfiles are simple, so that's a win.  I usually generate those in my
>> code, then (in a script) call ImageMagick's 'convert' to make them into
>> .jpg or .png or whatever.
>> 
>> Cheers
>> 
>> Phil [system("convert foo.bmp foo.png") covers a multitude of sins]Hobbs
>
>Kinda hard for John to do since he has no OS (if I remember this whole 
>thread well enough).

And I won't have much ram; 256K bytes in the ARM, and some in the
FPGA, but not enough to store an entire bmp anywhere. 

SVG looks good so far; all we'd have to do is send the data points, as
text, not an image. A couple of kbytes might do it.


-- 

John Larkin         Highland Technology, Inc
picosecond timing   precision measurement 

jlarkin att highlandtechnology dott com
http://www.highlandtechnology.com

[toc] | [prev] | [next] | [standalone]

#21516

On Fri, 24 Jul 2015 14:11:12 -0700, John Larkin wrote:

> On Fri, 24 Jul 2015 14:55:50 -0500, Tim Wescott
> <seemywebsite@myfooter.really> wrote:
> 
>>On Thu, 23 Jul 2015 19:56:41 -0400, Phil Hobbs wrote:
>>
>>> On 7/23/2015 7:22 PM, John Larkin wrote:
>>>> On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
>>>> <seemywebsite@myfooter.really> wrote:
>>>>
>>>>> On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>>>>>
>>>>>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>>> wrote:
>>>>>>
>>>>>>> On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>>>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff
>>>>>>>> <dp@tgi-sci.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>>>>>> interface as one way to talk to it. I thought it would be
>>>>>>>>>>>> cool to include an ADC so we could display waveforms, too. My
>>>>>>>>>>>> software guys here are mostly embedded types so we don't know
>>>>>>>>>>>> a lot about Javascript and such. I did a little searching and
>>>>>>>>>>>> mostly found things for displaying audio envelope cartoons; I
>>>>>>>>>>>> want a real oscilloscope-looking thing, so users can see what
>>>>>>>>>>>> happens as they change gains and filtering and trigger level
>>>>>>>>>>>> settings. Dual trace would be nice, the analog waveform and
>>>>>>>>>>>> corresponding comparator outputs.
>>>>>>>>>>>>
>>>>>>>>>>>> Has anybody done this? We'd consider getting outside help,
>>>>>>>>>>>> either advice or actual coding.
>>>>>>>>>>>>
>>>>>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>>>>>> Javascript, and maybe some zipped JS libraries to the
>>>>>>>>>>>> browser. And the company logo of course. The browser will
>>>>>>>>>>>> send us text strings to parse if the user wants to change
>>>>>>>>>>>> parameters or such. We would also deliver blocks of waveform
>>>>>>>>>>>> data on request.
>>>>>>>>>>>> That's my PHB perspective on things; I'm just the hardware
>>>>>>>>>>>> designer.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> One approach is a CGI script that runs gnuplot under the
>>>>>>>>>>> covers.
>>>>>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy
>>>>>>>>>>> myself.)
>>>>>>>>>>
>>>>>>>>>> Isn't there an actual oscilloscope display package under Linux?
>>>>>>>>>> It should be fairly straightforward to drive that from an
>>>>>>>>>> internet connection.  I guess requiring the customer to
>>>>>>>>>> installing such a package is not preferred.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> He is after a browser plugin - something like VNC, the way I do
>>>>>>>>> it on our spectrometers (I do not use a plugin but I could if I
>>>>>>>>> wanted to).
>>>>>>>>
>>>>>>>> Actually, I don't want a plugin, just a way for the browser to
>>>>>>>> display a waveform, using some javascript. We can store any
>>>>>>>> reasonable zipped javascript libraries in our gadget and deliver
>>>>>>>> them to the browser.
>>>>>>>
>>>>>>> I am not sure I have seen that done for live graphics - then
>>>>>>> scaling, perhaps autoranging etc., even if doable it would be a
>>>>>>> massive pain to support with all browsers as they keep on
>>>>>>> evolving.
>>>>>>> Your best bet might be to produce locally a .gif (or .png or
>>>>>>> whatever)
>>>>>>> bitmap, maintain it live and persuade the browser to refresh it
>>>>>>> regularly. Don't know how the latter is to be done though.
>>>>>>
>>>>>> We could do that in the FPGA! If nobody murders me for suggesting
>>>>>> it.
>>>>>
>>>>> I don't know how to persuade a browser to auto-refresh, but GIF
>>>>> format uses run-length limiting for compression.  That means that
>>>>> line drawings of few colors tend to be very small -- you'll use up
>>>>> way more bits on text than on the pictures.
>>>>
>>>> There is some simple HTML thing that makes a page reload
>>>> periodically. That's apparently easy to do.
>>>>
>>>> A BMP would be easy to make inside the FPGA, but that would be slow
>>>> to load. Maybe the ARM could make a GIF or PNG. That would avoid all
>>>> the javascript nonsense. We'd just have to find the code somewhere.
>>>>
>>>> This bmp is 556K bytes.
>>>>
>>>> https://dl.dropboxusercontent.com/u/53724080/Circuits/
Current_Limiters/
>>LM317L_ilim.bmp
>>>>
>>>> That wouldn't be really terrible to send once a second or so over 100
>>>> MBPS Ethernet. But my FPGA doesn't have enough RAM.
>>>>
>>>>
>>> Bumpfiles are simple, so that's a win.  I usually generate those in my
>>> code, then (in a script) call ImageMagick's 'convert' to make them
>>> into .jpg or .png or whatever.
>>> 
>>> Cheers
>>> 
>>> Phil [system("convert foo.bmp foo.png") covers a multitude of
>>> sins]Hobbs
>>
>>Kinda hard for John to do since he has no OS (if I remember this whole
>>thread well enough).
> 
> And I won't have much ram; 256K bytes in the ARM, and some in the FPGA,
> but not enough to store an entire bmp anywhere.
> 
> SVG looks good so far; all we'd have to do is send the data points, as
> text, not an image. A couple of kbytes might do it.

I would make sure that SVG is universally available on browsers, but if 
it is -- go for it.

GIF or TIFF would reduce a typical O-scope image down to kbytes, too.  
TIFF, it appears, uses a bunch of different compression formats 
(including LZW); if you use the RLL version then the file is bigger than 
GIF, but still less than 100kB.

Just for giggles I did it, once to GIF, and once to TIFF using RLL.  The 
GIF file here is 10kB, the TIFF file is 25kB:

<<https://drive.google.com/file/d/0B5lSHlBBxGvjNl90MFA0MkI5NlU/view?
usp=sharing>>
<<https://drive.google.com/file/d/0B5lSHlBBxGvjQ2l1T05qV1VvejQ/view?
usp=sharing>>

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

[toc] | [prev] | [next] | [standalone]

#21533

On 24.07.2015 23:11, John Larkin wrote:

> 
> SVG looks good so far; all we'd have to do is send the data points, as
> text, not an image. A couple of kbytes might do it.

You can calculate the bitmap within the browser. Here a minimal
html file which displays a random bitmap:


<!DOCTYPE HTML><html> <head></head><body><script>

window.onresize = resize; function resize(){window.location.href=window.location.href;}
var intFrameWidth = window.innerWidth-16; var intFrameHeight = window.innerHeight-24;
document.write('<canvas id="Canvas" width="'+intFrameWidth+'" height="'+intFrameHeight+'"></canvas>');


var canvas = document.getElementById('Canvas');
var context = canvas.getContext('2d');

   // Creates an Image Object of size intFrameWidth * intFrameHeight
var imageData = context.createImageData(intFrameWidth, intFrameHeight);

  // Takes data in the Canvas Pixel Array
var CanvasPixelArray = imageData.data;

  // Calculate total no of pixels
var total_pixel = imageData.width*imageData.height;

  // Random RGBa values for each pixel
for (var i = 0; i < total_pixel; i++)
  {CanvasPixelArray[i*4] = Math.floor(Math.random()*255);
   CanvasPixelArray[i*4+1] = Math.floor(Math.random()*55);
   CanvasPixelArray[i*4+2] = Math.floor(Math.random()*155);
   CanvasPixelArray[i*4+3] = 255;
  };

  // Display the Image
context.putImageData(imageData, 0, 0);

</script> </body> </html>

[toc] | [prev] | [next] | [standalone]

#21509

On Thu, 23 Jul 2015 16:22:04 -0700, John Larkin wrote:

> On Thu, 23 Jul 2015 17:54:47 -0500, Tim Wescott
> <seemywebsite@myfooter.really> wrote:
> 
>>On Thu, 23 Jul 2015 15:30:11 -0700, John Larkin wrote:
>>
>>> On Fri, 24 Jul 2015 01:19:09 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>> wrote:
>>> 
>>>>On 24.7.2015 ?. 00:50, John Larkin wrote:
>>>>> On Fri, 24 Jul 2015 00:13:19 +0300, Dimiter_Popoff <dp@tgi-sci.com>
>>>>> wrote:
>>>>>
>>>>>> On 23.7.2015 ?. 23:49, rickman wrote:
>>>>>>> On 7/23/2015 4:34 PM, Phil Hobbs wrote:
>>>>>>>> On 7/23/2015 2:18 PM, John Larkin wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I'm designing a tachometer box and it will have a web page
>>>>>>>>> interface as one way to talk to it. I thought it would be cool
>>>>>>>>> to include an ADC so we could display waveforms, too. My
>>>>>>>>> software guys here are mostly embedded types so we don't know a
>>>>>>>>> lot about Javascript and such. I did a little searching and
>>>>>>>>> mostly found things for displaying audio envelope cartoons; I
>>>>>>>>> want a real oscilloscope-looking thing, so users can see what
>>>>>>>>> happens as they change gains and filtering and trigger level
>>>>>>>>> settings. Dual trace would be nice, the analog waveform and
>>>>>>>>> corresponding comparator outputs.
>>>>>>>>>
>>>>>>>>> Has anybody done this? We'd consider getting outside help,
>>>>>>>>> either advice or actual coding.
>>>>>>>>>
>>>>>>>>> I assume our box will, through some port, deliver HTML,
>>>>>>>>> Javascript, and maybe some zipped JS libraries to the browser.
>>>>>>>>> And the company logo of course. The browser will send us text
>>>>>>>>> strings to parse if the user wants to change parameters or such.
>>>>>>>>> We would also deliver blocks of waveform data on request. That's
>>>>>>>>> my PHB perspective on things; I'm just the hardware designer.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> One approach is a CGI script that runs gnuplot under the covers.
>>>>>>>> IIRC quite a few folks do that.  (I'm a static HTML guy myself.)
>>>>>>>
>>>>>>> Isn't there an actual oscilloscope display package under Linux? 
>>>>>>> It should be fairly straightforward to drive that from an internet
>>>>>>> connection.  I guess requiring the customer to installing such a
>>>>>>> package is not preferred.
>>>>>>>
>>>>>>>
>>>>>> He is after a browser plugin - something like VNC, the way I do it
>>>>>> on our spectrometers (I do not use a plugin but I could if I wanted
>>>>>> to).
>>>>>
>>>>> Actually, I don't want a plugin, just a way for the browser to
>>>>> display a waveform, using some javascript. We can store any
>>>>> reasonable zipped javascript libraries in our gadget and deliver
>>>>> them to the browser.
>>>>
>>>>I am not sure I have seen that done for live graphics - then scaling,
>>>>perhaps autoranging etc., even if doable it would be a massive pain to
>>>>support with all browsers as they keep on evolving.
>>>>Your best bet might be to produce locally a .gif (or .png or whatever)
>>>>bitmap, maintain it live and persuade the browser to refresh it
>>>>regularly. Don't know how the latter is to be done though.
>>> 
>>> We could do that in the FPGA! If nobody murders me for suggesting it.
>>
>>I don't know how to persuade a browser to auto-refresh, but GIF format
>>uses run-length limiting for compression.  That means that line drawings
>>of few colors tend to be very small -- you'll use up way more bits on
>>text than on the pictures.
> 
> There is some simple HTML thing that makes a page reload periodically.
> That's apparently easy to do.
> 
> A BMP would be easy to make inside the FPGA, but that would be slow to
> load. Maybe the ARM could make a GIF or PNG. That would avoid all the
> javascript nonsense. We'd just have to find the code somewhere.
> 
> This bmp is 556K bytes.
> 
> https://dl.dropboxusercontent.com/u/53724080/Circuits/Current_Limiters/
LM317L_ilim.bmp
> 
> That wouldn't be really terrible to send once a second or so over 100
> MBPS Ethernet. But my FPGA doesn't have enough RAM.

I haven't personally done this, but I've poked at it, and an office-mate 
of mine did it, before all the file conversion stuff was readily 
available.

If I recall correctly, GIF encoding is on the lines of

100 black, 1 white, 25 black, etc., for each line.

So if you could generate a bmp in your FPGA, you could generate the meat 
of a GIF almost as easily, then have the ARM processor wrap it with the 
appropriate header and footer and send it out.

I'll even do it for you -- if you wait until November for me to get 
started on it.

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

[toc] | [prev] | [next] | [standalone]

#21511

On 2015-07-24, Tim Wescott <seemywebsite@myfooter.really> wrote:

> If I recall correctly, GIF encoding is on the lines of
>
> 100 black, 1 white, 25 black, etc., for each line.

That's call run-length encoding, and it's what TIFF uses.

GIF files are encoded as 8-bits-per-pixel (with a 256-byte color
lookup table), and then compressed using the Lempel-Ziv-Welch
algorithm.

https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch

> So if you could generate a bmp in your FPGA, you could generate the meat 
> of a GIF almost as easily, then have the ARM processor wrap it with the 
> appropriate header and footer and send it out.

Implementing LZW in an FPGA would be a daunting, but people have done
it.

> I'll even do it for you -- if you wait until November for me to get 
> started on it.

-- 
Grant Edwards               grant.b.edwards        Yow! Gee, I feel kind of
                                  at               LIGHT in the head now,
                              gmail.com            knowing I can't make my
                                                   satellite dish PAYMENTS!

[toc] | [prev] | [next] | [standalone]

#21515

On Fri, 24 Jul 2015 20:15:21 +0000, Grant Edwards wrote:

> On 2015-07-24, Tim Wescott <seemywebsite@myfooter.really> wrote:
> 
>> If I recall correctly, GIF encoding is on the lines of
>>
>> 100 black, 1 white, 25 black, etc., for each line.
> 
> That's call run-length encoding, and it's what TIFF uses.
> 
> GIF files are encoded as 8-bits-per-pixel (with a 256-byte color lookup
> table), and then compressed using the Lempel-Ziv-Welch algorithm.
> 
> https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch

Huh. I musta had TIFF and GIF confused.  TIFF may be suitable, if John 
doesn't end up using SVG.

>> So if you could generate a bmp in your FPGA, you could generate the
>> meat of a GIF almost as easily, then have the ARM processor wrap it
>> with the appropriate header and footer and send it out.
> 
> Implementing LZW in an FPGA would be a daunting, but people have done
> it.

I'm not so sure it would be all that bad, if you were writing something 
specific to GIF format.

>> I'll even do it for you -- if you wait until November for me to get
>> started on it.

My offer still stands, GIF or TIFF.  John's looking at SVG, which isn't a 
bad choice if it's universal.

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.arch.embedded

csiph-web