Raspberry PI 4 Install?

[crmerrill]

I have been trying to run DiscChanger on a Raspberry Pi 4 set-up, but seem to be encountering some serial issues. Wondering if you could provide guidance on where to trouble shoot?

Current Configuration:
(1) Waveshares 2-CH RS232 HAT. Tested that Serial 1 and Serial 2 can talk to one another via null cable using python (i.e. hat appears to TX and RX via python script). For reference: https://www.waveshare.com/wiki/2-CH_RS232_HAT

(2) .NET runtimes installed: (a) Microsoft.AspNetCore.App 5.0.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]; (b) Microsoft.NETCore.App 5.0.2 [/usr/share/dotnet/sharedMicrosoft.NETCore.App]

(3) DiscChanger installed in /usr/share/dotnet/DiscChanger

(4) DVP-CX777ES to CH1 on serial hat

PROBLEM:
(1) When I run 'dotnet ./DiscChanger.NET.dll', I am able to navigate to localhost:5000 and get a configuration page

(2) When I attempt to add a new DiscChanger I am able to select /dev/ttySC0 (the appropriate serial connection)

(3) When I test the new DiscChanger, the program hangs with no response. Console continues to show service running, but there is no apparent activity (via lights on serial hat board or otherwise) vis a vis serial connection.

[hugo-lyppens]

Ok, I will try that tomorrow on my Raspberry Pi 4. I have not tested the latest version on my Pi 4. Depending on your interface, if you do not have CTS/RTS lines, do not enable the flow control. Also is rs232 enabled in your changer?

…

On Sat, Feb 13, 2021, 6:41 PM crmerrill ***@***.***> wrote: I have been trying to run DiscChanger on a Raspberry Pi 4 set-up, but seem to be encountering some serial issues. Wondering if you could provide guidance on where to trouble shoot? Current Configuration: (1) Waveshares 2-CH RS232 HAT. Tested that Serial 1 and Serial 2 can talk to one another via null cable using python (i.e. hat appears to TX and RX via python script). For reference: https://www.waveshare.com/wiki/2-CH_RS232_HAT (2) .NET runtimes installed: (a) Microsoft.AspNetCore.App 5.0.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]; (b) Microsoft.NETCore.App 5.0.2 [/usr/share/dotnet/sharedMicrosoft.NETCore.App] (3) DiscChanger installed in /usr/share/dotnet/DiscChanger (4) DVP-CX777ES to CH1 on serial hat PROBLEM: (1) When I run 'dotnet ./DiscChanger.NET.dll', I am able to navigate to localhost:5000 and get a configuration page (2) When I attempt to add a new DiscChanger I am able to select /dev/ttySC0 (the appropriate serial connection) (3) When I test the new DiscChanger, the program hangs with no response. Console continues to show service running, but there is no apparent activity (via lights on serial hat board or otherwise) vis a vis serial connection. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALVHMH5NEGAEG55ZNBD4VVLS64EYLANCNFSM4XST4RUA> .

[crmerrill]

Have tried with and without flow control - neither works. RS-232 appears enabled on the changer, but not sure how to confirm. On Feb 13, 2021, at 3:51 PM, Hugo Lyppens <notifications@github.com> wrote:  Ok, I will try that tomorrow on my Raspberry Pi 4. I have not tested the latest version on my Pi 4. Depending on your interface, if you do not have CTS/RTS lines, do not enable the flow control. Also is rs232 enabled in your changer?

On Sat, Feb 13, 2021, 6:41 PM crmerrill ***@***.***> wrote: I have been trying to run DiscChanger on a Raspberry Pi 4 set-up, but seem to be encountering some serial issues. Wondering if you could provide guidance on where to trouble shoot? Current Configuration: (1) Waveshares 2-CH RS232 HAT. Tested that Serial 1 and Serial 2 can talk to one another via null cable using python (i.e. hat appears to TX and RX via python script). For reference: https://www.waveshare.com/wiki/2-CH_RS232_HAT (2) .NET runtimes installed: (a) Microsoft.AspNetCore.App 5.0.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]; (b) Microsoft.NETCore.App 5.0.2 [/usr/share/dotnet/sharedMicrosoft.NETCore.App] (3) DiscChanger installed in /usr/share/dotnet/DiscChanger (4) DVP-CX777ES to CH1 on serial hat PROBLEM: (1) When I run 'dotnet ./DiscChanger.NET.dll', I am able to navigate to localhost:5000 and get a configuration page (2) When I attempt to add a new DiscChanger I am able to select /dev/ttySC0 (the appropriate serial connection) (3) When I test the new DiscChanger, the program hangs with no response. Console continues to show service running, but there is no apparent activity (via lights on serial hat board or otherwise) vis a vis serial connection. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALVHMH5NEGAEG55ZNBD4VVLS64EYLANCNFSM4XST4RUA> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKGQ7ITGZMFY7X6NZCOZVGTS64F7ZANCNFSM4XST4RUA>.

