Re: Device i2c address 0x57 and 0x5f?
I completely replaces i2cbb.c, unless you want to keep some i2c bitbanging for the Si5351A (are they in the same i2c bus?). What exactly is your setup in the DE? The RTC is in a different i2c bus than the Si5351A?
- Rafael
toggle quoted message
Show quoted text
On 8/23/23 13:19, Evan Hand wrote: Hello Rafael,
Thank you for the information.? It will take me some time to digest it.
One quick question: Does this replace the i2cbb.c bus, or is it added to allow the RTC module to connect directly to the system?
73
Evan
AC9TU
|
Re: Device i2c address 0x57 and 0x5f?
Hello Rafael,
Thank you for the information.? It will take me some time to digest it.
One quick question: Does this replace the i2cbb.c bus, or is it added to allow the RTC module to connect directly to the system?
73
Evan
AC9TU
|
Re: Device i2c address 0x57 and 0x5f?
Hi Evan,
I did here. Use this as reference:
toggle quoted message
Show quoted text
On 8/23/23 10:54, Evan Hand wrote: Hello Gyula,
Thank you, I can read the pdf.? If I understand correctly, to make it work on the sbitx, you would need to modify the sbitx code to remove the i2cbb.c code and change the calls to the second hardware-based i2c bus in addition to adding the config.txt change.
I will try implementing the system based i2c-2 on my test RPi and see how it works.? If successful, I will look at the changes required to implement on my DE.
Thank you again!
73
Evan
AC9TU
|
Re: Device i2c address 0x57 and 0x5f?
I just removed fake_hwclock package here.
toggle quoted message
Show quoted text
On 8/23/23 01:57, Mark Erbaugh wrote:
The bit-banged RTC is available to the system and can be used to set the system clock at boot by adding a line to /boot/config.txt.
If there is internet time available, the Pi will update the RTC.
I let the RTC set the system time and modified sBitx to just use the system time and not do anything with the RTC. I also installed and configured chrony to set the time from a USB GPS dongle, if available. My sBitx will automatically work with three time sources (4 if you count fake_hwclock) and set the system time from the best one available. By using the system time, the same time is available to all programs.
--
73,
Mark, N8ME
|
Re: Device i2c address 0x57 and 0x5f?
I haven't tried it out yet. Just remembered Mark posted this pdf.
--
Gyula HA3HZ
|
Re: Device i2c address 0x57 and 0x5f?
Hello Gyula,
Thank you, I can read the pdf.? If I understand correctly, to make it work on the sbitx, you would need to modify the sbitx code to remove the i2cbb.c code and change the calls to the second hardware-based i2c bus in addition to adding the config.txt change.
I will try implementing the system based i2c-2 on my test RPi and see how it works.? If successful, I will look at the changes required to implement on my DE.
Thank you again!
73
Evan
AC9TU
|
According to the photo it's 160-10M
Maybe the owner fitted a 160M LPF to use it on Tx.
You can receive on 160 but you need a LPF to Tx.
anyone know about this? I have it coming from ebay.? tnx Don w8ptb
|
|
|
Re: Device i2c address 0x57 and 0x5f?
|
I meant normal ubitx originally designed by farhan vu2ese.?
|
It is a normal ubix? ver 3,4 or 5 with kd8cec firmware. You can get details of said firmware at? ubitx.net.
73s
Sarma vu3zmv
|
Re: Device i2c address 0x57 and 0x5f?
Mark,
Will you share the line to add in config.txt?
Thank you
73
Evan
AC9TU
|
Re: Device i2c address 0x57 and 0x5f?
The bit-banged RTC is available to the system and can be used to set the system clock at boot by adding a line to /boot/config.txt.
If there is internet time available, the Pi will update the RTC.?
I let the RTC set the system time and modified sBitx to just use the system time and not do anything with the RTC. I also installed and configured chrony to set the time from a USB GPS dongle, if available. My sBitx will automatically work with three time sources (4 if you count fake_hwclock) and set the system time from the best one available. By using the system time, the same time is available to all programs.
--
73,
Mark, N8ME
|
Correct. sBITX stores the log info in an sqlite database.? The sqlite browser mentioned here /g/BITX20/topic/99777967#103269 will let you view and edit the log database. The python tool mentioned will query the log database and write out the log in a ADIF format file that you can load into another logger, including LOTW. -- 73 ??? Bob? KD8CGH
|
I believe the log is not a discrete ASCII file log, but is
instead kept inside the sqlite database.? the "log tools"
mentioned likely provide a convenient interface to manage those
tables in the database.
On 8/22/23 09:58, Bob wrote:
toggle quoted message
Show quoted text
I know just enough about Linux to be dangerous. Here is my
question. Is there a log file that I can go in and correct my log?
I'm sorry if I'm being ignorant about this stuff, but it's only
because I am. Would really appreciate some help.
?
|
Re: File /uBITX_6_N8ME_2_VU3GAO_Mods.zip uploaded
#file-notice
I'm glad it worked out !? ?So I just wonder, are there any unique features of the N8ME software that you find particularly useful or better that the other versions that you have tried ?? ?
|
Re: File /uBITX_6_N8ME_2_VU3GAO_Mods.zip uploaded
#file-notice
Rolan, I uploaded the file and it is working OK, sidebands are displayed correctly. Thanks again.?
Tibor Lakati
HA8SLT
|
Re: IW2NDH Panadapter Kit for uBitx
Sam,
thanks! ?That is very reasonable. You can¡¯t get a reasonable RF switch for less than $50. One more question, ?so this includes a processor for the display? I had assumed that there was a raspberry pi somewhere but not likely at that price point¡
73
Mark
--
AJ6CU
KD8CEC 2.0, Nextion Screens,? and open source uBITX Raduino boards for Arduino IOT, BLE, RP2040, Teensy 4.0, and Raspberry Pi Pico
https://github.com/aj6cu
|
I know just enough about Linux to be dangerous. Here is my question. Is there a log file that I can go in and correct my log? I'm sorry if I'm being ignorant about this stuff, but it's only because I am. Would really appreciate some help.
?
|
Re: Device i2c address 0x57 and 0x5f?
Rafael,
I have connected an RTC module and an ATTiny85 programmed with the SWR/PWR sketch from Ashhar Farhan to a stand-alone RPi 4 connected on the default i2c bus.? When I run the i2cdetect, I get three addresses:
08 = SWR/PWR meter
57 and 68 = RTC
I confirmed by removing the RTC and SWR/PWR devices independently.? Since I do not have the RPi in the sbitx, I do not get the 60 address for the Si5351.
I do not know what the 5F address is.
When I run i2cdetect on the sbitx, with the sbitx program running in the background, I get only the WM8731 codec.
How are you using the i2cdetect on the sbitx?? The Si5352, RTC, and SWR/PWR are on a separate bus that is a bit banged bus in the sbitx program.? I do not believe it is available without the sbitx program running and not available to the system-level devices, only the sbitx program.
73
Evan
AC9TU
|
HA3HZ
Mark Erbaugh
Bob Benedict, KD8CGH