Paul Webster wrote:
> I remember the paper tape reader
Can't help one more off topic reminisce:
I remember these. They didn't come close to your tape speeds though. The
paper moved along at 50 bauds and stopped at each traction hole where 5
small steel rods pressed upwards to see if a hole
I enjoyed remembering the old days and hearing similar experiences of
the "technology breakthroughs" of the 80's.
Back to my OP, got it, thank you. I thought Python, but appreciate the
confirmation and the suggestion of Perl. I wanted to avoid effort down
the wrong path. For example, back in
bpa wrote:
> They were modified telex system which were circuit switched devices - so
> when ,message were sent there was a "copper loop" between device,IIRC
> signalling was done via current not volts and so guaranteed messages.
> The company I worked, one of their products was a compatible
Paul Webster wrote:
>
> I think that the only one that we did that was airline related was for
> Iceland Air Traffic Control.
> Surprisingly busy because of all of the routing over the north pole -
> they had control of flights over the airspace and there were a lot.
> I was sent over there
Paul Webster wrote:
> IATA messages ... although most of our systems were in places that used
> similar format but were not airlines.
They were modified telex system which were circuit switched devices - so
when ,message were sent there was a "copper loop" between device,IIRC
signalling was
At college (EE) we had a VAX 11/780 with 4MB of RAM. I remember when it
was upgraded to 8MB and student users got bumped from 1200 baud VT100s
to 9600. Started out in DEC Basic, Fortran and Pascal. After getting my
first Squeezeboxes in 2008 I decided to learn a 'modern' language like
Perl. When
IATA messages ... although most of our systems were in places that used
similar format but were not airlines.
I think that the only one that we did that was airline related was for
Iceland Air Traffic Control.
Surprisingly busy because of all of the routing over the north pole -
they had
Paul Webster wrote:
>
> ZCZC ABC123
> RR CHICAGO MILAN
> .123
> THE QUICK BROWN FOX ...
>
This was secure text messages on original teletype TTY ! All message
began ZCZC and ended . I did work with Airline networks and with
such a message you could halt a flight.
The ASR33 was
I remember the paper tape reader being PR: as a device (papertape
reader) ... and this one looks similar
https://www.vintagecomputer.net/browse_thread_record.cfm?id=737=1
from the back it looks like it could handle 60 characters a second.
I remember the tape whizzing through it.
In fact I was
Paul Webster wrote:
> For my first professional work we wrote on coding sheets and then about
> a week later we received punched paper tapes with the result of our
> scrawl.
> After loading them into the mini computer, the paper tapes went into the
> fire safe for backup.
Paper tape - and an
Paul Webster wrote:
> I used punched cards at university (first year only).
>
> and a 2nd cheer some considerable time later when we could use cursor
> keys to move around in a full screen editor!
ohhh.., I had forgotten about that! Writing fortran on a PC in DOS when
a small canadian company
I used punched cards at university (first year only).
For my first professional work we wrote on coding sheets and then about
a week later we received punched paper tapes with the result of our
scrawl.
After loading them into the mini computer, the paper tapes went into the
fire safe for
Could add Algol and Cobol to the list.
And I had the experience of using punch cards. The fact that they had no
automatic sequence numbers on it called for trouble every once in a
while...
reinholdk's Profile:
paul- wrote:
> Pascal yes, but otherwise I avoided that other stuff. I'm a mechanical
> engineer, so coding is just for fun.
>
> I was lucky enough not to have to use punch cards. The university
> installed the mainframe a year or two before I got there.
I am an EE but also got a CS degree
Pascal yes, but otherwise I avoided that other stuff. I'm a mechanical
engineer, so coding is just for fun.
I was lucky enough not to have to use punch cards. The university
installed the mainframe a year or two before I got there.
piCorePlayer a small player for the Raspberry Pi in RAM.
For the Raspberry Pi, Python seems to be the language of choice,
although we were able to write 99% of piCorePlayer using just shell
scripts.
You will find most RPi example code on the web is written in Python, so
choosing Python will make life easier.
The most important thing you have to do
Redrum wrote:
> Fortran, you(we) are dating ourselves Paul- :p How about Lisp, Ada,
> Prolog, Pascal, and Modula-2?
Fortran II, BCPL and Snobol.
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View
Fortran, you(we) are dating ourselves Paul- :p How about Lisp, Ada,
Prolog, Pascal, and Modula-2?
Thanks for helping getting me kicked off in the right direction, exactly
the info I was looking for.
bpa, I should have been more clear, not home automation, automation. My
bad. At the risk of
Hey, I remember Fortran. Did that in college. My first Unix experience
was also in college on Silicon Graphics machines.
In today's Raspberry Pi, Python seems to be the code of choice. Its
quite powerful, handles all of the interfacing options. (GPIO, i2c,
spi, etc) Lots of code examples
There are many home automation (HA) platforms on Pi. Lots of ground work
already done. Each platform has a different emphasis.
Buy a few smart devices you need and then spend time getting them to
work with the platforms to see the advantages.
Python is quite popular with these platforms but
Hi,
I need a little advice/direction...
I am a retired electrical engineer with embedded hardware and "retro"
software development experience (Retro - unix, qnx, C (before "++",
assembly). So I know how to code, but am not familiar with anything
relatively current. I actually remember using
21 matches
Mail list logo
