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

Groups > comp.lang.forth > #33926

Re: ball-hours

Cross-posted to 2 groups.

Show all headers | View raw

On 10/15/2014 8:36 AM, Joerg wrote:
> rickman wrote:
>> On 10/14/2014 3:37 PM, Joerg wrote:
>>> rickman wrote:
>>>>
>>>> I use a program under Win32Forth to run my test fixture.
>>>>
>>>
>>> I have to go by what talent pool is available and regarding Forth that
>>> looks pretty parched. Tomorrow I am going to meet with a new SW
>>> contractor. For the upcoming project I need someone local because later
>>> we'll have to work together a lot in the lab. Plus if I use my mountain
>>> bike I can get there without a car and partially without roads :-)
>>>
>>> What you usually find locally is C and sometimes assembler. Occasionally
>>> people know Basic but then that's about it.
>>>
>>> It's similar with hardware. Being able to secure local talent is a major
>>> factor driving 8051 family designs. Unfortunately I can't do that with
>>> the new project because I need a ton more horsepower but first I am
>>> going to see what the SW guy is familiar with.
>>
>> I was actually talking about you learning a language, but either way.
>>
>
> The only language I'd rally like to learn is Spanish :-)
>
> But seriously, I do not want to get too involved in the actual
> programming job because I am fully loaded with analog/mixed projects
> already and want to reserve at least a few hours per week for mountain
> biking.
>
>
>> It is funny how in the forth community Forth is considered to be easy to
>> learn and very facile for many tasks, especially when you need to
>> interact with hardware or anything else where you don't have all the
>> details clearly laid out.  But outside that community Forth is treated
>> like a three eyed toad.
>>
>
> Problem is, there is no Forth community out here. The last die-hard
> Forth aficionado I personally met was about 30 years ago in Europe.

I think you may be surprised.  I've already heard from three programmers 
from the few posts I've made in just three groups.  Unless you want me 
to send then directly to you, I am referring them to this thread.


>> I seem to recall that you use the 8051 because you want a 20 year
>> product life or something like that, right? ...
>
>
> Not on this project but otherwise, yes. One of my designs containing an
> 8051 will celebrate its 20th next year. Still in production and no end
> in sight. Second source is another concern and you can only get that for
> a small selection of 8051 uC.
>
>
>>    ... Does that affect your talent pool?
>>
>
> For other projects it does. We need to make sure that 10 years down the
> road it will be possible to find someone locally who can re-write the
> code. With 8051 that's usually not a problem.
>
>
>> http://www.forth.com/embedded/swiftx-embedded-systems-development-tools.html?MCU=8051
>>
>>
>> http://www.mpeforth.com/xc7.htm#f7targets
>>
>>  From your web page it looks like you are a half hour east of Sacramento,
>> California in Cameron Park.
>>
>
> Yep, near Hwy 50 just before Placerville. But the project is already
> committed to a local guy if he feels comfortable to do it. Which I
> should know by tomorrow. It has to be local in this case.
>
>
>> I am cross posting to the forth group.  Tell us a few details and we'll
>> see if anyone can accommodate your needs.
>>
>
> Can't reveal too many details but from a code point of view essentially
> several FFTs, one of them a big one, 1024 point complex (I/Q) every
> 5msec, overlapping. Extract phase, some complex-conjugate math to
> extricate component values every 5msec (sort of a poor man's reverse
> network analysis), followed by filtering, some more math or a LUT, then
> modulating the result onto an audio carrier. Sprinkled with user
> interface handling and calibration routines. Back of the envelope calcs
> indicate that this will reasonably fit into a 100MHz ARM but of course
> I'd rather have a few more megahoitzes.

I thought your current project was for an 8051?  I guess that was old 
projects or maybe old programmers... lol.  Your other post seemed to be 
talking about bitbanging the I2S port to the CODEC.  How does that work 
into the 100 MHz need?  Bitbanging a serial port of any kind can be CPU 
cycle intensive.

-- 

Rick

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-15 00:25 -0400
  Re: ball-hours bruce.person@gmail.com - 2014-10-14 23:51 -0700
    Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-15 03:15 -0400
  Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-15 05:36 -0700
    Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-15 16:22 -0400
      Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-15 16:12 -0700
        Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-15 22:48 -0400
          Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-16 11:21 -0700
            Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 15:24 -0400
              Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-16 13:37 -0700
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 17:42 -0400
                Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-17 07:14 -0700
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-17 14:03 -0400
                Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-17 12:03 -0700
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-17 15:23 -0400
                Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-17 12:44 -0700
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-17 18:37 -0400
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 20:59 -0400
                Re: ball-hours albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-10-17 08:43 +0000
                Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-17 13:53 -0400
                Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-17 07:50 -0700
        Re: ball-hours Raimond Dragomir <raimond.dragomir@gmail.com> - 2014-10-15 20:42 -0700
          Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 01:50 -0400
            Re: ball-hours Raimond Dragomir <raimond.dragomir@gmail.com> - 2014-10-16 00:49 -0700
              Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 05:14 -0400
            Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-16 11:58 -0700
        Re: ball-hours "Elizabeth D. Rather" <erather@forth.com> - 2014-10-16 08:32 -1000
          Re: ball-hours rickman <gnuarm@gmail.com> - 2014-10-16 15:32 -0400
          Re: ball-hours Joerg <news@analogconsultants.com> - 2014-10-16 13:45 -0700

csiph-web