Neutrino Newbie learning curve?

Does that make me a NeuNew?)

I’ve read the FAQs and searched the news, but I still need your help
please.

I’m trying to determine the best steps to take to get myself to a
somewhat competent level of embedded NTO programming skill.

Here’s where I am:

  • I can program micros (like AVR) in ANSI C – no RTOS experience.
  • I have never used C++ – unless my grades count.
  • I have never written programs for any operating system.
  • You don’t want me to administer your Linux server.
  • I understand hardware.
  • I understand (to a reasonable degree) TCP/IP-based networking.
  • I do NOT understand message-based programming, but I barely have a
    clue.
  • I designed an oscillator that ended up on Mars! – I had to say that
    because my list was depressing me. :[

Here’s where I want to be:

I want to be able to develop embedded NTO-enabled devices which
incorporate one or more of the following features:

  1. LCD interface (up to 1024x768 @ 256 colors)
  2. TCP/IP connectivity
  3. GUI
  4. Terminal emulator like vt100
  5. Web browser
  6. RS-422 serial communications
  7. Customized GUI shell for sending/receiving RS-422 commands
  8. It works.

I certainly do not have any real-time requirements at this point, but
the possibility exist that I will want it in the future. (ie. I have no
real-time real-time requirement.)

Should I start with learning my way around Linux and programming in that
environment with GNU tools? Or, should I jump right in to RTP on a PC
and sink-or-swim using the upcoming CW tools? At some point I want to
take a 3-5 day course (from Parse or QSSL), but I also want to have a
chance of comprehending the material. Please let me know if I am
missing something or just doing it all wrong.

And, yes, I’m wearing Nomex.

Thank you!
Ray Page
Raylar Design, Inc.
Austin, TX

You sound pretty experienced to me, and I’m still going to try :wink:

Based on your honest description of yourself, you sounds like a guy who got
the right spirit, and therfore will make it.

But now for my question to you:
What is your oscillator on mars doing? Still swinging?
And on what project was it?

Just curiose…

Janne // once made a oscillator that happened to be on the same freq as the
local radiostation, and made my own “local” radio…

“Ray Page” <rtpage_@austin.rr._com> wrote in message
news:MPG.142007f4e7273c9c989685@209.226.137.7

Does that make me a NeuNew?)

I’ve read the FAQs and searched the news, but I still need your help
please.

I’m trying to determine the best steps to take to get myself to a
somewhat competent level of embedded NTO programming skill.

Here’s where I am:

  • I can program micros (like AVR) in ANSI C – no RTOS experience.

RTOS is a concept of its own IMHO. If you’ve never
done that, expect to hit a few walls :wink:

  • I have never used C++ – unless my grades count.

QRTP/NTO don’t rely on C++

  • I have never written programs for any operating system.

Depending on what you want to acheive this may not be to
bad.

  • You don’t want me to administer your Linux server.

That should be ok

  • I understand hardware.

That’s good

  • I understand (to a reasonable degree) TCP/IP-based networking.

Great!

  • I do NOT understand message-based programming, but I barely have a
    clue.
  • I designed an oscillator that ended up on Mars! – I had to say that
    because my list was depressing me. :[

Here’s where I want to be:

I want to be able to develop embedded NTO-enabled devices which
incorporate one or more of the following features:

  1. LCD interface (up to 1024x768 @ 256 colors)
  2. TCP/IP connectivity
  3. GUI
  4. Terminal emulator like vt100
  5. Web browser
  6. RS-422 serial communications
  7. Customized GUI shell for sending/receiving RS-422 commands
    :sunglasses: > It works.

I certainly do not have any real-time requirements at this point, but
the possibility exist that I will want it in the future. (ie. I have no
real-time real-time requirement.)

Should I start with learning my way around Linux and programming in that
environment with GNU tools? Or, should I jump right in to RTP on a PC
and sink-or-swim using the upcoming CW tools? At some point I want to
take a 3-5 day course (from Parse or QSSL), but I also want to have a
chance of comprehending the material. Please let me know if I am
missing something or just doing it all wrong.

I would jump right into RTP on a PC. Since you want to use a GUI
better learn Photon right away. Plus why spend time learning linux
specifics
when will be useless on QRTP.

I stay away from CW, why spend >2000$ on an IDE and debugger (they
still use the GCC compiler I beleive)

You could also get someone to give you a head start in the
early design stage of your project. The courses are nice,
but they often don’t show you what NOT to do, and this
is what a learning curve is about :wink: Outside help will
steer you in the right direction.






And, yes, I’m wearing Nomex.

Thank you!
Ray Page
Raylar Design, Inc.
Austin, TX

It is part of the communications module on the Path Finder base unit. I think
the system has been dormant for a long time due to battery lifespan. I was
going to write my name inside of the oscillator case when I built it, but I was
so caught up in making sure it was sealed properly (imagine that) that I forgot
to do it. It would have been cool for someone to find my name in it a million
years from now.

Another one is one the NEAR (Near Earth Asteroid Rendezvous) vehicle. It is
used for the time-base for the laser doppler rangefinder system. They make
great conversation for an otherwise boring analog guy.

BTW, unauthorized broadcast stations can be a lot of fun! --Not that I have
ever done that.

Janne W wrote:

You sound pretty experienced to me, and I’m still going to try > :wink:

Based on your honest description of yourself, you sounds like a guy who got
the right spirit, and therfore will make it.

But now for my question to you:
What is your oscillator on mars doing? Still swinging?
And on what project was it?

Just curiose…

Janne // once made a oscillator that happened to be on the same freq as the
local radiostation, and made my own “local” radio…