Awesome Idea  the si4732 integration 🥇

Hello phdlee,
I discovered your firmware here on github almost by chance. since I have a k5 dedicated to testing and a si4732 in the drawer, I'll try to put it in place of the original chip! I just have a doubt about the work around the chip.. Looking at the shematic around the actual BK1080, it would make sense bypass or adapt the Q7 circuit.. and replace C28?
Last, if you could share a picture of your PCP modified it could be helpful to have a clear idea :)
Sorry to have used the issues form but it was the easiest way to contact you :)

I worked on SI4732 MOD a few months ago. I didn't have a circuit diagram at
the time, but I really like the circuit diagram you sent me.
I checked whether the clock occurred in OSC1 to reduce the number of parts,
but was not successful.
So, three more parts were used. (X-TAL, CAP 2) If I had seen this circuit
diagram earlier, I think I would have challenged myself a little more LOL
In my opinion, the Q7 should be there. It acts as a PIN diode. There is a
(FM RADIO ANT) RX PIN diode on the front of the Q7, so there is no big
problem, but the radio designer probably took interference with the
BK4819's RX IN into consideration.
I installed a CAPACITOR on the Q7's BASE and connected it directly to
SI4732. It didn't seem to make much of a difference, so I kept it back to
its original state.
If you are going to give up FM radio, it would be a good idea to replace
c28, l9, and c29.
I investigated OSC1's clock and according to the BK1080's manual, it said
that BK1080 does not need a clock, so I determined that OSC1 did not
generate a clock.
If this circuit diagram is correct, it would be a good idea to study OSC1 a
little more.
DE KD8CEC
On Sat, Jan 20, 2024 at 2:28 AM iu0azb @.***> wrote:

Hello phdlee,
I discovered your firmware here on github almost by chance. since I have a
k5 dedicated to testing and a si4732 in the drawer, I'll try to put it in
place of the original chip! I just have a doubt about the work around the
chip.. Looking at the shematic around the actual BK1080, it would make
sense bypass the Q7.. and replace C28?
Sorry to have used the issues form but it was the easiest way to contact
you :)
BK1080.JPG (view on web)
https://github.com/phdlee/uvk5cec/assets/63300383/14ffe2e1-cd40-4ab6-b5aa-d12c29cbf73a
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPAAVOLSSWYJFYIFODDYPKUK3AVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4TAOJXHAYDENA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

After sent the message I decided to attempt a frankestein to have a look into the factibility of it... and after some tentative I won :)
Here attached the working monster :)
About BK1080 pin 1 is getting 26mhz reference (200mV) .. bit far from 32.768 but not sure this reference change can be adjusted from settings.

Thanks for the interesting research. If 26Mhz is measured, it will be
difficult to use. In the code that controls the bk1080, there are values
that are entered into the internal area that are not disclosed to the
general user, so unlike the bk1080 manual, it is not possible to know
whether other frequencies can be input.

The code says that an external clock is used.
The manual says to use a 32.768Khz clock. However, 26Mhz is measured
(bk4819 source clock)
3.bk1080 register addresses 0x16~0x32 are not disclosed, but specific
values are put there in the source code. The source code has been reverse
engineered, so even those who release the source code may not know what it
means.
This is the conclusion lol

Thanks for the measurements.
On Sat, Jan 20, 2024 at 6:42 AM iu0azb @.***> wrote:

After sent the message I decided to attempt a frankestein to have a look
into the factibility of it... and after some tentative I won :)
Here attached the working monster :)
About BK1080 pin 1 is getting 26mhz reference (200mV) .. bit far from
32.768 but not sure this reference change can be adjusted from settings.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1901153813, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPAFYDADYYZKVLVGO6TYPLSFRAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBRGE2TGOBRGM
.
You are receiving this because you commented.Message ID:
@.***>

Yeap I'll try to investigate in codes too
For si4732 there is a pre scaler setting as detailed in pu2clr pages
https://github.com/pu2clr/SI4735/blob/master/extras/schematic/README.md

I think you found the answer. I am so happy.
It is specified on page 35 of the 4735 manual.
I can try it out right away and, if possible, reduce 3 useless parts.
On Sat, Jan 20, 2024 at 3:54 PM iu0azb @.***> wrote:

Yeap I'll try to investigate in codes too
For si4732 there is a pre scaler setting as detailed in pu2clr pages
https://github.com/pu2clr/SI4735/blob/master/extras/schematic/README.md
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1901806380, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPFNF4BPOXXNTLYE7OTYPNSZLAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBRHAYDMMZYGA
.
You are receiving this because you commented.Message ID:
@.***>

Great ;)

Hi Seongho,
today on a work break I've reopened your website, noticed that you updated the article. Thanks for mentioning me :)
However, I noticed that you may have tried to use the prescaler without success. Do you confirm? Hopefully if I could share the bin file I could do some tests to overcome the reset problem.   No rush because I'm currently looking for the best solution to place the chip.

all right. I will send you a binary that allows you to use it as a
prescaler.
On Tue, Jan 23, 2024 at 5:37 AM iu0azb @.***> wrote:

Hi Seongho,
today on a work break I've reopened your website, noticed that you updated
the article. Thanks for mentioning me :)
However, I noticed that you may have tried to use the prescaler without
success. Do you confirm? Hopefully if I could share the bin file I could do
some tests to overcome the reset problem. No rush because I'm currently
looking for the best solution to place the chip.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1904764880, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPF7RT3XCJH5DKDW3J3YP3EX7AVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUG43DIOBYGA
.
You are receiving this because you commented.Message ID:
@.***>

I'm also trying to find the MCU schematic .. if an I/O pin is not used it can be used to reset the si. This should simplify the integration using common libraries

The circuit diagram is on GitHub.
https://github.com/ludwich66/Quansheng_UV-K5_Wiki/tree/main/hardware/KiCad/Kicad_UVK5_reversing20230909
According to CPU.kicad_sch, it seems that PB15 and PC3 are unused.
PB15 is pin-25, and since it's at the corner of the QFP, it might be easy to connect a wire.

That's great.. At the moment I've installed the si4732 on the K5 PCB with RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share 👍

I wrote an email, but it wasn't all sent due to capacity issues, so I'll
send it in several parts.
iu0azb, jh4vaj
According to the datasheet, it looks like PC3 can output a clock from a
timer.
I can't be sure because I can't see the circuit diagram right now (it's
somewhere other than my computer), but I'll check for recycling of the SWD
port tomorrow.
today I found out a few things

I worked on sending the firmware to IU0AZB. I had to be careful because
I had to send firmware that didn't work in my environment.
I looked at the code to make sure the si4732 library was working
correctly and found a few unknown bugs.
si4732 has two pins that receive clock input, and I took turns testing
them.
However, as you can see in the library source, that part is commented
out.. All the DCLK pins I tested were unnecessary lol
If the 12th BIT is 1, it is DCLK, and if it is 0, it is the REFC pin. It
seems to have been commented out because it does not work while shifting 1
to the left 13 times.
Anyway, I have checked all reference clock related parts, almost completed
the firmware for 26Mhz clock, and completed all checks.
I'll send it tomorrow, (checked firmware bin)  and I'll send it to everyone
who needs it. please send me your email address
@.***

[image: image.png]
On Wed, Jan 24, 2024 at 11:54 PM iu0azb @.***> wrote:

That's great.. At the moment I've installed the si4732 on the K5 PCB with
RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share
👍
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908292997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDQEJXFZFSGKWRM2FLYQEOCJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGI4TEOJZG4
.
You are receiving this because you commented.Message ID:
@.***>

2.I found out why it didn't work.
It seems the clocks are not satisfactory. That's because the clock size
is small and the bias is at 0 volt.
In uv-k5, the clock comes through cap. It is the cap on the left of pin 1
of the bk1080.
As it passes through the cap, the bias becomes 0volt.
It seems that bk1080 can operate that way. However, when I experimented
with si4732-a10, it was the same as a normal digital clock (1/2 of vcc).
The photo below shows the minimum operating conditions.
[image: image.png]
It started to operate when the above conditions were met.
[image: image.png]
On Wed, Jan 24, 2024 at 11:54 PM iu0azb @.***> wrote:

That's great.. At the moment I've installed the si4732 on the K5 PCB with
RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share
👍
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908292997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDQEJXFZFSGKWRM2FLYQEOCJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGI4TEOJZG4
.
You are receiving this because you commented.Message ID:
@.***>

there
The email could not be sent continuously due to a file size issue, so I
sent it repeatedly.
2.I found out why it didn't work.
It seems the clocks are not satisfactory. That's because the clock size
is small and the bias is at 0 volt.
In uv-k5, the clock comes through cap. It is the cap on the left of pin 1
of the bk1080.
As it passes through the cap, the bias becomes 0volt.
It seems that bk1080 can operate that way. However, when I experimented
with si4732-a10, it was the same as a normal digital clock (1/2 of vcc).
The photo below shows the minimum operating conditions.
[image: image.png]
On Thu, Jan 25, 2024 at 12:13 AM Ian Lee @.***> wrote:

2.I found out why it didn't work.
It seems the clocks are not satisfactory. That's because the clock size
is small and the bias is at 0 volt.
In uv-k5, the clock comes through cap. It is the cap on the left of pin 1
of the bk1080.
As it passes through the cap, the bias becomes 0volt.
It seems that bk1080 can operate that way. However, when I experimented
with si4732-a10, it was the same as a normal digital clock (1/2 of vcc).
The photo below shows the minimum operating conditions.
[image: image.png]
It started to operate when the above conditions were met.
[image: image.png]
On Wed, Jan 24, 2024 at 11:54 PM iu0azb @.***> wrote:

That's great.. At the moment I've installed the si4732 on the K5 PCB with
RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share
👍
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908292997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDQEJXFZFSGKWRM2FLYQEOCJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGI4TEOJZG4
.
You are receiving this because you commented.Message ID:
@.***>

