Gotcha buddy.


https://www.amazon.com/Console-Essential-Accesory-Ubiquity-Switches/dp/B01AFNBC3K/ref=mp_s_a_1_3?keywords=usb+serial+rj45&qid=1565091778&s=gateway&sr=8-3

This what I use. Imagine you are using Windows. Double check to make sure your serial port is showing up in hardware manager. If you can see the port in the program but it’s not connecting make sure the baud rates match.

Or you made need a USB to serial adapter if the array doesn’t have an rj45 comms port and has a db9 comms port.


https://www.amazon.com/Sabrent-Converter-Prolific-Chipset-CB-DB9P/dp/B00IDSM6BW/ref=mp_s_a_1_3?keywords=usb+to+serial&qid=1565092473&s=gateway&sr=8-3

Yes if you buy the kit you need a machine with a serial connection or USB 2.0 to Serial converter plus a null modem serial cable.

Here is a basic how to

Edit: Fixed link thanks to /u/nick_danger

Unless you have 32-bit Windows 10 (which you probably don't) there is no support for the USB tower. There simply are no 64-bit USB tower drivers in existence.

You have a couple options: I would suggest setting up a 32-bit Windows XP VM like /u/nullabillity said, and install your software within. I can personally confirm that this works.
The other option (which I've also tested) is to buy a serial IR tower and a serial-to-usb adapter. This is the only way to program an RCX using a modern 64-bit operating system.

You will need to do one of these two things regardless. But, based on your error message, there may be an additional problem - are you using the right version of Robolab? Are you sure that your current version supports RCX, and is not just an NXT-only version?

If you still can't get Robolab working, you might want to switch to a different programming software. You can download a disk image of the original RIS 2.0 software from here (many thanks to whoever put these online). Or, if you're comfortable with text-based languages, you could try NQC or LeJOS instead.
Good luck, and let me know how it turns out!

I ordered this one.

https://www.amazon.com/gp/product/B00IDSM6BW/ref=ppx_yo_dt_b_asin_title_o00__o00_s00

It's a good switch to play around with to learn Cisco command line, and you will want to, because it may not even function correctly depending on the previous configuration. You will want to pick up a USB to serial, and a Cisco Console cable to at least factory reset it.

>and a gaming PC with an asus z170 board I'd like to use as my console.

You don't access the console full-time. Usually you just use the console cable for:

1. Setting up initially
   
2. Emergencies when your machinations lock yourself out of the switch
   
   Once the switch is set up, you just access it via its management IP over something like SSH.
   
   >there is no way to connect a DB9 to RJ45 console cable to my board
   
   I'm assuming your board has USB, and the switch comes with a console cable it looks like, so you can use either:
   
   

• USB to Serial. This will allow you to use the cable it came with.
  
• Or you can skip the adaptor and just get a direct cable.
  
  I use the latter. With an RJ45->DB9 adaptor, I'm able to connect to basically any switch, new or old.
  

Use a regular console cable [RJ45 to DB9][1], coupled with a serial to USB [DB9 to USB][2].

The above is a better setup, and a bit more reliable than a straight up [RJ45 to USB][3] cable. (imo)



[1]:http://www.amazon.com/72-3383-01-Rollover-Console-Cable-Female/dp/B005S2KPPU "RJ45 to DB9"
[2]:http://www.amazon.com/Sabrent-Serial-RS-232-Converter-CB-DB9P/dp/B00IDSM6BW "DB9 to USB"
[3]:http://www.amazon.com/CISCO-Console-Cable-Replaces-72-3383-01/dp/B00I8CT8YG "RJ45 to USB"

I was just reading about null modems for file transfer. I'm having a rather hard time locating a good walk-through. A lot to learn with all this, which is why I am doing it I suppose. A link to some good tutorials would be appreciated so I can stop bothering you

Would this work: StarTech Null Modem - female to male

Sabrent USB to Serial Converter

Can I simply do the copy command via my Windows 10 command prompt or should I be booting some sort of MS DOS installation? Also, can you elaborate more on avoiding IRQ 4? Would I need to buy a separate serial adapter card?

EDIT: Upon further research it looks like there may be more to it than just the simple copy command, including having to initialize the com port beforehand with speeds and stuff I am not familiar with. However I am unable to locate anything conclusive. Other people have to have done this to be able to use mTCP at all so I am puzzled why my googlefu is failing me

The Prolific Serial -> USB is what you use to plug into your PC.

Switch Console port -> Cisco Console to Serial cable -> serial to USB adapter -> USB port on PC

Cisco console cable: https://www.amazon.com/Cisco-72-3383-01-Rollover-Console-Female/dp/B005S2KPPU/

Prolific Serial to USB adapter: https://www.amazon.com/Sabrent-Converter-Prolific-Chipset-CB-DB9P/dp/B00IDSM6BW/

They have console -> usb cables, but YMMV on that.

it's an old type of computer interface

https://en.wikipedia.org/wiki/RS-232

You can buy a serial to USB converter though and use them on a modern computer just fine.

example:
https://www.amazon.com/Sabrent-Converter-Prolific-Chipset-CB-DB9P/dp/B00IDSM6BW/ref=sr_1_1?ie=UTF8&qid=1521575806&sr=8-1&keywords=serial+to+USB

just google serial to USB on amazon, monoprice, or whatever.

This might be worth a $10 gamble. I haven't tried it, but unless Trimble is doing something proprietary, I don't see why a generic 9-pin serial to USB wouldn't work.

> I just couldn't connect to the other ports. Do I have to activate them in some way or should they be active out of the box?

By default Eth0 has 192.168.1.1 and that is it. The other ports are lit but without an IP address.

> I held the reset button for 10 second while it was running (runtime reset because that's what the manual recommended).

That's not what the manual says to do to reset. They say: power down device, hold pin in, power on, keep holding it til Eth 1 (or maybe eth2 I forget) blinks orange, hold until that orange light dies out, then let go of pin.

> eBay would work?

Yea eBay should work just fine, Amazon too if you want to get this back up and running in a timely manner.

I got this one and it has worked for me, but there are loads out there even cheaper.

RJ-45 console cables are often propitiatory and different pins depending on the device :(

You'll need to use a USB -> Serial adapter then the proper cable that came with the device.

This is the model I use, it works good even on Windows 10: http://smile.amazon.com/Sabrent-Serial-RS-232-Converter-CB-DB9P/dp/B00IDSM6BW/

I do not recommend the IO Gear one. I haven't used it in years but unless they've done a much better job in recent years it was extremely buggy. It would often crash my terminal application. This is the one: http://smile.amazon.com/IOGEAR-Serial-RS-232-Adapter-GUC232A/dp/B000067VB7/

This one seems to have great reviews and some serial troubleshooting features: http://smile.amazon.com/GearMo-Adapter-Indicators-Windows-Support/dp/B00AHYJWWG/

https://www.amazon.com/Sabrent-Converter-Prolific-Chipset-CB-DB9P/dp/B00IDSM6BW/ref=pd_lpo_vtph_147_bs_t_1?_encoding=UTF8&psc=1&refRID=347S3YAMRB8G0AKJVT1Q

:)

TL:DR; Press <RETURN> after IN#2; you should see IMMEDIATE input on the //c. You CAN use lower-case. You may need to select File > Serial Config > Apple //c ImageWriter Cable option. Try a different USB-DB9 cable if after #Troubleshooting (below) doesn't work.

---

AppleWin developer here -- I just went through this exact same issue this week having recently moved and started unboxing my Apple 2 Lab these past few weeks. Sadly I didn't pay attention to the exact ADTPro setup I had before so I was forced to start over from scratch. In the end this actually worked out since I never documented what I did before so here is an opportunity for me to do this now -- and you get the benefit. :-)

Requirements

• MacBook Pro (MBP)
  
• OSX (I'm running 10.10 but version shouldn't matter)
  
• Apple //c
  
• Serial Cable DB-9 (Female) to DIN-5 (male) null modem cable
  
• USB to RS232 DB9 (male) serial adapter
  
• ADTPro 2.x
  
  

  Caveats
  

  
  NOT all USB-DB9 serial cables work!!! Of the three I have only this one works:
  
  

• IOcrest USB 2.0 to RS232 DB9.
  
  These ones do NOT work:
  
  
• Sabrent USB 2.0 to Serial (9-Pin) DB-9 RS-232
  
• Tripp Lite Keyspan High-Speed USB to Serial Adapter, PC & Mac (USA-19HS) -- Note: I believe this one might work -- as I see the serial port with the with provided /Applicatons/Keyspan Serial Assistant. You need to install the kernel driver and reboot OSX (macOS). HOWEVER, every time I plug it in the mouse and OS freeze. You are forced to hold down the power button reboot. :-/
  
  I'm not sure if the serial cable being a null modem is a factor or not.
  
  

  Solution
  

  
  

1. Make sure the serial cable connected to the port on the floppy drive side. The serial port is on the opposite side of the power supply on the back of the //c. NOTE: You'll see a 2 <phone icon> engraved above the serial port.
   
   
2. When you plug in your USB cable and start ADTPro you must see it listed under File > Serial Configuration. For me it was /dev/tty/usbserial.DN000MLG4 but this will vary depending on which brand/model you have. Check your manual for details. Also, I have:
   
   

• Speed: 19,200 (Note: You CAN use 115,200)
  
• [x] Apple //c w/ Imagewriter cable <-- This was THE key for me.
  
  

3. Press the Serial button.
   
   
4. Select the menu Bootstrapping > ProDOS > Speediboot
   
   
5. The docs for ATDPro are missing an essential keypress as it is implied. On the Apple //c side you MUST press RETURN after IN#2:
   
   IN#2 <RETURN>
   <Ctrl-A>14B
   
   
6. Lower-case DOES work!
   
   
7. When you press Ctrl-A the cursor will change to a question mark ?. If you don't see this then the serial card is NOT active.
   
   
8. When press type B the cursor will change back to the regular checkerboard glyph. You CAN press <RETURN> after the B as well but it isn't needed like the first one after the IN#2.
   
   
9. After pressing OK within ADTPro you should immediately see the CALL -151 and hex input on the Apple //c. If ADTPro sends the file (~30 seconds) but there is NO input on the Apple //c side then your connection is working. See the following Troubleshooting section.
   
   

   Troubleshooting
   

   
   

• Physical verify the USB-DB9 cable connection is solid. My USB-DB9 adapter has a red LED when hooked up to the MBP -- the other lights turn on when actual sending.
  
• Serial config: Lower the speed to 19,200 until you verify the higher speed works
  
• Serial config: Toggling the Imagewriter option
  
• Serial config: Verify you are using the correct /devdevice
  
• If you have exhausted all other options try another USB-DB9 cable
  
  

  Models
  

  
  I have the following Apple //c models in my Apple Lab. I've tested two of them:
  
  | Version | Works |
  |:---|:---|
  |255 (Original) | Yes |
  | 0 (3.5 ROM IIc) | Yes |
  | 5 (//c+) | ? (Haven't tested) |
  
  NOTE: You can find which ROM version your //c is via:
  
  ? PEEK(64447)
  
  Good luck!
  
  Edit: Replaced //c+ pic with //c one.

https://www.amazon.com/Sabrent-Serial-RS-232-Converter-CB-DB9P/dp/B00IDSM6BW/ref=sr_1_1?ie=UTF8&qid=1479225100&sr=8-1&keywords=9pin+serial+to+usb ?