Serial Control on BasX MC-1

[thecreativeone91]

Has anyone been able to get serial control working on the Emotiva BasX MC-1?

I am am using a straight thru cables (have tried multiples) with either my Global Cache iTach IP2SL or a USB -to- Serial adapter just for testing either one yields the same results. 

The MC-1 does not respond to any commands (Neither by the MC-1 taking the action or a response in the Serial console). However I do see the responses for when I activate any action directly on the MC-1 or by using the IR remote. I'm about to the point where I'm thinking either I got a bad unit, or there is an issue with the firmware in regards to serial control. I'm hoping someone else can test. 

Serial Settings



Sending Command, the MC-1 does not take the action for the command, and I've tried it both with and without a CR. (Doing this in Putty or Termite using USB to Serial yields the same results as well). 




Turning the Unit on via the front panel yields the correct response codes for the action taken to be sent over serial. (once again, Termite or Putty using USB to Serial yields the same results). 




Thanks for any help. 

[cofford]

I'm guessing my reply is a bit late for the OP but I'll post it anyway in case it helps others. I've been able to control my MC-1 over serial using a laptop with a USB-serial adapter, and with an ESP32 (Wemos D1 Mini) and a TTL-RS232 adapter. On my MC-1, the data needs to be sent to pin 3 and not pin 2 as stated in the manual. I made my own cable and it works great.  For the ESP32/TTL-RS232 adapter setup, I had to route pin 2 to pin 3.

The ESP32 hosts a web server, so I can now control my MC-1 using my phone, or any other device on my network with a browser.

Thanks,
Casey

[KeithL]

I'm pretty sure the pinout listed in the manual is not "incorrect".

However, some RS-232 devices, and some adapters, expect a straight-through cable, while others expect a "crossover cable".
So "in the old days" most RS-232 "cables crossed" over several sets of pins, including pins 2 and 3, and several of the pins used for various optional hardware handshakes as well.

Dec 6, 2022 22:51:12 GMT -5 cofford said:

I'm guessing my reply is a bit late for the OP but I'll post it anyway in case it helps others. I've been able to control my MC-1 over serial using a laptop with a USB-serial adapter, and with an ESP32 (Wemos D1 Mini) and a TTL-RS232 adapter. On my MC-1, the data needs to be sent to pin 3 and not pin 2 as stated in the manual. I made my own cable and it works great.  For the ESP32/TTL-RS232 adapter setup, I had to route pin 2 to pin 3.

The ESP32 hosts a web server, so I can now control my MC-1 using my phone, or any other device on my network with a browser.

Thanks,
Casey

[cofford]

From the MC-1 RS-232 commands document:

Internal Pin Configuration: Pin 3 is data from the MC1 to your controller. Pin 2 is data from your controller to the MC1. Pin 5 is ground/common.

I'm sending commands to Pin 3 on the MC-1 female connector and it is working properly.  Only Pin 3 and Pin 5 are connected.

Dec 7, 2022 9:34:44 GMT -5 KeithL said:

I'm pretty sure the pinout listed in the manual is not "incorrect".

However, some RS-232 devices, and some adapters, expect a straight-through cable, while others expect a "crossover cable".
So "in the old days" most RS-232 "cables crossed" over several sets of pins, including pins 2 and 3, and several of the pins used for various optional hardware handshakes as well.

Dec 6, 2022 22:51:12 GMT -5 cofford said:

I'm guessing my reply is a bit late for the OP but I'll post it anyway in case it helps others. I've been able to control my MC-1 over serial using a laptop with a USB-serial adapter, and with an ESP32 (Wemos D1 Mini) and a TTL-RS232 adapter. On my MC-1, the data needs to be sent to pin 3 and not pin 2 as stated in the manual. I made my own cable and it works great.  For the ESP32/TTL-RS232 adapter setup, I had to route pin 2 to pin 3.

The ESP32 hosts a web server, so I can now control my MC-1 using my phone, or any other device on my network with a browser.

Thanks,
Casey