When I attach photos or files, an error continues to occur.
I'm removing all photos and reposting only the text.
If you need firmware for UV-K5 SI4732 for 26mhz OSC, please let me know
your personal email address.
kd8cec at gmail com
I will send it to you all tomorrow. A photo is not attached, but this is
firmware that has been confirmed to work with a different oscillator.
(26Mhz with 1.5 volt)
Below is the original email I wanted to send today. (photo remove
Ian KD8CEC
iu0azb, jh4vaj
According to the datasheet, it looks like PC3 can output a clock from a
timer.
I can't be sure because I can't see the circuit diagram right now (it's
somewhere other than my computer), but I'll check for recycling of the SWD
port tomorrow.
today I found out a few things

I worked on sending the firmware to IU0AZB. I had to be careful because
I had to send firmware that didn't work in my environment.
I looked at the code to make sure the si4732 library was working
correctly and found a few unknown bugs.
si4732 has two pins that receive clock input, and I took turns testing
them.
However, as you can see in the library source, that part is commented out.
If the 12th BIT is 1, it is DCLK, and if it is 0, it is the REFC pin. It
seems to have been commented out because it does not work while shifting 1
to the left 13 times.
Anyway, we have checked all reference clock related parts, almost completed
the firmware for 26Mhz clock, and completed all checks.
I'll send it tomorrow, and I'll send it to everyone who needs it. please
send me your email address
@.***

image.png
2.I found out why it didn't work.
It seems the clocks are not satisfactory. That's because the clock size
is small and the bias is at 0 volt.
In uv-k5, the clock comes through cap. It is the cap on the left of pin 1
of the bk1080.
As it passes through the cap, the bias becomes 0volt.
It seems that bk1080 can operate that way. However, when I experimented
with si4732-a10, it was the same as a normal digital clock (1/2 of vcc).
The photo below shows the minimum operating conditions.
image.png
The operation starts when the above conditions
image.png
I tried increasing the bias of the clock, but without success.
The photo below is for the next experiment.
Please ignore the MCU pins being removed or the PCB being scribbled lol
image.png
ian
KD8CEC
On Wed, Jan 24, 2024 at 11:54 PM iu0azb @.***> wrote:

That's great.. At the moment I've installed the si4732 on the K5 PCB with
RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share
👍
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908292997, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDQEJXFZFSGKWRM2FLYQEOCJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGI4TEOJZG4
.
You are receiving this because you commented.Message ID:
@.***>

I haven't obtained the SI4732 chip yet, so I can't try the firmware at this time.
I applaud your work.

I wrote an email, but it wasn't all sent due to capacity issues, so I'll send it in several parts. iu0azb, jh4vaj According to the datasheet, it looks like PC3 can output a clock from a timer. I can't be sure because I can't see the circuit diagram right now (it's somewhere other than my computer), but I'll check for recycling of the SWD port tomorrow. today I found out a few things 1. I worked on sending the firmware to IU0AZB. I had to be careful because I had to send firmware that didn't work in my environment. I looked at the code to make sure the si4732 library was working correctly and found a few unknown bugs. si4732 has two pins that receive clock input, and I took turns testing them. However, as you can see in the library source, that part is commented out.. All the DCLK pins I tested were unnecessary lol If the 12th BIT is 1, it is DCLK, and if it is 0, it is the REFC pin. It seems to have been commented out because it does not work while shifting 1 to the left 13 times. Anyway, I have checked all reference clock related parts, almost completed the firmware for 26Mhz clock, and completed all checks. I'll send it tomorrow, (checked firmware bin) and I'll send it to everyone who needs it. please send me your email address @.*** [image: image.png]
…
On Wed, Jan 24, 2024 at 11:54 PM iu0azb @.> wrote: That's great.. At the moment I've installed the si4732 on the K5 PCB with RCLK connected to ex pin1 of bk1080.. Ready to test bin file once you share 👍 — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDQEJXFZFSGKWRM2FLYQEOCJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGI4TEOJZG4 . You are receiving this because you commented.Message ID: @.>
iu0azb at gmail ... thanks

I just appreciate your interest.
On Thu, Jan 25, 2024 at 12:49 AM jh4vaj @.***> wrote:

I haven't obtained the SI4732 chip yet, so I can't try the firmware at
this time.
I applaud your work.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908405747, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPGW6K2NAKURUOOL4NLYQEURRAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYGQYDKNZUG4
.
You are receiving this because you commented.Message ID:
@.***>

Yeap, unfortunately after have installed the si4732 on the PCB defenitly I''ve reconginze that the chip became deaf in HF :(   too many welding cycles.. that's bad.
For now I'm stuck untill new chips will be here on the desk
Btw, I've also discovered that on my K5 actually the PA15 is always at 0V.. that's probably why it suffered from first day from poor FM reception.

There is no PA15.  buit  GPIO B15 ?
When B15 is 0, the RF signal is connected.
Press the EXIT button on the radio to switch to High.
The firmware I am sending you now has been checked for operation by setting
it to 26Mhz with an external oscillator.
And si4732 does not break easily.
The radio screen will appear even if only the sclk, sdio pin, gnd, and vcc
of the si4732 are connected.
If the si4732 chip is dead, the radio screen will not appear.
The radio will stop while waiting indefinitely for communication.
If you press the 0 button to switch to the radio screen, si4732 is normal.
Thanks~
On Thu, Jan 25, 2024 at 6:34 AM iu0azb @.***> wrote:

Yeap, unfortunately after have installed the si4732 on the PCB defenitly
I''ve reconginze that the chip became deaf in HF :( too many welding
cycles.. that's bad.
For now I'm stuck untill new chips will be here on the desk
Btw, I've also discovered that on my K5 actually the PA15 is always at
0V.. that's probably why it suffered from first day from poor FM reception.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1908953675, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPEWTKKRVRKRERAIQK3YQF5AFAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYHE2TGNRXGU
.
You are receiving this because you commented.Message ID:
@.***>

I tried to investigate using the schematic.. where the base of Q03 goes to PA15.. as also reported on my original schematic

But when look at MCU schematic, you are right, it doesn't exist..  and B15 is reported as unused.

Anyway I've indetified the problem, L56 coil (0.36uH) is open.. I'll replace it :)

Ah, the schematic was wrong.
When I include pictures, an error occurs and I can't post, but the two you
included were sent successfully.
This is what I marked on the CPU for comparison with the source code.
[image: image.png]
ian
On Thu, Jan 25, 2024 at 6:05 PM iu0azb @.***> wrote:

I tried to investigate using the schematic.. where the base of Q03 goes to
PA15.. as also reported on my original schematic
image.png (view on web)
https://github.com/phdlee/uvk5cec/assets/63300383/af090537-2c9a-4391-a807-a97fe95193f6
But when look at MCU schematic, you are right, it doesn't exist.. and B15
is reported as unused.
image.png (view on web)
https://github.com/phdlee/uvk5cec/assets/63300383/afccc9fc-0a2b-4bef-83bc-23465e469f41
Anyway I've indetified the problem, L56 coil (0.36uH) is open.. I'll
replace it :)
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1909702761, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPFNGHSJHGXPRABLNDTYQIN35AVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZG4YDENZWGE
.
You are receiving this because you commented.Message ID:
@.***>

The schematic may not be complete.
Perhaps PA15 is a typo.
Looking at this photo, it seems that all pins of the MPU are used.

https://github.com/ludwich66/Quansheng_UV-K5_Wiki/blob/main/hardware/UV-K5_1.4_PCB_2024-01-22_1900px/UV-K5_1.4_PCB_4%2BBT_1900.png
Note that this photo appears to be a view from the back.
Therefore, it is mirrored left to right.

Yeap, the reverse engineering  in schematics is not an easy task :)
So, no i/o available on MCU, mean no  way to reset the si4732 other than with RC.
I look forward to receiving the new chips and go ahed.  I've time to rethink how to place the chip in the area. I had instinctively placed it this way but I think there is better.

I also realized that exactly the thickness of the si4732 passes between the plastic of the cover and the PCB ... an usefull info fo who want to enjoy the project

I read new post. so, it was possible to omit the C and R for the reset. That's great.
I have designed a PCB to mount additional parts (this includes the C and R).
Currently, due to Chinese New Year, the PCB manufacturers in China are on holiday, so once that's over, I plan to place an order.

I read new post. so, it was possible to omit the C and R for the reset. That's great.
I have designed a PCB to mount additional parts (this includes the C and R).
Currently, due to Chinese New Year, the PCB manufacturers in China are on holiday, so once that's over, I plan to place an order.

The PCB would be the best cleaner way to mod the radio.. I've just the doubt if there will be enough room to place it. Actually on my radio the space between the pcb and speaker is almost exactly the thickness of si4732 🙁

Wow never used too ;)

It's just something I've been thinking about. You did it. That's cool.
If it doesn't fit a little, you can replace the speaker, and it works even
if you force it in, but there's no major problem.
My first version was a bit thick.
If it is operated with a PCB, including C and R will be much more
convenient for users who modify it.
This is because it is much easier to attach the PCB on top than to put a
jumper with POINT.A (RESET).
I will continue to maintain C and R versions as well.
I'm so excited. Even if it doesn't fit well, send me the Gerber file and I
will order it and test it.
Ian KD8CEC
On Tue, Feb 13, 2024 at 1:41 AM jh4vaj @.***> wrote:

I will order it as Flex-PCB.
Its thickness is 0.11mm. I am hoping it will fit in the enclosure.
However, this is my first experience with Flex-PCB, so I am worried.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1939116752, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPD3SL3PLJYRXI2LR23YTJA2TAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGEYTMNZVGI
.
You are receiving this because you commented.Message ID:
@.***>

Hi Ian,
I read your new post about the si4732 experiments.. you did amazing improvements on that. no more RC!! About the clock at this point I will go ahead with the xtal solution.. not big deal compared with the two bias resistor.. It make software easier :)
Fortunately I've received the chips and I'm ready to install it on radio.. At this time I'll wait you release the new bin file to avoid RC
Thanks again for your great job!
Luca

I have placed a 1uF cap for MOD S2 on the PCB.
Then, I printed it on paper and tried to put it on the UV-K5's PCB.
It seems to fit nicely.
I am thinking of expanding this PCB a little and adding a dummy pad to fix it to the UV-K5's PCB.
Once that's done, I will order this PCB.

Hi all, after few days of test I would like to share my feedback on this :)
If you scroll up I mentioned that once isntalle the si4732 on the radion it became deaf... but later with new chip I recognised that the probem occurred again.. and confirmed on two different K5.
Once I connect the AMI to pin 6 or C point with or without the additonal cap the si4732 saturate and no signals can be detected  also attaching an external hf antenna.  If I connect same antenna on the chip pin 8, insulating RF input from K5, the reception is at normal level ok an si4732..  I've tried to play a bit aronund the Q7 with no success. With oscope I note a strong noise coming from bias circuit that till now I can't filter out.  What's your results on this? I read that PA2JSA added a cap to ground on pin8.. that's improve the noise but wouldn't fix the situation :)

