|
I currently have? WSJTZ working. It has many extra features compared to WSJTX.. both has some interaction issues with sbitx app. WSJTZ seems to be more stable for syncing radio and receive audio.
This all leads up to using Digital modes more with software that provides much better visual feedback.
A large external monitor for home shack use is essential. For mobile.. the 7 inch is fine. I think we all agree on that. As I see it, the sbitx app with a non selectable fixed screen is the issue. It cannot be easly resized by dragging the window, unlike all other apps. Even if the sbitx app screen is changed , It still occupies the whole external screen If I change code from fixed to a specific size.. smaller screen size..the display does resize but it still takes the whole screen. It just shrinks it and it appears in say the upper left corner of the screen. It needs to be didplayable as a movable? adjustable window.
HELP!
Joe VE1BWV
On Mon, Jul 10, 2023, 6:50 AM HA3HZ < gyula@...> wrote: I also tried HDMI and DSI display mode last night. I'm a little disappointed.
I know this structure is a bit like a male egg, you should only touch it gently.
I always have a previous version, so when something doesn't work out the way I imagined, I go back to it.
So I got to the point where I made the changes in sbitx_gtk.c. I copied it to a pen drive and from there to the device's ../sbitx folder.
I restarted it, then as I read the sequence here, I started it.
(The sbitx-v2 image was basic, without update or upgrade. Maybe this is important?)
I can perform mouse operations between DSI and HDMI. I noticed the passage option.
On the right side for DSI, on the top left for HDMI.
I can't bring up the 3rd picture of Evan's message? ? #103519 only.
I only see this when I start with only HDMI without DSI.
Another disappointment this morning. Since dpkg wasn't working correctly when installing some .debs, I started by tidying up the RPi.
So I thought I did an update and then a dist-upgrade. I restarted and had no sound, just two clicks.
The receiver works because I switched it off at FT8 and the decoding is fine.
Headphone test is fine, some measurements, then an external sound amplifier for the headphone output, sound is fine.
I will order the LM380N.
So I'm wondering what I missed with DSI and HDMI working together?
I tested with HDMI, WSJT-X is fine with the original version 2.5.4.
When I tried to upload the WSJT-Z, I only found the original version.
--
Gyula HA3HZ
|
Evan, Apparently I needed the second attempt and I read the #103494 message again. I just realized where I made a mistake. So the modification of sbitx_gtk.c is incorporated into the program with ./Build Sbitx. I had to understand this thing to do. Then reboot and then enter the terminal in the cd sbitxsudo xinput map-to-output "raspberrypi-ts" "DSI-1"./sbitx &> errlog.txtAnd Heureka ... now it's okay. And one more thing, I operate the device from 12V 70 Ah battery and the battery was discharged, so it hasn't had a voice since this morning :-( Now is the time to install the power monitor. I have a network power supply that I used to make the connectors (XT60 and 16A banana plugs) so I could deal with bug fixes :-) The images saved from the screen (use Print Screen button) show the contents of the two monitors. In the screen, you can choose which screen the menu is on the screen with the right button. -- Gyula HA3HZ    
|
Joe,
The code is written to take in the full screen where the software is started.? As long as the scaling is less than the screen size, you can minimize the gtk screen with the lower right-hand box that may or may not contain a "-".? To bring it up again, click on the started icon in the taskbar (NOT the startup icon on the left side of the taskbar).
If you have two screens, start the sbitx program on the smaller screen IF you have adjusted the scaling in the sbitx_gtk.c program and rebuilt the code.
Setting the screen size would be another good addition to the hw_settings.ini file with changes to the code.? One of these days, I will dig into that part of the code to make it configurable.??
73
Evan
AC9TU
|
ps.: The passage between the two monitors is possible.
Move the mouse on the HDMI screen to the upper area on the left side.
Here you can transfer the cursor to the DSI screen to the lower right side.
Back and forth as you like. You will like it.
--
Gyula HA3HZ
|
Thanks for updates.
From? what I see, I can display the same with no issues. The issue I have is the sbitx screen not the web browser screen.
The sbitx screen is the only one that takes up a full screen . Even with a Size change in code, it still takes a the full size of the monitor screen,? just the data of the display is shrunk. All other apps and windows are fully sizeable and dragable on the fly.
Joe VE1BWV?
On Mon, Jul 10, 2023, 11:22 AM HA3HZ < gyula@...> wrote: Evan,
Apparently I needed the second attempt and I read the #103494 message again.
I just realized where I made a mistake.
So the modification of sbitx_gtk.c is incorporated into the program with ./Build Sbitx.
I had to understand this thing to do.
Then reboot and then enter the terminal in the
cd sbitx
sudo xinput map-to-output "raspberrypi-ts" "DSI-1"
./sbitx &> errlog.txt
And Heureka ... now it's okay.
And one more thing, I operate the device from 12V 70 Ah battery and the battery was discharged, so it hasn't had a voice since this morning :-(
Now is the time to install the power monitor.
I have a network power supply that I used to make the connectors (XT60 and 16A banana plugs) so I could deal with bug fixes :-)
The images saved from the screen (use Print Screen button) show the contents of the two monitors.
In the screen, you can choose which screen the menu is on the screen with the right button.
--
Gyula HA3HZ
|
I further clarify my solution was:
I copied the modified sbitx_gtk.c with the RPI file manager to the Sbitx folder.
Before that, I renamed the existing sbitx_gtk.c file to sbitx_gtk.c.old.
Then you need a ./build Sbitx at the terminal to override the old GTK.
Then reboot. When both monitors sign up, I call the terminal (Ctrl-Alt-T) on the DSI touch screen monitor and enter the following:
cd sbitx
sudo xinput map-to-output "raspberrypi-ts" "DSI-1"
./sbitx &> errlog.txt
You have to do this every time you use.
If you know another solution, publish that we'll get to know it.
If something didn't work, it can be read in Errlog.txt.
Then I start the SBITX program on the DSI touch screen and log in to the web interface by typing PWD.
I can perform an operation with the mouse on both surfaces.
I even pull the launched program into the other window.
When you start the program, you will see the traditional SBITX screen on the HDMI screen.
There is a "-" button in the lower right corner, clicking this, then the departure screen will appear.
Here you can do additional operations.
I called the window on the HDMI interface with the right button and set it to the menu tab to see the menu on the HDMI screen.
You can claim it as you like.
The DSI interface has SBITX and the HDMI interface shows the programs running in the menu line.
If you want to start another digital program, turn off the fldigit first.
I attach the modified sbitx_gtk.c file.
So far, I hope I was understandable.
Thanks to Evan AC9TU, without whom this could not have been created.
--
Gyula HA3HZ
|
Joe, do this -- Gyula HA3HZ 
|
Yes, I see your hdmi screen. It is actually using the whole monitor display area. Just the data/ control is shrunk With this setup you cannot have that hdmi screen and use it to display other screens in the unused space area located all around.
Joe
On Mon, Jul 10, 2023, 1:06 PM HA3HZ < gyula@...> wrote: Joe, do this
--
Gyula HA3HZ
|
This will eliminate this small screen and large blackness. After that, click the right mouse button on the screen and in the window that opens, move the menu to hdmi and you can start the next program, just don't forget to close the 'fldigi' program. The launched program can be resized freely. I did it, it works for me.
--
Gyula HA3HZ
|
On 7/10/23 11:28, HA3HZ wrote:
cd sbitx
sudo xinput map-to-output "raspberrypi-ts" "DSI-1"
./sbitx &> errlog.txt
You have to do this every time you use.
If you know another solution, publish that we'll get to know it.
There is likely a way to do it in an xorg.conf file somewhere,
but it would involve dissecting the Xorg configuration sequence to
determine 'when' (during the configuration/setup of the Xorg
environment) both "raspberrypi-ts" and "DSI-1" are defined, as we
cannot successfully execute the map if the objects it is using
haven't been defined yet!, then creating the appropriately named
.conf file in the appropriate directory, etc, etc...? so it's
probably easiest just to add that xinput command your Startup
Applications on the RaspberryPi.? To do that, just:
-
Open
'Startup Applications'.
-
Click
'Add' and in the command field paste the desired command.
Click 'Add'.
-
You have
added the first command.
...so, in the command field type in:? xinput map-to-output
"raspberrypi-ts" "DSI-1"??????? [..? I don't think you need the sudo
for this specific command ..]
then shutdown and reboot the radio.? once the radio is restarted,
your touchpad should already be mapped.
|
Another option is creating a shell script to do all the commands.? I created a str_sbitx.sh with the commands and made it executable.? I can then type ./str_sbitx.sh when in the pi folder where the command is stored.
From a terminal window:
cd /home/pi
nano str_sbitx.sh
Enter the lines in the nano window and then <ctrl>o and <ctrl>x
chmod a+x str_sbitx.sh
You should be able to type ./str_sbitx.sh and start the sbitx program with the touchscreen mapping and redirecting the error and standard terminal info to a file.
The above works for me.
73
Evan
AC9TU
|
I think we have made progress on this topic.
Several solutions are possible, so I tried to choose the simplest one. 'How to Auto Start a Program on Raspberry Pi?' description provided the inspiration.
?
In the previous Raspberry Pi OS version, this could be handled graphically, but it seems that this is not available in the new Raspberry Pi OS versions.
?
So here's how to do it with a configuration file:
Create a file in the /etc/init directory (not init.d!):
sudo nano /etc/init/str_sbitx.conf
Paste the following content:
?
description "str_sbitx"
start on startup
task
exec /home/pi/sbitx/str_sbitx.sh
?
Place str_sbitx.sh in the sbitx folder
sudo nano /home/pi/sbitx/str_sbitx.sh
?
#!/bin/bash
cd sbitx
?xinput map-to-output "raspberrypi-ts" "DSI-1"
?
That is all!
Creating the files is enough to make it work on every boot.
?
If it is installed, start GridTracker first, then sbitx.
?I set the menu to the HDMI monitor and turn off 'fldigi' so I can start JTDX or WSJT-X.
I do all this on the HDMI screen. The mouse moves freely between DSI and HDMI monitors.
If you press the 'Print Screen' button, it takes a picture of both screens, which you can find in the /home/pi/ folder in .png image file format.
-- Gyula HA3HZ
|
ps.: I think a step was missed when creating str_sbitx.sh:
Enter the lines in the nano window and then <ctrl>o <enter> and <ctrl>x
chmod a+x str_sbitx.sh
--
Gyula HA3HZ
|
Gyula, Thanks for inputs.
I went thru the process. No errors Rebooted and loaded pgms in the sequence as you suggested.
Well, everything looks like before. No changes I can see. It all work like it did before... strange
I will reboot again then load sbitx in a terminal on the DSI and see if that's helps.
Joe VE1BWV?
On Tue, Jul 11, 2023, 7:35 PM HA3HZ < gyula@...> wrote:
I think we have made progress on this topic.
Several solutions are possible, so I tried to choose the simplest one. 'How to Auto Start a Program on Raspberry Pi?' description provided the inspiration.
?
In the previous Raspberry Pi OS version, this could be handled graphically, but it seems that this is not available in the new Raspberry Pi OS versions.
?
So here's how to do it with a configuration file:
Create a file in the /etc/init directory (not init.d!):
sudo nano /etc/init/str_sbitx.conf
Paste the following content:
?
description "str_sbitx"
start on startup
task
exec /home/pi/sbitx/str_sbitx.sh
?
Place str_sbitx.sh in the sbitx folder
sudo nano /home/pi/sbitx/str_sbitx.sh
?
#!/bin/bash
cd sbitx
?xinput map-to-output "raspberrypi-ts" "DSI-1"
?
That is all!
Creating the files is enough to make it work on every boot.
?
If it is installed, start GridTracker first, then sbitx.
?I set the menu to the HDMI monitor and turn off 'fldigi' so I can start JTDX or WSJT-X.
I do all this on the HDMI screen. The mouse moves freely between DSI and HDMI monitors.
If you press the 'Print Screen' button, it takes a picture of both screens, which you can find in the /home/pi/ folder in .png image file format.
--
Gyula HA3HZ
|
Joe,
the solution is in the details. Could you post a screenshot of where it is now?
When I turn on the device and both screens are present.
You can easily move from one screen to another with the mouse, when you have this option in the upper corner on the right side of the DSI and on the left side of the HDMI screen. My two monitors are physically reversed, so it is a little more difficult to use the reversed mouse.
So, when you turn it on, I have the mouse in the middle of HDMI, I have to move it to DSI and click on GridTracker, then on Sbitx.
Mouse stays here, because web login requires a password.
After logging in on the DSI, I then move the mouse over to the HDMI.
If the menu is not here, click the right mouse button somewhere on the screen.
By clicking on the Menu tab in the window, I select HDMI so that the menu is visible here. In this case, the GridTracker is present on the right side of the HDMI. The currently running programs are visible in the menu line. If you want to use another digital device, switch off Fldigit first.
Then, under the Raspberry icon, find the program you want to start. You start it and wait for it to log in.
If you haven't used it yet, the settings must be filled out and configured. Also set the image size of the program.
Today I tried JTDX and I find that I can hear the sound, but the program logs in very slowly and first I see the call sign data, then at some point you can see the packets. With wsjt-x, the login is slow, but when it comes in, it is immediately decoded and visible.
So I have these details.
The image size of DSI is 800x480, HDMI is 1920x1080 pixels.
This is a PC monitor with HDMI, D-Sub and DVI inputs.
I hope I could help you.
--
Gyula HA3HZ
|
I did the github jtx install Copy and paste? All good except Line 23 error unknown argument --prefix =? /user
Line 26 error? no rule to make target
I did a? ?cake --help and it displayed the commands
On Wed, Jul 12, 2023, 5:36 PM HA3HZ < gyula@...> wrote: ps.: I just noticed that jtdxhamlib is different from the installed one. When I have time I will see if it works better.
--
Gyula HA3HZ
|
I re did the update command Then did the jtdx copy paste All in one shot. It's now compiling..? Will take a while Will see what happens
Joe VE1BWV?
I did the github jtx install Copy and paste? All good except Line 23 error unknown argument --prefix =? /user
Line 26 error? no rule to make target
I did a? ?cake --help and it displayed the commands
On Wed, Jul 12, 2023, 5:36 PM HA3HZ < gyula@...> wrote: ps.: I just noticed that jtdxhamlib is different from the installed one. When I have time I will see if it works better.
--
Gyula HA3HZ
|
HA3HZ