2023. február 26., vasárnap
VFD Mania 2. - Inverting boost converter
VFD Mania 1. - Preface
I'm kind of maniac, if it comes to the VFD displays. I've several instruments in my lab with VFD.
Even I collected many various versions with the thought, once I'll build something from it. Actually my first acquisitions were VFD modules, what already have all of the power supplies, so I not need to know, how to power, how to drive them.
On the other side, I always wanted to know, how VFD displays are working, how they need to be driven.
This story begins 8 month ago, just the half written article was put asside.
Then I seen this nice bare VFD so cheep, I couldn't resist. Bought them and my learning journey begins.
...but I had a feeling, I may did something wrong, so I broke the design into pieces, ordered the power supply boards separately, so I can test it, before send the whole module to manufacturing.
The git repo of the design is here:
https://gitlab.com/suf/suf-electronics-vfd-futaba-15mt67gnk
To be continue..
2023. január 16., hétfő
New Arrival 9.
2023. január 9., hétfő
AS/400 and me
EPROM burning 21/25V 3. - Closing
- The TL866II is unable to handle any device programable above 18V
- My HP 8903B has 21V EPROMs and I wanted to refresh them
- The T56 programmers cost are way above the amount I would pay for this
2023. január 3., kedd
Azure, AKS, Terraform, proxy
Happy New Year to everybody!
It maybe unexpected, but I start the year with some professional content and not my hobbies.
When you try to deploy an Azure Kubernetes Cluster from Terraform, and the cluster has proxy configuration, on any terraform apply on the cluster will cause redeployment, what is not what you expect.
The reason is that the Azure mechanism add a few addresses to the no_proxy list in addition to the ones you set. Changing the no_proxy list will force recreation. The list stored in the state will always be different from the list on the AKS resource itself.
First let check, what are those addresses:
- localhost and 127.0.0.1 - need no explanation, it is the VM loopback address
- konnectivity - Kubernetes Konnectivity service
- 168.63.129.254 - Azure platform resources: https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16
- 169.254.169.254 - Azure Instance Metadata Service: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/instance-metadata-service
- Address space of the VNET where the cluster installed
- pod_cidr of the AKS cluster. Default: 10.244.0.0/16
- service_cidr of the AKS cluster. Default: 10.0.0.0/16
- If it is a private cluster, cluster's private_fqdn. It looks like this: <clustername>-<8 hex random number>.<DNS Zone Guid>.privatelink.<region>.azmk8s.io
The values above, can be known before the cluster creation, except the last one. This is created during the deployment of the cluster, so adding all of the items to your no_proxy list before the cluster creation will not help, if you have a private cluster.
What you can do:
Add lifecycle management to the cluster. It will look like this:
This would work, but you just half way to the solution.
When you reapply your plan, it will not recreate the AKS cluster. But what if you willingly change the no_proxy parameters? In this case this will still ignored and the AKS doesn't recreate, what is not the expected behavior.
Lets assume, you heave the user provided no_proxy parameters in a no_proxy variable:
The lifecycle management is able to trigger recreation of the resource with replace_triggered_by property. The problem with it, that the variable above, can't be the source of the trigger. But for example a resource can.
Here comes a dirty trick. How convert a variable list into a resource?
Hashicorp has a Terraform provider named tfcoremock (https://registry.terraform.io/providers/hashicorp/tfcoremock/latest/docs). I'll use it here.
First add it to the providers list:
Now, we can store the list above into the state:
Now, we can reference it from the replace_triggered_by:
This is almost perfect, but not completely.
When you change any element in the no_proxy variable list, it will trigger the replacement, but if you add, or remove element from the list, it will ignore it.
One last step. Make the length of the list into work:
Now, it is replace the AKS on any change in the no_proxy variable list, but keep it intact otherwise.
2022. december 31., szombat
End of 2022
This is some valuation of the year from this blogs perspective.
At the beginning of the year I was planning to write at least one post weekly. This would be 52 posts. Actually done 31.
Although, I'm not satisfied with the result, I is better than the previous years. The last year I was writing more, was 2018. I intend to achieve this as a goal for 2023.
Some highlights of 2022, also from my hobby perspective:
- My new lab is still not finished, but I can tell, I moved in. Now I feel comfortable and spend more and more time in it
- Finished the Videoton Melodyn project. I'm very proud of it. It was ready in time and functioning flawlessly
- I closed my Hungarian language blog, what was running in parallel with this one. The decision come from anger at the first place, but today I feel, not writing (or translating) in to languages spare some time to me. So I keep it that way.
- Started a few projects, what looks like shelved to me, also have a few revisited, but put back to the shelve:
- E1300A Front connectors
- Measurement control
- CNC Router
- Pan & Tilt gimbal
- TL866II EPROM programmer update
- PM3082 repair
- Rackmount power amplifier
- Function generator power amplifier
- Contract project involving 4-20mA current loop and infra gates (not to discuss here deeper)
- VFD display driver (even the first post of it kept in draft)
In 2023, I plan to work on my projects on a more organized way. Not to do many projects in parallel, focus on one, and finish it.
Also in 2020, I started to work on "project of the month", to force myself, to finish things in timely manner. This was washed by the COVID right at the beginning. I want to bring this back to life, to trigger myself.
Here I announce my January project (I really like to continue with more in February and further):
Fully working 3D printing
I've three 3D printers now. Actually only one of it working, and that one even kept in my old lab. Namely Anet A8, Geeetech i3 Pro, Anycubic Photon Mono 4k.
The goal, to have those fully working by end of January.
Those were my random thoughts for the end of 2022. I say good bye to 2022 with my current lab photos, and whish a
HAPPY NEW YEAR!





























