|
Any help in fixing this would be much appreciated.
JOE
VE1BWV
|
Joe, I replied to your prior post: /g/BITX20/message/103494The issue with the screen size is how the sbitx program adjusts the gtk screen.? As outlined in the above post, it would be better to force the screen size to 800x480. To better describe what is happening, look at the following picture:  Note that the layout has the screens side by side.? This makes the stock software size to the total shaded area larger than either screen, so DSI-1 and HDMI-1 are included in the desktop.? I changed how the gtk screen is sized to equal the smaller DSI-1 screen (800x480).? Even if the screen is populated on the HDMI screen, it will write the text and button boxes to the original 800x480 size.? You can click the mouse on the lower right box of the gtk screen to minimize it and then get to the desktop. To see which screen the gtk interface will open to, open a terminal window and then move it to fit inside the screen that you want to be populated with the original gtk interface.? Here is how my screens show up:  Pardon the messy work area. 73 Evan AC9TU
|
Thanks again for your help.
Your last 2 screens look like mine.
The problem? only occurs when the sbitx app is selected,? then the screen on the large monitor displays the sbitx screen.. just to large.
Ok, so by forcing the screen to fixed value the sbitx screen would display the fixed value? which is smaller than the larger screen resolution, so it fits ?
Would the sbit screen be adjustable or is it fixed to the exact values.?
Wow, seems like programming issue in that the sbit screen does not auto adjust to the current ext monitor resolution. Or that there are no points on the screen to shrink or expand it.
Every other screen is adjustable / resizeable.
Joe VE1BWV?
On Wed, Jul 5, 2023, 1:38 PM Evan Hand < elhandjr@...> wrote: Joe,
I replied to your prior post:
/g/BITX20/message/103494
The issue with the screen size is how the sbitx program adjusts the gtk screen.? As outlined in the above post, it would be better to force the screen size to 800x480.
To better describe what is happening, look at the following picture:
Note that the layout has the screens side by side.? This makes the stock software size to the total shaded area larger than either screen, so DSI-1 and HDMI-1 are included in the desktop.? I changed how the gtk screen is sized to equal the smaller DSI-1 screen (800x480).? Even if the screen is populated on the HDMI screen, it will write the text and button boxes to the original 800x480 size.? You can click the mouse on the lower right box of the gtk screen to minimize it and then get to the desktop.
To see which screen the gtk interface will open to, open a terminal window and then move it to fit inside the screen that you want to be populated with the original gtk interface.? Here is how my screens show up:
Pardon the messy work area.
73
Evan
AC9TU
|
I see your ext monitor has the system top bar. I tried this, but, if I select the sbitx screen it comes up and blocks the screen so I cannot make it disappear because it hides the top bar.
Joe
Thanks again for your help.
Your last 2 screens look like mine.
The problem? only occurs when the sbitx app is selected,? then the screen on the large monitor displays the sbitx screen.. just to large.
Ok, so by forcing the screen to fixed value the sbitx screen would display the fixed value? which is smaller than the larger screen resolution, so it fits ?
Would the sbit screen be adjustable or is it fixed to the exact values.?
Wow, seems like programming issue in that the sbit screen does not auto adjust to the current ext monitor resolution. Or that there are no points on the screen to shrink or expand it.
Every other screen is adjustable / resizeable.
Joe VE1BWV?
On Wed, Jul 5, 2023, 1:38 PM Evan Hand < elhandjr@...> wrote: Joe,
I replied to your prior post:
/g/BITX20/message/103494
The issue with the screen size is how the sbitx program adjusts the gtk screen.? As outlined in the above post, it would be better to force the screen size to 800x480.
To better describe what is happening, look at the following picture:
Note that the layout has the screens side by side.? This makes the stock software size to the total shaded area larger than either screen, so DSI-1 and HDMI-1 are included in the desktop.? I changed how the gtk screen is sized to equal the smaller DSI-1 screen (800x480).? Even if the screen is populated on the HDMI screen, it will write the text and button boxes to the original 800x480 size.? You can click the mouse on the lower right box of the gtk screen to minimize it and then get to the desktop.
To see which screen the gtk interface will open to, open a terminal window and then move it to fit inside the screen that you want to be populated with the original gtk interface.? Here is how my screens show up:
Pardon the messy work area.
73
Evan
AC9TU
|
Joe,
The trick is first to start a terminal window.? Move the window so it fits in the 7" display.? Then start the sbitx program by changing to the sbitx directory and typing ./sbitx.? The icons do not reliably start the program in the correct window.
You can make the gtk screen whatever size you want.? It will open across the displays that fit the size you entered in the code change.? If the size is smaller than the start screen, it will stay inside that screen.? Otherwise, the scaling will adjust the lines and characters to fit the full desktop size, which is too big for either screen.
You can try overlapping the HDNM and the DSI screen (clone vs extend).? With that arrangement, you can minimize the gtk screen as the far right lowest box will be available.? ?That box minimizes the gtk screen.
I do not do videos, or I would show you, as that is much easier than trying to describe it.
73
Evan
AC9TU
|
I think I got it now. Will try your suggestions this eve and see how it goes.
Much appreciated?
Joe VE1BWV?
On Wed, Jul 5, 2023, 4:23 PM Evan Hand < elhandjr@...> wrote: Joe,
The trick is first to start a terminal window.? Move the window so it fits in the 7" display.? Then start the sbitx program by changing to the sbitx directory and typing ./sbitx.? The icons do not reliably start the program in the correct window.
You can make the gtk screen whatever size you want.? It will open across the displays that fit the size you entered in the code change.? If the size is smaller than the start screen, it will stay inside that screen.? Otherwise, the scaling will adjust the lines and characters to fit the full desktop size, which is too big for either screen.
You can try overlapping the HDNM and the DSI screen (clone vs extend).? With that arrangement, you can minimize the gtk screen as the far right lowest box will be available.? ?That box minimizes the gtk screen.
I do not do videos, or I would show you, as that is much easier than trying to describe it.
73
Evan
AC9TU
|
|
|
Typos again ;-(
You can try overlapping the HDNM and the DSI screen (clone vs extend).?
Should be?
You can try overlapping the HDMI and the DSI screen (clone vs extend).?
|
I did your suggested changes and it worked.
Now the weird part.
I rebooted and loaded the sbitx and wsjtx It sync fine to radio? but I noticed no audio input... Tx works audio and tf out Put ok Just no rx audio All works on sbit just no wsjt rx audio. Spent the past hour troubleshooting. No go Even put in a known good backup sd card Puzzled
On Wed, Jul 5, 2023, 5:26 PM Evan Hand < elhandjr@...> wrote: Typos again ;-(
You can try overlapping the HDNM and the DSI screen (clone vs extend).?
Should be?
You can try overlapping the HDMI and the DSI screen (clone vs extend).?
|
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
|
One thing that one might remember is that the sBitx v2 runs a non-customized standard Linux system. All these operations, for example, setting the output monitor or even installing fldigi and other software the sbitx software is exactly the same as in any other (Debian-based) Linux. Indeed, one could choose to use any other ham radio software for Linux to operate the sBitx. I think a crash course on the Linux stacks - audio, graphics and OS architecture - and Debian sys admin is kind of a must for a owner of a sBitx tinkerer. I could help on this.
Rafael
toggle quoted message
Show quoted text
On 7/10/23 10:50, HA3HZ 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 </g/BITX20/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
|
That would be great, Rafael.
I could use some education on the items you listed !!
Gordon Kx4z
toggle quoted message
Show quoted text
On Jul 10, 2023, at 06:19, Rafael Diniz <rafael@...> wrote:
?One thing that one might remember is that the sBitx v2 runs a non-customized standard Linux system. All these operations, for example, setting the output monitor or even installing fldigi and other software the sbitx software is exactly the same as in any other (Debian-based) Linux. Indeed, one could choose to use any other ham radio software for Linux to operate the sBitx. I think a crash course on the Linux stacks - audio, graphics and OS architecture - and Debian sys admin is kind of a must for a owner of a sBitx tinkerer. I could help on this.
Rafael
On 7/10/23 10:50, HA3HZ 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 </g/BITX20/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
|
May be a live presentation on the sBitx v2 software internals could be a start. I could address all setup needed to bring up the audio codec and explain all controls (which could be set in any other OS). I'll not risk myself talking about the RF radio details (and my electrical engineer knowledge is nothing compared to you all), but I can describe all sBitx software architecture, going down to the Wolfram audio codec setup, GPIO, I2S setup (for the audio codec), I2C bitbanging on GPIO as currently done, RTC I/O, etc.
Rafael
toggle quoted message
Show quoted text
On 7/10/23 11:22, Gordon Gibby wrote: That would be great, Rafael.
I could use some education on the items you listed !!
Gordon Kx4z
On Jul 10, 2023, at 06:19, Rafael Diniz <rafael@...> wrote:
?One thing that one might remember is that the sBitx v2 runs a non-customized standard Linux system. All these operations, for example, setting the output monitor or even installing fldigi and other software the sbitx software is exactly the same as in any other (Debian-based) Linux. Indeed, one could choose to use any other ham radio software for Linux to operate the sBitx. I think a crash course on the Linux stacks - audio, graphics and OS architecture - and Debian sys admin is kind of a must for a owner of a sBitx tinkerer. I could help on this.
Rafael
On 7/10/23 10:50, HA3HZ 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 </g/BITX20/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
|
Gyula, Did you change to the sbitx directory and do a ./build sbitx after making the changes to sbitx_gtk.c?? The changes to the c programs do not take effect until you build the program again.? Do not do a ./update; it will pull the GitHub files and wipe out your changes. The trick to getting the sbitx gtk screen on the 7" DSI display is to start a terminal window and ensure that it fits on the DSI display.? Then start the sbitx program in the terminal window.? You can also start the touch screen mapping in the terminal window first, then start the sbitx program.? The piping of the log files to errlog.txt is optional.? It allows me to review all the messages that come up when starting the sbitx program.  I have learned that the placement of the DSI-1 window in relation to the HDMI-1 window is not essential as long as they do not overlap.
Did you configure the screens to be separate?? The setting is in the "Preferences" tab here:
?
This brings up a window where you can drag the screen as you like.? Here is how I have then?set up now because I have the DSI monitor to the left of the HDMI:
?
?
I also have the menu set for the HDMI.? That is a right mouse click on the desktop and then select the Desktop Preferences menu tab:?
?
?
?
?
Here is a pic with both monitors shown.
?
 Please excuse the messy workbench. 73 Evan AC9TU
|
Thanks Rafael
? I would appreciate an accompanying doc with any relevant commands and options. With Linux I am often in the place of knowing what to do but, not remembering the exact syntax and the two out of 99 options I need to do it. Scanning through videos to find when someone demoed something is slow and difficult on the sBITX.
I keep a text file cheat sheet on my desktop with handy commands.
--
73
??? Bob? KD8CGH
|
Rafael,
I would be interested in the presentation as well!
73
Evan
AC9TU
|
Joe
? I see the same thing. I just put windows on top of the sBITX display and finally exit sBITX with the /cmd "exit" at the end of a session.
? I launch a browser first. When I launch sBITX it takes over the monitor as you noticed. If I click on the browser icon in the LCD menu bar it pops on top. If it's on the LCD I pull it over to the monitor and size it. I can then launch another browser, terminal, ... and pull them over. Clicking an apps icon in the menu bar pops it to the top.
--
73
??? Bob? KD8CGH
|
Certainly. I plan to make the presentation slides this document. I'll commit the source code of the presentation to git, so we could keep evolving the document.
I put an initial skeleton here:
source of the presentation will be here:
Rafael
toggle quoted message
Show quoted text
On 7/10/23 11:53, Bob Benedict, KD8CGH wrote: Thanks Rafael
? I would appreciate an accompanying doc with any relevant commands and options. With Linux I am often in the place of knowing what to do but, not remembering the exact syntax and the two out of 99 options I need to do it. Scanning through videos to find when someone demoed something is slow and difficult on the sBITX.
I keep a text file cheat sheet on my desktop with handy commands.
--
73
??? Bob? KD8CGH
|
Evan,
unfortunately, I can't see the pictures of your message #103656, only the frames.
I also tried with MS Edge, but there is no image there either.
In answer to your question, yes, after modifying sbitx_gtk.c, I open the terminal, where I continue with cd sbitx...sudo xinput.... ./sbitx.
I guess that's why I can move from one screen to another with the mouse.
About monitor sizing: automatic recognition for DSI, 1920x1200 (if I remember correctly) for HDMI.
If I make it smaller, I see less of the sbitx screen. I can't make it bigger.
I used the HDMI for an LG 22" monitor PC before (with HDMI, DVI and D-SUB input).
So far, I haven't updated and upgraded the RPi, because I thought that I would mess something up with the updates.
This morning I tried update and then dist-upgrade (the latter installed about 800MB from 2021-12 to 2023-05).
I haven't moved on since then because I don't have a voice on the speaker. There is a headphone output.
So what I'm using is the latest (2023-06-13) firmware, then I used ./update for the last time.
--
Gyula HA3HZ
|
Gyula,
Try viewing the posts on the 开云体育 pages.? There is a link at the bottom of the email.
73
Evan
AC9TU
|
HA3HZ
Bob Benedict, KD8CGH