First, don't connect the AMI to anything.

Attach a 10cm wire to the FMI and check if FM radio is being received.
Please test whether it works well when switching AM/FM/LSB/USB and
changing frequencies.
If everything is normal up to this point, SI4732-A10 is installed
properly.
If possible, it would be helpful to understand the situation if you
took a video of this operation and uploaded it.
3.If everything went well up to this point, remove the wire attached to the
FMI and connect a 10cm wire to the AMI.
Connect the other end of the 10cm wire to the antenna.
Even if it doesn't work perfectly, you should get acceptable reception.
Please note that the antenna's GND must not be connected anywhere.

Also, when testing, do not use an adapter or USB-C cable, but connect it to
the battery and test it.
The tests so far have not used any of the K5's RF PATHs.
If you tell me the test results, I may be able to figure out the problem.
Ian KD8CEC
On Tue, Feb 20, 2024 at 7:06 PM iu0azb @.***> wrote:

Hi all, after few days of test I would like to share my feedback on this :)
If you scroll up I mentioned that once isntalle the si4732 on the radion
it became deaf... but later with new chip I recognised that the probem
occurred again.. and confirmed on two different K5.
Once I connect the AMI to pin 6 or C point with or without the additonal
cap the si4732 saturate and no signals can be detected also attaching an
external hf antenna. If I connect same antenna on the chip pin 8,
insulating RF input from K5, the reception is at normal level ok an
si4732.. I've tried to play a bit aronund the Q7 with no success. With
oscope I note a strong noise coming from bias circuit that till now I can't
filter out. What's your results on this? I read that PA2JSA added a cap to
ground on pin8.. that's improve the noise but wouldn't fix the situation :)
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1953871545, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDIZAZBYSXPTLBMLILYURYTFAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTHA3TCNJUGU
.
You are receiving this because you commented.Message ID:
@.***>

Hi Ian,
Thanks to detailed reply.
I did the test and attaching a short wire to FMI it received normally.. same connecting it to AMI.. with or without rf ground connected.
All settings can be modified and edit ..
while using the "Q7" circuit for  HF I've the issue mentioned earlier.

Short wire connnected only to AMI
https://github.com/phdlee/uvk5cec/assets/63300383/9e14e446-f334-4a8b-a95a-6cb1365c4305

Short wire connected to AMI while connected to Q7 circuit.. sorry no dx blocking cap.. but it's the same
https://github.com/phdlee/uvk5cec/assets/63300383/0772fce7-83cd-4184-b21d-ac32d05658aa

Same wire connected to the C7 cap pad before Q7 .. AMI connected as it suppose to stay pin6
https://github.com/phdlee/uvk5cec/assets/63300383/b8b822fb-b582-45e7-bc47-78836fe297ae

Thank you for sending the video.
The test I suggested is to connect the antenna directly to the AMI chip of
SI4732-A10 as shown below.
Connect the antenna directly to AMI on SI4732-A10 and move to a place where
there is always a shortwave radio frequency or (USB) signal such as
14.074Mhz.
Connecting the antenna directly to the AMI generally creates an environment
similar to that of a radio using the SI4732-A10. This should work
regardless of UV-K5 characteristics.
Another interesting thing is that when I touch it with my hand, I can hear
shortwave broadcasting. If it is a normal 15Mhz shortwave broadcast, the
signal seems too big.
I think it would be a good idea to try change the frequency.
The crystal and CAP connection is so cool.
Ian KD8CEC
[image: image.png]
On Wed, Feb 21, 2024 at 9:29 PM iu0azb @.***> wrote:

Same wire connected to the C7 cap pad before Q7 .. AMI connected as it
suppose to stay pin6
https://github.com/phdlee/uvk5cec/assets/63300383/b8b822fb-b582-45e7-bc47-78836fe297ae
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956546975, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPGFYU2V64DJRTD52U3YUXSEJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGU2DMOJXGU
.
You are receiving this because you commented.Message ID:
@.***>

I also thought about another possibility, and the frequency you are
receiving frequency may not be a shortwave broadcast.
If it is received when you touch it, it may be an FM or AM broadcast.
I've just tested it and found a similar phenomenon to yours in case of FM
broadcasts or incorrect broadcasts coming from other bands.
(I tried it again, and the characteristic of radio waves coming from FM
broadcasting is that they have a large BandWidth.)
Try receiving around 15Mhz to 20Mhz during the day and below 7Mhz at night.
I just tested it and was able to receive about 20-40 stations.
If tested, connect the wiring as normal and connect the antenna to the
antenna terminal of the original UV-K5 to receive signals such as 14.074 or
7.074.
Ian KD8CEC
On Wed, Feb 21, 2024 at 9:29 PM iu0azb @.***> wrote:

Same wire connected to the C7 cap pad before Q7 .. AMI connected as it
suppose to stay pin6
https://github.com/phdlee/uvk5cec/assets/63300383/b8b822fb-b582-45e7-bc47-78836fe297ae
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956546975, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPGFYU2V64DJRTD52U3YUXSEJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGU2DMOJXGU
.
You are receiving this because you commented.Message ID:
@.***>

Another thing is, could the signal from your antenna be too strong? First,
try adjusting the LNA to maximize ATT.
What antenna did you use for testing?
If this problem occurs because your antenna's signal is too strong and it
cannot be controlled with the ATT of the SI4732-A10, you may need to
install an external ATT.
Ian KD8CEC
On Wed, Feb 21, 2024 at 11:48 PM Ian Lee @.***> wrote:

I also thought about another possibility, and the frequency you are
receiving frequency may not be a shortwave broadcast.
If it is received when you touch it, it may be an FM or AM broadcast.
I've just tested it and found a similar phenomenon to yours in case of FM
broadcasts or incorrect broadcasts coming from other bands.
(I tried it again, and the characteristic of radio waves coming from FM
broadcasting is that they have a large BandWidth.)
Try receiving around 15Mhz to 20Mhz during the day and below 7Mhz at night.
I just tested it and was able to receive about 20-40 stations.
If tested, connect the wiring as normal and connect the antenna to the
antenna terminal of the original UV-K5 to receive signals such as 14.074 or
7.074.
Ian KD8CEC
On Wed, Feb 21, 2024 at 9:29 PM iu0azb @.***> wrote:

Same wire connected to the C7 cap pad before Q7 .. AMI connected as it
suppose to stay pin6
https://github.com/phdlee/uvk5cec/assets/63300383/b8b822fb-b582-45e7-bc47-78836fe297ae
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956546975, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPGFYU2V64DJRTD52U3YUXSEJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWGU2DMOJXGU
.
You are receiving this because you commented.Message ID:
@.***>

I'm sure that chip works..
here a short video connecting a longer wire receiving 40m band. I'd be strongly satisfied if get same results using original SMA path.
https://github.com/phdlee/uvk5cec/assets/63300383/ce2f6e15-912b-4475-8a7d-3e0be1e5b1eb
Once I try to connect AMI to L56 any signals drop down..

Another way is to skip Q17. You can remove Q17 and bypass it, but when
using a portable antenna, you need to check whether reception performance
is poor.
Even if Q17 is removed, there does not seem to be a major problem with the
radio's performance because TX/RX is controlled by the PIN diode.
On Wed, Feb 21, 2024 at 11:45 PM iu0azb @.***> wrote:

Yeap, on first video the antenna was attached strictly to AMI.. and it
works like a charm, Even with 20cm wire I can hear FT8 signals on 20m band
:)
But as soon I tried to conect with the rest of circuit the issue mask
anything..
I forgot to mentioned that I've also verified the signal path and bias on
Q7 and noted that Q8 introduce a strong dirty sinewave signal at 176khz
40mVpp.. maybe is not the root couse of issue.. but not sure
image.png (view on web)
https://github.com/phdlee/uvk5cec/assets/63300383/cbce75d9-a598-4cfb-87a1-25381c149229
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956809329, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPHAJUP3VA4ALTDZ5X3YUYB7XAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHAYDSMZSHE
.
You are receiving this because you commented.Message ID:
@.***>

https://github.com/phdlee/uvk5cec/assets/63300383/3896cd93-734a-48e3-be94-0d8fe95f757e

If you can test it, would you try bypassing Q17 as shown below?
Connect the antenna to the UV-K5 antenna connector.
Or, how about reattaching the removed C102 (connected and disconnected in
the last video) or connecting it with a capacitor of about 1uF?
(At this time, the antenna must be connected to the antenna connector of
UV-K5)
[image: image.png]
On Thu, Feb 22, 2024 at 12:06 AM iu0azb @.***> wrote:

https://github.com/phdlee/uvk5cec/assets/63300383/3896cd93-734a-48e3-be94-0d8fe95f757e
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956868120, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPE7SW4YM2F7B3D4ZGTYUYENVAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHA3DQMJSGA
.
You are receiving this because you commented.Message ID:
@.***>

Bypassing Q17 I got similar issue, no strong noise as when it's active.
C102 is having no impact.. initially, following your reccomandation I've inserted 1uF.. but investigating I've removed.
I don't want to disturb you further... I assume that the problem is not common and therefore not of wide interest..
Anyway I just tried connecting AMI directly to the input of C99.. and the signal drop down. I therefore need to understand the path of the FM_Radio_Ant to move forward... there could be something on the other side of PCB that impacting..

Thank you for sending us the various experiment results.
Please try the below when you have time.You don't have to reply.
Lastly, how about connecting everything normally and connecting one of the
antenna wires directly to the UV-K5's antenna terminal?
(Excluding the antenna ground, only the antenna center line is connected
directly to the center of the UV-K5 connector)
The UV-K5's antenna connector is not standard, so all my cables and
contacts are bad. (90% of the cables I have do not fit well.)
So, when shooting video, I only use the cable I always use.
Thank you for your hard work testing.
Please let me know if you have any other results later.
Ian KD8CEC
On Thu, Feb 22, 2024 at 12:23 AM iu0azb @.***> wrote:

Bypassing Q17 I got similar issue, no strong noise as when it's active.
C102 is having no impact.. initially, following your reccomandation I've
inserted 1uF.. but investigating I've removed.
I don't want to disturb you further... I assume that the problem is not
common and therefore not of wide interest..
Anyway I just tried connecting AMI directly to the input of C99.. and the
signal drop down. I therefore need to understand the path of the
FM_Radio_Ant to move forward... there could be something on the other side
of PCB that impacting..
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1956932629, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPENUO57Z33MINODWWLYUYGQNAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHEZTENRSHE
.
You are receiving this because you commented.Message ID:
@.***>

