<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments for Hobby</title>
	<atom:link href="https://hobby.farit.ru/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://hobby.farit.ru</link>
	<description></description>
	<lastBuildDate>Fri, 27 Feb 2026 07:11:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>Comment on HML087 coding plug ROM for BMW E30 instrument cluster by Farit</title>
		<link>https://hobby.farit.ru/hml087-coder-rom-for-e30-instrument-cluster/#comment-97</link>
		<dc:creator><![CDATA[Farit]]></dc:creator>
		<pubDate>Fri, 27 Feb 2026 07:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=693#comment-97</guid>
		<description><![CDATA[I added a timing diagram that I measured using my actual coder and the latest SI board.

If the SI board sends pulses every 5.583 µs, then the frequency is 180 kHz.

My measured delay is 725 ns. When I used Attiny, delays were 2-3 µs.
]]></description>
		<content:encoded><![CDATA[<p>I added a timing diagram that I measured using my actual coder and the latest SI board.</p>
<p>If the SI board sends pulses every 5.583 µs, then the frequency is 180 kHz.</p>
<p>My measured delay is 725 ns. When I used Attiny, delays were 2-3 µs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HML087 coding plug ROM for BMW E30 instrument cluster by Aladin</title>
		<link>https://hobby.farit.ru/hml087-coder-rom-for-e30-instrument-cluster/#comment-96</link>
		<dc:creator><![CDATA[Aladin]]></dc:creator>
		<pubDate>Fri, 20 Feb 2026 14:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=693#comment-96</guid>
		<description><![CDATA[Thank you for your reply.
To summarize your answer :
ATtiny85 didn&#039;t work with the latest SI board (works only with early SI board) -&gt; delays issue ?
Ch32v003 works with the 3 latest SI board  ?

If this is the case, normally the CH32V003 should work with the early SI board also.

Do you know what is the clock frequency sent by the latest SI board to the CH32 ?]]></description>
		<content:encoded><![CDATA[<p>Thank you for your reply.<br />
To summarize your answer :<br />
ATtiny85 didn&#8217;t work with the latest SI board (works only with early SI board) -&gt; delays issue ?<br />
Ch32v003 works with the 3 latest SI board  ?</p>
<p>If this is the case, normally the CH32V003 should work with the early SI board also.</p>
<p>Do you know what is the clock frequency sent by the latest SI board to the CH32 ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HML087 coding plug ROM for BMW E30 instrument cluster by Farit</title>
		<link>https://hobby.farit.ru/hml087-coder-rom-for-e30-instrument-cluster/#comment-95</link>
		<dc:creator><![CDATA[Farit]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 21:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=693#comment-95</guid>
		<description><![CDATA[Yes, I tested it with the 3 latest SI boards that I have.
The ch32v003 is a 48 MHz microcontroller and it&#039;s pretty fast.

When I ran the code using the ATtiny85 with its 8 MHz frequency, I experienced unacceptable delays. It only worked with early SI boards.
Other people may use assembler code to make their versions work.

Though, I can&#039;t guarantee that my code will work with all SI boards.]]></description>
		<content:encoded><![CDATA[<p>Yes, I tested it with the 3 latest SI boards that I have.<br />
The ch32v003 is a 48 MHz microcontroller and it&#8217;s pretty fast.</p>
<p>When I ran the code using the ATtiny85 with its 8 MHz frequency, I experienced unacceptable delays. It only worked with early SI boards.<br />
Other people may use assembler code to make their versions work.</p>
<p>Though, I can&#8217;t guarantee that my code will work with all SI boards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HML087 coding plug ROM for BMW E30 instrument cluster by Aladin</title>
		<link>https://hobby.farit.ru/hml087-coder-rom-for-e30-instrument-cluster/#comment-94</link>
		<dc:creator><![CDATA[Aladin]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 19:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=693#comment-94</guid>
		<description><![CDATA[Hello,

Is this coding plug compatible with all e30 clusters ?
The reading frequency is not the same for all models ? (30 and 5 microseconds pereiod)]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Is this coding plug compatible with all e30 clusters ?<br />
The reading frequency is not the same for all models ? (30 and 5 microseconds pereiod)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 3D-printed BMW E30, E32, E34, E36 connector 61130007441 61130007442 by Rodney Bonello</title>
		<link>https://hobby.farit.ru/bmw-e30-connector-61130007441/#comment-93</link>
		<dc:creator><![CDATA[Rodney Bonello]]></dc:creator>
		<pubDate>Sun, 14 Dec 2025 16:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=503#comment-93</guid>
		<description><![CDATA[Thanks a lot for sharing such valuable information!!]]></description>
		<content:encoded><![CDATA[<p>Thanks a lot for sharing such valuable information!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 3D-printed BMW E30, E32, E34, E36 connector 61130007441 61130007442 by Farit</title>
		<link>https://hobby.farit.ru/bmw-e30-connector-61130007441/#comment-92</link>
		<dc:creator><![CDATA[Farit]]></dc:creator>
		<pubDate>Sat, 15 Nov 2025 01:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=503#comment-92</guid>
		<description><![CDATA[Hello,

No, I haven&#039;t done any angled terminals.
The straight ones won&#039;t fit into angled connectors.
But BMW sells straight connectors pretty cheaply, and they can usually replace angled connectors. The part numbers are in the post.

The main problem with angled connectors is finding suitable angled sockets. If you find them, share the information.
Straight sockets are available for different wire diameters from at least 2 companies.]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>No, I haven&#8217;t done any angled terminals.<br />
The straight ones won&#8217;t fit into angled connectors.<br />
But BMW sells straight connectors pretty cheaply, and they can usually replace angled connectors. The part numbers are in the post.</p>
<p>The main problem with angled connectors is finding suitable angled sockets. If you find them, share the information.<br />
Straight sockets are available for different wire diameters from at least 2 companies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 3D-printed BMW E30, E32, E34, E36 connector 61130007441 61130007442 by David Writer</title>
		<link>https://hobby.farit.ru/bmw-e30-connector-61130007441/#comment-91</link>
		<dc:creator><![CDATA[David Writer]]></dc:creator>
		<pubDate>Tue, 11 Nov 2025 21:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=503#comment-91</guid>
		<description><![CDATA[Hi My car has the 90 degree angle connectors for all the lights  and I’ve just bought new connectors but the rubber seals are all shot as well and need replacement. I wondered if you have done a CAD design for them as well or will the straight one fit.]]></description>
		<content:encoded><![CDATA[<p>Hi My car has the 90 degree angle connectors for all the lights  and I’ve just bought new connectors but the rubber seals are all shot as well and need replacement. I wondered if you have done a CAD design for them as well or will the straight one fit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Framebuffer fbtft Installation on Intel Edison for OLED Display SSD1322 by Meghan</title>
		<link>https://hobby.farit.ru/framebuffer-fbtft-installation-intel-edison-oled-display-ssd1322/#comment-90</link>
		<dc:creator><![CDATA[Meghan]]></dc:creator>
		<pubDate>Fri, 04 Jul 2025 03:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=102#comment-90</guid>
		<description><![CDATA[Hardware Setup
﻿
Confirm SPI Mode 3 (CPOL=1, CPHA=1) matches your OLED spec.
﻿
Wiring should include:
﻿
GP49 → RESET
﻿
GP15 → D/C (Data/Command)
﻿
SPI2_CLK → SCLK
﻿
SPI2_TXD → SDIN
﻿
CS0 → Chip Select
﻿
For Maclight&#039;s 2.08&quot; OLED: Verify if additional pins (e.g., VCC enable) are needed.
https://www.szmaclight.com/2-08-inch-oled-module-display-256x64-sh1122.html
﻿
Driver Configuration
﻿
Use the presslab-us/fbtft fork (SSD1322 support included).
﻿
Critical edits in fbtft_device.c:
﻿
Disable DMA (dma_enabled=false) due to Intel Edison limitations.
﻿
Customize init_display() for your panel (timings/commands may vary).
﻿
Kernel config must enable:
﻿
config
CONFIG_FB_TFT_SSD1322=m
CONFIG_FB_TFT_FBTFT_DEVICE=m
SPI Bus Conflict Resolution
﻿
Disable conflicting devices (e.g., comment out ads7955 in board.c if using SPI bus 5).
﻿
Apply patches via Yocto (linux-yocto_3.10.bbappend).
﻿
Testing
﻿
Load module:
﻿
bash
modprobe fbtft_device name=er_oled028 busnum=5
Validate with dmesg &#124; grep fb0 for successful registration.
﻿
Test display:
﻿
bash
cat /dev/urandom &gt; /dev/fb0  # Random noise test
For Maclight 2.08&quot; OLED:
﻿
Model Differences: Confirm if it uses SSD1322 (check datasheet). Adjust resolution in fbtft_platform_data if needed (e.g., 256×64 vs 128x32).
﻿
SPI Speed: Reduce max_speed_hz (e.g., 8MHz) if artifacts occur.
﻿
Backlight Control: Map an unused GPIO to led in fbtft_gpio[] if the panel has enable logic.
﻿
Debug Tips:
﻿
If module fails to load:
﻿
bash
dmesg &#124; tail -20  # Check for SPI/GPIO errors
lsmod &#124; grep fbtft  # Verify module dependencies
For blank screen: Double-check init_display() sequence against your OLED’s datasheet.
﻿
Let me know if you need help adapting this to Maclight’s specific pinout or initialization sequence!
﻿
This response is:
✅ Structured – Clear sections for hardware/software steps.
✅ Actionable – Includes commands and config snippets.
✅ Adaptable – Notes where Maclight-specific changes may apply.
✅ Concise – Avoids unnecessary technical digressions.
﻿
Would you like me to elaborate on any section?]]></description>
		<content:encoded><![CDATA[<p>Hardware Setup<br />
﻿<br />
Confirm SPI Mode 3 (CPOL=1, CPHA=1) matches your OLED spec.<br />
﻿<br />
Wiring should include:<br />
﻿<br />
GP49 → RESET<br />
﻿<br />
GP15 → D/C (Data/Command)<br />
﻿<br />
SPI2_CLK → SCLK<br />
﻿<br />
SPI2_TXD → SDIN<br />
﻿<br />
CS0 → Chip Select<br />
﻿<br />
For Maclight&#8217;s 2.08&#8243; OLED: Verify if additional pins (e.g., VCC enable) are needed.<br />
<a href="https://www.szmaclight.com/2-08-inch-oled-module-display-256x64-sh1122.html" rel="nofollow">https://www.szmaclight.com/2-08-inch-oled-module-display-256&#215;64-sh1122.html</a><br />
﻿<br />
Driver Configuration<br />
﻿<br />
Use the presslab-us/fbtft fork (SSD1322 support included).<br />
﻿<br />
Critical edits in fbtft_device.c:<br />
﻿<br />
Disable DMA (dma_enabled=false) due to Intel Edison limitations.<br />
﻿<br />
Customize init_display() for your panel (timings/commands may vary).<br />
﻿<br />
Kernel config must enable:<br />
﻿<br />
config<br />
CONFIG_FB_TFT_SSD1322=m<br />
CONFIG_FB_TFT_FBTFT_DEVICE=m<br />
SPI Bus Conflict Resolution<br />
﻿<br />
Disable conflicting devices (e.g., comment out ads7955 in board.c if using SPI bus 5).<br />
﻿<br />
Apply patches via Yocto (linux-yocto_3.10.bbappend).<br />
﻿<br />
Testing<br />
﻿<br />
Load module:<br />
﻿<br />
bash<br />
modprobe fbtft_device name=er_oled028 busnum=5<br />
Validate with dmesg | grep fb0 for successful registration.<br />
﻿<br />
Test display:<br />
﻿<br />
bash<br />
cat /dev/urandom &gt; /dev/fb0  # Random noise test<br />
For Maclight 2.08&#8243; OLED:<br />
﻿<br />
Model Differences: Confirm if it uses SSD1322 (check datasheet). Adjust resolution in fbtft_platform_data if needed (e.g., 256×64 vs 128&#215;32).<br />
﻿<br />
SPI Speed: Reduce max_speed_hz (e.g., 8MHz) if artifacts occur.<br />
﻿<br />
Backlight Control: Map an unused GPIO to led in fbtft_gpio[] if the panel has enable logic.<br />
﻿<br />
Debug Tips:<br />
﻿<br />
If module fails to load:<br />
﻿<br />
bash<br />
dmesg | tail -20  # Check for SPI/GPIO errors<br />
lsmod | grep fbtft  # Verify module dependencies<br />
For blank screen: Double-check init_display() sequence against your OLED’s datasheet.<br />
﻿<br />
Let me know if you need help adapting this to Maclight’s specific pinout or initialization sequence!<br />
﻿<br />
This response is:<br />
✅ Structured – Clear sections for hardware/software steps.<br />
✅ Actionable – Includes commands and config snippets.<br />
✅ Adaptable – Notes where Maclight-specific changes may apply.<br />
✅ Concise – Avoids unnecessary technical digressions.<br />
﻿<br />
Would you like me to elaborate on any section?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 3D-printed BMW E30, E32, E34, E36 connector 61130007441 61130007442 by Farit</title>
		<link>https://hobby.farit.ru/bmw-e30-connector-61130007441/#comment-89</link>
		<dc:creator><![CDATA[Farit]]></dc:creator>
		<pubDate>Fri, 09 May 2025 16:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=503#comment-89</guid>
		<description><![CDATA[The file is above.
https://hobby.farit.ru/wp-content/uploads/2021/05/contact.stl]]></description>
		<content:encoded><![CDATA[<p>The file is above.<br />
<a href="https://hobby.farit.ru/wp-content/uploads/2021/05/contact.stl" rel="nofollow">https://hobby.farit.ru/wp-content/uploads/2021/05/contact.stl</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 3D-printed BMW E30, E32, E34, E36 connector 61130007441 61130007442 by Sebastian</title>
		<link>https://hobby.farit.ru/bmw-e30-connector-61130007441/#comment-88</link>
		<dc:creator><![CDATA[Sebastian]]></dc:creator>
		<pubDate>Sun, 04 May 2025 23:16:35 +0000</pubDate>
		<guid isPermaLink="false">http://hobby.farit.ru/?p=503#comment-88</guid>
		<description><![CDATA[Hey,
That&#039;s great one, its really hard to get them now.
Do you still have files by any chance?]]></description>
		<content:encoded><![CDATA[<p>Hey,<br />
That&#8217;s great one, its really hard to get them now.<br />
Do you still have files by any chance?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