[hugo-lyppens]

I tested the current DiscChanger.NET using ASP.NET Core Runtime 5.0.3 and .NET 5.0.3 runtime on my Raspberry Pi 4 and can confirm it works for me. I use in my boot.config:

enable_uart=1
dtoverlay=uart2,ctsrts=on

This is the serial port /dev/ttyAMA1. I am not sure how UART numbers map to tty numbers, but it is what it is.
Be careful hooking it all up with the wires to the serial port adapter. I assume you use a proper adapter chip from Raspberry Pi to RS232 DB9.

I wrote some scripts that can help you ascertain the RS232 connection is good before attempting to use DiscChanger.NET (see attached zip file as well).

broadcast.sh:
#!/bin/bash
MODE=${1:-2} #ONLY use 0, 1 or 2 for cx777es
SP=${2:-/dev/ttyAMA1}
SUMHEX="$(printf %x $((16#CB - $MODE)) )"
echo $SUMHEX
echo Broadcast setting $MODE to: $SP
printf "\x02\x03\xd0\x62\x$MODE\x$SUMHEX" >$SP

poweron.sh:
#!/bin/bash
MODE=${1:-1} #ONLY use 0, 1 for off/on
SP=${2:-/dev/ttyAMA1}
SUMHEX="$(printf %x $((16#CD - $MODE)) )"
for i in {1..10}
do
echo Powerin on via $SP attempt $i
printf "\x02\x03\xd0\x60\x$MODE\x$SUMHEX" >$SP
read <$SP -t 0 |od -t x1
sleep .1
done

poweron.sh takes 0 or 1 followed by the serial port device. Default is on and /dev/ttyAMA1. Check whether you can turn on&off your changer using this script. The script retries 10 times because the documentation I have specifies that the poweron command needs to be repeated at 100ms intervals until successful.

Then run broadcast.sh to enable broadcast mode (DiscChanger.NET uses 2). Broadcast mode tells the changer to send updates to the controller every time something happens (mode change. disc or track change etc.). This script lets you ascertain broadcast messages make it to the Pi.
I have CuteCom installed, once you enable broadcast mode, go into CuteCom and connect the serial port. Enable the checkmark on 'Hex Output'. Then play/pause some discs on the changer and you will see hex messages coming into CuteCom. Normally DiscChanger.NET takes care of setting the broadcast mode, but this script enables you to test broadcast connectivity from the changer to the Pi easily.

Once these prerequisites are met, you will be in a good position to try DiscChanger.NET again. Please let me know if this helps you to get going.
troubleshooting.zip

[hugo-lyppens]

In testing this on my PI, I noticed a bug in my deserialization code as it recognized /dev/ttyAMA1 (or any Linux serial port device) as an URI instead of a string. This is fixed now. Once you are able to power on/off the changer using the bash script and to see broadcast messages from the changer in a terminal program (hex mode) such as CuteCom (installable from Add/Remove programs in the desktop menu), please download the latest release v1.2 zip file and try it on your Raspberry Pi. Good luck.

[hugo-lyppens]

Previously I had not paid attention to what you have for serial port on your Pi (2CH Waveshare with its own UART). I am not sure it makes sense to add another UART to the Pi 4, as it already has five of them.

All you need is this type of adapter, which converts the voltages from GPIO level to RS232 level. This is the one I use: RS232 to TTL converter board DCE with Female DB9 3.3V to 5V but there are many cheaper ones on AliExpress and eBay. Note that many of the very cheap ones only convert TxD and RxD, not RTS&CTS.

If you use a DCE one, then you need a straight through RS232 cable, female (disc changer side) to male. If you use a DTE converter board, then you will need to use a null modem cable, female to female. Either way works. What confused me initially is that I had to connect the TxD output from the GPIO to the pin marked RxD on the DCE converter board from Amazon. Conversely RxD from GPIO connected to TxD. There are little arrows on the PCB indicating the direction of the data flow. Same for RTS/CTS. If I had bought a DTE converter then probably RxD/TxD would be connected as labeled. Then the swapping would have occurred in the null modem cable required for a DTE-to-changer connection.

Word of caution: please test serial connection from Pi to perhaps an old laptop computer with DB9 serial port or another device that you do not care about. I would hate for anyone to damage their CX777ES or CX7000ES serial port due to incorrect wiring. For testing and other legacy applications, I keep an old Dell Precision M4300 notebook computer, which still works great under Windows 10 and has a serial port built in.