At the end of a day spent to understand the problem I decide to bypass it, adding a dedicated SMA in the LED spot 😊.
For who want to try, be informed that there is almost no space between case and pcb/lcd flex.
The back of SMA need to be plunged inside plastic and back need to be modified to void any extra space other than central wire.
Cool working result.

Hello Ian, I made the mod and it works quite well.  It dosen't look pretty, but it works. Probably I'll go for a sma port like Luca did.
Things to mention/suggestions:

add some sort of memory for Commercial FM and for band VFO
More use of keyboard instead of menu+side buttons.
Like said by Luca there are some noise/click, so maybe a sma port should be better.
With (hi gain) antennas loks like there is some sort of saturation. Again, maybe point 3 resolves
a notch for FM or (better) a bandpass filter is mandatory with hig gain antennas

Thank you for your wonderful work!
73 de IU3POA.

Someone was too fast then us 😳
https://a.aliexpress.com/_Ey5oFHF

Someone was too fast then us 😳
https://a.aliexpress.com/_Ey5oFHF

This is unfair, but maybe more OM will mod their radio, expanding the community. Anyway, maybe someone will make a "open" version of the PCB so more and more OM can have the PCB at the ceapest price and with greetings to Ian

Excellent
For experiments, I am planning to convert my UV-K5 to a dual antenna in the
same way as you.
I plan to increase the impedance of the Antenna In that goes into
SI4732-A10. (It was done that way a long time ago, and it has the effect of
greatly increasing reception performacne. However,  increase interference
with FM broadcasting and AM broadcasting )
On Thu, Feb 22, 2024 at 6:53 AM iu0azb @.***> wrote:

At the end of a day spent to understand the problem I decide to bypass it,
adding a dedicated SMA in the LED spot 😊.
For who want to try, be informed that there is almost no space between
case and pcb/lcd flex.
The back of SMA need to be plunged inside plastic and back need to be
modified to void any extra space other than central wire.
Cool working result.
907E46C0-F503-4D79-A02D-29162C1416A7.jpeg (view on web)
https://github.com/phdlee/uvk5cec/assets/63300383/13af8f29-accf-41ef-b26f-c8c1a33ba37f
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1958044888, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDBEGPMIHW34HVEPNDYUZUD3AVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYGA2DIOBYHA
.
You are receiving this because you commented.Message ID:
@.***>

IU3POA
I also agree with your opinion.
Usually, products using SI4732-A10 use a telescopic antenna.
While working on SI4735 (same SI4732) a few years ago, I increased the
impedance so that it could receive very sensitive signals.
However, the signals from stations with strong signals were all distorted.
However, I was very satisfied with USB/LSB (SSB).
Be sure to send me your mods and videos.
It will be of great help to many people who want to modify for HF reception.
Ian KD8CEC
On Mon, Feb 26, 2024 at 5:59 PM alboc2k @.***> wrote:

Hello Ian, I made the mod and it works quite well.  It dosen't look pretty, but it works. Probably
I'll go for a sma port like Luca did.
Things to mention/suggestions:

add some sort of memory for Commercial FM and for band VFO
More use of keyboard instead of menu+side buttons.
Like said by Luca there are some noise/click, so maybe a sma port
should be better.
With (hi gain) antennas loks like there is some sort of saturation.
Again, maybe point 3 resolves
a notch for FM or (better) a bandpass filter is mandatory with hig
gain antennas

Thank you for your wonderful work!
73 de IU3POA.
photo1708765195.jpeg (view on web)
https://github.com/phdlee/uvk5cec/assets/18322550/a8bbf343-46b8-4da4-adbd-62e7662b7208
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1963615416, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDUALWJQDLPGHQCUYDYVRFHNAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTGYYTKNBRGY
.
You are receiving this because you commented.Message ID:
@.***>

thank you for the information.
It is expensive, but I think it will be helpful for people who have
difficulty soldering.
I'm quite impressed that you scraped the PCB and connected GND.
I think it will be easier to work that way.
Ian KD8CEC
On Mon, Feb 26, 2024 at 10:55 PM iu0azb @.***> wrote:

Someone was too fast then us 😳
https://a.aliexpress.com/_Ey5oFHF
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1964203620, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPE3YA6VYWPBLV4KKA3YVSH37AVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGIYDGNRSGA
.
You are receiving this because you commented.Message ID:
@.***>

I've just made a prototype similar to the chinese one (a copy of copy? :-D
Some tests needed...

I've put some credits to Ian in the back.

It's a first try and I'm waiting for some errors report from JLPCP. I assume that castellated holes are needed, but I'll go without, just because they make the PCB too much expensive. Also, if all works, I'll post results. Once defined price should be around 10€ for 60 (panelized).

At the end of a day spent to understand the problem I decide to bypass it, adding a dedicated SMA in the LED spot 😊.
For who want to try, be informed that there is almost no space between case and pcb/lcd flex.
The back of SMA need to be plunged inside plastic and back need to be modified to void any extra space other than central wire.
Cool working result.

Overall after a week of test I'm quite impressed for reception results in portable operation with 50ms whip antenna on dedicate antenna connector.  Next step is to add a 30mhz lpf to mitigate FM intermodulation... and rethink the Q7 circuit as hf dedicated preamp..
Hope to find time to put in place ideas 🙏

I made it with Flex PCB.
It seems to be working, but the sensitivity is remarkably low.
will investigate the cause of this.
Other issues include
FM radio: side up/down buttons do not work properly (same behavior as Exit button)
Exit: It appears to exit on the display, but the sound of the radio broadcast continues to be heard
I have posted the details on my blog.
It is written in Japanese, but you should be able to understand most of it from the photos and figs.
You can also download the gerber file from my blog.
https://www.jh4vaj.com/archives/42905

For the audio that remain exiting from the HF mode I noted that depend from dual HF menu enabled.
Also I don't see that you removed the two components just before pin6.. you can improve bit more the reception

I overlooked the 'HF Dual' menu.
I set it to 'OFF', the HF reception ended with 'Exit'.
By the way, when 'HF Dual' is 'ON', I hear a very loud noise ('pata-pata').
Even in 'HF mode' reception, I can hear it, albeit faintly.
What could this be? Is it a problem specific to my UV-K5?
The issue with the reception sensitivity in 'HF mode' was due to my soldering.
The pin-8 (AMI) of SI4732-A10 was not properly connected. I apologize for the confusion.
The two components I removed are 'MOD. S1'.
By the way, could the function of the side Down button (F2 button) be assigned to another button?
Under Japanese regulations, we must prevent transmission outside the amateur band.
After setting that state in the UV-K5's hidden menu, we need to block access to the hidden menu.
Therefore, I have to cut the wiring to the F2 button and physically disable the F2 button.
Of course, this applies not only to the HF version but to all.
I would be very happy if you could consider this.
Back and forth, you can download the gerber file for that Flex PCB from my blog.
If you're interested, please give it a try.

Sorry. I misunderstood a bit.
The picture above is before the mod.S1 was implemented.
MOD.S1 was then performed. In other words, I have removed those two components.
The very poor reception was, as I wrote earlier, a problem with my poor soldering.

I'm glad it's working well.
If the sound is a little quiet, you can short the resistor connected to
pins 3 and 4.
There will be no bad effects because there is a capacitor before going to
the Audio Amp.
HF Dual is an experimental feature.
Please disable it.
The HF Dual function was created to test a Real Dual Receeive(as Kenwood or
icom - highend class transceiver).
Rather than monitoring the frequency by toggling A/B and activating the
receiving side like a typical dual watch, this is a function that allows
A/B simultaneous reception (reception from vfoA and vfoB are heard
together) found in high-end radios.
To do this, you need to mix the audio volume of BK-4819 and SI4732-A10. I
was testing it.
If I can increase the free space of the program a little more, I will do
more testing and either complete this function or remove the menu.
2.Activate/deactivate the firmware with the Hidden menu and then re-upload
it with the firmware with the Hidden menu removed, wouldn't the legal
problem in Japan be resolved?
Ian KD8CEC
On Sun, Mar 3, 2024 at 4:14 PM jh4vaj @.***> wrote:

Sorry. I misunderstood a bit.
The picture above is before the mod.S1 was implemented.
MOD.S1 was then performed. In other words, I have removed those two
components.
The very poor reception was, as I wrote earlier, a problem with my poor
soldering.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/6#issuecomment-1975070062, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPGS4POX2RBT7EGFG33YWLEUJAVCNFSM6AAAAABCCJD6GCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGA3TAMBWGI
.
You are receiving this because you commented.Message ID:
@.***>

If the HF Dual function is to be implemented, it may be necessary to allow independent adjustment of A/B volume.
I'm talking about something that may have to do with sound-volume.
Currently, the SI4732's Rout are connected to both 3 (ROUT) and 4 (LOUT).
How about connecting the Rout of the SI4732 to 3 (ROUT) and the Lout to 4 (LOUT)?
Would this not make sense? Or will it cause some problems?
I would like to experiment with that connection if it does not cause any particular problem.
Two other issues I noticed are

AM and FM broadcasts are received well, but SSB (HAM radio) is extremely low volume (both LSB and USB).
The Up/Down button on the side does not work while receiving FM broadcasts. It exits from HF mode.

As for how to deal with Japanese law, I cannot say exactly because it is not explicitly stated in it's details and I am not in a position to judge the law.
However, I understand that what is required is that "off-band transmission cannot be easily performed.
Therefore, firmware without hidden menus could be a suitable approach.
More correctly, only "F Lock" option should not be present among the hidden menus.

Hi,
Let me partially reply based on my experience.
Since uvk5 is mono, it make no sense spend time to split the signal till the two resistors. In all my samples I connected the audio just after the resistors to increase the audio output..
I noticed too that in ssb the level is almost the half of AM. I remember there was a value in the library to adjust it but need to check.
😊Luca IU0AZB

Thanks a lot.
I figured that if there is an audio signal (even if it is mono) output from both LOUT and ROUT on the SI4732, then using both of them might increase the volume.
I designed my PCB to allow for both "ROUT - 3, 4" and "ROUT - 3 / LOUT - 4" wiring.
However, I am not familiar with the SI4732, so I cannot determine if the latter connection would cause any problems.

Hi, Let me partially reply based on my experience. Since uvk5 is mono, it make no sense spend time to split the signal till the two resistors. In all my samples I connected the audio just after the resistors to increase the audio output.. I noticed too that in ssb the level is almost the half of AM. I remember there was a value in the library to adjust it but need to check.
😊Luca IU0AZB

