Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
The content of hw_settings.ini is incorrect
#sbitx_v2
Is it possible that I am doing something wrong? I performed the Sbitx v2 software operations published on May 4, 2023 as described. First on May 6, when I connected the output to a 250W heatsink artificial load via a Daiwa CN801-H power/swr meter. To check the meter calibration procedure: slowly increase the drive level until the external power meter reads 20W. Here only 5W power could be set at 100% drive with the original ini files. In the Calibrate meter action, type metercal and Enter (do not touch the screen from now on). I didn't know it at the time, because I turned the top right rotary knob on the front to the right and there was no change. I thought that the internal shows 3W compared to the external 9W, then you have to turn it to the right to increase it, as when you also increase the volume or sensitivity in this way. I did the txcal action all the way through when it sets each bar. I've seen 80M and 40M about 25W, while upwards at 10M I see 6W on the external meter. I didn't look at the contents of user_settings.ini and hardware_settings.ini until yesterday. That's when I was surprised, because in the attached files, the bridge value was set to 64 (50) by the software and the scale=0.0156247 is the same everywhere for the frequency bands. Yesterday, I performed the description operations several times in a row. I overwrote the contents of the two files to their previous state and repeated the operations of the description several times. I restarted the RPi when necessary. The contents of the files didn't change even after I figured out how to set the Sbitxv2's internal power meter. (I turned the upper right control on the front panel to the left.) Is it possible that one of the components is not good and that is why I cannot adjust it? -- Gyula HA3HZ |
Hello Gyula, My sBitx v2 broke the final and I ended up having a new board sent to me. It just arrived yesterday, so it has probably been adjusted. The settings are as follows. Ichiro JE1JGC 2023Äê6ÔÂ13ÈÕ(»ð) 20:04 HA3HZ <gyula@...>: I'll help you: the files are in the /home/pi/sbitx/data/ folder and you can copy them to a usb stick with the file manager. |
Gyula, In the screen capture, can you tell us which file is yours?? - f On Wed, Jun 14, 2023, 1:59 AM HA3HZ <gyula@...> wrote: ps.: Note: I only used the device for transmission with the artificial load during the calibration. |
The problem is solved, although the scale values stored in hw_settings.ini are far from the default.
I assume it's due to the variance of the parts. The value of the bridge stored in user_settings.ini is set by metercal, which is 59 for me. Could it be because of the different characteristics of the diodes? So not matched pair. -- Gyula HA3HZ |
Gyula, in the DE and also in the V2 when I have replaced PA IFRZ24Ns and re-trimmed the PA_BIAS potentiometer, for what it¡¯s worth I have found that I need to re-tweak the scale coefficients in hw_settings.ini to get power output to match the DRIVE settings. My DE does not yet have an swr bridge but nonetheless I think that components and calibrations can lead to variations from the factory to daily use.? Jack, N6LN |
Jack,
thanks for the information. When I take the time to tear apart the v2, I'll check out the Bias as well. I didn't have to change IRFZ24s, I just wanted to do the May 4 settings. The success is only partial, because the maximum output is 25W. And I have to forget about txcal, because then it raises the value of scale everywhere to 0.0156247. With the 20% increase per lane, I got to the point that now there is something, but not yet the real thing. I'm physically tired right now... I'm in the process of demolishing and building an old concrete fence 64 meters long. I'm 72. Thanks again. -- Gyula HA3HZ |
I find no hw_settings.ini file in the file system of my sbitx v2. I have an April issue of a V2 and I ran the ./update and ./build three days ago. I've seen no documentation on the proper files structure and system-file dependencies so I have no way to figure out (1) what I should have in my file system and (2) whether the values in the files are correct. The dialog with HA3HZ makes me think I'm lacking some critical files or data values. That my signal is not being heard by anyone makes me doubly suspicious that something is missing.
I'm fluent in electronic schematics and many kinds of software architecture diagrams but have not found any of these latter so far. I may be looking in the wrong places, groups.io and sbitx.net. How do I sort all this? |
Hi Bruce,
you can see the installed contents of the sbitx folder in the picture below. The firmware is on github, not groups.io or sbitx.net. This file is part of the firmware. What you are looking for is in the /home/pi/sbitx/data folder with your Raspberry File Manager. I took this picture under Windows, because I copied the content to a Pen drive so that I could look at it at any time. In addition, I also make a copy of the installed system with the SD Card Copier. Use sbitx-v2_image.rar because it has more fixes compared to the previous ones. For example, recording log data works here. -- Gyula HA3HZ |
Hi Bruce,
you can see the installed contents of the sbitx folder in the picture below. The firmware is on github, not groups.io or sbitx.net. This file is part of the firmware. What you are looking for is in the /home/pi/sbitx/data folder with your Raspberry File Manager. I took this picture under Windows, because I copied the content to a Pen drive so that I could look at it at any time. In addition, I also make a copy of the installed system with the SD Card Copier. Use because it has more fixes compared to the previous ones. For example, recording log data works here. As far as I know, when updating from github, some files are not updated, because then several operations would have to be started from the beginning. So it doesn't overwrite hw_settings.ini either. Those who received it with an April delivery had to do it according to the May 4th description. You can read here that default_hw_settings.ini is there so that if the setting fails, you can use it again without default. I also received it with April delivery. -- Gyula HA3HZ |
My problem has not been solved till today.
I thought that if the value of the bridge (default=100) is changed by the program (in my case, for example, to 59 or 64), then I should look for the cause around the diodes of the measuring bridge. The measuring bridge has GE diodes marked 1N63 according to the schematic. This may be the same as the Tungsram OA1161 diode, which was produced 50-60 years ago. Since I managed to buy an unopened package of diodes, I was confident that this would solve the problem. But not. I selected and replaced D27 and D28 for opening direction voltage only. I measured it with a DVM at the time of removal and found that D28 had a much higher voltage in the opening direction (858mV) compared to D27 (297mV). Also, D28 leads in the closing direction. According to the schematic it is in the FWD branch. After the replacement, I checked the output power and it was lower. My logic is that the ATtiny85 gives the output level control to the RPi via the IIC. If the diodes are fine, there may be an additional error somewhere. Should I look for the reason in the ATtiny? Or am I not understanding things correctly? Since I've been testing the device, the output level on 80M and 40M has never been higher than 25W. 17M-10M approx. 8-5 W. At that time, the scale value was high on all bands and the bridge value was also set to around 50-60 by the meter. The values stored in hw-settings.ini were always higher than the default. That's why I gave the above title to the topic. -- Gyula HA3HZ |
On Fri, Jun 30, 2023 at 08:27 AM, HA3HZ wrote:
At that time, the scale value was high on all bands and the bridge value was also set to around 50-60 by the meter.At that time, the scale value was high on all bands and the bridge value was also set to around 50-60 by the 'metercal' operation. ? -- Gyula HA3HZ |
I replaced the Ge diodes D27 and D28 with OA1160 Tungsram (340mV) in my previous testing, which did not give the desired result.
I replaced the diodes with OA60, whose opening voltage is 165mV. I changed the ini files back to default and the measurements showed that the power displayed on the screen is the same as the external power meter. I checked user_settings.ini where bridge=100, so no need to calibrate the meter. Output power varied only slightly in each band. I used to increase the scale value per bar, but that didn't help now. Can anyone help me how to proceed? -- Gyula HA3HZ |
I would like to close this topic.
Replacing D27 and D28 solved the problem that the swr-power meter can now measure correctly. This is how output power monitoring works. I received the IRFZ24Ns I ordered yesterday. I didn't want to change anything without them. As you can read, their existence was necessary. I measured their characteristics with a tester (which the meter can indicate: connection of legs, input capacity and opening voltage.) First, I measured with a used 9V battery, according to the display it was 7.1V. Since a measurement is not a measurement, I also supplied it with 9.0V from an external power supply according to the display. According to the measurements, I measured input capacitance between 555pF...562pF and opening voltages of 3.1...3.2V from the IOR P925 J 80 0C production product (10 pcs). I only mention as an interesting fact that I ordered the 2N2219A from two dealers, and I measured their characteristics similarly. There was a difference in HFE characteristics. My measurement was 163 from one dealer, and 216 from the other. What is interesting is that the batch marking does not fit on the part from the same manufacturer, only here. After that I returned to Sbitx. Since the arrival of the device, I have only used it in reception, with the exception of the May 4 testing txcal artificial load transmission mode. It was possible to short-circuit one of the FETs with a previously modified hw_settings.ini during the txcal (PSU 12.5V limited to 8 amps), so the replacement was now possible. I soldered the FETs as shown in the picture. I turned 'VR_bias' all the way towards the ground. Power on: ssb mode, drive 1, mic 0 to set the quiescent current of the final stage, then reboot. My power supply has a current monitor and current limiter, so I limited it to 2 Amps. The quiescent current is different when receiving and transmitting. This quiescent current taken during transmission (i.e. in the absence of an input signal) must be increased in the case of 2 FETs by 100-100 mA, i.e. 200mA (maximum 250 mA). The transmission is started by pressing PTT. There is artificial load on the output. My further measurements show that I am satisfied with my output even without changing the original hw_settings.ini. Measured with an external power meter at 80% drive, 80M and 40M= 35W. 30M and 20M = 20W. 17M and 15M= 15W. 12M and 10M= 10W In short, I received a good product, except for the D28, which became the cause of all the problems. I write this only for the edification of others. I have no hurtful intentions. -- Gyula HA3HZ |
Gyula, I found your presentation very informative even if i dont own the sbitx yet. Wont have to worry about hurtful intentions. I think anyone with truth behind them and actually wanting to learn or seeking out an answer will enjoy reading your post.been printing them out and keeping them in a file like i did with the bitx40,ubitx. . Sometimes another set of eyes helps.Thats what makes electronics so fascinating.? Yes i agree. on the transceiver Ashhar has designed. Its quite a beautiful transceiver. fully capable of keeping up with even the best commercially made transceivers. 73 david ac9xh
On Saturday, July 15, 2023 at 05:49:02 AM EDT, HA3HZ <gyula@...> wrote:
I would like to close this topic. Replacing D27 and D28 solved the problem that the swr-power meter can now measure correctly. This is how output power monitoring works. I received the IRFZ24Ns I ordered yesterday. I didn't want to change anything without them. As you can read, their existence was necessary. I measured their characteristics with a tester (which the meter can indicate: connection of legs, input capacity and opening voltage.) First, I measured with a used 9V battery, according to the display it was 7.1V. Since a measurement is not a measurement, I also supplied it with 9.0V from an external power supply according to the display. According to the measurements, I measured input capacitance between 555pF...562pF and opening voltages of 3.1...3.2V from the IOR P925 J 80 0C production product (10 pcs). I only mention as an interesting fact that I ordered the 2N2219A from two dealers, and I measured their characteristics similarly. There was a difference in HFE characteristics. My measurement was 163 from one dealer, and 216 from the other. What is interesting is that the batch marking does not fit on the part from the same manufacturer, only here. After that I returned to Sbitx. Since the arrival of the device, I have only used it in reception, with the exception of the May 4 testing txcal artificial load transmission mode. It was possible to short-circuit one of the FETs with a previously modified hw_settings.ini during the txcal (PSU 12.5V limited to 8 amps), so the replacement was now possible. I soldered the FETs as shown in the picture. I turned 'VR_bias' all the way towards the ground. Power on: ssb mode, drive 1, mic 0 to set the quiescent current of the final stage, then reboot. My power supply has a current monitor and current limiter, so I limited it to 2 Amps. The quiescent current is different when receiving and transmitting. This quiescent current taken during transmission (i.e. in the absence of an input signal) must be increased in the case of 2 FETs by 100-100 mA, i.e. 200mA (maximum 250 mA). The transmission is started by pressing PTT. There is artificial load on the output. My further measurements show that I am satisfied with my output even without changing the original hw_settings.ini. Measured with an external power meter at 80% drive, 80M and 40M= 35W. 30M and 20M = 20W. 17M and 15M= 15W. 12M and 10M= 10W In short, I received a good product, except for the D28, which became the cause of all the problems. I write this only for the edification of others. I have no hurtful intentions. -- Gyula HA3HZ |
to navigate to use esc to dismiss