(1)
Configure SIO : Primary (USB
Programming Port)
(2) Configure ACR : Not mapped
(3) Configure 2SIO port 1 : Serial (pin 18/19)
(4) Configure 2SIO port 2 : Serial (pin A6/A7)
--
You received this message because you are subscribed to the Google Groups "Altair-Duino" group.
To unsubscribe from this group and stop receiving emails from it, send an email to altair-duino...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/altair-duino/0151a188-35c6-43a8-bc61-acd9181377bfn%40googlegroups.com.
-c.jpg?part=0.1&view=1)
-c.jpg?part=0.2&view=1)
don't you lose the GEOFF terminal functionality with this method of removing the PIC and connecting to the board that way for the second serial port?
I think he is going to want to keep it, but up to him.this is why i prefer the direct soldering to the DUE board itself, to add the second serial, it can be dangerous as you can easily damage the DUE.
your method is good if you do want to replace the GEOFF as the default terminal: thumb up.
i can't speak for the switch turning the pic on and off, but i will say that with all the TTL 232 converters i had major issues with them running at 5V i couldn't figure it out until i switched power to 3.3V then everything started working. no idea, chinese-ium i guess.
On Mar 30, 2025, at 1:29 AM, John Galt <furba...@gmail.com> wrote:you have to change SIO primary to Serial (pin A6/A7) that is the port on the back of the Altair-duino.
To view this discussion visit https://groups.google.com/d/msgid/altair-duino/ad30cd1e-5ca4-4d2d-981d-ee24ca2967b2n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/altair-duino/22ae535d-d44b-44d2-b9bb-f8f1d4e2614fn%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/altair-duino/751d9570-ee13-4a79-a4d7-206e36e610d7n%40googlegroups.com.
keep in mind when your remapping the serial ports its like the old way of connecting a phone call, your flipping jumper wires aroundso if you remap a port the software still sees the same ports no different its just on the hardware side something else has been connected in the place of the original.
It is in the 88-2 serial input/output board manual 2sio and 2sio2 manuals.Together with the configuration menu:Ports in decimal.control register/data register2SIO port 1 ------ 16/172SIO port 2 ----- 18/192SIO2 port 1 ---- 20/212SIO2 port 2 ---- 22/23SIO is port 0/1----The mapping of all that in the configuration menu is just up to the user."A6/A7" is the 9 pin serial port on the back always.Serial (pin 18/19) would be the serial port to the Geoff PIC32 on that terminal board.On the original:profile #0 it defaults to using the Programmer micro USB connection as your connection to a primary terminal. putty or teratermProfile #1 is set for the GEOFF terminal on Serial (pin 18/19) which is really a fully internal serial device on the PRO kit.that is all you get with the default pro kit as built by the manual.I think the original WIFI add on went in place of the Geoff terminal as it shared the pins; I can't remember have to look at the old manual, because you had to map that to use pin (18/19) later i think you could map that in place of (A6/A7) then the rear serial port was disabled as the WIFI was using it. when the Geoff was not used then you needed to Map through the programmers micro usb port.
It is in the 88-2 serial input/output board manual 2sio and 2sio2 manuals.Together with the configuration menu:Ports in decimal.control register/data register2SIO port 1 ------ 16/172SIO port 2 ----- 18/192SIO2 port 1 ---- 20/212SIO2 port 2 ---- 22/23SIO is port 0/1----The mapping of all that in the configuration menu is just up to the user."A6/A7" is the 9 pin serial port on the back always.Serial (pin 18/19) would be the serial port to the Geoff PIC32 on that terminal board.On the original:profile #0 it defaults to using the Programmer micro USB connection as your connection to a primary terminal. putty or teratermProfile #1 is set for the GEOFF terminal on Serial (pin 18/19) which is really a fully internal serial device on the PRO kit.that is all you get with the default pro kit as built by the manual.I think the original WIFI add on went in place of the Geoff terminal as it shared the pins; I can't remember have to look at the old manual, because you had to map that to use pin (18/19) later i think you could map that in place of (A6/A7) then the rear serial port was disabled as the WIFI was using it. when the Geoff was not used then you needed to Map through the programmers micro usb port.
On Sunday, March 30, 2025 at 1:51:20 PM UTC-4 r4r...@gmail.com wrote:
-c1K.jpg?part=0.1&view=1)
I didn't, Tom said:You could tie into the RX and TX on the PIC32 of the Geoff and create an external Serial I/O portHowever, that really didn't involve keeping the original Geoff terminal working as he wrote about removing the PIC32 completely to make the connections.there is also a question as if it would even work keeping the PIC32 in place and attempted to keep its original functionality.You don't have to go that untested route.Understand there is a another serial port the RX and TX on the Arudino DUE board itself.If you remove the LEDS on the DUE for RX and TX then you can solder 2 new wires and create a new serial port which is mapped RX/TX under the configuration menu.go to page 26