I see there are a lot of settings for SI chip. I think future releases of FW will adjust a lot of nounces we are experimentig, hoping flash space will suffice. For example I experiment a lot of freq offset in 20m. Maybe a menù to assign a BFO default value, like BFO zero,  will circumvent the issue. But, again, this will be space for firmware upgrading!
73 de IU3POA!

Hello everyone,
I would like to ask @phdlee if the link below with SI4732 additional part for K5 will work with your firmware?
https://www.aliexpress.us/item/1005006603092025.html?gatewayAdapt=4itemAdapt&fbclid=IwAR0vdrz8DAsLToOhCzIvDAVzjXcHADi9kouPmmTMo2qH1z7ke8urbjgpCmM

73
Sean, N7SIX

I would confirm you ;) it works

I can confirm 3 successfully modded radios. Mine and 2 other OM, IW3GPO and IZ3ALE, same with "pre" BATCH PCB I designed. We all go for dedicated AMI port, with different solutions.
Stay tuned ;-D

73 de IU3POA!

I can confirm 3 successfully modded radios. Mine and 2 other OM, IW3GPO and IZ3ALE, same with "pre" BATCH PCB I designed. We all go for dedicated AMI port, with different solutions. Stay tuned ;-D

A info video:
https://www.youtube.com/watch?v=05nBVLC5yCo
73 de IU3POA!

Did you remove some parts from the original board?

Connecting the antenna input of si4732 to a dedicated output no ;)
If you want to use a single antenna, follow the tips described on CEC website

There seems to be a new model of the extension board, which seems to connect the FM port to the original FM preamp, while connecting the HF port to the 2nd antenna. There seems to be a new HF preamp chip on the addon board.

https://vi.aliexpress.com/item/1005007196802850.html?ug_edm_item_id=1005007196802850&pdp_npi=4%40dis!CZK!CZK412.66!CZK325.92!!!!!%402141351617208402169365076d084d!12000039770152008!edm!!!&edm_click_module=alg_product_3_8345504470&creative_img_ind=17&edm_log_data=edm-item-list-three-columns.store-product-log-link&tracelog=rowan&rowan_id1=aeug_edm_23869_1_en_US_2024-07-12&rowan_msg_id=bub*COWS_23869_%24aea334561def445d8a0647c8b84b6ffd&ck=in_edm_other&gatewayAdapt=glo2vnm
IMHO I don't think the preamp is needed for HF and it seems the HF input is heavily overloaded by the preamp. None of the application notes propose a preamp for HF.
https://pdf1.alldatasheet.com/datasheet-pdf/view/792143/SILABS/AN400.html
https://www.digikey.cn/Site/Global/Layouts/DownloadPdf.ashx?pdfUrl=5C850C92D37D4D12BD444A9A0FA3D79C

I have built a PCB that splits the signal from the antenna into HF and FM broadcasts and inputs to AMI and FMI.
I skipped the UV-K5 preamp and did not use it.
I posted the details on my blog (written in Japanese).
https://www.jh4vaj.com/archives/44346


Run lane failed Permission denied (SPM)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I try to implement fastlane into project using SPM, when i try run lane it end with error Permission denied
Package FastlaneRunner
import PackageDescription

let package = Package(
    name: "FastlaneRunner",
    products: [
        .executable(
            name: "FastlaneRunner",
            targets: ["FastlaneRunner"]
        )
    ],
    dependencies: [
        .package(url: "https://github.com/fastlane/fastlane", exact: "2.212.0")
    ],
    targets: [
        .executableTarget(
            name: "FastlaneRunner",
            dependencies: [
                .product(name: "Fastlane", package: "fastlane")
            ]
        )
    ]
)

Command executed

swift run --package-path CI/FastlaneRunner FastlaneRunner lane testLane
Building for debugging...
 I had fastlane installed using bundler in project directory (bundle install --path vendor/bundle). Now i install fastlane using homebrew and it is working.


Add community sounds

Need a system to randomly choose sounds from a community member (the same dummy should have the same spawn and death sound from the same person for example though, so not entirely random)

The parts where we will use their sounds are now marked in the spreadsheet and their localization keys are already in the mod. Need to add them to code and write some logic to randomly select one.


Update vmware-azure-tutorial.md

It's VMware not VMWare - adjusting for consistency within the documentation.

@sbkuehn : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[tool_crash] _TypeError: (#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39))

Command
flutter --no-color run --machine --track-widget-creation --device-id=emulator-5554 --start-paused --dart-define=flutter.inspector.structuredErrors=true lib\main.dart

Steps to Reproduce

...
...
...

Logs
_TypeError: (#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39))
#0      AndroidStudioJavaGradleConflictMigration.migrate (package:flutter_tools/src/android/migrations/android_studio_java_gradle_conflict_migration.dart:107:39)
#1      ProjectMigration.run (package:flutter_tools/src/base/project_migrator.dart:84:16)
#2      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:280:15)
#3      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:208:11)
#4      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:578:29)
<asynchronous suspension>
#5      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:468:33)
<asynchronous suspension>
#6      Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
<asynchronous suspension>
#7      HotRunner.run (package:flutter_tools/src/run_hot.dart:421:34)
<asynchronous suspension>
#8      AppDomain.launch.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:649:9)
<asynchronous suspension>
#9      AppDomain.launch (package:flutter_tools/src/commands/daemon.dart:647:5)
<asynchronous suspension>
#10     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:638:15)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1294:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)

[✓] Flutter (Channel master, 3.10.0-16.0.pre, on Microsoft Windows [Version 10.0.19045.2846], locale ru-RU)
    • Flutter version 3.10.0-16.0.pre on channel master at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 55c988fb45 (3 days ago), 2023-04-27 20:32:55 -0400
    • Engine revision 1d25906b4c
    • Dart version 3.1.0 (build 3.1.0-49.0.dev)
    • DevTools version 2.23.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at C:\Android\SDK
    • Platform android-33, build-tools 33.0.2
    • ANDROID_SDK_ROOT = C:\Android\SDK
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-9586694)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.5.4)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.5.33530.505
    • Windows 10 SDK version 10.0.22000.0

[✓] Android Studio (version 2022.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-9586694)

[✓] Connected device (4 available)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.19045.2846]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 112.0.5615.138
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 112.0.1722.64

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: master
Creation framework version: 55c988fb453eddd97cb2e4d6df9ec28d72e2e899

Closing this as duplicate of #125712 which has more details on potential cause and possible fix as mentioned #125712 (comment), so please upgrade to latest master and see if you still get the same crash or not. If yes, please write in comments and I'll reopen it.


Upgrade to ICON 2.0

Need to upgrade to ICON 2.0. Testnet running
Sejong Testnet

medium
Network: https://sejong.net.solidwallet.io
Tracker: https://sejong.tracker.solidwallet.io
Nid: 0x53

JSON RPC - https://github.com/icon-project/icx_JSON_RPC
Implementation

Include flag for running 2.0 spec
Include block height cutoff for running 2.0 spec

We need to be able to pick up transactions like this on Sejong - https://sejong.tracker.solidwallet.io/transaction/0xba153538258f0863178c1e9e46ca128dbc87c6b36743f8a79e7dca678e8793a6


Rename XEncoder to Encoder.AsX

We currently have Encoder, ObjectEncoder, ArrayEncoder, and RootEncoder all at the top level of the io.circe package—not to mention KeyEncoder, which only adds to the confusion, since it's a totally different kind of thing.
I'm in the process of adding a new Codec type class (in a separate branch), and I don't want to clutter up the package even more with ObjectCodec, etc.
This PR implements a proposal that would rename e.g. ObjectEncoder to Encoder.AsObject. Instead of ObjectCodec we can then have Codec.AsObject without being inconsistent, and we actually end up with a smaller io.circe package footprint than we had before.
The old ObjectEncoder, ArrayEncoder, etc. would be available but deprecated. I think we could remove ArrayEncoder and RootEncoder in 0.13.x, but we probably want to keep ObjectEncoder around a little longer.

Codecov Report

Merging #1150 into master will decrease coverage by 0.12%.
The diff coverage is 85.07%.

@@            Coverage Diff            @@
##           master   #1150      +/-   ##
=========================================
- Coverage   86.02%   85.9%   -0.13%
=========================================
  Files          87      85       -2
  Lines        2834    2837       +3
  Branches      117     109       -8
=========================================
- Hits         2438    2437       -1
- Misses        396     400       +4

Impacted Files
Coverage Δ

...ed/src/main/scala/io/circe/disjunctionCodecs.scala
100% <ø> (ø)
:arrow_up:

...hared/src/main/scala/io/circe/syntax/package.scala
100% <ø> (ø)
:arrow_up:

.../core/shared/src/main/scala/io/circe/package.scala
0% <0%> (ø)

...red/src/main/scala/io/circe/generic/semiauto.scala
100% <100%> (ø)
:arrow_up:

...hared/src/main/scala/io/circe/scodec/package.scala
93.33% <100%> (ø)
:arrow_up:

.../src/main/scala/io/circe/testing/EqInstances.scala
100% <100%> (ø)
:arrow_up:

...io/circe/generic/util/macros/JsonCodecMacros.scala
95% <100%> (ø)
:arrow_up:

.../io/circe/generic/extras/ConfigurableDeriver.scala
100% <100%> (ø)
:arrow_up:

.../main/scala/io/circe/generic/extras/semiauto.scala
100% <100%> (ø)
:arrow_up:

...irce/generic/encoding/DerivedAsObjectEncoder.scala
100% <100%> (ø)

... and 12 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a731554...940e89d. Read the comment docs.

@travisbrown, should I revamp this PR if Codec is back in discussion?
https://github.com/circe/circe/pull/811

@lorandszakacs I'm taking a different approach—the main motivation is to make semi-automatic derivation more efficient, so having deriveCodec rely on resolving separate encoders and decoders won't work. I'm also intentionally and explicitly not providing any implicit summoning for Codec instances given encoders and decoders (the idea is that Codec is a convenience for definitions and generally should not be used as a constraint).
I'll open a PR soon and we can discuss the merits of my approach vs. the one in your PR. Thanks for bringing it up.

@travisbrown if you can squeeze efficiency out of your approach then it does sound better.
At the very least I'll rebase my branch and bring it up to date.


Add a demo gif image explaining how to use our rocket

We need now a demo section in our README, to show our application in action, it should be a GIF.

I could help with this

