https://community.element14.com/members-area/A place for members to hang out!en-USTelligent Community 12https://community.element14.com/members-area/f/forum/56961/top-tech-voices-podcast-s2-e6-smart-cities-urban-tech/235810Mon, 25 May 2026 14:35:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:dc64ada3-e2bc-4f9c-a906-7e7f7f07ed7abeacon_dave[quote userid="41967" url="~/members-area/f/forum/56961/top-tech-voices-podcast-s2-e6-smart-cities-urban-tech/235688"]At the time, I recall that there were quite a few interesting TV programmes about the type of stuff they were doing[/quote] This was one: The Joy of Datahttps://community.element14.com/members-area/f/forum/56961/top-tech-voices-podcast-s2-e6-smart-cities-urban-tech/235809Mon, 25 May 2026 14:06:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:72f92d73-f9d9-41d4-b2da-9965abe16640beacon_daveI think that citizen trust probably has already been lost with the number of historical cases of data leaks and data being sold onto private companies without any citizen approval. Not only that, there is a problem that 'data x' may appear to be safe to openly share now but when combined with new 'data y' in the future, then it may not have been such a great idea to have shared 'data x'. Equally data processing and analytics has now become powerful enough to combine multiple large data sets and it could end up too late for the citizen to do anything about it retrospectively. Policy and governance may be reluctant to openly share data as it could start to be used against them. One example might be the condition of the road network. If citizens can openly access data that shows that the authorities had access to information about the location of a defect in the road prior to an accident or damage, then this data could potentially be used in law to support a claim of negligence resulting in compensation pay-outs. Similar with air quality monitoring if it can be shown that it was known that pollution levels regularly exceeded safe limits, then a sensor network originally for safeguarding the community then it could become a weapon in the hands of the legal system. With that being the case, then any open data may end up being filtered or manipulated (e.g. filter out peak readings or use a long term averages to round off them off), causing distrust. A lot of data is already held centralized on municipal servers and is openly made available already (if you know where to look) but it tends to be anonymized summary data rather than raw live data, and often with little information on how exactly it has been collected and processed. In some cases, I think the line has probably already been crossed. With the likes of forced roll-out of 'smart' utility meters, then data is already being collected and probably not being securely stored and may already being shared with partner companies without the knowledge of the citizen. Often there is also no clarity on what data is actually being captured, transmitted, stored, shared. Similar with the likes of data from traffic cameras. Edge processing requires trust in the person that is providing the product to ensure that the data is strictly anonymized both in normal use and can remain so even after an unexpected device security breach. Also need to consider the integrity of anonymity when multiple devices are in use and a third party has access to multiple data sets which can be cross-linked. I think the issue is perhaps that the technology is developing at a far faster rate than the policy required to protect the citizen being exposed to it.https://community.element14.com/members-area/f/forum/56973/introduction/235808Mon, 25 May 2026 13:55:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:18a727d7-e4ff-4de3-ace5-796ce5bfb867battlecoderWelcome!https://community.element14.com/members-area/f/forum/56884/top-tech-voices-podcast-s2-e5-work-tech-life-balance/235807Mon, 25 May 2026 12:03:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:0f6e2bf4-9a8f-46cc-8ddc-8136218fe07cDipeshkachhi​@fyaocn This deeply aligns with your systematic approach to engineering documentation. Around the 21-minute mark, the podcast explores balancing 'internal data' (cognitive fatigue) with 'external data' (system logs). For a complex engineering pipeline, tracking this friction is critical. If our development environments don't account for human cognitive bottlenecks, the entire project timeline suffers. Do you think managing this 'tech overwhelm' requires building better, minimalist software IDEs, or is it strictly an individual discipline issue?https://community.element14.com/members-area/f/forum/56884/top-tech-voices-podcast-s2-e5-work-tech-life-balance/235806Mon, 25 May 2026 12:02:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:ae41c99c-e71a-48eb-8671-f301ef4c8796Dipeshkachhi​@jelektro Your points on workflow efficiency really connect with Dr. Le Cunff’s segment on 'Tiny Experiments' (11:00). In hardware development, we never deploy an entire unverified system architecture at once—we isolate variables on a breadboard and run incremental tests. Applying that exact modular prototyping mindset to our daily cognitive habits is a great framework. It makes you wonder: why haven't we built more dedicated, physical desk widgets with tactile e-ink displays strictly to log these workflow iterations without needing to open a distracting PC monitor?https://community.element14.com/members-area/f/forum/56961/top-tech-voices-podcast-s2-e6-smart-cities-urban-tech/235805Mon, 25 May 2026 11:53:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:42046084-bff3-4a8a-b882-ca854816bea8Dipeshkachhi@kmikemoo Exactly! I really liked the segment around 21:30 where they discussed 'Technology vs. Community.' If a smart city is just a sterile, top-down surveillance matrix built by big corporations, it loses its soul. The real magic happens when open data empowers independent makers and community developers to build hyper-localized hardware tools—like a custom neighborhood air quality monitor or transit tracker—tailored directly to their own streets. It keeps the community at the center of the tech.https://community.element14.com/members-area/f/forum/56961/top-tech-voices-podcast-s2-e6-smart-cities-urban-tech/235804Mon, 25 May 2026 11:52:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:6e62953d-0820-4940-bf24-c96f78a53304Dipeshkachhi​@beacon_dave You've hit on the core dilemma Carlo brought up around the 13-minute mark regarding privacy and trust. When we move tracking from the digital space to physical urban infrastructure, the stakes skyrocket. From a hardware perspective, do you think the solution to building that citizen trust relies on moving entirely toward decentralized, local Edge processing where data is strictly anonymized at the sensor node before hitting any municipal servers, or is it fundamentally a policy and governance problem that hardware can't fix?https://community.element14.com/members-area/f/forum/56959/are-you-using-ai/235803Mon, 25 May 2026 11:41:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:92051096-f719-4183-b69d-ee82088b20e9WorkshopshedI am using AI for work (writing software). I've found quite a lot of variability in the models with Claude series working best for my platform C# .Net / React / K8s. Have seen some subtle bugs slip in and have had moments where I felt I was fighting rather than colaborating. Typically take an iterative approach rather than leaving it to its own devices. Some interesting discoveries/approaches have been seen so it has proven useful as a learning tool. On the whole, software has been written and quality/productivity has not suffered.https://community.element14.com/members-area/f/forum/56973/introduction/235802Mon, 25 May 2026 11:15:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:793d1e4a-0272-4092-a5ef-5cc7712d493eDipeshkachhiThanks i will check it outhttps://community.element14.com/members-area/support/f/forum/56964/was-there-a-problem-with-my-image/235800Mon, 25 May 2026 04:04:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:97211440-a86f-4e82-ad6c-76f1194d3e10embeddedguyDudley Thanks. sure.! It's fine.https://community.element14.com/members-area/f/forum/56973/introduction/235796Sun, 24 May 2026 19:24:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:42511dd5-2506-4c3f-85d1-dde04f589577colporteurThere's been a few post on SPI and IC2. Clem did a setup How Far Can I2C Go? -- Episode 666 to see how far I2C can travel.https://community.element14.com/members-area/personalblogs/b/michael-kellett-s-blog/posts/two-pre-amplifiers-and-a-power-amplifierSun, 24 May 2026 15:01:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:945341cd-3352-4b7a-aa4c-b84d618ff657michaelkellettshabaz has been working on a Simple DCR (Direct Conversion Receiver) and an intercom which both need pre-amplifiers and small power amplifiers. To keep within the spirit of the original DCR project he wants to use discrete component designs with no ICs. I made some suggestions about the design of the audio sub components and when Shabaz had some board made he was kind enough to send not just some boards but most of the components to fit on them. You can read about the project here: https://community.element14.com/technologies/open-source-hardware/b/blog/posts/simple-dcr-direct-conversion-receiver-part-2-common-emitter-amplifier?CommentId=0f0868bb-7391-4262-9d02-b9f24ed4e146 This blog is about building the two pre-amp designs and the power amplifier and testing them. The plan is that these amplifiers shall work from a 9V battery or a DC power source and I have taken that to mean that they must work well with 8-9V and to some extent with 6 - 10V. The kit of parts that Shabaz sent to me: The three amplifier boards The K1 Pre-amp The K1 pre-amp is based on the original in the DCR project. It's a very simple design but has low gain and quite high distortion. I measured it using the HP654A Test Oscillator which I have had for some time. It's a nice LF oscillator with good amplitude flatness and a 99dB range output attenuator with an additional +/- 1dB fine control of the oscillator output amplitude. The huge attenuator range is great for measuring amplifiers. The downside of the 654A is its rather high distortion (approx 1% at 1kHz and worse above 1MHz). One day I might replace some of its insides (but not until all the magic smoke of the original parts is used up). You can still find the service manual on the web. I measured the amplifier outputs with the B&K 2426 auto-ranging voltmeter. It's a recent acquisition from an auction and cost about £55. It needed a little attention to its switch contacts but is working nicely now. The other tool used was the Picscope 6424E which I Road Tested some time ago. It's been replaced as my everyday scope by the R&S MXO4 but Pico keep poking me about their Picoscope7 software and I thought I should give it an outing. The picture actually shows the K2 pre-amp but the tests set up was mostly the same. (I do wish that people wouldn't deface beautiful instruments with silly calibration stickers - this one is so well stuck that I think removing it will bring the lettering off too.) The K1 Pre_Amplifier circuit I built the pre_amplifier exactly as shown on the ciruit diagram and it worked almost as intended except that the low frequency -3dB cut off was at 475Hz. This was because C4 is too small. The AC impedance of the emitter circuit is set by R4 in series with C4 (R5 impedance should be a lot higher at operating frequencies than C4 impedance so we can ignore it.) There are three separate RC combinations that set the low frequency cut off of this circuit (C1:R1//R2, C4:R4, C2: load resistance). The cut off frequency of a series RC network is 1 / 2.pi.R.C and if all three are in play we should set each to cut off at about 1/2 of the required lower operating frequency, which is about 200Hz. So the ideal value for C4 = 1/(2.pi.100.47) = 33uF. I used 47uF. On the same basis C1 should be 65nF and C2 should be 80nF (with a 20k load as fitted to the power amplifier). The load resistance might be a lot lower than 20k and the 4.7uF cap for C2 will be OK with a load of less than 1k. Changing C4 to 47uF changed the LF cut off to 196Hz, which is a little higher than I expected but not enough to worry about. Later on I changed C1 to 220nF and the LF cutoff moved to 68Hz. The K1 pre-amp has a measured gain of 27.6dB. For detailed performance of both pre-amps see the "Pre-amps performance data " section below. K1 pre-amp Distortion I used the Picoscope to measure the distortion. The K1 distortion is so bad that the HP654A was quite good enough as the signal generator. All measurements were made at 1kHz with an 8V supply. Distortion performance of K1 pre-amp 1V p-p output Distortion performance of K1 pre-amp 2V p-p output The distortion performance is pretty grim - 24.36dB is about 6%. The K2 Pre-amp The K2 pre-amp is based on the DC coupled pair pre-amp design which was popular in the mid 1970s fin HiFi magnetic pickup pre-amplifiers (eg Quad 33, Lustraphone LP100). This design has an emitter follower buffer on the output to enable it to drive low impedance loads while operating from quite a low supply voltage. The K2 design is a near clone of the LP100 but works with a 6 - 10V supply rather than 30V. The K2 pre-amp works much better than the K1 - much higher gain and much lower distortion - the price paid is that the supply working range is less good - it won't work at all with a 4V supply and barely works with 5V. It might be possible to optimise the DC biasing to improve this. The HP signal generator is not anywhere near good enough to measure the distortion of the K2 pre-amp so I used a Neutrik A1 Audio Tester as the signal generator. It can measure distortion as well but I stuck with the Picoscope for a more direct comparison with the K1. Neutrik A1 Audio Tester, 1kHz distortion approx 0.004%.(-88dB) K1 pre-amp distortion 2.35Vp-p out, 1kHz, 8V supply = -65.6dB = 0.05% Pre-amps Performance Data Pre-amps - summary The K2 pre-amp uses a few more parts but massively out-performs the K1 in all respects other than low voltage working. If that's a problem the design could be tweaked a little to optimise the DC bias of the K2 for a different voltage range. The K1 Power Amplifier In Simple DCR: Assembling a 7 MHz (40m) Direct Conversion Radio Receiver – Part 1 Shabaz explains his problems with the simple transformer coupled power amp in the original DCR design. He could only get about 830mV pk-pk into an 8R load which is a about 10mW. A transformer-less design should be able to manage about 6V p- p with an 8V supply which is about 560mW into 8R. My first attempt was a simple 4 transistor design based on a very old (1969) Mullard book. I couldn't get it to work on strip board although it looked OK in simulation. I decided to start again with a design which is the basis of almost every HiFi amplifier made in the 1970s and 80s. Long tailed pair input, single inverting amplifier and level shifter with current source load and emitter follower type output. The K1 power amplifier In HiFi applications the output transistors were often darlingtons or other multi-transistor composites and the load was frequently DC coupled, requiring the use of dual +/- power supplies. Once I had built the amplifier on Shabaz's board it sort of worked but not at all well. My strip board version worked fine. I wasted quite a lot of time trying to work out the problem during which I had lots of issues with the Picoscope triggering badly. Eventually I gave up on it and switched to the R&S MSO4 and found the issue in about 2 minutes (scope warm up time + 10 seconds) - the amplifier was oscillating at about 100MHz which caused lots of distortion and excess current drain - and of course was the reason for the bad triggering on the Picoscope. I checked it again and realised that I had, at some time earlier, engaged a digital lows pass filter at 20kHz on Picscope Channel 1 - this rendered the 100MHz oscillation invisible but the Picoscope doesn't have a big pre-digital filter overload margin which is why the signals looked clean but distorted. (To be fair the Pico was flashing up an overload warning which I hadn't noticed - so don't take any of this as a Picoscope fault - it was just me not being used to the PicoScope7 software.) The solution to the oscillation was a 120pF capacitor between Q3 base and emitter. Amps with this basic topology very often need a cap here and I should have put it on the design with a zero value. I can only assume that my strip board version had enough stray capacity in the right place. Once this was resolved I was able to do some measuring. The distortion of the power amplifier is a bit too low to be measured on a scope so I used the Neutrik A1 to measure distortion but an HP8904A signal generator because it has much easier level adjustment and it hadn't had an outing for a while. It has a nice new blue display because the old grey one had almost no contrast any more. HP8904A signal generator with replacement LCD display With an 8V supply the best output power I could get just before clipping was about 1.357V into 8R = 230mW I was able to improve this a little by replacing the output capacitor with a rather large low ESR type. A quick glance at the ciruit shows that R1 and R2, are going to waste a lot of power, but if they are reduced there will be excessive quiescent current though Q2 and Q4. My solution was to short out one of the diodes (D2) and short out R1 and R2. The distortion at 1V RMS out (8V supply 1kHz) was 0.09% and after D2 was shorted rose to 0.19%. The modification actually reduces the total amplifier quiescent current from 10mA to 6mA. But now the amplifier can manage 430mW with an 8V supply at 0.5% distortion or 585mW with a 9V supply. The distortion added by shorting one of the diodes is crossover distortion because there is a small period where one output transistor turns off but the other hasn't turned on. You can see this on a scope if you look hard: single diode X over distortion same signal and same cursors to put the crossover step into scale approx 1V RMS output with spectrum K1 Power amp summary The K1 power amplifier works very well once the 120pF capacitor has been added. The amplifier power output can be significantly increased (and Iq decreased) by removing D2 and R1 and R2 (by shorting them out)). The power output at 8V is about 1.1dB less than the target when the modifications have been made (3.8dB without). The distortion (modded or not) is very low, < 0.2% at 125mW output.audioanalog_electronicshifihttps://community.element14.com/members-area/f/forum/56914/we-have-made-changes-to-the-element14-community-homepage/235785Sat, 23 May 2026 17:11:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:b05e17a9-6f6e-4937-af44-deba2f6b6759beacon_dave[quote userid="17018" url="~/members-area/f/forum/56914/we-have-made-changes-to-the-element14-community-homepage/235784"]I'm estimating 14 years for my next level, based on past performance[/quote] It feels as if it's getting harder to collect points now. It would perhaps be interesting to see a graph showing the points accumulated at level changes & each year of participation, against the dates, to see how past participation performance has varied over the years.https://community.element14.com/members-area/f/forum/56914/we-have-made-changes-to-the-element14-community-homepage/235784Sat, 23 May 2026 16:28:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:d875d5bc-9f5c-423b-b13e-3d711ee2da68Jan Cumps[quote userid="35177" url="~/members-area/f/forum/56914/we-have-made-changes-to-the-element14-community-homepage/235610"]I stopped looking at my points and how many I needed for the next level, a long time ago because they were moving so slowly. [/quote] I'm estimating 14 years for my next level, based on past performancehttps://community.element14.com/members-area/f/forum/56959/are-you-using-ai/235775Sat, 23 May 2026 08:13:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:53aff794-e55e-46f8-8887-6f0967ee2ae8acdc90in the past when working on a old domestic device if its audio there is usually someone that has a manual. if its industrial if the owner doesnt have a manual, then sit down and nut out how it works then check sensors or relays and if boards have capacitors that have dried up then if any moving cables that could have broken. After that make a flow chart of eventshttps://community.element14.com/members-area/f/forum/56944/what-is-your-favorite-road-test-on-element14/235773Sat, 23 May 2026 07:45:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:0cb609fb-c7a3-424f-9fde-d7364a3a3361dougwI did both a series of blogs and summarized them in a road test.