The board on page 26 is the Arduino DUE, that is the main PCB that has all the pin headers that is plugged into the front panel board with all the Data and address switches and the LEDS.
yup that is the correct picture.
I use a fork of PuTTY called ExtraPuTTY as the terminal program and transfer program. It contains a very nice version of XModem built in, so all you need do is use the terminal to find what you want to transfer or where you want to put something from the computer you're using to access it, then activate the XModern feature and the file is losslessly transferred. I now use ExtraPuTTY, for all retro computers I use. It's no harder than regular PuTTY, and it saves steps because the file transport is in the same program as the terminal.
To view this discussion visit https://groups.google.com/d/msgid/altair-duino/ea0eaff7-7383-4946-bde4-76edf833208dn%40googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/altair-duino/ea0eaff7-7383-4946-bde4-76edf833208dn%40googlegroups.com.
I use Teraterm i like it better then putty or extraputty.the defaults for the connection is usually 9600,8N1unless you really did set your baud rates that high to 115,200its somewhat confusing because there are a few places you need to set your baud rates.The Pro board with the GEOFF has its own port management first thing i would do is Control F12 with the Geoff terminal and make sure you have the RS232 settings correct in there. 9600,8N1after that you want to go into the configuration menu and if remember under E and S you want to make sure all the settings match up with each other.one that is done and you have your USB to your windows 11 machine and Teraterm is running and making a connection...here is where an anomaly comes in that i noticed: i can only say this happens with windows machines and teraterm....teraterm for some reason will not complete the initial connection until it sees something come into the port that it picks up.so i wrote a little program called "PING" i actually sent you this program a few years ago in our email exchanges.its a little MBASIC program which i compiled and put into the Root of the A: for Cp/M to see for all users.Ping asks you which port you want to send out a ABC alphabet test string to.first it asks what port you want to ping in decimal 18 is usually the 9 pin serial port on the back of your altair-pro machine. 20,22 are the 2SIO2 ports that are higher and require a Firmware recompile to enable.once you select 18 it will then send out the ABC test string on that port. tera term will then see the test string and complete the connection.Now you want to use the mini usb port for your connection and leave the 9 pin serial alone on its own.so you have to be careful how you map them for file transfer without modifications. to use the standard pcput and pcget it can only see 2SIO port 1 and port 2 that is 16/17,18/19 in decimal.16/17 is in use with the disk drives and the primary terminal so you only have 18/19 to play with... in the configuration menu you would need to change your port mapping from the A6/A7 to USB programming for 2sio port 2 in order to have a file transfer connection.you would then use PING in the same way so that teraterm completes the connection over USB.now on my setup i have added USB native on the back of my case, so i have 2 micro USB connectors easy modification. i have also modified the altair firmware to enable 2sio2 ports 1 and 2i then map 2sio2 port 1 to my USB Native.the USB then goes from native into my windows 10/11 machine.i establish a connection via teraterm.then i run PING on the altair in cp/m to port 20.that sends out the ABC test string and teraterm completes the connection.i have modified PCPUT AND PCGET into PCPUT2 and PCGET2 these new versions only talk to 2sio2 where the original only talks to 2sio.now i can send and receive my files from my windows to altair machine on this higher serial port using Xmodem.this leaves all my lower port mapping alone i never have to change them.otherwise because you only have one usable 2sio port 2 serial port then your stuck going into your configuration menu and changing around your port mapping.with one available portthen you would the commandPCPUT WALT.BAS B to send to your windows 11 machineorPCGET WALT.BAS B to receive from your windows 11 machine.The "B" is super important because you have to be mapped to only open port you have that PCGET and PCPUT can see without modifications.if you have a serial port ABCD switch then you can really play around with devices you have connected.thing to remember is teraterm will see the port and make the initial connection but it won't finalize it until it sees activity coming in. it kind of sits there in a waiting loop and then Xmodem will not transfer just sits there waiting.also you have to make sure you have mapped the port such that your communications software under Cp/M can see it and talk to it this is limited without modification.just about all the standard communications programs will only see 2SIO PORT 1 or 2 and that means you need to switch around your ports in the configuration menu.since you have a stock setup then make sure you remap 2SIO port 2 from A6/A7 to USB programming.all of this sounds complex and overwhelming but it isn't you just have to understand why your shifting things around in the first place.
i good handshake message could be "CONNECT [BAUD RATE]" just like the old modem days. that would trigger teraterm and off you go.On Thursday, April 3, 2025 at 2:58:06 PM UTC-4 John Galt wrote:Whatever you use.When you establish a connection with teraterm, send it a some characters.If you see them on the teraterm terminal then you have established a connection.from there you use any communications software you like and you can send in any format you wish X,Y,Z modem transfers back and forth.just remember most cp/m communications software was only designed to see the first SIO card and its ports, so make sure you have your ports mapped as you need them in the configuration menu.