@phr-nk awesome! Go ahead!! It's yours!

Finished! in #47


Remove travis

Now using github actions for CI etc.

@sjkelly or @tejasvaidhyadev is there any reason to keep travis here?
My impression is that most julia repos use github actions now.
But I'd like a 2nd pair of eyes before deleting it.


add behaviour phenotype terms for FlyBowl dataset

Behavior list is here:
http://research.janelia.org/bransonlab/FlyBowl/BehaviorResults/behaviorlist.html
These are all keys for quantitative recording.  Working out what can be expressed using (qualitative) ontology terms will take discussion.  Some look straightforward though e.g.:
walking
wing flicking
touching
wing extension
righting

Actually - looks like we should be using this 'classifications' list for ontologising:
http://research.janelia.org/bransonlab/FlyBowl/BehaviorResults/glossary.html#behaviorclassifications

Also - IIRC, there should be video examples available for many or all of these.  Would be great if we could link terms out to reference vids.    May need to request these as don't see them on FlyBowl site.

FYI this paper (FBrf0236042) will also require thin curation - thought it would be easier/most efficient to do everything in one go once new CV terms are in place, which is why I haven't curated it yet (it's a massive screen so would probably need to be curated with some scripting anyway).
Also keep in mind that we heard from Alice Robie (via FlyBase helpmail) offering to provide Bloomington stock numbers for the lines assayed around the time the paper was published (we said the paper would be curated in collaboration with VFB and that we may be in touch in future). So it might be possible to coordinate with her/people at Janelia to get a csv file or such to help with curation.

FYI, will be loading thin curation of this paper on Thursday - processed using Gillian's helpful scripts.


Would it be possible to have a sorter command line for ng generate @ngxs/schematics ?

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[x] Support request => https://github.com/ngxs/store/blob/master/CONTRIBUTING.md
[ ] Other... Please describe:

Current behavior
In my opinion, ng generate @ngxs/schematics ... is kind of a long command. Would you be possible to have a sorter one, e.g ng generate ngxs ... (inspired from nrwl)
Expected behavior
N.A.
Minimal reproduction of the problem with instructions
N.A.
What is the motivation / use case for changing the behavior?
It is faster to type ng generate ngxs comparing to ng generate @ngxs/schematics.
Environment

Libs:
- @angular/core version: 7.1.0
- @ngxs/store version: 3.3.1

Browser:
- [x] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: 8.14.0
- Platform:  Mac, Windows

Others:
N.A.

Its a little odd that you would use mention using ng generate instead of ng g in an issue about command length.
To achieve what @nrwl/schematics has you'll need to modify your angular.json and add a cli entry if there isn't one. The cli entry should be an object - you'll need a line in it that says "defaultCollection": "@ngxs/schematics"
If you're in a Nrwl Nx workspace you will already have this value set to '@nrwl/schematics'. Know that changing this means that now to use any nrwl schematics you'll have to use the longform - ng g @nrwl/schematics:library
There's also the option of using Angular Console (another nrwl project) when Ngxs integration is ready. You'll notice that even in Angular Console nrwl's own commands are the longer version as it doesn't use the workspace's default collection.

Thank you for the guide. I'll follow it 👍


Added NATTT app

NATTT is Not Another Time Tracking Tool.
No timers you have to start and stop. No complex task creation dialogs. Just say what you are doing. It's that simple. Oh, and it's FREE.
NATTT website
NATTT is an electron & cordova based application.

electron & cordova

Interesting! Can you share more about how you're using the two in combination?

Hey @zeke , sure. NATTT is basically an Angular application and I created it using the Angular CLI in the first place. I wanted it to be a web / Angular-first application and added integration with electron and cordova afterwards. The electron integration was easy, I just created a main.js file and added it to the package.json. The only thing I had to change was the default output folder (dist -> www).
The cordova integration was a bit more of a problem, but I managed it by creating a subfolder for the cordova stuff and created a symlink for the www folder.
In order to get the default Angular routing to work, I also had to change the routing strategy to use the "old" hash strategy.
With this architecture I'm now able to develop my application like a normal Angular app and build & test it for electron & cordova with a simple build step.

✨ Fantastic ✨
If you were to blog about this setup, I'm sure many people would be interested. We could also promote it from the Electron side as a way to build and package web applications for all platforms.

Actually I already work on some blog posts around NATTT ;-)
I will let you know if the first (technical) one is ready and it would be awesome if you'll promote it. I already wrote a small one regarding my motivation to create this app: http://timokorinth.de/nattt-not-another-time-tracking-tool/.


TW_STIME API

This PR is a new API for user defined tw_stime. It is implemented through #define macros, which should have minimal performance impact in the nominal case.

If this merge represents a feature addition to ROSS, the following items must be completed before the branch will be merged:

[ ] Document the feature on the blog (See the website Contributing guide).
Include a link to your blog post in the Pull Request.
[ ] Builds should cleanly compile with -Wall and -Wextra.
[ ] One or more TravisCI tests should be created (and they should pass)
[ ] Through the TravisCI tests, coverage should increase
[ ] Test with CODES to ensure everything continues to work

@caitlinross Heads up that I changed some things in the instrumentation code. Namely, I changed the st_collect_xx_data functions to use tw_clock instead of tw_stime for the real-time variables. I think some stats collecting variable types also changed. See commits f03e6cbeb5b38293f77905efeb6364ed76bb1952,  d8a24c1359e921836f58f00dbe4725b51c4b91c2, and 56c4f19431a65113596ee06c01d104b70e673988.

Thanks, Elsa! - what models have been tested w/ this PR ?
Thanks again,
Chris
On Thu, Jul 18, 2019 at 12:15 PM Elsa Gonsiorowski, PhD <
<EMAIL_ADDRESS>wrote:

This PR is a new API for user defined tw_stime. It is implemented through
#define macros, which should have minimal performance impact in the
nominal case.
If this merge represents a feature addition to ROSS, the following items
must be completed before the branch will be merged:

Document the feature on the blog (See the website Contributing guide
https://github.com/ROSS-org/ross-org.github.io/blob/master/CONTRIBUTING.md
).
Include a link to your blog post in the Pull Request.
Builds should cleanly compile with -Wall and -Wextra.
One or more TravisCI tests should be created (and they should pass)
Through the TravisCI tests, coverage should increase
Test with CODES to ensure everything continues to work

You can view, comment on, or merge this pull request online at:
https://github.com/ROSS-org/ROSS/pull/157
Commit Summary

whitespace
added TWOPT_DOUBLE type
whitespace
convert some global vars to be explicitly doubles
whitespace
start of TW_STIME API
convert ROSS over to TW_STIME API
whitespace
tw-opts: removed STIME opt, replaced with DOUBLE
st_collect functions should use tw_clock (not tw_stime)
instrumentation global vars should be doubles (not tw_stime)
explicit use of ternary operator from ROSS_MIN for tw_stime
one more instrumentation update
removed ROSS_MIN with some code changes

File Changes

M core/avl_tree.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-0 (62)
M core/gvt/mpi_allreduce.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-1 (34)
M core/gvt/mpi_allreduce.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-2 (20)
M core/instrumentation/ross-lps/analysis-lp.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-3 (31)
M core/instrumentation/st-event-trace.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-4 (9)
M core/instrumentation/st-instrumentation.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-5 (8)
M core/instrumentation/st-instrumentation.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-6 (16)
M core/instrumentation/st-model-data.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-7 (9)
M core/instrumentation/st-sim-engine.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-8 (7)
M core/instrumentation/st-stats-buffer.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-9 (14)
M core/network-mpi.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-10 (12)
M core/queue/calendar.c.old
https://github.com/ROSS-org/ROSS/pull/157/files#diff-11 (34)
M core/queue/splay.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-12 (28)
M core/ross-extern.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-13 (6)
M core/ross-global.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-14 (6)
M core/ross-inline.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-15 (10)
M core/ross-types.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-16 (2)
M core/ross.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-17 (4)
M core/tw-event.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-18 (18)
M core/tw-eventq.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-19 (6)
M core/tw-kp.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-20 (5)
M core/tw-opts.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-21 (28)
M core/tw-opts.h
https://github.com/ROSS-org/ROSS/pull/157/files#diff-22 (24)
M core/tw-pe.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-23 (3)
M core/tw-sched.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-24 (45)
M core/tw-setup.c
https://github.com/ROSS-org/ROSS/pull/157/files#diff-25 (4)

Patch Links:

https://github.com/ROSS-org/ROSS/pull/157.patch
https://github.com/ROSS-org/ROSS/pull/157.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ROSS-org/ROSS/pull/157?email_source=notifications&email_token=AAHVJE25LLGX4UTMTY6ESPDQACJLXA5CNFSM4IE5KPR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HABRGMQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHVJE7YFPTB5T4JVKK5EA3QACJLXANCNFSM4IE5KPRQ
.

--
Christopher D. Carothers
Director, Center for Computational Innovations
Professor, Department of Computer Science
Rensselaer Polytechnic Institute
110 8th Street
Troy, New York 12180-3590
e-mail<EMAIL_ADDRESS>web page: www.cs.rpi.edu/~chrisc http://www.cs.rpi.edu/~chrisc
phone:<PHONE_NUMBER>
fax:<PHONE_NUMBER>

Besides phold, this is used with Tomas’s matrix models (using his own tw_stime type). A separate PR will include his time implementation.
I plan to test this with CODES and write some documentation before merging.

I don't think I fully understand what's going on in these changes.  I remember we had discussions about have a new time type to support Tomas' needs, but I don't remember all the details. Maybe it will make sense when you complete the documentation.
Here's some comments based on my current understanding:

This should be requested to merge into develop not master. Especially since it seems it requires changes to models to support.
Some changes for the instrumentation are incorrect. Any cases of tw_stime should be converted to double, not tw_clock. The changes to tw_clock messes up reporting of the real time value of the sampling time (it's being divded by g_tw_clock because it's supposed to be reported as amount of time and not number of clock cycles).
I think this is going to result in some big changes to CODES, NeMo, right? If I understand correctly, every call to tw_now requires a call to some TW_STIME_XXX macro?  And tw_stime now needs to be converted to double in all these models?
There's still a typedef double tw_stime in ross.h. Is that an accident? If it is supposed to be there, then why does tw_stime need to be changed to double in other places in the code?

Yes, this would require some changes to NEMO since there is some significant logic involved with TW_NOW. But I think the ability to change what the clock datatype is would be worth the work - it could potentially give NeMo the ability to handle denser simulations.
So as far as I’m concerned, as long as the release tag is has the old version of TW_NOW, then this would be fine

Mark Plagge
Sent from my iPhone

On Jul 24, 2019, at 1:50 PM, Caitlin Ross<EMAIL_ADDRESS>wrote:
I don't think I fully understand what's going on in these changes. I remember we had discussions about have a new time type to support Tomas' needs, but I don't remember all the details. Maybe it will make sense when you complete the documentation.
Here's some comments based on my current understanding:
This should be requested to merge into develop not master. Especially since it seems it requires changes to models to support.
Some changes for the instrumentation are incorrect. Any cases of tw_stime should be converted to double, not tw_clock. The changes to tw_clock messes up reporting of the real time value of the sampling time (it's being divded by g_tw_clock because it's supposed to be reported as amount of time and not number of clock cycles).
I think this is going to result in some big changes to CODES, NeMo, right? If I understand correctly, every call to tw_now requires a call to some TW_STIME_XXX macro? And tw_stime now needs to be converted to double in all these models?
There's still a typedef double tw_stime in ross.h. Is that an accident? If it is supposed to be there, then why does tw_stime need to be changed to double in other places in the code?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Spam
Not spam
Forget previous vote

This shouldn't change any of the model code and does not change the tw_now call (only how tw_now is implemented). I would expect models to not be abstracted over the tw_stime type, so models developers could assume whatever tw_stime type they wanted.
As for the instrumentation change, tw_stime does not represent real time. I will make the change to doubles (undoing my change to tw_clock).

Ah okay. I think I understand the changes better now.  So the calls to macros like TW_STIME_DBL are just needed internally in ROSS to handle the different ways a model.
So yeah we just need to have those instrumentation changes changed from tw_clock to double.  Also this needs to be merged into develop, since we're no longer directly merging features into master.  I think after the instrumentation changes are made and it's been tested out with CODES, it'd be fine to go ahead and merge into develop.  But we'd want documentation to be final before the next release is merged into master.

Closing this PR to open one against develop.


Error in CI: ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE  Cannot perform a frozen installation because the lockfile needs updates

My Action Step is
`
  uses<EMAIL_ADDRESS>
  with:

    version: 6.x

    run_install: true

`
I am getting below error when running this  action
Error in CI: ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE  Cannot perform a frozen installation because the lockfile needs updates
and when try to fix my lockfile locally with command npm i --fix-lockfile i get following error:
`
npm i --fix-lockfile
npm ERR! Cannot read properties of null (reading 'matches')
npm ERR!      /Users/un/.npm/_logs/2022-05-01T10_32_11_056Z-debug-0.log
`

npm i --fix-lockfile

Can you try pnpm i --fix-lockfile?

@KSXGitHub
pnpm i --fix-lockfile
 ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  next@12.1.5_react-dom<EMAIL_ADDRESS>isn't supported by any available resolver.

This error happened while installing the dependencies of<EMAIL_ADDRESS>Progress: resolved 28, reused 29, downloaded 0, added 0

Note that npm i --legacy-peer-deps works fine when using npm.

For now i have fixed issue by adding following to my .npmrc file
auto-install-peers=true

strict-peer-dependencies=false

and when try to fix my lockfile locally with command npm i --fix-lockfile i get following error:

Why do you run npm i if you use pnpm?
You should run pnpm install and commit the lockfile.

Is you using latest pnpm the version of 7.x?

the same error
➜  toolbox git:(master) pnpm i --fix-lockfile
 ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  react-hook-form<EMAIL_ADDRESS>isn't supported by any available resolver.

the same error
➜  toolbox git:(master) pnpm i --fix-lockfile
 ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  react-hook-form<EMAIL_ADDRESS>isn't supported by any available resolver.

rerun pnpm install and commit the lockfile, its ok

Same error here.
➜  pnpm i --fix-lockfile
Scope: all 10 workspace projects
.../apps/app:
 ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  react-hook-form<EMAIL_ADDRESS>isn't supported by any available resolver.

This error happened while installing the dependencies of<EMAIL_ADDRESS>Progress: resolved 309, reused 309, downloaded 0, added 0

getting this in CI:
Scope: all 10 workspace projects
Lockfile is up to date, resolution step is skipped
 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with apps/app/package.json

Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"

Same error! Running pnpm i --fix-lockfile does not change the lockfile, but in CI I keep getting an error.
This is with a project that has a peer dependency listed like this:
"peerDependencies": {
  "@ethersproject/bignumber": "5.x"
},

You need to update pnpm before running it :)

Yeah, I was on v7.30.1. After upgrading to v8, I can confirm that running --fix-lockfile fixed the issue.

Just encountered the same issue in Azure Pipelines. I can also confirm that updating from pnpm 7 to 8 fixed it for me.

Same here. Upgraded from pnpm v7 to v8 and fixing the lock file using the --fix-lockfile option fixed the issue

same problem today. worked for us.

@jyono The spike is probably related to  the pnpm v8 release just a few hours ago, which seems to require a new lockfile version when installing with --frozen-lockfile (which some CI/CD environments default to).
We ran into this issue too, because our CI/CD was installing pnpm, pulling the latest version. Until earlier today, that was v7—until that switched to v8, breaking our builds due to the unsupported lockfile version.
Locally installing pnpm v8 and updating the lockfile (as per above posts) worked.
Alternatively, you can also fix your pnpm version to pnpm@^7 and stick with the old lockfile.

I guess the takeaway from this issue is always to use specific versions of external dependencies in CI.

I guess the takeaway from this issue is to always use specific versions of external dependencies in CI.

(+1, ironically also why the lockfiles in question exist)

pnpm lock is incompatible between v7 and v8? any plan to fix?

I have a @formkit/auto-animate dependency, version 1.0.0-beta.6, pnpm version 8.1.0
I'm getting the ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  @formkit<EMAIL_ADDRESS>isn't supported by any available resolver. error in CI.

@jyono The spike is probably related to the pnpm v8 release just a few hours ago, which seems to require a new lockfile version when installing with --frozen-lockfile (which some CI/CD environments default to).
We ran into this issue too, because our CI/CD was pulling the latest pnpm version. Earlier today, that was v7, until this switched to v8, breaking our builds due to the unsupported lockfile version.
Locally installing pnpm v8 and updating the lockfile (as per above posts) worked.
Alternatively, you can also fix your pnpm version to pnpm@^7 and stick with the old lockfile.

thanks!

Summary:
Use corepack to manage package manager is the best choice. This enforces the same manager in different environments. For example, you are running pnpm@7 locally but pnpm@8 in ci, the lockfile format will break the installation. So, please make sure you have packageManager field defined in your package.json instead of specifing a pnpm version in the workflow file manually.

If you encounter this error with pnpm catalog you might have an incorrectly added " or , in the pnpm-workspace.yaml file.


Vehicles and Map Dimensions

Hi CARLA team,
I have a few question about the model and maps dimensions.

Based on some previous issues, I knew that that the pixel density is 0.1643 m/pixel. #262 . Can I use this to calculate the distance traveled by measuring the pixels traveled?

Since I am interested in how far away the vehicle is from the intersection, could you give some information about the dimensions( Height, Width and Length) of both vehicles (Mustang and Model 3)? I am assuming that the GPS info of the vehicle is always located at the center of the vehicle according to your documentation.

How to measure the dimension(actual lenght) of both maps? Could you let me know what is size of maps in the unit of pixel so that I can calculate the length on my own?

If I want to make the distance to intersection in town 1 and town 2 the same, should I use the same pixel and node density? Also, what is the dimensions of map town 2?

I greatly appreciate every effort of your development team.
Sincerely,

Based on some previous issues, I knew that that the pixel density is 0.1643 m/pixel. #262 . Can I use this to calculate the distance traveled by measuring the pixels traveled?

I think it should do the job.
But you have the exact car positions each frame. So I think a more accurate solution should be adding each frame the distance between the old frame and the current frame.

Since I am interested in how far away the vehicle is from the intersection, could you give some information about the dimensions( Height, Width and Length) of both vehicles (Mustang and Model 3)? I am assuming that the GPS info of the vehicle is always located at the center of the vehicle according to your documentation.

We provide the bounding box extent so you can calculate the bounding box of each vehicle. Take a look at these old issues: #64 #314.

How to measure the dimension(actual lenght) of both maps? Could you let me know what is size of maps in the unit of pixel so that I can calculate the length on my own?

You can open the Unreal Engine editor and measure it. @TheNihilisticRobot just made it for you (in m).
Town 1 - 410,68 x 344,26
Town 2 - 205,59 x 204,48

4 If I want to make the distance to intersection in town 1 and town 2 the same, should I use the same pixel and node density? Also, what is the dimensions of map town 2?

I do not understand your question :(

Hi marcgpoig,
Thank you for taking your time answering me questions.
I think that I have answers for most of my questions.
To clarify the last question, I want to calculate the distance from the vehicle's current position to the intersection. For example, my measurement of distance from current vehicle's position to the intersections in the unit of pixel might be different in two maps due to different dimensions of the map. But as long as I use the same pixel density, can I say if the measurement of distance in the unit of pixel  from current vehicle's position to the intersection is the same in both maps, the actual distance to the intersection will be the same?
Thanks,

@tayloryang722 Sorry for the late reply!
If I understand you correctly, you are right in your assumptions :)

@marcgpuig @TheNihilisticRobot Would it be possible to find the dimension of Town10 map? Thank you!


Implement cilium upgrade using Helm

Summary
Implements the cilium upgrade command using a thin wrapper around Helm rather than direct Kubernetes API calls.
A few of the self-contained features are broken down into separate commits.
Motivation
This implementation allows for more consistent documentation and behavior among Cilium installation methods, such as those docs which use only Helm directly.
This implementation includes an alternate implementation for the cilium {clustermesh,hubble} {enable,disable} family of commands. The "legacy" implementation of those commands came from a time when using Helm was insecure (it installed a daemon into the cluster with cluster-admin privileges. Helm is now relatively safe to use, thus we use Helm here as a library to implement all features for Cilium installation, upgrade, and feature enable/disable whcih are currently implemented in the Cilium Helm chart.
Example Usage
For example, we can use this new upgrade command to enable Cluster Mesh on a set of two Cilium clusters with the following procedure.
Create a kind cluster with the following config
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: c1
nodes:
  - role: control-plane
  - role: worker
  - role: worker
  - role: worker
networking:
  disableDefaultCNI: true
  podSubnet: "<IP_ADDRESS>/16"
  serviceSubnet: "<IP_ADDRESS>/16"

kind create cluster --config c1.kindconfig.yaml

Test that the kind cluster came up with k get pods -A
Install Cilium using the CLI, making sure to set a Cluster ID and Cluster Name
export CILIUM_CLI_MODE=helm
cilium install --help
# note the suggestion to use --helm-set flags
cilium install --helm-set cluster.id=1 --helm-set cluster.name=cluster1

Create a second cluster using kind with the following config
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: c2
nodes:
  - role: control-plane
  - role: worker
  - role: worker
  - role: worker
networking:
  disableDefaultCNI: true
  podSubnet: "<IP_ADDRESS>/16"
  serviceSubnet: "<IP_ADDRESS>/16"

kind create cluster --config c2.kindconfig.yaml

Check that you are authed for Cluster kind-c2
Run k get pods -A and look for kube-apiserver-c2-control-plane
Install Cilium using the CLI, making sure to set a Cluster ID and Cluster Name
export CILIUM_CLI_MODE=helm
cilium install --help
# note the suggestion to use --helm-set flags
cilium install --helm-set cluster.id=2 --helm-set cluster.name=cluster2

Enable clustermesh on Cluster 1 using the new Helm upgrade command
export CILIUM_CLI_MODE=helm
cilium upgrade --help
# note the suggestion to use --helm-set flags
cilium upgrade --context $CLUSTER1 \
    --helm-set clustermesh.useAPIServer=true \
    --helm-set clustermesh.apiserver.service.type=NodePort
# observe that the clustermesh apiserver is running
k get pods -A

Prep environment for the clustermesh enable.
export CLUSTER1=kind-c1 CLUSTER2=kind-c2

Extract the CA cert from Cluster 1 and install it into Cluster 2, then restart Cilium on Cluster 2
kubectl --context $CLUSTER2 delete secret -n kube-system cilium-ca && \
kubectl --context $CLUSTER1 get secrets -n kube-system cilium-ca -oyaml \
    | kubectl --context $CLUSTER2 apply -f -
# you should see the following output
# secret "cilium-ca" deleted
# secret/cilium-ca created
# proceed to restart Cilium on kind-c2
kubectl --context $CLUSTER2 delete pod -l app.kubernetes.io/part-of=cilium -A

Enable clustermesh on Cluster 2 using the new Helm upgrade command
export CILIUM_CLI_MODE=helm
cilium upgrade --help
# note the suggestion to use --helm-set flags
cilium upgrade --context $CLUSTER2 \
    --helm-set clustermesh.useAPIServer=true \
    --helm-set clustermesh.apiserver.service.type=NodePort

Move the secrets expected by the cilium clustermesh connect command (this quirk to be fixed with a helm-mode PR for that command)
k get secrets --context $CLUSTER1 -n kube-system clustermesh-apiserver-remote-cert \
    -oyaml \
    | sed 's/name: .*/name: clustermesh-apiserver-client-cert/' \
    | k apply --context $CLUSTER1 -f -

k get secrets --context $CLUSTER2 -n kube-system clustermesh-apiserver-remote-cert \
    -oyaml \
    | sed 's/name: .*/name: clustermesh-apiserver-client-cert/' \
    | k apply --context $CLUSTER2 -f -

Connect the two clusters using ClusterMesh
cilium clustermesh connect --context $CLUSTER1 --destination-context $CLUSTER2

Run the Multi-Cluster connectivity tests.
cilium connectivity test --context $CLUSTER1 --multi-cluster $CLUSTER2

(This has been included as a CI workflow)
closes #1493

removing github-sec and ci-structure from reviewers. this pr got updated, and now it's only modifying files owned by cli and sig-hubble teams.

EKS (ENI): failed https://github.com/cilium/cilium-cli/issues/1514


Offcanvas + fixed header jumps the content

All the recent versions as of today.
What is happening?
When you use Offcanvas, and you have navbar with fixed-top, the content of navbar will jump.
That is expected because scrollbar disappears so it jumps.
I tried to fix the issue by allowing scrolling, so I passed scrollable prop.
Now the whole body jumps because reactstrap keeps adding body-padding: -15px (scrollbar width).
What should be happening?
If canvas is scrollable the body padding shouldn't be applied
https://github.com/user-attachments/assets/d1f14a6f-0379-4de2-be4f-8e752e121999

I want to work on it can you please assign it to me?


sometime this week, all our previous SDK releases became unavailable.

Describe the bug
We have many years of package versions available on PyPi.org.
Last week they were all available, e.g. you could PIP install older versions of our SDK like 1.15.0.
Sometime this week, all but the current/latest version of our SDK stopped working.
They still show up as valid package version on PyPi.org web search, but the PIP command started failing sometime this week.
Expected behavior
I expect PIP install to work for not only the current package release, but all older version too.
To Reproduce
C:\git\spx\spx>pip install azure-cognitiveservices-speech==1.14.0
ERROR: Could not find a version that satisfies the requirement azure-cognitiveservices-speech==1.14.0 (from versions: 1.20.0)
ERROR: No matching distribution found for azure-cognitiveservices-speech==1.14.0
C:\git\spx\spx>pip install azure-cognitiveservices-speech==1.16.0
ERROR: Could not find a version that satisfies the requirement azure-cognitiveservices-speech==1.16.0 (from versions: 1.20.0)
ERROR: No matching distribution found for azure-cognitiveservices-speech==1.16.0
C:\git\spx\spx>pip install azure-cognitiveservices-speech==1.19.0
ERROR: Could not find a version that satisfies the requirement azure-cognitiveservices-speech==1.19.0 (from versions: 1.20.0)
ERROR: No matching distribution found for azure-cognitiveservices-speech==1.19.0
C:\git\spx\spx>pip install azure-cognitiveservices-speech==1.20.0
Collecting azure-cognitiveservices-speech==1.20.0
Using cached azure_cognitiveservices_speech-1.20.0-cp310-cp310-win_amd64.whl (1.7 MB)
Installing collected packages: azure-cognitiveservices-speech
Successfully installed azure-cognitiveservices-speech-1.20.0
My Platform
I'm trying this on windows, but this also fails on our Ubuntu CiCd pipeline that produces docker images for the SDK...
Additional context
I was able to install 1.15.0 last week, and we have not uploaded any new package versions, or changed anything on PyPi.org since the last time I successfully installed an older version of the Speech SDK.

Is it possible you're trying to install with Python 3.10? I see that the latest release has built distributions for Python 3.7, 3.8, 3.9 and 3.10 but previous versions don't have built distributions for 3.10. None of the releases publish source distributions either, so pip can't fall back on building from source when there is no appropriate built distribution.

Is it possible you're trying to install with Python 3.10? I see that the latest release has built distributions for Python 3.7, 3.8, 3.9 and 3.10 but previous versions don't have built distributions for 3.10. None of the releases publish source distributions either, so pip can't fall back on building from source when there is no appropriate built distribution.

You are correct.  Apparently all our machines auto installed an update and now have python 3.10 as the default python.
This makes the older packages disappear.  If I select python 3.9 or lower, they come back.
Thank you for the better set of eyes!


Checkboxes are floating further away from stream names

Currently the streams list on the dashboard have information in separate rows, equal distance from each other.

Ideally the name of the stream is immediately next to the selector box so users can easily see what line they're selecting.

This appears resolved, I assume to some work @clacladev did a while back. Closing.


Any plans to update to 2.3.x?

I misread - I think you said you were going to add 3.x support, but I assume 2.3.x is already fine with the 2.2 version.


Fixed progress bar display

Unfortunately, double progress bars are still very fragile.
Either remove progress bars or simplify the implementation.

Current coverage is 74.35% (diff: 100%)

Merging #28 into master will increase coverage by 0.75%

@@             master        #28   diff @@
==========================================
  Files            10         10
  Lines           341        351    +10
  Methods          53         53
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            251        261    +10
  Misses           90         90
  Partials          0          0

Powered by Codecov. Last update 9b72b29...39d24fc


PowerMeasTest has in Spectrum Inquiry Response "Channel Type" = PAL instead of GAA

Executing the PowerMeasTest, the SAS Harness replies in Spectrum Inquiry Response that "channelType"= PAL instead of GAA (see log extract below). The following Grant Response in the PowerMeasTest does say correctly "channelType=GAA".
The JSON files in te SAS Harness in all the test cases are built to reply as GAA in order to cover the entire 3.55-3.7GHz frequency range and to avoid issues with the definition/configuration of PAL licenses in the CBSD/DP UUT.
"spectrumInquiryResponse": [
{
"availableChannel": [
{
"channelType": "PAL",
"frequencyRange": {
"highFrequency":<PHONE_NUMBER>,
"lowFrequency":<PHONE_NUMBER>
},

Addressed in release v<IP_ADDRESS>

Issue still exists in SAS Harness release v<IP_ADDRESS>

Missed one case in original fix.  Fixed in branch predev_<IP_ADDRESS>


ZendeskChat is undefined

ZendeskChat.startChat({
      chatOnly: true
    });

alwaus ZendeskChat / RNZendeskChat is undefined

There is a typo in Docs, ideally it should be RNZendeskChat.startChat. Also if it occurs with that too then, please provide some more info like which RN version you are using, have you imported the library properly and initialised it?

hi @Saranshmalik , I have a question please, your plugin is react-native-zendesk-v2 so I installed why we imported from react-native-zendesk and not react-native-zendesk-v2? when I use react-native-zendesk-v2 I get new issue:

"Cannot read property 'startChat' of undefined"

so when I imported from react-native-zendesk, I get this:

bundling failed: Error: Unable to resolve module react-native-zendesk from /App/Containers/Menu/ControlPanel.js: Module react-native-zendesk does not exist in the Haste module map.

environment
"react-native": "0.59.0",
"react-native-zendesk-v2": "^0.2.1",

Okay the doc has some issues, my bad will fix those.
Please try this
import RNZendesk from 'react-native-zendesk-v2'
Also since you are on RN v0.59 make sure you follow the package linking as per RN docs.

it works thank you @Saranshmalik


Cache not being cleaned on planned article

Using Wordpress, the cache is not being cleaned on a planned article.
Our articles are published also on the homepage so they are published on the category but not in the homepage. only solution, re-save the article after it has been published.

The templates repo has moved to workers-sdk monorepo, if you are still encountering problems with this, can you leave a comment and let us know.

@mtissington I'm closing this for now since we haven't heard from you in a while, but feel free to re-open if this is still an issue, and we can investigate further