![\"\"](\"./human-focused-mdns-browser-concept.png\")
Proposal for an open, decentralized social credit system for publishing and consuming reputation, boycott, and recommendation data about organizations, political groups, companies, and products.
\nAnyone can publish a static reputation file; anyone can build a client.
\nUsers choose which sources they trust, with no central server, no mandatory account, and no enforced ideology.
\nThere is already boycott apps and voting recommendation website, in addition to even more centralised or state wide concept of a 'social credit system' but they are often closed source and are fixed to a specific ideology.
\nUnlike these previous approach, this proposed system has:
\nWhat we should create is a standard for interchange of reputation, so that apps or web browser extension for voting recommendations and boycotting can be done as part of a federated social credit ecosystem.
\nIf possible I would like to see an open standard defined for publishing boycott and reputation data as simple static files, and an open-source Android app or web browser extension that reads them. NGOs, researchers, unions, or individuals can host their own lists. Users choose who to trust and compare sources side-by-side.
\nSo for this feed if I'm making a first stab, I'll like to see:
\nWhere in json it might look like:
\n{\n \"feed\": {\n \"id\": \"example.mixed.feed\",\n \"name\": \"Example Mixed Reputation Feed\",\n \"license\": \"CC-BY-4.0\",\n \"updated_at\": \"2026-01-01\"\n },\n \"entities\": [\n {\n \"entity_id\": \"company_example_corp\",\n \"type\": \"company\",\n \"name\": \"Example Corporation\"\n },\n {\n \"entity_id\": \"party_example_green\",\n \"type\": \"political_party\",\n \"name\": \"Example Green Party\",\n \"country\": \"DE\"\n }\n ],\n \"products\": [\n {\n \"barcode\": \"4006381333931\",\n \"name\": \"Example Chocolate Bar\",\n \"entity_id\": \"company_example_corp\"\n }\n ],\n \"claims\": [\n {\n \"entity_id\": \"company_example_corp\",\n \"type\": \"company\",\n \"status\": \"boycott\",\n \"score\": -80,\n \"reason\": \"Labor violations\",\n \"source_url\": \"https://example.org/report\"\n },\n {\n \"entity_id\": \"party_example_green\",\n \"type\": \"political_party\",\n \"status\": \"recommended\",\n \"score\": 75,\n \"reason\": \"Strong environmental platform\",\n \"source_url\": \"https://example.org/platform\"\n }\n ]\n}In recfiles it might look like below (more friendly for git diffs):
\n# Feed metadata\n%rec: feed\n\nid: example.mixed.feed\nname: Example Mixed Reputation Feed\nlicense: CC-BY-4.0\nupdated_at: 2026-01-01\n\n\n# Entities\n%rec: entity\n\nentity_id: company_example_corp\ntype: company\nname: Example Corporation\n\nentity_id: party_example_green\ntype: political_party\nname: Example Green Party\ncountry: DE\n\n\n# Products\n%rec: product\n\nbarcode: 4006381333931\nname: Example Chocolate Bar\nentity_id: company_example_corp\n\n\n# Claims\n%rec: claim\n\nentity_id: company_example_corp\nstatus: boycott\nscore: -80\nreason: Labor violations\n\nentity_id: party_example_green\nstatus: recommended\nscore: 75\nreason: Environmental platformAbove was ran though a recfix rep.recfile command to double check that it is valid.
In SQLlite maybe it will look internally like below. Where the idea is that it's a faster way to partially look up a database without having to download the whole feed (e.g. via http range select) e.g. sqlite3vfshttp:
\nCREATE TABLE entities (\n entity_id TEXT PRIMARY KEY,\n type TEXT,\n name TEXT,\n country TEXT\n);\n\nCREATE TABLE products (\n barcode TEXT PRIMARY KEY,\n name TEXT,\n entity_id TEXT REFERENCES entities(entity_id)\n);\n\nCREATE TABLE claims (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n entity_id TEXT REFERENCES entities(entity_id),\n status TEXT,\n score INTEGER,\n reason TEXT,\n source_url TEXT\n);Anyway I hope this sketch will provide enough detail for building a federated style reputation sharing mechanism of social credits.
\nIdeally we will get to the point where even individuals can their their scoring list with other friends directly to bypass the issue of organizations getting compromised as well (e.g. legal bans on boycott or reputation scoring organisation)
\nSome extra considerations
\nWe would include trusted entities as well which has no positive/negative claims against it, which would help disambiguate potential website or products.
\nWe got an entity ID, but how do we canonically identify them in a global manner? It's possible for multiple people to identify the same organisation/company/etc... entity ID is essentially just a local key.
\nThis identifier would also be useful in example of a browser extension which may use "domain" id to detect that "example.com" url is associated with this entry.
\n\"entities\": [\n {\n \"identity\": [\n {\n \"scheme\": \"lei\",\n \"value\": \"549300JGZ5X0Y1Q1JX75\",\n \"confidence\": 1.0\n },\n {\n \"scheme\": \"company_number\",\n \"country\": \"SE\",\n \"value\": \"556703-7485\",\n \"confidence\": 0.95\n },\n {\n \"scheme\": \"wikidata\",\n \"value\": \"Q306656\",\n \"confidence\": 0.7\n },\n {\n \"scheme\": \"domain\",\n \"value\": \"example.com\",\n \"confidence\": 0.6,\n \"evidence\": [\n \"https://example.com/legal\",\n \"https://whois.example.com\"\n ]\n }\n ],\n \"entity_id\": \"company_example_corp\",\n \"type\": \"company\",\n \"name\": \"Example Corporation\"\n }\n]Note that it is an array so that we can assign levels of priority when matching IDs.
\nOne person also recommended that the standard should also encode a URI for the schema being used to define the canonicity of the entity as it would be a big concern to have misidentified entities. Unsure how that can be done, but I presume that would be via putting a correctly formatted URI into the "scheme" field.
\nThis should be decided by the user's software on their end.
\n\"trusted_feeds\": [\n { \"feed_id\": \"labor.union.se\", \"weight\": 1.0 },\n { \"feed_id\": \"random.github.user\", \"weight\": 0.3 }\n]\"effective_from\": \"2024-01-01\",\n\"review_after\": \"2026-01-01\",\n\"last_reviewed\": \"2025-06-01\"Using these timestamps clients on their side can:
\nThis is similar to OPML which is a list of feed of other feeds, but for our use case of a distributed federated trust system rather than federated news feeds.
\n{\n \"feed\": {\n \"id\": \"example.feed_index.labor\",\n \"type\": \"feed_index\",\n \"maintainer\": \"Example Labor NGO\"\n },\n \"feeds\": [\n {\n \"feed_id\": \"labor.eu.textiles\",\n \"url\": \"https://example.org/textiles.json\",\n \"topics\": [\"labor\", \"manufacturing\"],\n \"trust_hint\": 0.9\n }\n ]\n}This will be useful for clients to interchange feeds when moving between devices... or for feeds to share other feeds.
\n", "date_published": "2026-01-02T00:00:00Z" }, { "id": "/blog/2026/01/02/concept-mdns-local-search-engine/", "url": "/blog/2026/01/02/concept-mdns-local-search-engine/", "title": "concept: mdns local search engine", "content_html":"What if we can add additional metadata and records into mdns standard to make it easier to have a local 'webapp' or search engine.
\nThis is an open idea, so feel free to develop it.
\nI would like mdns to have the capability for me to create a local web search engine that can do two things targeted for human use:
\nDirectory listing of all *.local web server
Search capability of searching individual local web servers
\nWhat I'm envisioning is that we have two different standards here. So let's split this idea into two parts:
\nIf you use
\navahi-browse -a -r\nYou might see something like
\n+ en0 IPv4 MyPrinter _ipp._tcp local\n= en0 IPv4 MyPrinter _ipp._tcp local\n hostname = [myprinter.local]\n address = [192.168.1.45]\n port = 631\n txt = ["note=Office Printer"]\n+ en0 IPv4 MyNAS _smb._tcp local\n= en0 IPv4 MyNAS _smb._tcp local\n hostname = [mynas.local]\n address = [192.168.1.50]\n port = 445\n txt = ["workgroup=WORKGROUP"]\nOften you can jst type myprinter.local and it brings up the printer local web server interface.
But it really doesn't tell you much about it or why you may want to care about it (e.g. kitchen inventory web server).
\nI'm proposing that we add more record type to allow for encoding these extra information useful for a human rather than machine focused search engine. If we look at what mdns records may look like right now, see below:
\n= enp6s0 IPv6 Chromecast-lnHsPEJoDHHfvKbdGTa3BUFcp3mhZA3 _googlecast._tcp local\n hostname = [f81d4fae-7dec-11d0-a765-00a0c91e6bf6.local]\n address = [8856:2245:4553:8:43:3343:3334:2222]\n port = [8009]\n txt = ["rs=Youtube" "rr=lnHsPEJoD" "ct=lnHwedf" "nf=1" "bs=lnHsPEJoD" "st=1" "ca=lnHs" "fn=Living Room TV" "ic=/setup/icon.png" "md=Chromecast" "ve=05" "rm=lnHsPEJoDHHf" "cd=lnHsPEJoDHH\nRight now txt records are full of machine focused information... that doesn't really tell you much about it from a human perspective of where to find the 'web site' or a 'thumbnail' or 'visual logo' etc... (or if it's a light bulb... the simple commands you can trigger from a human perspective on it).
\nWe could try cramming more keywords into txt, but it's a bit packed and I would worry about smashing into something important. So maybe let's add new record type like hrd, icon, tags or something (details can be fleshed out with a proper working group). Assuming we go with those, maybe we see something like:
+ en0 IPv4 WebAppX _http._tcp local\n= en0 IPv4 WebAppX _http._tcp local\n hostname = [webappx.local]\n address = [192.168.1.101]\n port = 8080\n txt = ["version=1.4.2", "author=SmartTech Inc."]\n hrd = ["Interactive dashboard for IoT devices, shows live sensor data, supports remote control"]\n icon = ["https://webappx.local/icon.png"]\n tags = ["#IoT", "#Dashboard", "#SmartHome"]\n\n+ en0 IPv4 MusicPlayer _http._tcp local\n= en0 IPv4 MusicPlayer _http._tcp local\n hostname = [musicplayer.local]\n address = [192.168.1.102]\n port = 3000\n txt = ["version=2.0.1", "author=AudioLabs"]\n hrd = ["Stream and manage your music library from any device, create playlists, and share"]\n icon = ["https://musicplayer.local/logo.svg"]\n tags = ["#Music", "#Streaming", "#App"]\n\n+ en0 IPv4 SmartLight _http._tcp local\n= en0 IPv4 SmartLight _http._tcp local\n hostname = [smartlight.local]\n address = [192.168.1.103]\n port = 5000\n txt = ["version=0.9.8-beta", "author=BrightTech"]\n hrd = ["Control lighting with schedules and moods, supports voice commands"]\n icon = ["https://smartlight.local/light_icon.png"]\n tags = ["#SmartHome", "#Lighting", "#IoT"]\n mini_card = ["https://smartlight.local/card.html"]\n url = ["https://smartlight.local/"]\nFor a random vibe based render of this concept, below is a chatgpt rendered image of what the user may see:
\n
With this local web search system... either we figure out a custom approach where we broadcast a search string and have web servers reply with possible search entries.
\nOr we can enhance mdns records with a recommended 'search api' location. E.g.
\n+ en0 IPv4 WebAppX _http._tcp local\n= en0 IPv4 WebAppX _http._tcp local\n hostname = [webappx.local]\n address = [192.168.1.101]\n port = 8080\n txt = ["version=1.4.2", "author=SmartTech Inc."]\n hrd = ["Interactive dashboard for IoT devices, shows live sensor data, supports remote control"]\n icon = ["https://webappx.local/icon.png"]\n tags = ["#IoT", "#Dashboard", "#SmartHome"]\n search = [webappx.local?q=<SEARCH_TERM_HERE>]\nWhere it will discover search point of various webservers... and if the human request something it will ping each endpoint like webappx.local?q=<SEARCH_TERM_HERE> and receive a json/xml/whatever record of various search stuff the user may have wanted.
Not sure how one would deal with security here... as you may not want a NAS to tell on all the possible files you got, but again that's just implementation detail if this idea is explored further. Hopefully the point is taken across.
\n", "date_published": "2026-01-02T00:00:00Z" }, { "id": "/blog/2025/11/29/bash-script-for-testing-a-syn6988-voice-synth-module/", "url": "/blog/2025/11/29/bash-script-for-testing-a-syn6988-voice-synth-module/", "title": "Bash script for testing a syn6988 voice synth module", "content_html":"Got a device that can do voice synth and is controlled over serial. Would like to have a simple bash script to at least test that it's working.
\nIt's a SYN6988 and has some pretty decent voice synth capability for being an embedded module.
\nLearned the basic on controlling it via reading the source of this pill dispenser robot and created a bash script so I can quickly check if my module is working. Below script is confirmed to be working, but happy to hear other suggestions to make this test script more useful.
\nJust make sure to remember to flip the correct dip switches to set the correct baud rate.
\nAlso note that the output sound will be quite soft, you will need to amplify it to get useful signal out of it.
\n#!/bin/bash\n\n# SYN6988 basic test script\n# This will simply send a small set of commands to check that speech synth is working as well as demo various soundbank sounds within it\n\n# Adjust this to match the serial port you connected the syn6988 to\nPORT=\"/dev/ttyUSB0\"\n\nstty -F \"$PORT\" 9600 cs8 -cstopb -parenb -ixon -ixoff\nhttps://www.lcsc.com/product-detail/C2858033.html\nspeak() {\n local msg=\"$1\"\n\n # Calculate packet length = 2 + strlen(msg)\n local len=$((2 + ${#msg}))\n local len_hex\n printf -v len_hex '\\\\x%02X' \"$len\"\n\n # Build & send packet\n printf \"\\xFD\\x00${len_hex}\\x01\\x00%s\" \"$msg\" > \"$PORT\"\n echo \"Sent: \\\"$msg\\\" (len=$len)\"\n}\n\nplay_sound_prompt_range() {\n local start=$1\n local end=$2\n\n for ((i=start; i<=end; i++)); do\n printf -v padded \"%03d\" \"$i\"\n speak \"[x1]sound${padded}\"\n sleep 1\n done\n}\n\necho \"=== Sending test speech commands ===\"\n\nspeak \"[x0][t6][v5][s6][m51][g2][h2][n1] Hello World\"\nsleep 3\n\necho \"=== Sending test sound prompt commands ===\"\n# Ref: In Datasheet SYN6988-translated.pdf\n# Refer to section 12.3.1 Sound Prompt List\n\nspeak \"Now playing sound prompt beep type\"\nsleep 3\n\nplay_sound_prompt_range 101 124\n\nspeak \"Now playing sound prompt ringtone type\"\nsleep 3\n\nplay_sound_prompt_range 201 209\n\nspeak \"Now playing sound prompt alert type\"\nsleep 3\n\nplay_sound_prompt_range 301 314\n\nspeak \"Now playing sound prompt credit card success type\"\nsleep 3\n\nplay_sound_prompt_range 401 408\n\necho \"=== Done ===\"You can get it from LCSC but as of 2026-01-02 it's out of stock.
\nFor my test rig I was using:
\n![\"SYN6988](\"./SYN6988-Speech-Synth-Module.trimmed.jpg\")
| Left Header Row | \nRight Header Row | \n
|---|---|
| GND | \nVCC | \n
| GND | \nAO_P : Audio + | \n
| GND | \nAO_N : Audio - | \n
| R / B | \nRXD | \n
| RST | \nTXD | \n
| NC | \nNC | \n
| SCK | \nSSEL | \n
| MISO | \nMOSI | \n
![\"PAM8403](\"./PAM8403-Audio-Amplifier-Module.trimmed.jpg\")
USB --- [USB to Serial] --- [SYN6988] --- [PAM8403] --- (Speaker)\nI got a meshtastic device and my understanding is you can get it to output a serial data of chat log in the form of:
\n<nick0>: <chat message 0>\n<nick1>: <chat message 1>\n<nick2>: <chat message 2>\nDocumentation about the Serial Module in meshtastic
\nJust to make sure... I ran the below bash command
\nspeak "nick: Hello World"\nAnd found that it spoke nick <pause> hello world and didn't really need these [x0][t6][v5][s6][m51][g2][h2][n1] to start speaking.
This is very convenient... as I can now just plug it to the meshtastic stream output to a microcontroller acting as a glue and have it speak without needing to modify the meshtastic firmware.
\nAlternatively I can modify the meshtastic firmware to speak it directly and keep parts count lower.
\nFound out later this github project TTS by jscrane that is practically the same but on as a semi-portable text to speech library. This does look a bit chunky enough that it won't fit into the meshtastic firmware project... but it's small enough that this can sustainability be ported to various microcontrollers as a stand alone text to speech module. Which is good as the SYN6988 looks to be no longer manufactured so it will become out of stock.
\nDo follow his project in his blog as he also appeared to have ported it to ESP8266 as well!
\n", "date_published": "2025-11-29T00:00:00Z" }, { "id": "/blog/2025/10/07/screw-back-plane-openscad/", "url": "/blog/2025/10/07/screw-back-plane-openscad/", "title": "Screw Back Plane OpenSCAD", "content_html":"This allows for creating custom screw backplane that you often find in junction boxes etc... and also was researching on typical size and spacing for future custom PCB projects.
\nBased on https://www.aliexpress.com/item/1005009909495336.html, i manually measured the screw size and spacing for future custom PCB designs. Basically you want to stick to these spec:
\nTo make your life easier, here is a openscad library that let's you generate a panel with the corresponding holes.
\n// Screw Back Plane\n// Brian Khuu 2025\n// This allows for creating custom screw backplane that you often find in junction boxes etc...\n// Found out that these junction boxes typically have screw size of M2 and screw pitch of 5mm\n// At least based on https://www.aliexpress.com/item/1005009909495336.html\n\nmodule screwBackPlaneHoles(width, length, thickness=3, pitch=5, screwSize=2)\n{\n xCount = floor(width/pitch)-1;\n yCount = floor(length/pitch)-1;\n xCalcWidth = xCount * pitch + pitch/2;\n yCalcWidth = yCount * pitch + pitch/2;\n translate([-xCalcWidth/2,-yCalcWidth/2,0])\n translate([screwSize/2,screwSize/2,0])\n {\n for (xoffset = [0:1:xCount])\n for (yoffset = [0:1:yCount])\n translate([xoffset*5,yoffset*5,0])\n render()\n {\n translate([0,0,thickness+0.5]) \n cube([screwSize+1,screwSize+1,1], center = true);\n hull()\n {\n translate([0,0,thickness]) \n cube([screwSize+1,screwSize+1,0.01], center = true);\n translate([0,0,0]) \n cube([screwSize,screwSize,0.01], center = true);\n }\n translate([0,0,-0.5]) \n cube([screwSize,screwSize,1], center = true);\n }\n } \n}\n\nmodule screwBackPlane(width=67, length=117, pitch=5, screwSize=2, thickness=3)\n{\n difference()\n {\n translate([0,0,thickness/2]) \n cube([width, length, thickness], center=true);\n screwBackPlaneHoles(width=width, length=length, thickness=thickness, pitch=pitch, screwSize=screwSize);\n }\n}\n\nscrewBackPlane();Also published this to https://www.thingiverse.com/thing:7165838
\n", "date_published": "2025-10-07T00:00:00Z" }, { "id": "/blog/2025/09/28/keepteen-d5-solar-lora-dual-heltec-v3-experimentation/", "url": "/blog/2025/09/28/keepteen-d5-solar-lora-dual-heltec-v3-experimentation/", "title": "KEEPTEEN D5 Solar Lora Dual Heltec v3 Experimentation", "content_html":"Just modified a KEEPTEEN D5 Solar Lora station so that it can hold two radios to run both Meshtastic and Meshcore at the same time.
\n![](\"dual_heltec_lora32.jpg\")
\nMain insight here is:
\nBelow are the screenshot of the D5 with dual Heltec LoRa32 v3 (Loaded with meshtastic and meshcore firmware), which showed that it's draining too fast:
\n![](\"Dual-Hetec-LoRa32-v3-Graph.jpg\")
\nCompare this with dual T114 radios (Loaded with meshtastic and meshcore firmware), showing that the current draw is smaller this time:
\n![](\"Dual-T114s-Graph.jpg\")
\nThis image is of the two T114 radio placed into the D5 solar station:
\n![](\"dual_t114.jpg\")
\nBelow is the two tray holding Dual Lora32 and Dual T114
\n![](\"heltec_lora32_tray.jpg\")
\n![](\"t114_tray.jpg\")
\nJust discovered also that https://github.com/gargomoma/fakeTec_pcb after creating this and it looks like a good candidate for keeping cost low if you are willing to DIY. This is because the D5 Solar Enclosure already has it's own charger circuitry so the T114 and LoRa32 v3 is a bit overkill with the support for oled screen (skippable here) and solar charger (not really needed here as well). As long as you are up for soldering it yourself of course!
\n", "date_published": "2025-09-28T00:00:00Z" }, { "id": "/blog/2025/08/03/reversed-engineered-handle-switch-pcb-for-electrolux-ergorapido-zb3012-and-zb3004/", "url": "/blog/2025/08/03/reversed-engineered-handle-switch-pcb-for-electrolux-ergorapido-zb3012-and-zb3004/", "title": "Reversed Engineered Handle Switch PCB For Electrolux ErgoRapido ZB3012 and ZB3004", "content_html":"Was trying to figure out why a Vacuum called Electrolux ErgoRapido ZB3012 is not working.\nFound that there is a likely issue with the button controls and found that there is some replacement board in:
\nAlso found this youtube video useful https://www.youtube.com/watch?v=38R1_EWN77s
\nUsing these above clue I was able to give my best guess on the design and sketch up the schematic
\n![\"\"](\"2025-08-04_Electrolux_ErgoRapido_ZB3012.svg\")
You can open it as a pdf or dxf or download the KiCAD Schematic
\nOverall the key insight is:
\nThe button control consist of two wires, where different resistance is applied to trigger different button press.
\nCharging indicator
\nI've logged it to the schematic above regardless of if it's of use (or my reverse engineering correctness) currently as the design process is still interesting. Especially the use of resistors to indicate multiple different buttons, which is kind of what some wired mobile phone headphones are doing.
\n", "date_published": "2025-08-03T00:00:00Z" }, { "id": "/blog/2025/07/27/a-justfile-for-use-with-ptouch-print/", "url": "/blog/2025/07/27/a-justfile-for-use-with-ptouch-print/", "title": "A Justfile for use with ptouch-print", "content_html":"Found a really good guide on using ptouch-print in this github notes
\nTook a bit of time, but figure out how to get it working on PT-P710BT.
\nTo make life easier for future people to get started, here's the justfile if you have just installed. Or you could just read it directly as a quick guide.
\n# Directory where build files and artifacts are generated\nBUILD_DIR := \"build\"\n\n# Default target: build the project and install system-wide\ndefault: install\n\ndebian-dependencies:\n sudo apt-get install gettext git pkg-config libgd-dev libusb-dev libusb-1.0-0-dev\n\n# Build the project in the build directory\nbuild:\n #!/bin/bash\n set -e # Exit immediately if a command fails\n mkdir -p \n cd \n # Configure the project with Release build type and generate build files\n cmake ../ -DCMAKE_BUILD_TYPE=Release\n # Compile the project using generated build files\n make\n\n# Install the built files system-wide (requires sudo)\ninstall: build\n sudo cmake --install \n\n# Remove build artifacts to clean the workspace\nclean:\n rm -rf \n\n# Print printer info\nprinter-info:\n ptouch-print --info\n\n# Test printing simple text on one line (Dry Run)\ntest-one-line:\n ptouch-print --text 'A' --writepng test.png\n xdg-open test.png\n\n# Test printing simple text on two line (Dry Run)\ntest-two-line:\n ptouch-print --text 'A' 'B' --writepng test.png\n xdg-open test.png\n\n# Test printing simple text on one line (Dry Run)\ntest-print-one-line:\n ptouch-print --text 'A'\n\n# Test printing simple text on two line (Dry Run)\ntest-print-two-line:\n ptouch-print --text 'A' 'B'Occationally I would have a http api endpoint that I would like to access and use via a python script. However most examples online requires installing https://docs.python-requests.org/en/latest/index.html. This is certainly a good advice for more complex scripts... but for stand-alone scripts where you just want to use only builtin python features... it would fail. Below are some functions that does away with such requirements.
\nAlso note that I've added user-agent support here as some endpoints I try to use, assumes that you are trying to access it via another browser. This will not work for more locked down apis, but it shall be fine for most cases.
\nimport urllib.request\nimport json\n\ndef get_url_content(url: str) -> str:\n \"\"\"\n Retrieves the content of a given URL as a string.\n Args:\n url (str): The URL to retrieve content from.\n Returns:\n str: The content of the response.\n \"\"\"\n try:\n headers = {\n 'User-Agent': 'Mozilla/5.0'\n }\n request = urllib.request.Request(url, headers=headers)\n response = urllib.request.urlopen(request)\n if not response.getcode() == 200:\n raise Exception(f\"Failed to retrieve content. Status code: {response.getcode()}\")\n return response.read().decode('utf-8')\n except urllib.error.HTTPError as e:\n print(f\"HTTP Error: {e}\")\n return None\n except Exception as e:\n print(f\"An error occurred: {e}\")\n return None\n\ndef get_url_json_api(url: str) -> dict:\n \"\"\"\n Retrieves JSON content from a given URL.\n Args:\n url (str): The URL to retrieve JSON content from.\n Returns:\n dict: The parsed JSON content.\n \"\"\"\n received_content = get_url_content(url)\n if not received_content:\n return None\n try:\n return json.loads(received_content)\n except json.JSONDecodeError as e:\n print(f\"Failed to parse JSON. Error: {e}\")\n return NoneWhen creating a build of materials from ITEM, I was hoping for a way to easily get the latest specs and other basic product information from it.\nThis shows how I figured it out.
\nFirst I was browsing the page https://www.item24.com/en-au/0002633 which autoresolved to https://www.item24.com/en-au/profile-8-40x40-light-natural-2633 on the browser.
\nI then checked the source of the page and found this interesting section:
\n <body class=\"font-item dark:bg-item-grey-90 text-item-grey-60 bg-white dark:text-white\" id=\"top\">\n <div style=\"display: contents\">...\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/object-aggregation/objects/en?exclude-helper-geometries=true&product=2633&visible-only=true&limit=1&country=AU&availability=available&availability=soon&availability=discontinued&availability=temp-not-available\">{\"status\":200,\"statusText\":\"OK\", ........ }</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/object-aggregation/parameters/en?id=4v0.4&id=398v0.2&id=1v1.1&id=494v2.9&id=2v1.2&id=29v0.2&id=589v0.2&id=5v2.9&id=37v1.2&id=24v2.9&id=63v0.2&id=68v0.1&id=69v0.1&id=10v0.0\">{\"status\":200,\"statusText\":\"OK\", .... }</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/product-data/products/2633?lang=en\">{\"status\":200,\"statusText\":\"OK\", ....... }</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/object-aggregation/categories/223e008e-a679-485a-a33e-b628bfa7839d/en/paths/objects/7\">{\"status\":200,\"statusText\":\"OK\", ...... }</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/product-data/specifications?id=BAUREIHE_BR8&id=ESD_1&id=KZ_REACH_J&id=KZ_ROHS_J&lang=en\">{\"status\":200,\"statusText\":\"OK\",\"headers\":{\"content-type\":\"application/json; charset=utf-8\"},\"body\":\"[{\\\"id\\\":\\\"BAU ...... batteries, etc.\\\"}]\"}</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/product-data/products?id=2601&id=62716&id=42709&country=AU&availability=available&availability=soon&availability=discontinued&availability=temp-not-available&lang=en&fields=id%2Ctitle%2Cattributes%2Cmedia%2FpreviewImage%2Cslug&limit=3&offset=0\">{\"status\":200,\"statusText\":\"OK\", ........... }</script>\n\t\t\t<script type=\"application/json\" data-sveltekit-fetched data-url=\"https://api.item24.com/product-data/attributes?id=ANTISTATIK&id=ANZAHL_GRUNDMENGE&id=ANZAHL_STUECK&id=AVAILABLEINSEARCH&id=BAUREIHE&id=BAUREIHE_STATISTIK&id=BAUSYMBLEISTE&id=BIEGUNGSRECHNER&id=CADBOX&id=CANBEUSEDFORENGINEERING&id=DIRECTLYORDERABLE&id=EINHEIT&id=ESD&id=FLAECHE&id=FL_MOMENT_TOR&id=FL_MOMENT_X&id=FL_MOMENT_Y&id=GEW_SPEZ_L_KG%2FM&id=HD_ART_AKTIV_KZ&id=HD_ART_KZ&id=HD_ART_RABATT_KZ&id=INHALTSEINHEIT&id=KD_ART_RABATT_KZ&id=KZ_BASISARTIKEL&id=KZ_MASTERARTIKEL&id=KZ_REACH&id=KZ_ROHS&id=KZ_VERFUEGBARKEIT&id=LIEFEREINHEIT&id=LIEFEREINHEIT_AX&id=MATERIAL&id=MAXLAENGE_MM&id=MINLAENGE_MM&id=NUTAUSZUG&id=ORDER_UNIT_TYPE&id=PL_SORTIMENT&id=POSITIONSRABATT&id=PRODUKTFARBE&id=PRODUKTGRUPPE&id=PROFILBAUART&id=REVERSE_CHARGE&id=SELECTOR&id=SELECTOR&id=SYSTEM&id=VORSTELLDATUM&id=WARENGRUPPE&id=WI_MOMENT_X&id=WI_MOMENT_Y&id=ZOLLTARIFNUMMER&id=ZUSCHLAGART&lang=en\">{\"status\":200,\"statusText\":\"OK\", ..... }</script>\n\t\t\t<script>\n ... some sort of page logic here ...\n\t\t\t</script>\n\t\t</div>\n </body>There was this url https://api.item24.com/product-data/products/2633
\nWhen accessed I get this output:
\n{\n \"id\": \"2633\",\n \"formattedId\": \"0.0.026.33\",\n \"title\": {\n \"de\": \"Profil 8 40x40 leicht, natur\",\n \"en\": \"Profile 8 40x40 light, natural\",\n \"fr\": \"Profilé 8 40x40 léger, naturel\",\n \"it\": \"Profilato 8 40x40 leggero, naturale\",\n \"pl\": \"Profil 8 40x40 lekki, kolor naturalny\",\n \"es\": \"Perfil 8 40x40 L, natural\",\n \"zh\": \"型材 8 系列 40x40 轻型，氧化银白\",\n \"cs\": \"Profil 8 40 x 40 L, přírodní odstín\"\n },\n \"lastModified\": 1748946630,\n \"keywords\": [\n {\n \"de\": \"EX-01006\",\n \"en\": \"EX-01006\",\n \"fr\": \"EX-01006\",\n \"it\": \"EX-01006\",\n \"pl\": \"EX-01006\",\n \"es\": \"EX-01006\",\n \"zh\": \"EX-01006\",\n \"cs\": \"EX-01006\"\n },\n {\n \"de\": \"EX-01076\",\n \"en\": \"EX-01076\",\n \"fr\": \"EX-01076\",\n \"it\": \"EX-01076\",\n \"pl\": \"EX-01076\",\n \"es\": \"EX-01076\",\n \"zh\": \"EX-01076\",\n \"cs\": \"EX-01076\"\n },\n {\n \"de\": \"EX-01077\",\n \"en\": \"EX-01077\",\n \"fr\": \"EX-01077\",\n \"it\": \"EX-01077\",\n \"pl\": \"EX-01077\",\n \"es\": \"EX-01077\",\n \"zh\": \"EX-01077\",\n \"cs\": \"EX-01077\"\n },\n {\n \"de\": \"item\",\n \"en\": \"item\",\n \"fr\": \"item\",\n \"it\": \"item\",\n \"pl\": \"item\",\n \"es\": \"item\",\n \"zh\": \"item\",\n \"cs\": \"item\"\n },\n {\n \"de\": \"item24\",\n \"en\": \"item24\",\n \"fr\": \"item24\",\n \"it\": \"item24\",\n \"pl\": \"item24\",\n \"es\": \"item24\",\n \"zh\": \"item24\",\n \"cs\": \"item24\"\n },\n {\n \"de\": \"ESD\",\n \"en\": \"ESD\",\n \"fr\": \"ESD\",\n \"it\": \"ESD\",\n \"pl\": \"ESD\",\n \"es\": \"ESD\",\n \"zh\": \"静电放电\",\n \"cs\": \"ESD\"\n },\n {\n \"de\": \"REACH\",\n \"en\": \"REACH\",\n \"fr\": \"REACH\",\n \"it\": \"REACH\",\n \"pl\": \"REACH\",\n \"es\": \"REACH\",\n \"zh\": \"REACH\",\n \"cs\": \"REACH\"\n },\n {\n \"de\": \"RoHS\",\n \"en\": \"RoHS\",\n \"fr\": \"RoHS\",\n \"it\": \"RoHS\",\n \"pl\": \"RoHS\",\n \"es\": \"RoHS\",\n \"zh\": \"RoHS\",\n \"cs\": \"RoHS\"\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"0.0.026.56\",\n \"en\": \"0.0.026.56\",\n \"fr\": \"0.0.026.56\",\n \"it\": \"0.0.026.56\",\n \"pl\": \"0.0.026.56\",\n \"es\": \"0.0.026.56\",\n \"zh\": \"0.0.026.56\",\n \"cs\": \"0.0.026.56\"\n },\n {\n \"de\": \"0.0.026.57\",\n \"en\": \"0.0.026.57\",\n \"fr\": \"0.0.026.57\",\n \"it\": \"0.0.026.57\",\n \"pl\": \"0.0.026.57\",\n \"es\": \"0.0.026.57\",\n \"zh\": \"0.0.026.57\",\n \"cs\": \"0.0.026.57\"\n },\n {\n \"de\": \"2656\",\n \"en\": \"2656\",\n \"fr\": \"2656\",\n \"it\": \"2656\",\n \"pl\": \"2656\",\n \"es\": \"2656\",\n \"zh\": \"2656\",\n \"cs\": \"2656\"\n },\n {\n \"de\": \"2657\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"availableInstances\": [\n \"CC\",\n \"CH\",\n \"CZ\",\n \"DE\",\n \"ES\",\n \"FR\",\n \"GB\",\n \"IT\",\n \"PL\",\n \"US\",\n \"COM\"\n ],\n \"targetGroup\": [\n \"customer\",\n \"retailer\"\n ],\n \"availability\": \"available\",\n \"directlyOrderable\": true,\n \"availableInSearch\": true,\n \"configurator\": \"none\",\n \"cadbox\": true,\n \"academy\": null,\n \"attributes\": [\n {\n \"id\": \"ANTISTATIK\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"ANZAHL_GRUNDMENGE\",\n \"value\": 1,\n \"visible\": false\n },\n {\n \"id\": \"ANZAHL_STUECK\",\n \"value\": 1,\n \"visible\": false\n },\n {\n \"id\": \"AVAILABLEINSEARCH\",\n \"value\": true,\n \"visible\": false\n },\n {\n \"id\": \"BAUREIHE\",\n \"value\": \"BR8\",\n \"visible\": true\n },\n {\n \"id\": \"BAUREIHE_STATISTIK\",\n \"value\": \"BRS8\",\n \"visible\": false\n },\n {\n \"id\": \"BAUSYMBLEISTE\",\n \"value\": \"X-X-8-X\",\n \"visible\": false\n },\n {\n \"id\": \"BIEGUNGSRECHNER\",\n \"value\": \"ALUMINIUMPROFIL\",\n \"visible\": false\n },\n {\n \"id\": \"CADBOX\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"CANBEUSEDFORENGINEERING\",\n \"value\": true,\n \"visible\": false\n },\n {\n \"id\": \"DIRECTLYORDERABLE\",\n \"value\": true,\n \"visible\": false\n },\n {\n \"id\": \"EINHEIT\",\n \"value\": \"ZUSCHNITT\",\n \"visible\": false\n },\n {\n \"id\": \"ESD\",\n \"value\": true,\n \"visible\": true\n },\n {\n \"id\": \"FLAECHE\",\n \"value\": 6.46,\n \"visible\": true\n },\n {\n \"id\": \"FL_MOMENT_TOR\",\n \"value\": 1.36,\n \"visible\": true\n },\n {\n \"id\": \"FL_MOMENT_X\",\n \"value\": 9,\n \"visible\": true\n },\n {\n \"id\": \"FL_MOMENT_Y\",\n \"value\": 9,\n \"visible\": true\n },\n {\n \"id\": \"GEW_SPEZ_L_KG/M\",\n \"value\": 1.74,\n \"visible\": true\n },\n {\n \"id\": \"HD_ART_AKTIV_KZ\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"HD_ART_KZ\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"HD_ART_RABATT_KZ\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"INHALTSEINHEIT\",\n \"value\": \"M\",\n \"visible\": false\n },\n {\n \"id\": \"KD_ART_RABATT_KZ\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"KZ_BASISARTIKEL\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"KZ_MASTERARTIKEL\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"KZ_REACH\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"KZ_ROHS\",\n \"value\": \"J\",\n \"visible\": false\n },\n {\n \"id\": \"KZ_VERFUEGBARKEIT\",\n \"value\": \"V\",\n \"visible\": false\n },\n {\n \"id\": \"LIEFEREINHEIT\",\n \"value\": \"MAX6000\",\n \"visible\": true\n },\n {\n \"id\": \"LIEFEREINHEIT_AX\",\n \"value\": \"M\",\n \"visible\": false\n },\n {\n \"id\": \"MATERIAL\",\n \"value\": \"AL_ELOX\",\n \"visible\": true\n },\n {\n \"id\": \"MAXLAENGE_MM\",\n \"value\": 6000,\n \"visible\": false\n },\n {\n \"id\": \"MINLAENGE_MM\",\n \"value\": 20,\n \"visible\": false\n },\n {\n \"id\": \"NUTAUSZUG\",\n \"value\": 2500,\n \"visible\": true\n },\n {\n \"id\": \"ORDER_UNIT_TYPE\",\n \"value\": \"CUT\",\n \"visible\": false\n },\n {\n \"id\": \"PL_SORTIMENT\",\n \"value\": \"KD-HD\",\n \"visible\": false\n },\n {\n \"id\": \"POSITIONSRABATT\",\n \"value\": \"BR8#4_AL\",\n \"visible\": false\n },\n {\n \"id\": \"PRODUKTFARBE\",\n \"value\": \"NATUR-AL\",\n \"visible\": true\n },\n {\n \"id\": \"PRODUKTGRUPPE\",\n \"value\": \"BM\",\n \"visible\": false\n },\n {\n \"id\": \"PROFILBAUART\",\n \"value\": \"LEICHT\",\n \"visible\": false\n },\n {\n \"id\": \"REVERSE_CHARGE\",\n \"value\": \"N\",\n \"visible\": false\n },\n {\n \"id\": \"SELECTOR\",\n \"value\": \"BAUR8\",\n \"visible\": false\n },\n {\n \"id\": \"SELECTOR\",\n \"value\": \"CHINA\",\n \"visible\": false\n },\n {\n \"id\": \"SYSTEM\",\n \"value\": \"MB\",\n \"visible\": false\n },\n {\n \"id\": \"VORSTELLDATUM\",\n \"value\": \"1985-07-01T00:00:00\",\n \"visible\": false\n },\n {\n \"id\": \"WARENGRUPPE\",\n \"value\": \"WG4_AL\",\n \"visible\": false\n },\n {\n \"id\": \"WI_MOMENT_X\",\n \"value\": 4.5,\n \"visible\": true\n },\n {\n \"id\": \"WI_MOMENT_Y\",\n \"value\": 4.5,\n \"visible\": true\n },\n {\n \"id\": \"ZOLLTARIFNUMMER\",\n \"value\": \"76042100\",\n \"visible\": false\n },\n {\n \"id\": \"ZUSCHLAGART\",\n \"value\": \"A\",\n \"visible\": false\n }\n ],\n \"specifications\": [\n \"BAUREIHE_BR8\",\n \"ESD_1\",\n \"KZ_REACH_J\",\n \"KZ_ROHS_J\"\n ],\n \"texts\": {\n \"description\": null,\n \"delivery\": null,\n \"descriptionShort\": {\n \"de\": \"Entdecken Sie das item Profil 8 40x40 leicht – hochwertig eloxiertes Aluminium; gewichtsreduziert. Vier offene Profilnuten 8. Jetzt item Profile 8 40x40 kaufen! \",\n \"en\": \"item Profile 8 40x40 is suitable for all kinds of fastening options. ESD-safe and approved under Directive 2002/95/EC.\",\n \"fr\": \"Le profilé item de la ligne 8 au format 40x40 convient à de nombreuses options de raccordement. Avec sécurité ESD et homologation selon 2002/95/CE.\",\n \"it\": \"Il profilato della serie 8 con dimensioni 40x40 item è indicato per diverse possibilità di collegamento. Antistatico e omologato secondo la normativa CE 2002/95/CE.\",\n \"pl\": \"Profil item serii 8 o wymiarach 40x40 nadaje się do wykorzystania w najróżniejszych połączeniach. Ochrona przed ESD i dopuszczenie do użytku według WE 2002/95/WE.\",\n \"es\": \"El perfil 8 40x40 de item es adecuado para todo tipo de opciones de fijación. Con protección ESD y aprobación de acuerdo con la Directiva 2002/95/CE.\",\n \"zh\": null,\n \"cs\": null\n },\n \"technicalNote\": null\n },\n \"features\": [],\n \"media\": {\n \"mainImage\": {\n \"keywords\": [\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Gesamtkatalog 8\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"MB8\",\n \"en\": \"MB8\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": {\n \"de\": \"<div class=\\\"gs01\\\">Die Profile 8 eignen sich für Konstruktionen aller Art.<br />Mit den Baureihen Profile 8, Profile 8 leicht und Profile 8 E kann der Materialeinsatz an die \\r\\nAufgabenstellung angepasst werden.</div>\",\n \"en\": \"<div class=\\\"gs01\\\">Profiles 8 are suitable for constructions of all kinds.<br />\\r\\nThe choice of Profiles 8, Profiles 8 light and Profiles 8 E enable the most suitable material to be selected for a given construction task.</div>\",\n \"fr\": \"<div class=\\\"gs01\\\">Les profilés 8 sont particulièrement appropriés pour les constructions de châssis, de tables, de cartérisations, etc...<br />Les différents types : économiques, légers et lourds permettent l’optimisation de chaque construction.</div>\",\n \"it\": \"<div class=\\\"gs01\\\">I profilati 8 sono adatti per realizzare strutture di ogni tipo. Con le serie Profilati 8, Profilati 8 leggeri e Profilati 8 E è possibile adeguare l’impiego di materiale alla \\r\\nspecifica problematica.</div>\",\n \"pl\": \"<div class=\\\"gs01\\\">Profile typoszeregu 8 nadają się do wszelkiego rodzaju konstrukcji.<br />Profile ciężkie, lekkie oraz ekonomiczne pozwalają na odpowiednie dostosowanie materiału do wyznaczonych zadań.</div>\",\n \"es\": \"<div class=\\\"gs01\\\">Los perfiles 8 son ideales para construcciones de todo tipo.<br />\\nLa elección de perfiles de la serie H, 8 L y 8 E, permite seleccionar el material más adecuado para cada tarea de construcción.</div>\",\n \"zh\": \"<div class=\\\"gs01\\\">铝型材 8 系列适用于所有类型的结构件。<br />铝型材 8 系列、铝型材 8 系列轻型和铝型材 8 系列经济型的选择，使其能够为既定的搭建任务选用最适合的材质。</div>\",\n \"cs\": \"<div class=\\\"gs01\\\">Profily 8 jsou vhodné pro všechny typy konstrukcí.<br />Díky konstrukčním řadám profilů 8, profilů 8 L <span class=\\\"nobreak\\\">a profilů 8 E</span> lze pomocí použitých prvků snadno splnit požadované zadání.</div>\"\n },\n \"sources\": {\n \"de\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"en\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"it\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"es\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ]\n }\n },\n \"previewImage\": {\n \"keywords\": [\n {\n \"de\": \"Previewgrafik\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Vorschau\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Vorschaugrafik\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": null,\n \"sources\": {\n \"de\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"en\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"it\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"es\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"jpg\",\n \"width\": 512,\n \"height\": 512,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP250GP_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 250,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PRE_0002633_%23SALL_%23AWEBP500GP_%23V1.webp\"\n }\n ]\n }\n },\n \"images\": [\n {\n \"keywords\": [\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Gesamtkatalog 8\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"MB8\",\n \"en\": \"MB8\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"classes\": [\n \"Hauptbild\"\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": {\n \"de\": \"<div class=\\\"gs01\\\">Die Profile 8 eignen sich für Konstruktionen aller Art.<br />Mit den Baureihen Profile 8, Profile 8 leicht und Profile 8 E kann der Materialeinsatz an die \\r\\nAufgabenstellung angepasst werden.</div>\",\n \"en\": \"<div class=\\\"gs01\\\">Profiles 8 are suitable for constructions of all kinds.<br />\\r\\nThe choice of Profiles 8, Profiles 8 light and Profiles 8 E enable the most suitable material to be selected for a given construction task.</div>\",\n \"fr\": \"<div class=\\\"gs01\\\">Les profilés 8 sont particulièrement appropriés pour les constructions de châssis, de tables, de cartérisations, etc...<br />Les différents types : économiques, légers et lourds permettent l’optimisation de chaque construction.</div>\",\n \"it\": \"<div class=\\\"gs01\\\">I profilati 8 sono adatti per realizzare strutture di ogni tipo. Con le serie Profilati 8, Profilati 8 leggeri e Profilati 8 E è possibile adeguare l’impiego di materiale alla \\r\\nspecifica problematica.</div>\",\n \"pl\": \"<div class=\\\"gs01\\\">Profile typoszeregu 8 nadają się do wszelkiego rodzaju konstrukcji.<br />Profile ciężkie, lekkie oraz ekonomiczne pozwalają na odpowiednie dostosowanie materiału do wyznaczonych zadań.</div>\",\n \"es\": \"<div class=\\\"gs01\\\">Los perfiles 8 son ideales para construcciones de todo tipo.<br />\\nLa elección de perfiles de la serie H, 8 L y 8 E, permite seleccionar el material más adecuado para cada tarea de construcción.</div>\",\n \"zh\": \"<div class=\\\"gs01\\\">铝型材 8 系列适用于所有类型的结构件。<br />铝型材 8 系列、铝型材 8 系列轻型和铝型材 8 系列经济型的选择，使其能够为既定的搭建任务选用最适合的材质。</div>\",\n \"cs\": \"<div class=\\\"gs01\\\">Profily 8 jsou vhodné pro všechny typy konstrukcí.<br />Díky konstrukčním řadám profilů 8, profilů 8 L <span class=\\\"nobreak\\\">a profilů 8 E</span> lze pomocí použitých prvků snadno splnit požadované zadání.</div>\"\n },\n \"sources\": {\n \"de\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"en\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"it\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"es\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AINO_%23V3.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP2000_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP500_%23V3.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_PRD_PRF_8-0270c4_%23SALL_%23AWEBP250_%23V3.webp\"\n }\n ]\n }\n },\n {\n \"keywords\": [\n {\n \"de\": \"uneloxiert\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nut 8\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"Neuheiten 2023 I\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"2023/ I\",\n \"en\": \"2023/ I\",\n \"fr\": \"2023/ I\",\n \"it\": \"2023/ I\",\n \"pl\": \"2023/ I\",\n \"es\": \"2023/ I\",\n \"zh\": \"2023/ I\",\n \"cs\": \"2023/ I\"\n }\n ],\n \"classes\": [\n \"engineeringDrawing\"\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": null,\n \"sources\": {\n \"de\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"en\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"it\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"es\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ]\n }\n },\n {\n \"keywords\": [\n {\n \"de\": \"EX-01006\",\n \"en\": \"EX-01006\",\n \"fr\": \"EX-01006\",\n \"it\": \"EX-01006\",\n \"pl\": \"EX-01006\",\n \"es\": \"EX-01006\",\n \"zh\": \"EX-01006\",\n \"cs\": \"EX-01006\"\n },\n {\n \"de\": \"EX-01076\",\n \"en\": \"EX-01076\",\n \"fr\": \"EX-01076\",\n \"it\": \"EX-01076\",\n \"pl\": \"EX-01076\",\n \"es\": \"EX-01076\",\n \"zh\": \"EX-01076\",\n \"cs\": \"EX-01076\"\n },\n {\n \"de\": \"EX-01077\",\n \"en\": \"EX-01077\",\n \"fr\": \"EX-01077\",\n \"it\": \"EX-01077\",\n \"pl\": \"EX-01077\",\n \"es\": \"EX-01077\",\n \"zh\": \"EX-01077\",\n \"cs\": \"EX-01077\"\n },\n {\n \"de\": \"item\",\n \"en\": \"item\",\n \"fr\": \"item\",\n \"it\": \"item\",\n \"pl\": \"item\",\n \"es\": \"item\",\n \"zh\": \"item\",\n \"cs\": \"item\"\n },\n {\n \"de\": \"item24\",\n \"en\": \"item24\",\n \"fr\": \"item24\",\n \"it\": \"item24\",\n \"pl\": \"item24\",\n \"es\": \"item24\",\n \"zh\": \"item24\",\n \"cs\": \"item24\"\n },\n {\n \"de\": \"ESD\",\n \"en\": \"ESD\",\n \"fr\": \"ESD\",\n \"it\": \"ESD\",\n \"pl\": \"ESD\",\n \"es\": \"ESD\",\n \"zh\": \"静电放电\",\n \"cs\": \"ESD\"\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"Render\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"classes\": [\n \"header\",\n \"details\"\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": {\n \"de\": \"Das Profil 8 40x40 leicht ist ein universelles Konstruktionsprofil aus hochwertig eloxiertem Aluminium im Rastermaß der Baureihe 8.<br />Das gewichtsreduzierte Aluprofil in der item Ausführung leicht besitzt vier offene Profilnuten 8.\",\n \"en\": \"Profile 8 40x40 light is a universal construction profile made of high-quality anodized aluminium in the modular dimension of Line 8.<br />This weight-reduced aluminium profile in the light design variant from item features four open Line 8 profile grooves.\",\n \"fr\": \"Le profilé 8 40x40 léger est un profilé de construction universel en aluminium anodisé de qualité aux dimensions modulaires de la ligne 8.<br />Ce profilé alu à poids réduit en version légère d’item dispose de quatre rainures 8 ouvertes.\",\n \"it\": \"Il profilato 8 40x40 leggero è un profilato costruttivo universale in pregiato alluminio anodizzato nella misura modulare della serie 8.<br />Nella versione leggera, il profilato in alluminio dal peso ridotto presenta quattro scanalature 8 aperte.\",\n \"pl\": \"Profil 8 40x40 lekki jest wszechstronnym profilem konstrukcyjnym wykonanym z wysokiej jakości anodowanego aluminium w wymiarze rastrowym serii 8.<br />Profil aluminiowy o zredukowanej wadze w wersji lekkiej item ma cztery otwarte rowki profilowe 8.\",\n \"es\": \"El perfil 8 40x40 ligero es un perfil de construcción universal de aluminio anodizado de alta calidad en la dimensión modular de la serie 8.<br />Este perfil de aluminio de peso reducido en la variante de diseño ligero de item cuenta con cuatro ranuras de perfil de la serie 8 abiertas.\",\n \"zh\": null,\n \"cs\": null\n },\n \"sources\": {\n \"de\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"en\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"it\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"es\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2633_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ]\n }\n },\n {\n \"keywords\": [\n {\n \"de\": \"item\",\n \"en\": \"item\",\n \"fr\": \"item\",\n \"it\": \"item\",\n \"pl\": \"item\",\n \"es\": \"item\",\n \"zh\": \"item\",\n \"cs\": \"item\"\n },\n {\n \"de\": \"item24\",\n \"en\": \"item24\",\n \"fr\": \"item24\",\n \"it\": \"item24\",\n \"pl\": \"item24\",\n \"es\": \"item24\",\n \"zh\": \"item24\",\n \"cs\": \"item24\"\n },\n {\n \"de\": \"ESD\",\n \"en\": \"ESD\",\n \"fr\": \"ESD\",\n \"it\": \"ESD\",\n \"pl\": \"ESD\",\n \"es\": \"ESD\",\n \"zh\": \"静电放电\",\n \"cs\": \"ESD\"\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Schwerprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"重型材\",\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"Render\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"classes\": [\n \"header\",\n \"details\"\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": {\n \"de\": \"Profile der Baureihe 8 sind in den Ausführungen standard, leicht und Economy (E) erhältlich. Durch zusätzliche Aussparungen wiegt ein Profil 8 40x40 leicht rund 30 Prozent weniger als ein Profil 8 40x40 bei gleicher Länge. Ein Profil 8 40x40 E wiegt rund 45 Prozent weniger.<br />Passend zur Belastung müssen die Flächenträgheitsmomente gegen Durchbiegung und die maximale Nutauszugskraft des gewählten Profils beachtet werden.\",\n \"en\": \"The profiles in Line 8 are available in standard, light and economy (E) design variants. Due to additional cavities, a Profile 8 40x40 light weighs around 30 percent less than a Profile 8 40x40 in the same length. A Profile 8 40x40 E weighs approximately 45 percent less.<br />The area moments of inertia against profile deflection and the maximum groove load-bearing capacity of the selected profile must be given due consideration in respect of the loads involved.\",\n \"fr\": \"Les profilés de la ligne 8 sont disponibles dans les versions standard, léger et Economy (E). Grâce à des évidements supplémentaires, un profilé 8 40x40 léger pèse environ 30 % de moins qu’un profilé 8 40x40 de même longueur. Un profilé 8 40x40 E pèse environ 45 % de moins.<br />En fonction de la charge, il faut tenir compte des moments quadratiques contre la flexion et de la force d’extraction de rainure maximale du profilé retenu.\",\n \"it\": \"I profilati della serie 8 sono disponibili nelle versioni standard, leggera ed E (Economy). Grazie ad ulteriori accorgimenti, a parità di lunghezza, un profilato 8 40x40 leggero pesa circa il 30% in meno di un profilato 8 40x40. Un profilato 8 40x40 E pesa circa il 45% in meno.<br />A seconda del carico è necessario rispettare i momenti di inerzia superficiale contro la flessione e la forza di estrazione massima della scanalatura del profilato selezionato.\",\n \"pl\": \"Profile serii 8 dostępne są w wersji standardowej, lekkiej i Economy (E). Dodatkowe wycięcia w profilu 8 40x40 lekkim sprawiają, że profil waży ok. 30 % mniej niż profil 8 40x40 o tej samej długości. Profil 8 40x40 E waży ok. 45 % mniej.<br />W zależności od obciążenia należy pamiętać o momentach bezwładności powierzchni względem ugięcia oraz maksymalnej sile wyrywania rowka wybranego profilu.\",\n \"es\": \"Los perfiles de la serie 8 están disponibles en las variantes de diseño estándar, ligero y económico (E). Debido a las cavidades adicionales, un perfil 8 40x40 ligero pesa alrededor de un 30 % menos que un perfil 8 40x40 de la misma longitud. Un perfil 8 40x40 E pesa aproximadamente un 45 % menos.<br />Deben tenerse en cuenta los momentos de inercia de la superficie frente a la flexión del perfil y la capacidad de carga máxima de la ranura del perfil seleccionado en relación con las cargas implicadas.\",\n \"zh\": null,\n \"cs\": null\n },\n \"sources\": {\n \"de\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"en\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"it\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"es\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"jpg\",\n \"width\": 3000,\n \"height\": 2000,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AINO_%23V1.jpg\"\n },\n {\n \"type\": \"webp\",\n \"width\": 2000,\n \"height\": 1333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP2000_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 500,\n \"height\": 333,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP500_%23V1.webp\"\n },\n {\n \"type\": \"webp\",\n \"width\": 250,\n \"height\": 167,\n \"url\": \"https://cdn.item24.com/product-assets/PIC_ANW_PRD_PRF_2603-Bauarten_%23SALL_%23AWEBP250_%23V1.webp\"\n }\n ]\n }\n },\n {\n \"keywords\": [\n {\n \"de\": \"Teleskopschienen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Teleskopauszug\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Auszugsschienen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Teleskope\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Schubladen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Schubladenschienen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Überauszug\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Schwerlast\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"ESD\",\n \"en\": \"ESD\",\n \"fr\": \"ESD\",\n \"it\": \"ESD\",\n \"pl\": \"ESD\",\n \"es\": \"ESD\",\n \"zh\": \"静电放电\",\n \"cs\": \"ESD\"\n },\n {\n \"de\": \"Hilfselemente\",\n \"en\": \"Auxiliary Elements\",\n \"fr\": \"Outillages et services\",\n \"it\": \"Elementi ausiliari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"辅助元件\",\n \"cs\": null\n },\n {\n \"de\": \"Nutöffner\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluminiumprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Balken\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"begehbar \",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Decke\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Statik\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Träger\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"Neuheiten 2024\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"2024\",\n \"en\": \"2024\",\n \"fr\": \"2024\",\n \"it\": \"2024\",\n \"pl\": \"2024\",\n \"es\": \"2024\",\n \"zh\": \"2024\",\n \"cs\": \"2024\"\n },\n {\n \"de\": \"Neuheiten\",\n \"en\": \"news\",\n \"fr\": \"nouveauté\",\n \"it\": \"novità\",\n \"pl\": \"New\",\n \"es\": \"New\",\n \"zh\": \"新特征\",\n \"cs\": \"New\"\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"reinraumtauglich\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Reinraum\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"classes\": [\n \"technical\"\n ],\n \"title\": {\n \"de\": \"zulässige Nutauszugskraft\",\n \"en\": \"Permissible groove extraction force\",\n \"fr\": \"Force d’extraction de rainure admissible\",\n \"it\": \"Forza di trazione F\",\n \"pl\": \"Dopuszczalna siła wyciągająca rowka\",\n \"es\": \"Fuerza de extracción admisible de la ranura\",\n \"zh\": null,\n \"cs\": \"Přípustná síla vytažení drážky\"\n },\n \"alt\": null,\n \"text\": null,\n \"sources\": {\n \"de\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"en\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"it\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"es\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"svg\",\n \"width\": 102,\n \"height\": 157,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_FUN_PRD_PRF_Nutauszugskraft-Profil-8-leicht_%23SALL_%23AINO_%23V1.svg\"\n }\n ]\n }\n },\n {\n \"keywords\": [\n {\n \"de\": \"Gesamtkatalog 8\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"MB8\",\n \"en\": \"MB8\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n }\n ],\n \"classes\": [],\n \"title\": null,\n \"alt\": null,\n \"text\": null,\n \"sources\": {\n \"de\": [],\n \"en\": [],\n \"fr\": [],\n \"it\": [],\n \"pl\": [],\n \"es\": [],\n \"zh\": [],\n \"cs\": []\n }\n }\n ],\n \"videos\": [],\n \"playlist\": [],\n \"engineeringDrawing\": {\n \"keywords\": [\n {\n \"de\": \"uneloxiert\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Aluprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Alustangen\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝棒\",\n \"cs\": null\n },\n {\n \"de\": \"Alustrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"铝制工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Grundelemente\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"基础元件\",\n \"cs\": null\n },\n {\n \"de\": \"item Profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"item 型材\",\n \"cs\": null\n },\n {\n \"de\": \"Itemprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"item-profil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Konstruktionsprofile\",\n \"en\": \"Construction Profiles\",\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"结构型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Stangenprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质杆状型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtes Vierkantprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Leichtprofil\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"轻质型材\",\n \"cs\": null\n },\n {\n \"de\": \"Nut 8\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"Nutenprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"凹槽型材\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilrohr leicht eckig\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"略带棱角的型材管\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstange\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材棒\",\n \"cs\": null\n },\n {\n \"de\": \"Profilstrebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"型材工作面\",\n \"cs\": null\n },\n {\n \"de\": \"Präzisionsprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"精密型材\",\n \"cs\": null\n },\n {\n \"de\": \"Rastermaß\",\n \"en\": \"Modular Dimensions\",\n \"fr\": \"Dimensions modulaires\",\n \"it\": \"Misure modulari\",\n \"pl\": null,\n \"es\": null,\n \"zh\": \"光栅大小\",\n \"cs\": null\n },\n {\n \"de\": \"Strebe\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"斜撑组件\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkant-Alu-Profile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形铝型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantprofile\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方形型材\",\n \"cs\": null\n },\n {\n \"de\": \"Vierkantrohre\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": \"方管\",\n \"cs\": null\n },\n {\n \"de\": \"Neuheiten 2023 I\",\n \"en\": null,\n \"fr\": null,\n \"it\": null,\n \"pl\": null,\n \"es\": null,\n \"zh\": null,\n \"cs\": null\n },\n {\n \"de\": \"2023/ I\",\n \"en\": \"2023/ I\",\n \"fr\": \"2023/ I\",\n \"it\": \"2023/ I\",\n \"pl\": \"2023/ I\",\n \"es\": \"2023/ I\",\n \"zh\": \"2023/ I\",\n \"cs\": \"2023/ I\"\n }\n ],\n \"title\": null,\n \"alt\": null,\n \"text\": null,\n \"sources\": {\n \"de\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"en\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"fr\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"it\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"pl\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"es\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"zh\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ],\n \"cs\": [\n {\n \"type\": \"svg\",\n \"width\": 75,\n \"height\": 85,\n \"url\": \"https://cdn.item24.com/product-assets/GRA_PMA_PRF_02633-x_%23SALL_%23AINO_%23V1.svg\"\n }\n ]\n }\n }\n },\n \"variants\": [\n {\n \"productId\": \"45280\",\n \"relation\": \"MASTER\"\n },\n {\n \"productId\": \"45281\",\n \"relation\": \"MASTER\"\n }\n ],\n \"relatedProducts\": {\n \"implicit\": [\n \"2630\"\n ],\n \"assemblyElements\": [],\n \"accessoires\": [\n \"2601\",\n \"62716\",\n \"42709\"\n ],\n \"tools\": [],\n \"services\": []\n },\n \"downloads\": [\n {\n \"title\": {\n \"de\": \"Technische Daten zum Profil\",\n \"en\": \"Technical documentation\",\n \"fr\": \"Spécifications\",\n \"it\": \"Specifiche tecniche dei profilati \",\n \"pl\": \"Dane techniczne\",\n \"es\": \"Datos técnicos\",\n \"zh\": \"技术文档\",\n \"cs\": \"Technická dokumentace\"\n },\n \"type\": \"pdf\",\n \"url\": {\n \"de\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SDE_%23AIN_%23V4.pdf\",\n \"en\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SEN_%23AIN_%23V4.pdf\",\n \"fr\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SFR_%23AIN_%23V4.pdf\",\n \"it\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SIT_%23AIN_%23V4.pdf\",\n \"pl\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SPL_%23AIN_%23V4.pdf\",\n \"es\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SES_%23AIN_%23V4.pdf\",\n \"zh\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SZH_%23AIN_%23V4.pdf\",\n \"cs\": \"https://cdn.item24.com/product-assets/DOK_DATA_profil-tech-daten_%23SCS_%23AIN_%23V4.pdf\"\n }\n },\n {\n \"title\": {\n \"de\": \"Chemische Beständigkeit Aluminium\",\n \"en\": \"Chemical resistance of aluminium\",\n \"fr\": \"Résistance chimique de l’aluminium\",\n \"it\": \"Resistenza chimica dell’alluminio\",\n \"pl\": \"Chemiczna odporność aluminium\",\n \"es\": \"Chemical resistance of aluminium\",\n \"zh\": \"铝的耐化性\",\n \"cs\": \"Chemická odolnost hliníku\"\n },\n \"type\": \"pdf\",\n \"url\": {\n \"de\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SDE_%23AIN_%23V1.pdf\",\n \"en\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SEN_%23AIN_%23V1.pdf\",\n \"fr\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\",\n \"it\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\",\n \"pl\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\",\n \"es\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\",\n \"zh\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\",\n \"cs\": \"https://cdn.item24.com/product-assets/DOK_DATA_Aluminium_%23SALL_%23AIN_%23V1.pdf\"\n }\n },\n {\n \"title\": {\n \"de\": \"ESD Produkt Qualifikation\",\n \"en\": \"ESD Product Qualification\",\n \"fr\": \"ESD Product Qualification\",\n \"it\": \"ESD Product Qualification\",\n \"pl\": \"ESD Product Qualification\",\n \"es\": \"ESD Product Qualification\",\n \"zh\": \"防静电产品认证\",\n \"cs\": \"ESD kvalifikace produktů\"\n },\n \"type\": \"pdf\",\n \"url\": {\n \"de\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SDE_%23AIN_%23V1.pdf\",\n \"en\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SEN_%23AIN_%23V1.pdf\",\n \"fr\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\",\n \"it\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\",\n \"pl\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\",\n \"es\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\",\n \"zh\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\",\n \"cs\": \"https://cdn.item24.com/product-assets/DOK_ESD_2633_%23SALL_%23AIN_%23V1.pdf\"\n }\n }\n ],\n \"applications\": [],\n \"classifications\": [\n {\n \"version\": \"11.0\",\n \"system\": \"eCl@ss\",\n \"code\": \"23360101\"\n },\n {\n \"version\": \"8.0\",\n \"system\": \"eCl@ss\",\n \"code\": \"23360101\"\n },\n {\n \"version\": \"7.1\",\n \"system\": \"eCl@ss\",\n \"code\": \"23360101\"\n },\n {\n \"version\": \"6.0.1\",\n \"system\": \"eCl@ss\",\n \"code\": \"23360101\"\n },\n {\n \"version\": \"4.0\",\n \"system\": \"eCl@ss\",\n \"code\": \"35020106\"\n },\n {\n \"version\": \"7.0\",\n \"system\": \"UNSPSC\",\n \"code\": \"30102306\"\n },\n {\n \"version\": \"9.0\",\n \"system\": \"UNSPSC\",\n \"code\": \"30102306\"\n },\n {\n \"version\": \"4.1\",\n \"system\": \"eCl@ss\",\n \"code\": \"35020106\"\n },\n {\n \"version\": \"5.0\",\n \"system\": \"eCl@ss\",\n \"code\": \"35020190\"\n },\n {\n \"version\": \"5.1\",\n \"system\": \"eCl@ss\",\n \"code\": \"35020190\"\n }\n ],\n \"identicalPartsCount\": 1,\n \"orderUnits\": [\n {\n \"type\": \"CUT\",\n \"productId\": \"2633\"\n },\n {\n \"type\": \"PIECE\",\n \"productId\": \"45280\"\n },\n {\n \"type\": \"PIECE\",\n \"productId\": \"45281\"\n }\n ],\n \"slug\": {\n \"de\": \"profil-8-40x40-leicht-natur-2633\",\n \"en\": \"profile-8-40x40-light-natural-2633\",\n \"fr\": \"profile-8-40x40-leger-naturel-2633\",\n \"it\": \"profilato-8-40x40-leggero-naturale-2633\",\n \"pl\": \"profil-8-40x40-lekki-kolor-naturalny-2633\",\n \"es\": \"perfil-8-40x40-l-natural-2633\",\n \"zh\": \"xing-cai-8-xi-lie-40x40-qing-xing-yang-hua-yin-bai-2633\",\n \"cs\": \"profil-8-40-x-40-l-prirodni-odstin-2633\"\n }\n}So based on that insight, I was able to write a script to extract the bits I care about below:
\n#!/usr/bin/env python3\n# Item API Basic Product Search\nimport urllib.request # Query API\nimport json # Parsing API response\nimport os # For cache support\n\ndef get_url_content(url: str) -> str:\n\t\"\"\"\n\tRetrieves the content of a given URL as a string.\n\n\tArgs:\n\t\turl (str): The URL to retrieve content from.\n\n\tReturns:\n\t\tstr: The content of the response.\n\t\"\"\"\n\ttry:\n\t\theaders = {\n\t\t\t'User-Agent': 'Mozilla/5.0'\n\t\t}\n\t\trequest = urllib.request.Request(url, headers=headers)\n\t\tresponse = urllib.request.urlopen(request)\n\t\tif not response.getcode() == 200:\n\t\t\traise Exception(f\"Failed to retrieve content. Status code: {response.getcode()}\")\n\t\treturn response.read().decode('utf-8')\n\texcept urllib.error.HTTPError as e:\n\t\tprint(f\"HTTP Error: {e}\")\n\t\treturn None\n\texcept Exception as e:\n\t\tprint(f\"An error occurred: {e}\")\n\t\treturn None\n\ndef get_url_json_api(url: str) -> dict:\n\t\"\"\"\n\tRetrieves JSON content from a given URL.\n\n\tArgs:\n\t\turl (str): The URL to retrieve JSON content from.\n\n\tReturns:\n\t\tdict: The parsed JSON content.\n\t\"\"\"\n\treceived_content = get_url_content(url)\n\tif not received_content:\n\t\treturn None\n\ttry:\n\t\treturn json.loads(received_content)\n\texcept json.JSONDecodeError as e:\n\t\tprint(f\"Failed to parse JSON. Error: {e}\")\n\t\treturn None\n\ndef get_item_product_data(id: str, cache_dir: str = None) -> dict:\n\t# id input can accept \"0.0.448.04\" or \"0044804\" or \"44804\"\n\t# and convert to api id internal format of \"44804\"\n\tid = int(id.replace('.', ''))\n\tapi_id = str(id)\n\n\t# If cache exists, load it\n\tif cache_dir:\n\t\tcache_file = os.path.join(cache_dir, f\"{api_id}.json\")\n\t\tif os.path.exists(cache_file):\n\t\t\twith open(cache_file, 'r', encoding='utf-8') as f:\n\t\t\t\ttry:\n\t\t\t\t\tjson_content = json.load(f)\n\t\t\t\t\tif json_content.get(\"id\", None) == api_id:\n\t\t\t\t\t\treturn json_content\n\t\t\t\texcept json.JSONDecodeError:\n\t\t\t\t\tprint(f\"Warning: Cache file {cache_file} is corrupted. Refetching...\")\n\n\t# Not cached. Fetch\n\tapi_url = f\"https://api.item24.com/product-data/products/{api_id}\"\n\tjson_content = get_url_json_api(api_url)\n\n\t# Save to cache\n\tif cache_dir:\n\t\twith open(cache_file, 'w', encoding='utf-8') as f:\n\t\t\tjson.dump(json_content, f, indent=2)\n\n\treturn json_content\n\n# Call ITEM API for 0.0.026.33\njson_content = get_item_product_data(\"0.0.026.33\")\n\n# Print Interesting Data\nrow = {}\nrow[\"Part Number\"] = json_content.get(\"formattedId\")\nif \"title\" in json_content and \"en\" in json_content[\"title\"] :\n\trow[\"Title\"] = json_content[\"title\"][\"en\"]\nif \"texts\" in json_content and \"descriptionShort\" in json_content[\"texts\"] and \"en\" in json_content[\"texts\"][\"descriptionShort\"]:\n\trow[\"Description\"] = json_content[\"texts\"][\"descriptionShort\"][\"en\"]\nif \"slug\" in json_content and \"en\" in json_content[\"slug\"] :\n\trow[\"Web Link\"] = \"https://www.item24.com/en-au/\" + json_content.get(\"slug\").get(\"en\")\nprint(json.dumps(row, indent=2))\n\n\"\"\"\nExpected Output:\n{\n \"Part Number\": \"0.0.026.33\",\n \"Title\": \"Profile 8 40x40 light, natural\",\n \"Description\": \"item Profile 8 40x40 is suitable for all kinds of fastening options. ESD-safe and approved under Directive 2002/95/EC.\",\n \"Web Link\": \"https://www.item24.com/en-au/profile-8-40x40-light-natural-2633\"\n}\n\"\"\"Hope it helps! Just be mindful it may break in the future as this is likely an internal ITEM api feature only.
\n", "date_published": "2025-06-11T00:00:00Z" }, { "id": "/blog/2025/05/05/hdd-thrasher-script-to-show-off-an-exposed-mechanical-hard-drive/", "url": "/blog/2025/05/05/hdd-thrasher-script-to-show-off-an-exposed-mechanical-hard-drive/", "title": "HDD Thrasher Script to show off an exposed Mechanical Hard Drive", "content_html":"Found an old HDD that I would like to show activity for fun. Got a bash script that would help demonstrate the hard drive motion
\nA while ago, I found a an old laptop HDD and found a transparent sata to USB adapter.
\nThis would be a good demo for others to see what old tech was like before SSDs.
\nBut to best demo its motion to other people, I needed a bash script to rapidly read the hdd to show the arm of the HDD in motion.
\nThis bash script will rapidly read from random sections of the HDD.
\n#!/bin/bash\nset -euo pipefail\n\n# ---- Configuration ----\nworkdir=\"thrashtest\"\nnum_files=60 # total files\nfile_size=\"1G\" # per-file size\nblock_size=$(stat -f --format=\"%S\" .)\n\n# calculate blocks per file\nfile_bytes=$(numfmt --from=iec $file_size)\nblocks_per_file=$(( file_bytes / block_size ))\n\necho \"Creating $num_files × $file_size files in ./$workdir\"\necho \"Filesystem block size: $block_size bytes\"\necho \"→ $blocks_per_file blocks per file\"\n\nmkdir -p \"$workdir\"\ncd \"$workdir\"\n\necho \"creating $workdir ($num_files bigfiles)\"\nfor i in $(seq 1 $num_files)\ndo\n fname=\"file_${i}.bin\"\n if [ ! -f \"$fname\" ]\n then\n echo \"writing $fname\"\n dd if=/dev/zero of=\"$fname\" bs=$block_size count=$blocks_per_file status=progress\n fi\ndone\necho \"finished creating $workdir\"\n\n# ---- Thrash loop (random read or write) ----\nwhile true; do\n # pick a random file index and offset\n idx=$(( RANDOM % num_files + 1 ))\n offset=$(( RANDOM % blocks_per_file ))\n fname=\"file_${idx}.bin\"\n\n # Random Read\n dd if=\"$fname\" of=/dev/null bs=$block_size count=1 skip=$offset status=none\ndoneYou could replace the random read with below if you want to read and write as well.\nIt's slower and does't look that much different in practice so not really needed here,\nbut it might be of interest to you from an understanding perspective.
\n# choose action: 0 = read, 1 = write\naction=$(( RANDOM % 2 ))\nif [ \"$action\" -eq 0 ]; then\n echo \"[READ ] $fname @ block $offset\"\n dd if=\"$fname\" of=/dev/null bs=$block_size count=1 skip=$offset status=none\nelse\n echo \"[WRITE] $fname @ block $offset\"\n dd if=/dev/urandom of=\"$fname\" bs=$block_size count=1 seek=$offset conv=notrunc status=none\nfiAfter running it, do take note about how the arm moves around and think about how the HDD has to physically move\nthe arm to the right spot to read.
\nThis is why random access is super slow compared to SSD flash memories.
\n", "date_published": "2025-05-05T00:00:00Z" }, { "id": "/blog/2025/03/26/brother-hl-4570cdw-paper-printer-toner-reset/", "url": "/blog/2025/03/26/brother-hl-4570cdw-paper-printer-toner-reset/", "title": "Brother HL-4570CDW Paper Printer Toner Reset", "content_html":"Was trying to reset the toner of a Brother HL-4570CDW Paper Printer.\nHere's the step you can follow.
\nK.TNR-STD on the printer screen)+ or - to select the toner colour you want to reset.\n<COLOR>.TNR-<CAPACITY> options.\nWas trying to streamline the process of producing archival Blu-Ray. Created a bash script that would create a hybrid ISO9660+UDF disc image using genisoimage and dvdisaster.
\nBelow is a script for create-archive-iso.sh that you can use to read a folder like:
./2025-01-13_Projects_2020_-_2025/
And generate a hybrid iso image like
\n./2025-01-13_Projects_2020_-_2025.iso
Where the disc volume title is Projects 2020 - 2025 when this command is run:
./create_iso.sh ./2025-01-13_Projects_2020_-_2025/
In addition it will run dvdisaster -i "$DEST_IMAGE" -mRS03 -o image -c which\nwill enhance the iso with extra error correction to make the disc more resiliant\nagainst bitrot (If borked, you can still recover the image using dvdisaster).
#!/bin/bash\n#\n# Blu‑ray Hybrid Disc Image Archival Script\n#\n# Brian Khuu 2025\n#\n# This script creates a hybrid ISO image that combines UDF with ISO9660 \n# (including Rock Ridge and Joliet extensions). It uses ISO‑level 3 to allow\n# files larger than 4GB, though note that ISO‑level 3 only removes the size \n# limit—not the filename/path length limits. Rock Ridge (-R) preserves full\n# POSIX attributes (and longer names up to 255 bytes), while Joliet (-J with \n# -joliet-long) creates a secondary directory tree for Windows compatibility.\n#\n# It then augments the generated ISO with error correction data using dvdisaster.\n#\n# Usage: ./create_iso.sh <source_folder> [<destination_iso_image>]\n\n# -----------------------------------------------------------\n# Step 1: Check for required dependencies\n# -----------------------------------------------------------\nfor cmd in genisoimage dvdisaster; do\n if ! command -v \"$cmd\" &> /dev/null; then\n echo \"Error: $cmd is not installed. Please install it.\"\n exit 1\n fi\ndone\n\n# -----------------------------------------------------------\n# Step 2: Validate script arguments\n# -----------------------------------------------------------\nif [ \"$#\" -lt 1 ]; then\n echo \"Got $# args\"\n echo \"Usage: $0 <source_folder> [<destination_iso_image>]\"\n exit 1\nfi\n\n# -----------------------------------------------------------\n# Step 3: Derive Source Folder and Default Names\n# -----------------------------------------------------------\nSOURCE_FOLDER=\"$1\"\n\n# Remove trailing slash (if any) and extract just the folder name\nDEFAULT_FOLDER_NAME=${SOURCE_FOLDER%/}\nDEFAULT_FOLDER_NAME=${DEFAULT_FOLDER_NAME##*/}\n\n# Generate a default volume label based on the folder name.\n# The expected folder name format is something like:\n# 2025-01-13_Projects_2020_-_2025\n# The script strips off the date part and converts the remaining \n# text to a title-cased label (with spaces instead of underscores).\n# So the folder name example above would be interpreted as:\n# Projects 2020 - 2025\nDEST_LABEL=${DEFAULT_FOLDER_NAME#*-*-*_} #<< Exclude date to better fit into ISO9660 volume label\nDEST_LABEL=$(echo \"$DEST_LABEL\" | sed 's/[^_]\\+/\\L\\u&/g' | sed 's/_/ /g')\n\necho \"SOURCE_FOLDER = $SOURCE_FOLDER\"\necho \"DEFAULT_FOLDER_NAME = $DEFAULT_FOLDER_NAME\"\necho \"DEST_LABEL = $DEST_LABEL\"\n\n# ISO9660 has a 32-character limit for the volume label.\nMAX_VOLID_LEN=32\nif [ ${#DEST_LABEL} -gt $MAX_VOLID_LEN ]; then\n echo \"Volume label is longer than $MAX_VOLID_LEN characters; '$DEST_LABEL'. Exiting...\"\n exit 1\nfi\n\necho \"Using volume label = $DEST_LABEL\"\n\n# Get the destination ISO image filename, defaulting to <folder_name>.iso if not provided\nDEST_IMAGE=${2:-${DEFAULT_FOLDER_NAME}.iso}\necho \"DEST_IMAGE = $DEST_IMAGE\"\n\n# -----------------------------------------------------------\n# Step 4: Create the Hybrid ISO Image using genisoimage\n# -----------------------------------------------------------\necho \"Creating hybrid ISO image...\"\n\n# Breakdown of key options:\n# -udf : Include UDF support (useful for DVD/BD formats)\n# -R : Enable Rock Ridge extensions for POSIX attributes and long filenames (up to 255 bytes)\n# -J -joliet-long : Create an additional Joliet tree for Windows with extended filename support (up to 64/103 characters)\n# -allow-lowercase : Retain lowercase letters in filenames\n# -allow-multidot : Allow filenames with multiple dots\n# -allow-limited-size : Prevent issues with files larger than 4GB in hybrid ISO/UDF images.\n# -iso-level 3 : Use ISO9660 level 3 to remove the 4GB file size limit\n# -V \"$DEST_LABEL\" : Set the volume label (must be 32 characters or less)\n# -o \"$DEST_IMAGE\" : Specify the output file for the ISO image\n# \"$SOURCE_FOLDER\" : Source directory to be included in the ISO image\ngenisoimage -udf -R -J -joliet-long -allow-lowercase -allow-multidot -allow-limited-size -iso-level 3 -V \"$DEST_LABEL\" -o \"$DEST_IMAGE\" \"$SOURCE_FOLDER\"\nif [ $? -ne 0 ]; then\n echo \"Error: Failed to create ISO image with genisoimage.\"\n exit 1\nfi\n\necho \"ISO image created at $DEST_IMAGE\"\n\n# -----------------------------------------------------------\n# Step 5: Enhance the ISO Image with Error Correction using dvdisaster\n# -----------------------------------------------------------\necho \"Enhancing image with error correction using dvdisaster...\"\n\n# Breakdown of dvdisaster options:\n# -i \"$DEST_IMAGE\" : Specify the input ISO image\n# -mRS03 : Use error correction method RS03 (suitable for larger images)\n# -o image : Specify that the output should be an augmented image (i.e. the ECC data is added to the ISO)\n# -c : Create ECC (error correction) information\ndvdisaster -i \"$DEST_IMAGE\" -mRS03 -o image -c\nif [ $? -ne 0 ]; then\n echo \"Warning: Failed to add error correction.\"\nelse\n echo \"Protected ISO image created successfully.\"\nfi\n\nexit 0Initially I was aiming to create a script that would create a pure UDF iso (So can burn 4gb+ video etc...) to a bluray disc with extra protection via mkudffs and dvdisaster... however upon mounting Got 'wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.' mount error.
\nI suspect it failed because of linux kernel impocompatibility with mounting v2.60 UDF image as read/write (The kernel module only supports ready only for v2.50 and v2.60).
\nIf you got suggestions on making this work or how the kernel module can be patched/developed to enable read/write... or a method to master a v2.50 and v2.60 UDF image, do get in touch with me! In the meantime, this is what I got at least...
\n#!/bin/bash\n#\n# Blu‑ray Archival Script\n#\n# Warning: Not working... got 'wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.' mount error\n#\n# This script creates a blank UDF image sized for Blu‑ray media,\n# formats it using mkudffs, and optionally mounts it for copying files.\n# It is intended for archival to Blu‑ray only.\n#\n# Usage: ./create_bluray_udf.sh <source_folder> [<image_name>]\n\n# Check for required dependencies\nfor cmd in mkudffs dvdisaster sudo dd truncate; do\n if ! command -v \"$cmd\" &> /dev/null; then\n echo \"Error: $cmd is not installed. Please install it.\"\n exit 1\n fi\ndone\n\n# Check for correct number of arguments\nif [ \"$#\" -lt 1 ]; then\n echo \"Got $# args\"\n echo \"Usage: $0 <source_folder> [<image_name>]\"\n exit 1\nfi\n\n# Get Source Folder\nSOURCE_FOLDER=\"$1\"\n\n# Derive default folder name from the source folder\nDEFAULT_FOLDER_NAME=${SOURCE_FOLDER%/}\nDEFAULT_FOLDER_NAME=${DEFAULT_FOLDER_NAME##*/}\n\n# Generate a default disc title from the folder name\nDEST_TITLE=$(echo \"$DEFAULT_FOLDER_NAME\" | sed 's/[^_]\\+/\\L\\u&/g' | sed 's/_/ /g')\n\n# Get destination image; if not specified, default to <foldername>.udf\nDEST_IMAGE=${2:-${DEFAULT_FOLDER_NAME}.udf}\n\necho \"SOURCE_FOLDER = $SOURCE_FOLDER\"\necho \"DEFAULT_FOLDER_NAME = $DEFAULT_FOLDER_NAME\"\necho \"DEST_TITLE = $DEST_TITLE\"\necho \"DEST_IMAGE = $DEST_IMAGE\"\n\n# mkudffs settings for Blu‑ray\nMEDIA_TYPE=bdr # bdr – BD-R (Blu-ray Disc Recordable)\nUDF_REV=2.60 # Use highest supported UDF version (Blu-ray requires UDF 2.50+)\necho \"MEDIA_TYPE = $MEDIA_TYPE\"\necho \"UDF_REV = $UDF_REV\"\n\n# Calculate the size needed (in bytes) for the source folder and add 10% overhead\nRAW_SIZE=$(du -sb \"$SOURCE_FOLDER\" | cut -f1)\nOVERHEAD=$(echo \"$RAW_SIZE * 0.10\" | bc -l | cut -d. -f1)\nTOTAL_SIZE=$(echo \"$RAW_SIZE + $OVERHEAD\" | bc)\n\necho \"Source folder size: $RAW_SIZE bytes\"\necho \"Caculate 10% UDF metadata overhead: $OVERHEAD bytes\"\necho \"Allocating image size (with overhead): $TOTAL_SIZE bytes\"\n\n# Create a blank file of the calculated size\necho \"Creating blank image file...\"\ntruncate -s \"$TOTAL_SIZE\" \"$DEST_IMAGE\"\nif [ $? -ne 0 ]; then\n echo \"Error: Failed to create blank image file.\"\n exit 1\nfi\n\n# Format the blank image as a UDF filesystem using mkudffs\necho \"Formatting image as UDF...\"\nmkudffs --media-type=$MEDIA_TYPE --udfrev=$UDF_REV --label=\"$DEST_TITLE\" \"$DEST_IMAGE\"\nif [ $? -ne 0 ]; then\n echo \"Error: Failed to format the image with mkudffs.\"\n exit 1\nfi\n\n# Create a temporary mount point and mount the image\nMOUNT_POINT=$(mktemp -d) \necho \"Mounting image at $MOUNT_POINT...\"\nsudo mount -t udf -o loop,rw \"$DEST_IMAGE\" \"$MOUNT_POINT\"\nif [ $? -ne 0 ]; then\n echo \"Error: Failed to mount the image.\"\n rmdir \"$MOUNT_POINT\"\n rm \"$DEST_IMAGE\"\n exit 1\nfi\n\n# Copy the source files into the mounted image\necho \"Copying files from $SOURCE_FOLDER to the UDF image...\"\nsudo cp -a \"$SOURCE_FOLDER\"/. \"$MOUNT_POINT\"\nif [ $? -ne 0 ]; then\n echo \"Error: Failed to copy files.\"\n sudo umount \"$MOUNT_POINT\"\n rmdir \"$MOUNT_POINT\"\n exit 1\nfi\n\nsync || echo \"Warning: sync command failed\"\n\n# Unmount the image and clean up the temporary mount point\necho \"Unmounting image...\"\nsudo umount \"$MOUNT_POINT\"\nrmdir \"$MOUNT_POINT\"\necho \"UDF image created at $DEST_IMAGE\"\n\n# Optional: Enhance the image with error correction using dvdisaster\necho \"Enhancing image with error correction using dvdisaster...\"\ndvdisaster -i \"$DEST_IMAGE\" -mRS02 -n 15% -o image\nif [ $? -ne 0 ]; then\n echo \"Warning: Failed to add error correction.\"\nelse\n echo \"Protected image created successfully.\"\nfi\n\nexit 0A good comment about this problem is made by dlarge6510.\nBelow is encoded as ROT13 so you are encouraged to read his original comment unless reddit takes it down somehow due to bitrot etc...
\nHQS vf n \"qhzcfgre sver\" ba nyy gur znva bcrengvat flfgrzf.\n\nV bayl guvax vg jbexf cebcreyl ba SerrOFQ.\n\nBa jvaqbjf lbh pna'g rira sbezng n qvfp nf HQS ivn gur THV, lbh unir gb hfr gur pbzznaq yvar. Vg pna nyfb bayl or hfrq ba UQQ vs lbh cnegvgvba gur UQQ va n fcrpvsvp jnl. Jura qbvat fb, ZnpBF jvyy abg or noyr gb ernq vg.\n\nBa ZnpBF ntnva, HQS vf s*pxrq hc. Gb hfr vg ba n UQQ be synfu qevir lbh unir gb cnegvgvba gur qevir va n jnl gung znxrf vg ol qrsnhyg nyzbfg hahfnoyr ba jvaqbjf.\n\nN svyrflfgrz qrfvtarq gb nyybj vagrepunatr bs svyrf orgjrra gur znva BF pbzcrgvgbef raqf hc hanoyr gb npghnyyl qb gung. Uzz, V jbaqre jul\n\nUbjrire, Yvahk orvat gur fhcrevbe BF vg vf ertneqvat svyrflfgrzf naq cnegvgvbavat pna ernq HQS jvgu cnegvgvbaf be ab cnegvgvbaf.\n\nVs lbh Tbbtyr nebhaq lbh'yy svaq n cebwrpg ba TvgUho jurer fbzrbar jebgr n fpevcg sbe nyy guerr BF' gung jvyy sbezng n synfu qevir va n jnl gung nyy 3 BF' jvyy npghnyyl or noyr gb hfr.\n\nNabgure jnl gung HQS unf yvgrenyyl orra fynzzrq ntnvafg gur jnyy vf vg vf bayl cbffvoyr gb ercnve n HQS svyrflfgrz ba... Jvaqbjf. Arvgure Yvahk abe ZnpBF unf na sfpx.\n\nHQS nf n svyrflfgrz jnf nonaqbarq ba Jvaqbjf, Yvahk naq ZnpBF. Jvaqbjf naq ZnpBF obgu ungrq vg nf vg nyybjrq vagrepunatr bs svyrf orgjrra gurzfryirf. V zrna, ubj qner fhpu n svyrflfgrz rkvfg! Lbh arrq gb nonaqba Zvpebfbsg naq orpbzr n Znp hfre!\n\nAbobql jnagrq gb unir HQS or gur havirefny svyrflfgrz. Vg jnf orsber vg'f gvzr. Bayl ba bcgvpny zrqvn qvq vg znantr gb npuvrir nal fbeg bs npprcgnapr.\n\nBa Yvahk, HQS unf orra nonaqbarq fvzcyl orpnhfr fbzr fbq arrq gb fgrc hc naq nqq jevgr fhccbeg gb gur xreary qeviref (be znxr n SHFR qevire). Ubjrire, nf HQS vf rssrpgviryl n qrnq svyrflfgrz gung'f bayl hfrq ba bcgvpny zrqvn vg frrzf crbcyr gung pna qb fhpu n guvat fvzcyl ner abg obgurevat.\n\nV zrna, jr nyy unir urneq gur \"jub gur s*PX hfrf bcgvpny zrqvn gurfr qnlf\"? Unira'g jr.\n\nHQS unf orra eryrtngrq gb n svyrflfgrz hfr ba OQ zrqvn gb ubyq UQ zbivrf. Gung'f vg'f ubzr va 2025 naq nf n gval unaqshy bs crbcyr npebff gur cynarg jnag gb znxr ubzrznqr UQ zbivr qvfpf gurer fvzcyl vf abobql vagrerfgrq va yrggvat nalbar qb gung ba Yvahk. Gehfg zr, V ybbxrq ng guvf 10 lrnef ntb. Nyy nal BF unf gb qb, juvpu Yvahk qbrf, vf gb cebivqr ernq bayl fhccbeg sbe nyy HQS irefvbaf.\n\nVs rabhtu crbcyr jnag jevgr fhccbeg sbe HQS 2.6 gura, jurer vf gur obhagl? Jurer vf gur Xvpxfgnegre? Nabgure BF V ybir; Evfp BF Bcra, unf arj qrirybczrag qbar ol hfref sebagvat hc gur pnfu gb uver n qrirybcre gb npghnyyl jevgr gur pbqr rgp.\n\nOhg abobql frrzf gb rira jnag gb tb gung sbe HQS. Gur pbqr nyernql rkvfgf va SerrOFQ naq pna rnfvyl or cbegrq.\n\nOnfvpnyyl zngr, nf zhpu nf jr nyy jnag gb unir HQS, nf zhpu nf jr ernq nobhg gur cebzvfrf vg bssrerq gb n jbeyq bs vagragvbany vapbzcngvoyl, n jbeyq gung jnf nyernql hfvat Sng32 naq AGSF qeviref vyyrtnyyl, n jbeyq gung nonaqbarq bcgvpny zrqvn naq npprcgrq nyy gur pehq gung pnzr jvgu zbivat svyrf orgjrra flfgrzf jvgu Sng32 naq vg fvmr yvzvgf rgp fvzcyl orpnhfr gurl jnagrq gb hfr n synfu qevir.\n\nPhr gur ivbyva 🎻 HQS vf ynlvat va n qvgpu, nonaqbarq nsgre orvat orng hc ol gur gjb znva ohyyvrf. Ur jnagrq gb svanyyl oevat crbcyr gbtrgure ohg gur ohyyvrf ehyrq gur cynltebhaq naq onpx gura gurl jnagrq gb fgnzc gung fbeg bs guvat bhg.\n\nVg'f n erny pelvat funzr.\n\nOhg vg vf cbffvoyr gb znfgre n HQS 2.6 vzntr. Lbh whfg arrq gb abg zbhag vg nf n ybbconpx naq gel gb jevgr vagb vg. Ubjrire, V qrpvqrq gung V qvqa'g arrq HQS ba zl OQ-Ef nf yvxr V fnvq vfb9660 yriry 3 qbrf vg nyy jvgu Ebpxevqtr naq Wbyvrg rkgrafvbaf. V'q bayl jnag HQS sbe OQ-ER jurer V jnag gb znavchyngr svyrf. Nf gung jnf vaperqvoyl fybbbbbj, V fvzcyl punatrq zl hfr pnfr.\n\nV qb hfr gung fpevcg gb sbezng synfu qevirf nf HQS gb zbir ynetr svyrf orgjrra jvaqbjf naq Yvahk znpuvarf ng jbex.For linux if you call env you will get a sequence of bash variable like:
XDG_SESSION_DESKTOP=cinnamon\nQT_QPA_PLATFORMTHEME=qt5ct\nXDG_SESSION_TYPE=x11What if you want to parse such files in C? I written a kv_parse_value() which might help you!
It has zero dependencies, doesn't require malloc and also can handle whitespace and quoted strings.
\nTypically application is linux software, embedded systems, simple configuration store... etc...
\nIf this helps you, please do let me know!
\nAlso it's now in github at https://github.com/mofosyne/kv_parse_value.c
\nIn addition, I noticed that for very simple INI files this will be able to parse it as well!
\nYou could potentially also parse some linux program output which uses a similar form...\nbut for those kind of unstructured output it would tend to have whitespace and use : instead of =.
I have intentionally written this in a way that you can easily modify and strip it down, in case you\nare trying to run this in an embedded or restricted context.
\nXDG_SESSION_DESKTOP : cinnamon\nQT_QPA_PLATFORMTHEME : qt5ct\nXDG_SESSION_TYPE : x11XDG_SESSION_DESKTOP=\"cinnamon\"\nQT_QPA_PLATFORMTHEME=\"qt5ct\"\nXDG_SESSION_TYPE=\"x11\"KV_PARSE_WHITESPACE_SKIP):\nKV_PARSE_QUOTED_STRINGS):\n') or double (") quotes."example\\"text").= and : as key-value separators (e.g., "key=value" or "key: value").value_max - 1 characters./* Simple ANSI C KV Parser\n * 2025 Brian Khuu (This Code Is Released To The Public Domain)\n * To test this function run `cat kvparser.h | tcc -DKV_PARSER_TEST -run -` */\n#define KV_PARSE_WHITESPACE_SKIP\n#define KV_PARSE_QUOTED_STRINGS\n\n/**\n * @brief Parses a key-value pair from a given string.\n *\n * 2025 Brian Khuu https://briankhuu.com/ (This function is dedicated to Public Domain)\n * https://briankhuu.com/blog/2025/01/30/simple-key-value-text-parser-in-c/\n *\n * This function extracts the value associated with a specified key in a formatted key-value string.\n *\n * ## Supported Features:\n * - **Whitespace Skipping** (`KV_PARSE_WHITESPACE_SKIP`): Ignores spaces and tabs around keys and values.\n * - **Quoted String Support** (`KV_PARSE_QUOTED_STRINGS`): Handles values enclosed in single (`'`) or double (`\"`) quotes.\n * - **Key Delimiters**: Supports both `=` and `:` as key-value separators.\n *\n * @param str Input string containing multiple key-value pairs (e.g., \"key=value\") separated by newline.\n * @param key The key to search for in the input string.\n * @param value Output buffer to store the extracted value.\n * @param value_max Maximum length of the output buffer (`value`), including the null terminator.\n * @return The length of the extracted value (excluding the null terminator) on success, or `0` if the key is not found.\n *\n * @note If `KV_PARSE_WHITESPACE_SKIP` is defined, leading and trailing whitespace is ignored before returning the value.\n * @note If `KV_PARSE_QUOTED_STRINGS` is defined, values can be enclosed in single (`'`) or double (`\"`) quotes.\n *\n * @example Usage Example:\n * @code\n * char buffer[50];\n * unsigned int len = kv_parse_value(\"username=admin\\npassword=1234\", \"username\", buffer, sizeof(buffer));\n * if (len > 0) {\n * printf(\"Username: %s\\n\", buffer);\n * } else {\n * printf(\"Key not found.\\n\");\n * }\n * @endcode\n */\nunsigned int kv_parse_value(const char *str, const char *key, char *value, unsigned int value_max)\n{\n for (; *str != '\\0'; str++)\n {\n#ifdef KV_PARSE_WHITESPACE_SKIP\n while (*str == ' ' || *str == '\\t')\n {\n str++;\n }\n#endif\n\n /* Check For Key */\n for (int i = 0; *str != '\\0' && key[i] != '\\0'; i++, str++)\n {\n /* Key Mismatched. Skip Line */\n if (*str != key[i])\n {\n goto skip_line;\n }\n }\n\n#ifdef KV_PARSE_WHITESPACE_SKIP\n while (*str == ' ' || *str == '\\t')\n {\n str++;\n }\n#endif\n\n /* Check For Key Value Delimiter */\n if (*str != '=' && *str != ':')\n {\n goto skip_line;\n }\n str++;\n\n#ifdef KV_PARSE_WHITESPACE_SKIP\n while (*str == ' ' || *str == '\\t')\n {\n str++;\n }\n#endif\n\n /* Copy Value To Buffer */\n#ifdef KV_PARSE_QUOTED_STRINGS\n char quote = '\\0';\n#endif\n for (int i = 0; i < (value_max - 1); str++)\n {\n if (*str == '\\0' || *str == '\\r' || *str == '\\n')\n {\n /* End Of Line. Trim trailing whitespace before returning the value. */\n value[i] = '\\0';\n#ifdef KV_PARSE_WHITESPACE_SKIP\n while (i > 0 && (value[i - 1] == ' ' || value[i - 1] == '\\t'))\n {\n i--;\n value[i] = '\\0';\n }\n#endif\n return i;\n }\n#ifdef KV_PARSE_QUOTED_STRINGS\n else if (quote == '\\0' && (*str == '\\'' || *str == '\"'))\n {\n /* Start Of Quoted String */\n quote = *str;\n continue;\n }\n else if (quote != '\\0' && *(str - 1) != '\\\\' && *str == quote)\n {\n /* End Of Quoted String. Return Value */\n value[i] = '\\0';\n return i;\n }\n else if (quote != '\\0' && *(str - 1) == '\\\\' && *str == quote)\n {\n /* Escaped Quote Character In Quoted String */\n value[i - 1] = *str;\n continue;\n }\n#endif\n\n value[i++] = *str;\n }\n\n /* Value too large for buffer. Don't return a value. */\n value[0] = '\\0';\n return 0;\n\n skip_line:\n /* Search for start of next line */\n while (*str != '\\n')\n {\n if (*str == '\\0')\n {\n /* End of string. Key was not found. */\n return 0;\n }\n str++;\n }\n }\n\n /* End of string. Key was not found. */\n return 0;\n}\n\n#ifdef KV_PARSER_TEST\n#include <assert.h>\n#include <stdio.h>\n#include <string.h>\n\n// Test case function\nvoid run_tests()\n{\n char buffer[100] = {0};\n int buffer_count = 0;\n\n // **Test 1: Basic Key-Value Retrieval**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"key1=value1\\nkey2=value2\", \"key1\", buffer, sizeof(buffer));\n assert(buffer_count == 6);\n assert(strcmp(buffer, \"value1\") == 0);\n\n // **Test 2: Retrieve Last Key**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"a=b\\nc=d\\ne=f\\ng=hello\", \"g\", buffer, sizeof(buffer));\n assert(buffer_count == 5);\n assert(strcmp(buffer, \"hello\") == 0);\n\n // **Test 3: Key Not Found**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"a=b\\nc=d\", \"z\", buffer, sizeof(buffer));\n assert(buffer_count == 0);\n\n // **Test 4: Buffer Too Small**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"longkey=longvalue\", \"longkey\", buffer, sizeof(buffer));\n assert(buffer_count == 9);\n assert(strcmp(buffer, \"longvalue\") == 0);\n\n // **Test 5: Empty Input**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"\", \"anykey\", buffer, sizeof(buffer));\n assert(buffer_count == 0);\n\n // **Test 6: Input Without Key-Value Pairs**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"randomtext\\nanotherline\", \"key\", buffer, sizeof(buffer));\n assert(buffer_count == 0);\n\n // **Test 7: Handling Spaces Around Key and Value**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\" key = value \\n next = test \", \"key\", buffer, sizeof(buffer));\n#ifdef KV_PARSE_WHITESPACE_SKIP\n assert(buffer_count == 5);\n assert(strcmp(buffer, \"value\") == 0);\n#else\n assert(buffer_count == 0);\n#endif\n\n // **Test 8: Duplicate Keys (Return First Occurrence)**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"x=1\\nx=2\\nx=3\", \"x\", buffer, sizeof(buffer));\n assert(buffer_count == 1);\n assert(strcmp(buffer, \"1\") == 0);\n\n // **Test 9: Newline Variations (Windows vs. Unix)**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"a=one\\r\\nb=two\", \"b\", buffer, sizeof(buffer));\n assert(buffer_count == 3);\n assert(strcmp(buffer, \"two\") == 0);\n\n // **Test 10: Key With Special Characters**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"user-name=admin\\nuser@domain.com=me\", \"user-name\", buffer, sizeof(buffer));\n assert(buffer_count == 5);\n assert(strcmp(buffer, \"admin\") == 0);\n\n // **Test 11: Value Containing '='**\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"path=/home/user=data\", \"path\", buffer, sizeof(buffer));\n assert(buffer_count == 15);\n assert(strcmp(buffer, \"/home/user=data\") == 0);\n\n // **Test 12: Quoted String **\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"path=\\\"/home/user=data\\\"\", \"path\", buffer, sizeof(buffer));\n#ifdef KV_PARSE_QUOTED_STRINGS\n assert(buffer_count == 15);\n assert(strcmp(buffer, \"/home/user=data\") == 0);\n#else\n assert(buffer_count == 17);\n assert(strcmp(buffer, \"\\\"/home/user=data\\\"\") == 0);\n#endif\n\n // **Test 13: Uncapped Quoted String **\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"path=\\\"/home/user=data\", \"path\", buffer, sizeof(buffer));\n#ifdef KV_PARSE_QUOTED_STRINGS\n assert(buffer_count == 15);\n assert(strcmp(buffer, \"/home/user=data\") == 0);\n#else\n assert(buffer_count == 16);\n assert(strcmp(buffer, \"\\\"/home/user=data\") == 0);\n#endif\n\n // **Test 14: Quoted String With Escaped Quote **\n memset(buffer, 0, sizeof(buffer));\n buffer_count = kv_parse_value(\"path=\\\"/home/\\\\\\\"user=data\\\"\", \"path\", buffer, sizeof(buffer));\n#ifdef KV_PARSE_QUOTED_STRINGS\n assert(buffer_count == 16);\n assert(strcmp(buffer, \"/home/\\\"user=data\") == 0);\n#else\n assert(buffer_count == 19);\n assert(strcmp(buffer, \"\\\"/home/\\\\\\\"user=data\\\"\") == 0);\n#endif\n\n printf(\"kv_parse_value() passed successfully!\\n\");\n}\n\n// Run tests in main()\nint main()\n{\n run_tests();\n return 0;\n}\n#endifWhen you run the above source in tcc via cat kvparser.h | tcc -DKV_PARSER_TEST -run -
kv_parse_value() passed successfully!\nIn response to this idea for clibs C package manager Filter packages by tags and features. E.g. Is this package heapless? #322, I created this C source scanner to scan C source code and generate keyword suggestions based on the code's properties of relevance for people browsing clib package list. Such as if the source code utilize dynamic memory (malloc, free, realloc)?
The scanner works as follows:
\nComment and String Removal:
\n//), multi-line (/* ... */) comments and (' ... ') single quoted or (" ... ") double quoted string to ensure only meaningful tokens are processed.Token Scanning:
\nKeyword Detection:
\nTag Emission:
\nInput with stderr output disabled 2>&-:
tcc -run ./source_keyword_suggester.c 2>&- << HEREDOC\n#include <stdlib.h>\nint main() {\n int *ptr = malloc(100);\n free(ptr);\n goto end;\nend:\n return 0;\n}\nHEREDOCOutput:
\n["heap used", "malloc", "free", "goto used"]\nThis shows how the scanner ignores certain tokens and find certain tokens
\nInput with stdout output disabled 1>&-:
tcc -run ./source_keyword_suggester.c 1>&- << HEREDOC\n#include <stdlib.h>\nint main() {\n int *ptr = malloc(100);\n free(ptr);\n goto end;\nend:\n return 0;\n}\nHEREDOCOutput:
\ninclude\nstdlib.h\nint\nmain()\nint\nptr\nmalloc()\nfree()\nptr\ngoto\nend\nend\nreturn\n/*\n Clibs Source Scanner For Keyword Suggestion\n Author: Brian Khuu (2025)\n\n This idea is to provide a mechanism for scanning a source code and\n giving some keyword suggestions based on the properties of the\n source code. In this case, I would like to mark a source code as\n using dynamic memory or not. This won't be perfect, but it may help\n encourage library writers to use keywords if it's already provided.\n\n # MIT License\n\n Copyright (c) 2025 Brian Khuu\n\n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the \"Software\"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n\n The above copyright notice and this permission notice shall be included in all\n copies or substantial portions of the Software.\n\n THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\n SOFTWARE.\n\n */\n\n#include <stdbool.h>\n#include <stdio.h>\n#include <string.h>\n\n#define TOKEN_MAX 256\n\ntypedef struct SourceTokenScanner\n{\n int prev;\n int quote_char;\n bool in_single_line_comment;\n bool in_multi_line_comment;\n\n bool token_ready;\n bool token_is_function;\n char token[TOKEN_MAX + 1];\n size_t token_size;\n} SourceTokenScanner;\n\ntypedef struct SourceTagger\n{\n bool uses_malloc;\n bool uses_free;\n bool uses_realloc;\n bool uses_goto;\n} SourceTagger;\n\nbool sourceTokenScanner(SourceTokenScanner *context, const char ch)\n{\n if (context->token_ready)\n {\n context->token[0] = '\\0';\n context->token_size = 0;\n context->token_ready = false;\n }\n\n if (ch == '\\'' || ch == '\"' || context->quote_char)\n {\n if (context->quote_char)\n {\n if (ch == context->quote_char && context->prev != '\\\\')\n {\n context->quote_char = '\\0';\n }\n else\n {\n context->prev = ch;\n }\n }\n else\n {\n context->quote_char = ch;\n context->prev = 0;\n context->token[0] = '\\0';\n context->token_size = 0;\n }\n return false;\n }\n\n if (context->prev == '/' && ch == '/' || context->in_single_line_comment)\n {\n if (context->in_single_line_comment)\n {\n if (ch == '\\n')\n {\n context->in_single_line_comment = false;\n }\n }\n else\n {\n context->in_single_line_comment = true;\n context->token[0] = '\\0';\n context->token_size = 0;\n }\n return false;\n }\n\n if (context->prev == '/' && ch == '*' || context->in_multi_line_comment)\n {\n if (context->in_multi_line_comment)\n {\n if (context->prev == '*' && ch == '/')\n {\n context->in_multi_line_comment = false;\n context->prev = '\\0';\n }\n else\n {\n context->prev = ch;\n }\n }\n else\n {\n context->in_multi_line_comment = true;\n context->prev = 0;\n context->token[0] = '\\0';\n context->token_size = 0;\n }\n return false;\n }\n\n context->prev = ch;\n\n if (('a' <= ch && ch <= 'z') || ('A' <= ch && ch <= 'Z') || ('0' <= ch && ch <= '9') || (ch == '_') || (ch == '.'))\n {\n if (context->token_size < TOKEN_MAX)\n {\n context->token[context->token_size++] = ch;\n context->token[context->token_size] = '\\0';\n }\n return false;\n }\n\n if (context->token_size > 0)\n {\n if (context->token_size <= 2 || ('0' <= context->token[0] && context->token[0] <= '9') || (context->token[0] == '.'))\n {\n // Exclude short tokens or invalid starting characters\n // Dev Note: Shortest function name is 3 characters long (e.g. sin, cos, tan, log etc...)\n context->token[0] = '\\0';\n context->token_size = 0;\n return false;\n }\n else\n {\n // Heuristic Token Found\n context->token_is_function = (ch == '(') ? true : false;\n context->token_ready = true;\n return true;\n }\n }\n\n return false;\n}\n\nvoid add_tags(char **tags, size_t *tag_count, size_t max_tags, char *tag)\n{\n // Check if tag already added\n for (int i = 0; i < max_tags; i++)\n {\n if (tags[i] != NULL && (strcmp(tags[i], tag) == 0))\n {\n return;\n }\n }\n\n // Add tag\n if (*tag_count < max_tags)\n {\n tags[*tag_count] = tag;\n *tag_count = *tag_count + 1;\n }\n}\n\nint main()\n{\n char ch;\n SourceTokenScanner sourceTokenScannerState = {0};\n SourceTagger sourceTagger = {0};\n\n /* Scan Source For Indicator Tokens */\n while ((ch = getchar()) != EOF)\n {\n if (sourceTokenScanner(&sourceTokenScannerState, ch))\n {\n if (sourceTokenScannerState.token_is_function)\n {\n // Function\n if (strcmp(sourceTokenScannerState.token, \"malloc\") == 0)\n {\n sourceTagger.uses_malloc = true;\n }\n else if (strcmp(sourceTokenScannerState.token, \"free\") == 0)\n {\n sourceTagger.uses_free = true;\n }\n else if (strcmp(sourceTokenScannerState.token, \"realloc\") == 0)\n {\n sourceTagger.uses_realloc = true;\n }\n }\n else\n {\n if (strcmp(sourceTokenScannerState.token, \"goto\") == 0)\n {\n sourceTagger.uses_goto = true;\n }\n }\n fprintf(stderr, \"%s%s\\n\", sourceTokenScannerState.token, sourceTokenScannerState.token_is_function ? \"()\" : \"\");\n }\n }\n\n /* Generate Tag Suggestions */\n char *tags[100] = {NULL};\n size_t tag_count = 0;\n if (!sourceTagger.uses_malloc && !sourceTagger.uses_free && !sourceTagger.uses_realloc)\n {\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"no heap\");\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"heapless\");\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"no malloc\");\n }\n\n if (sourceTagger.uses_malloc)\n {\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"heap used\");\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"malloc\");\n }\n\n if (sourceTagger.uses_free)\n {\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"heap used\");\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"free\");\n }\n\n if (sourceTagger.uses_realloc)\n {\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"heap used\");\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"realloc\");\n }\n\n if (sourceTagger.uses_goto)\n {\n add_tags(tags, &tag_count, (sizeof(tags) / sizeof(tags[0])), \"goto used\");\n }\n\n /* Print Tag Suggestions */\n printf(\"[\");\n for (int i = 0; i < tag_count; i++)\n {\n if (i > 0)\n {\n printf(\", \");\n }\n printf(\"\\\"%s\\\"\", tags[i]);\n }\n printf(\"]\");\n\n return 0;\n}As an alternative to writing JSON by hand using purely printf, I written a helper header file called json_fmt.h.\nThere are other options, but I just want something quick to get going with json output, so written a series of\nC macros that I can use to make it easier to write the formatting string for a printf call.
Note that this approach is quite limited to future expansion, but is suitable for quickly getting\na json output without including other dependencies as this is only a single header file.
\nBut it would be helpful for people who stumble on this post to checkout these repos that I personally\nwould recommend checking out for C code embedded system purpose. Just note that both options do\nuse the heap while my approach does not. This might be a factor in choosing mine or the options\nbelow.
\nBut if the above is too overkill or you don't got the time and mindspace to deal with integrating it\nin... or you want to minimize dependencies. That's when you can consider below.
\nThe design rule for this micro library is to only deal with the most common json elements that is\nerror prone or annoying to manually write. So in this context, it would tend to be dealing with "\nand keeping track of the keys and values. So ultimately instead of writing
printf(\"{\\\"user\\\":%s, \\\"age\\\":%d)}\", \"marcus\", 25);You would write:
\nprintf(\"{\" JSON_FMT_STR(\"user\") \", \" JSON_FMT_INT(\"age\") \"}\", \"marcus\", 25)You still need to manually write the values to the left side, but at least you can more easily\nkeep mental note of all the types when reading the manually written json strings. As well as\nbeing sure that you have not forgotten to escape " or : somewhere.
To use this micro library, just copy these code below into a file named json_fmt.h.
/*\n json_fmt.h (2025-05-21)\n A C Micro Formatting Library for manually writing json strings using printf\n e.g. printf(\"{\"JSON_FMT_STR(\"user\")\", \"JSON_FMT_INT(\"age\")\"}\", \"marcus\", 25)\n\n # MIT License\n\n Copyright (c) 2025 Brian Khuu\n\n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the \"Software\"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n\n The above copyright notice and this permission notice shall be included in all\n copies or substantial portions of the Software.\n\n THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\n SOFTWARE.\n */\n#ifndef JSON_FMT_H\n#define JSON_FMT_H\n#define JSON_FMT_KEY(KEY) \"\\\"\" KEY \"\\\"\"\n#define JSON_FMT(KEY, FMT) JSON_FMT_KEY(KEY) \":\" FMT\n#define JSON_FMT_STR(KEY) JSON_FMT(KEY, \"\\\"%s\\\"\")\n#define JSON_FMT_INT(KEY) JSON_FMT(KEY, \"%d\")\n#define JSON_FMT_FLT(KEY) JSON_FMT(KEY, \"%lf\")\n#define JSON_FMT_VAL(KEY) JSON_FMT(KEY, \"%s\")\n#define JSON_VAL_LIT(STR) \"\\\"\" STR \"\\\"\" ///< Note that STR must be json escaped \n#define JSON_VAL_STR \"\\\"%s\\\"\" ///< Note that %s must be json escaped \n#define JSON_VAL_TRUE \"true\"\n#define JSON_VAL_FALSE \"false\"\n#define JSON_VAL_NULL \"null\"\n#define JSON_VAL_BOOL(VAL) (VAL ? JSON_VAL_TRUE : JSON_VAL_FALSE)\nstatic inline char *json_fmt_escaped_string(char *buffer, const unsigned long buffer_size, const char *str)\n{\n // This escapes string for safe inclusion in json string (Ref: https://www.json.org/img/string.png)\n char esc_char[] = {'\\\"', '\\\\', '/', '\\b', '\\f', '\\n', '\\r', '\\t'};\n char alt_char[] = {'\"', '\\\\', '/', 'b', 'f', 'n', 'r', 't'};\n int char_count = 0;\n for (; *str && (char_count < buffer_size - 3); str++)\n {\n const char ch = *str;\n for (int i = 0; i < (sizeof(esc_char) / sizeof(esc_char[0])); i++)\n {\n if (ch == esc_char[i])\n {\n buffer[char_count++] = '\\\\';\n buffer[char_count++] = alt_char[i];\n goto escaped_character_applied;\n }\n }\n buffer[char_count++] = ch;\n\n escaped_character_applied:\n continue;\n }\n buffer[char_count] = '\\0';\n return buffer;\n}\n#endifFor example of how you can use this in your project, have a look at this example json_fmt_demo.c
#include <stdio.h>\n#include \"json_fmt.h\"\nint main()\n{\n char buffer[200];\n printf(\"Escaped String 1: \\\"%s\\\"\\n\", json_fmt_escaped_string(buffer, sizeof(buffer), \"Hello \\\"World\\\"!\"));\n printf(\"Escaped String 2: \\\"%s\\\"\\n\", json_fmt_escaped_string(buffer, sizeof(buffer), \"This is a line\\n And a newline\\n\\tplus tabs\"));\n printf(\"Escaped String 3: \\\"%s\\\"\\n\", json_fmt_escaped_string(buffer, sizeof(buffer), \"Backslash \\\\ and forward slash /\"));\n\n printf(\"Formatted JSON (String): {\" JSON_FMT_STR(\"name\") \"}\\n\", \"Alice\");\n printf(\"Formatted JSON (Integer): {\" JSON_FMT_INT(\"age\") \"}\\n\", 30);\n printf(\"Formatted JSON (Float): {\" JSON_FMT_FLT(\"height\") \"}\\n\", 5.9);\n printf(\"Formatted JSON (Bool=true): {\" JSON_FMT_VAL(\"ready\") \"}\\n\", JSON_VAL_BOOL(1));\n printf(\"Formatted JSON (Bool=false): {\" JSON_FMT_VAL(\"ready\") \"}\\n\", JSON_VAL_BOOL(0));\n printf(\"Formatted JSON (null): {\" JSON_FMT_VAL(\"ready\") \"}\\n\", JSON_VAL_NULL);\n\n printf(\"Combined JSON: {\" JSON_FMT_STR(\"user\") \", \" JSON_FMT_INT(\"age\") \"}\\n\", \"marcus\", 25);\n return 0;\n}When compiled using tcc -run json_fmt_demo.c you will get this output:
Escaped String 1: "Hello \\"World\\"!"\nEscaped String 2: "This is a line\\n And a newline\\n\\tplus tabs"\nEscaped String 3: "Backslash \\\\ and forward slash \\/"\nFormatted JSON (String): {"name":"Alice"}\nFormatted JSON (Integer): {"age":30}\nFormatted JSON (Float): {"height":5.900000}\nFormatted JSON (Bool=true): {"ready":true}\nFormatted JSON (Bool=false): {"ready":false}\nFormatted JSON (null): {"ready":null}\nCombined JSON: {"user":"marcus", "age":25}\nKey thing to note, is that I've also included a small function named json_fmt_escaped_string().\nThis is because while you can manually and easily sanitize integers and floats. It's much harder\nto manually sanitize each string.
Just note that you will need to have a separate buffer for each call to json_fmt_escaped_string()\nto the same printf. An example which illustrate this point is shown below
\n#include <stdio.h>\n#include \"json_fmt.h\"\nint main() {\n char buffer1[200];\n char buffer2[200];\n\n printf(\"Double Escaped String (Incorrect Usage): [ \\\"%s\\\", \\\"%s\\\" ]\\n\",\n json_fmt_escaped_string(buffer1, sizeof(buffer1), \"Bye \\\"World\\\"!\"),\n json_fmt_escaped_string(buffer1, sizeof(buffer1), \"Hello \\\"World\\\"!\"));\n\n printf(\"Double Escaped String (Correct Usage): [ \\\"%s\\\", \\\"%s\\\" ]\\n\",\n json_fmt_escaped_string(buffer1, sizeof(buffer1), \"Bye \\\"World\\\"!\"),\n json_fmt_escaped_string(buffer2, sizeof(buffer2), \"Hello \\\"World\\\"!\"));\n\n return 0;\n}Which will output this result:
\nDouble Escaped String (Incorrect Usage): [ "Hello \\"World\\"!", "Hello \\"World\\"!" ]\nDouble Escaped String (Correct Usage): [ "Bye \\"World\\"!", "Hello \\"World\\"!" ]\nAnyway hope this will be useful for you! Especially if you have a deadline!\nJust remember to revisit and update your code to use a proper json library\nwhen you get the time and space to do so!
\n", "date_published": "2025-01-22T00:00:00Z" }, { "id": "/blog/2025/01/10/minimal-multipart-form-data-parser-in-c/", "url": "/blog/2025/01/10/minimal-multipart-form-data-parser-in-c/", "title": "Minimal Multipart/Form-Data Parser in C", "content_html":"Created a C library for dealing with multipart form handling. It's very minimal but is going to be useful when I need to\ndeal with embedded systems occasionally with lack of memory or requirement to reduce complexity.
\nTo give it a shot head to https://github.com/mofosyne/minimal-multipart-form-data-parser-c
\nThe interface will be quite simple, like below
\nint c;\nstatic MinimalMultipartParserContext state = {0};\nwhile ((c = getc(stdin)) != EOF)\n{\n // Processor handles incoming stream character by character\n const MultipartParserEvent event = minimal_multipart_parser_process(&state, (char)c);\n\n // Handle Special Events\n if (event == MultipartParserEvent_DataBufferAvailable)\n {\n // Data Available To Receive\n for (unsigned int j = 0; j < minimal_multipart_parser_get_data_size(&state); j++)\n {\n const char rx = minimal_multipart_parser_get_data_buffer(&state)[j];\n // Output received data\n putc(rx, stdout);\n }\n }\n else if (event == MultipartParserEvent_DataStreamCompleted)\n {\n // Data Stream Finished\n break;\n }\n}\n\n// Check if file has been received\nif (minimal_multipart_parser_is_file_received(&state))\n{\n // File Received Successfully\n}\nelse\n{\n // File Reception Failed\n}But I think what would be more interesting to other readers here is other alternatives to consider\nif they want to solve this issue of multipart form data extraction.
\nDid a bit of research and these are what I found:
\nContent-Type from the response head yourself to get the boundary\n\\r\\n--BOUNDARY\\r\\n is the boundary which is a safe assumption to makefrancoiscolas/multipart-parser
\nContent-Type from the response head yourself to get the boundary\n\\r\\n--BOUNDARY\\r\\n is the boundary which is a safe assumption to makeThis is a digikey api v4 script that is focused only on just the flow needed to get product information.\n(FYI I'm running this script in a ubuntu linux context, so it has not been tested on windows or mac)
\nRecommend Reading:
\nDesign Principle: This script is written to be self contained besides requests and for each callout function to be composable, bu lacks much of more advance oauth implementation like token caching.
\nAlso this is restricted to sandboxed api at the moment... however this is okay as this was done as a learning exercise in addition to being for one-off internal projects.
\nOther Similar Code:
\nAnyway uploaded this script to gist https://gist.github.com/mofosyne/e15bb122024ff97ecc707dac68ab92b5 and to this page so people can use this if needed to solve their problems. If you do, then let me know that it helped you!
\nAlso by the way, I attempted to exclude the authorisation token because the https://developer.digikey.com/products/product-information-v4/productsearch/keywordsearch?prod=false page for the keyword search didn't have a red required flag next to it... but it turns out you still do need it in addition to the X-DIGIKEY-Client-Id which is extremely annoying... but it is what it is. Its working at least for me. Just don't forget to load in your client ID and secret to the bash enviroment.
#!/usr/bin/env python3\n\n# digikey_api_v4_product_search.py\n# Digikey Basic Product Search Script (Targeting Digikey API v4)\n# By Brian Khuu 2024\n\n# This is a digikey api v4 script that is focused only on just the flow needed to get product information.\n# Recommend Reading:\n# - https://developer.digikey.com/documentation\n# - Section \"OAuth 20: 2 Legged Flow\" has good information on basic authnetic\n\n# Design Principle: This script is written to be self contained besides requests and for each callout function to be composable\n# This lacks much of more advance oauth implementation like token caching.\n# Also this is restricted to sandboxed api at the moment...\n# However this is okay as this was done as a learning exercise in addition to being for one-off internal projects.\n\n# Other Similar Code:\n# - https://github.com/alvarop/dkbc/blob/master/dkbc/dkbc.py\n# - Just found this while coding this up which was very helpful in figuring out what I was missing\n\nimport os\nimport json\nimport requests\n\nDIGIKEY_CLIENT_ID=os.getenv(\"DIGIKEY_CLIENT_ID\")\nDIGIKEY_CLIENT_SECRET=os.getenv(\"DIGIKEY_CLIENT_SECRET\")\n\nDIGIKEY_AUTH_URL_V4 = 'https://sandbox-api.digikey.com/v1/oauth2/authorize'\nDIGIKEY_TOKEN_URL_V4 = 'https://sandbox-api.digikey.com/v1/oauth2/token'\nDIGIKEY_PRODUCT_SEARCH_URL_V4 = 'https://sandbox-api.digikey.com/products/v4/search/keyword'\n\n# Sanity Check That Authorisation Details Was Provided\nif not DIGIKEY_CLIENT_ID or not DIGIKEY_CLIENT_SECRET:\n print(\"Missing client id or secret\")\n quit()\n\ndef oauthV2_get_simple_access_token(url, client_id, client_secret):\n # Get the simple access token required for 2 Legged Authorization OAutV2.0 flow\n # This is typically used for basic search and retreival of publically avaliable information\n response = requests.post(\n url,\n data={\n \"client_id\": client_id,\n \"client_secret\": client_secret,\n \"grant_type\": \"client_credentials\",\n }\n )\n return response.json()\n\ndef oauthv2_product_search(url, client_id, token, keyword):\n # Dev Note: Why did I not just place the data?\n # https://stackoverflow.com/questions/15737434/python-requests-module-urlencoding-json-data\n data_payload = {\n \"Keywords\": str(keyword),\n }\n response = requests.post(\n url,\n headers = { \n \"X-DIGIKEY-Client-Id\": client_id,\n \"authorization\": \"Bearer {access_token}\".format(access_token=token.get(\"access_token\")),\n \"content-type\": \"application/json\",\n \"accept\": \"application/json\",\n },\n data = json.dumps(data_payload)\n )\n return response.json()\n\noauth_token = oauthV2_get_simple_access_token(DIGIKEY_TOKEN_URL_V4, DIGIKEY_CLIENT_ID, DIGIKEY_CLIENT_SECRET)\nprint(oauth_token)\n\nsearch_result = oauthv2_product_search(DIGIKEY_PRODUCT_SEARCH_URL_V4, DIGIKEY_CLIENT_ID, oauth_token, \"MCP2221A-I/SL-ND\")\n\nprint(json.dumps(search_result, indent=4))Was helping out a bit with this PR\nwhere one user was trying to get rid of special token being outputted in llama.cpp when being run in shell script\ncontext. One approach I thought was to allow for outputting the control tokens into a separate out of band stream\nrather than mixed into stdout.
\nUltimately we found a different approach that didn't require attaching an out of band stream approach.
\nNevertheless, I'm interested in understanding more about the non-standard pipes and how to use it in linux.\nWhich would allow for multiple pipe output and input of a program besides stdout and stdin.
\nWithin C standard library FILE stream add buffering and portability for text and binary I/O,\nfor ease of use in standard C programs and by default on program initialization stdin, stdout\nand stderr FILE stream is opened and associated with either a File Descriptor (Linux/Unix)\nor a HANDLE for Windows.
File descriptors on the other side provides direct low level access to system resources like files,\npipes and sockets.
\nThe key thing to note is that this is purely a linux facility and windows doesn't\nhave this capability as this write up is focused on utilizing File descriptor. Instead Windows reply on
\nThese File Descriptors can be interacted using system calls provided by unistd.h library's\npipe(), fork() and other Unix-centric IPC mechanism.
| Unix File Descriptor | \nWindows API HANDLE | \nStandard Stream | \n
|---|---|---|
| 0 | \nGetStdHandle(STD_INPUT_HANDLE) | \nStandard Input | \n
| 1 | \nGetStdHandle(STD_OUTPUT_HANDLE) | \nStandard Output | \n
| 2 | \nGetStdHandle(STD_ERROR_HANDLE) | \nStandard Error | \n
| 3 | \n3 | \n- | \n
| 4 | \n4 | \n- | \n
| etc... | \netc... | \n- | \n
These C test program was run under Linux Mint 21.3 x86_64.
#include <stdio.h>\n#include <unistd.h>\n#include <fcntl.h>\nint main() {\n for (int i = 0; i < 10; i++) {\n printf(\"Output descriptor %i is %s\\n\", i, (fcntl(i, F_GETFL) == -1) ? \"Not Attached\" : \"Attached\");\n }\n return 0;\n}Output on bash console:
\n$tcc -run ATTACHCHECK.c\nOutput descriptor 0 is Attached\nOutput descriptor 1 is Attached\nOutput descriptor 2 is Attached\nOutput descriptor 3 is Not Attached\nOutput descriptor 4 is Not Attached\nOutput descriptor 5 is Not Attached\nOutput descriptor 6 is Not Attached\nOutput descriptor 7 is Not Attached\nOutput descriptor 8 is Not Attached\nOutput descriptor 9 is Not Attached\n\n$tcc -run ATTACHCHECK.c 3>/dev/null 6>/dev/null\nOutput descriptor 0 is Attached\nOutput descriptor 1 is Attached\nOutput descriptor 2 is Attached\nOutput descriptor 3 is Attached\nOutput descriptor 4 is Not Attached\nOutput descriptor 5 is Not Attached\nOutput descriptor 6 is Attached\nOutput descriptor 7 is Not Attached\nOutput descriptor 8 is Not Attached\nOutput descriptor 9 is Not Attached#include <stdio.h>\n#include <unistd.h>\n#include <fcntl.h>\nint main() {\n printf(\"Output descriptor 3 is %s\\n\", (fcntl(3, F_GETFL) == -1) ? \"Not Attached\" : \"Attached\");\n return 0;\n}Output:
\n$ tcc -run ATTACHTEST.c 3>a\nOutput descriptor 3 is Attached\n$ tcc -run ATTACHTEST.c\nOutput descriptor 3 is Not Attached#include <stdio.h>\n#include <stdlib.h>\n#include <unistd.h>\n\nint main() {\n char outbuff[1000] = {0};\n size_t outbuff_length = 0;\n\n FILE *file_f = fdopen(0, \"r\");\n if (file_f) {\n char *buff = NULL;\n char inbuff[1000] = {0};\n ssize_t nread = read(0, inbuff, sizeof(inbuff) - 1);\n // Remove newline character if present\n if (nread > 0 && inbuff[nread - 1] == '\\n') {\n inbuff[nread - 1] = '\\0';\n nread--; // Decrement nread to exclude the newline character\n }\n if (nread != -1) {\n outbuff_length = snprintf(outbuff, sizeof(outbuff), \"Tried to read 0 got '%s' (%ld)\\n\", inbuff, nread);\n } else {\n outbuff_length = snprintf(outbuff, sizeof(outbuff), \"Tried to read 0 but got no input\\n\");\n }\n free(buff);\n } else {\n outbuff_length = snprintf(outbuff, sizeof(outbuff), \"Tried to read 0 but cannot open file descriptor\\n\");\n }\n\n write(0, outbuff, outbuff_length);\n write(1, outbuff, outbuff_length);\n\n return 0;\n}When run directly the program is able to read the piped in 'hello' as expected at File Descriptor 0.
\n$ echo \"hello\" | tcc -run INOUT.c\nTried to read 0 got 'hello' (5)Piping in to File Descriptor 0 via a FIFO pipe works as expected as well.
\n$ mkfifo fd0\n\n$ echo \"input_0\" > fd0 &\n[1] 373014\n\n$ tcc -run INOUT.c 0<fd0\nTried to read 0 got 'input_0' (7)\n[1]+ Done echo \"input_0\" > fd0However if you try to pipe out data from File Descriptor 0... it will hang\nas the read() system call fails/blocks indefinitely because there is no valid\ndata source for stdin.
\n$ mkfifo fd0\n\n$ echo \"input_0\" > fd0 &\n[1] 376622\n\n$ tcc -run INOUT.c 0>fd0\n... Program Crashes Here ...Also bash will throw an error if you try to output File Descriptor 0 to a file.\nI suspect 0>a did open as an output so hence the program cannot read from\nthe piped in "hello". Which means bash does not prevent me from redirecting 0 to\na file but this breaks the program logic.
$ echo "hello" | tcc -run INOUT.c 0>a\nTried to read 0 but cannot open file descriptor\n#include <stdio.h>\n#include <stdlib.h>\n#include <unistd.h>\nint main() {\n write(0, \"hello\\n\", 7);\n return 0;\n}Output:
\n$ echo \"yellow\" | tcc -run OUTTOD0.c 0>a\n\n$ cat a\nhelloThis indicates that it's possible to do non standard output
\n#include <stdio.h>\n#if defined (__unix__) || (defined (__APPLE__) && defined (__MACH__))\n#include <unistd.h>\n#elif defined(_WIN32)\n#include <io.h>\n#endif\nint main() {\n char name[1000] = {0};\n scanf(\"%s\", &name);\n printf(\"hello %s %s\\n\", name, isatty(fileno(stdin)) ? \"you decided to come in via terminal?\" : \"you decided to come in via pipe?\");\n return 0;\n}Output via pipe:
\n$ tcc -run stdinattach.c << __HEREDOC__\n$ mark\n$ __HEREDOC__\n\nhello mark you decided to come in via pipe?Output when manually called via interactive terminal:
\n$ tcc -run stdinattach.c # Then typed in yola manually\nhello yola you decided to come in via terminal?Anyway I hope all these examples above gives you a better sense of how this works.
\n", "date_published": "2024-05-20T00:00:00Z" }, { "id": "/blog/2024/04/11/initialise-minimal-autotools-script/", "url": "/blog/2024/04/11/initialise-minimal-autotools-script/", "title": "Initialise Minimal Autotools Script", "content_html":"Was aiming to get started on a small idea of a psv program to help parse markdown tables into json output.\nStudied how jq a popular json data handling tool structure it build system and found it is using autotools.
\nTo better use this means I first need to create a minimum autotool setup. To which i tend to prefer a scriptable approach to make the process a bit clearer to me (Since it ends up becoming a bit like a runbook).
\nOne thing to add is I quite like how jq approaches version strings in that they captured from the git tag the version name and use that to inform the autotool system the current version of this program. If you are interested, you would have a look at this script https://github.com/jqlang/jq/blob/master/scripts/version and then add this line m4_define([program_version], m4_esyscmd_s([scripts/version]))) to replace in configure.ac this line m4_define([program_version], [0.1]).
Here's the script, just copy it to a file and chmod +x <script name> in any linux based computer and it will be ready to use. Just note that I also added a .gitignore as I typically use git version control.
Also this script contains a trivial unit test example (to ensure ease of grokkability of the build system) so you may want to check out these other unit test frameworks for it and integrate it in manually.
\nBy the way I highly recommend watching Introduction to the Autotools by David A. Wheeler which would explain how autotools works at a basic level. You are also recommended to read GNU Autotools: a tutorial (Embedded Linux Conference 2016) IA Mirror as Thomas Petazzoni's diagrams is pretty good.
\nA copy of this script is also located here https://gist.github.com/mofosyne/21fca0eb74fbc788983c1068af92bc83 for those who prefer github gist.
\n#!/bin/bash\n\n# INITIALIZE MINIMAL AUTOTOOLS BASED C PROGRAM (Brian Khuu 2024)\n# https://briankhuu.com/blog/2024/04/11/initialise-minimal-autotools-script/\n\nset -euo pipefail\n\n# Function to display usage\nshow_usage() {\n echo \"Usage: $0 [PACKAGE_NAME]\"\n exit 1\n}\n\n# Parse command-line arguments\nif [ \"$#\" -eq 0 ]; then\n read -p \"Enter project name: \" PACKAGE_NAME\nelif [ \"$#\" -eq 1 ]; then\n PACKAGE_NAME=\"$1\"\nelse\n show_usage\nfi\n\n# Create project directory if it doesn't exist\nif [ ! -d \"$PACKAGE_NAME\" ]; then\n mkdir \"$PACKAGE_NAME\"\nfi\n\ncd \"$PACKAGE_NAME\" || exit 1\n\necho \"== GENERATING FILES ==\"\n\n# Create README.md\ncat <<EOF >README.md\n# $PACKAGE_NAME\n\nA minimal Autotools-based C project.\n\nQuickstart Tip: Just run \\`./bootstrap.sh && ./build.sh && ./test.sh\\` to build and test.\nYour executable will be located at \\`./$PACKAGE_NAME\\`.\nUse \\`./clean.sh\\ && ./bootstrap.sh\\` to reset to a clean slate.\nEOF\n\n# Create M4 folder\nmkdir -p m4\ncat <<EOF >m4/readme.md\n# Autotools M4 Macro Directory\nThis directory contains custom or third-party macros used by Autotools.\n## Purpose\nThese macros are included in the Autotools build process via the \\`AC_CONFIG_MACRO_DIRS([m4])\\` directive in the \\`configure.ac\\` file.\nIt is also accessible within \\`configure.ac\\` as well as m4 does a double pass as well.\n## Usage\nEnsure to include \\`-I m4\\` in the \\`ACLOCAL_AMFLAGS\\` variable within the \\`Makefile.am\\` file to instruct \\`aclocal\\` to search for macros in this directory.\nEOF\n\n# Create configure.ac\ncat <<EOF >configure.ac\nm4_define([program_version], [0.1])\nAC_INIT([$PACKAGE_NAME], [program_version])\nAC_PREREQ([2.65]) # Minimum version number for autoconf build system\nAC_CONFIG_SRCDIR([src/main.c]) # Ensure the main source file exists\nAC_CONFIG_HEADERS([src/config.h:config_h.in]) # Generate config header\nAC_CONFIG_AUX_DIR([build-aux]) # Put autotools auxiliary files into a seperate dir to reduce clutter\nAC_CONFIG_MACRO_DIRS([m4]) # Put autotools M4 macros files into a seperate dir to reduce clutter\nAM_INIT_AUTOMAKE([-Wall -Werror foreign subdir-objects]) # Initialize Automake with options\nAC_CONFIG_FILES([Makefile]) # Specify Makefile generation for main directory and src directory\nAC_PROG_CC # Find and set up C compiler\nAC_OUTPUT # Generate output files\nEOF\n\n# Create Makefile.am\ncat <<EOF >Makefile.am\nbin_PROGRAMS = $PACKAGE_NAME\n${PACKAGE_NAME}_SOURCES = src/main.c src/hello.h\n\ncheck_PROGRAMS = unit_test\nunit_test_SOURCES = tests/unit_test.c src/hello.h\n\n# ACLOCAL_AMFLAGS specifies additional flags for aclocal.\n# -I m4: Include the m4 directory for additional macros.\n# --install: Automatically install missing macros into the system-wide directory.\nACLOCAL_AMFLAGS = -I m4 --install\nEOF\n\n# Create source files\nmkdir -p src\ncat <<'EOF' >src/main.c\n#include <stdio.h>\n#include \"config.h\"\n#include \"hello.h\"\nint main() {\n printf(\"%s! (version: %s)\\n\", HELLO_MESSAGE, PACKAGE_VERSION);\n return 0;\n}\nEOF\n\n# Create header file src/hello.h\ncat <<'EOF' >src/hello.h\n#ifndef HELLO_H\n#define HELLO_H\n#define HELLO_MESSAGE \"Hello, world\"\n#endif /* HELLO_H */\nEOF\n\n# Create test source files\nmkdir -p tests\ncat <<'EOF' >tests/unit_test.c\n#include <stdio.h>\n#include <string.h>\n#include \"config.h\"\n#include \"hello.h\"\nint main() {\n if(strcmp(HELLO_MESSAGE, \"Hello, world\") != 0) {\n printf(\"Unit test failed: Message does not match expected output.\\n\");\n return 1;\n }\n printf(\"All Unit Test Passed\\n\");\n return 0;\n}\nEOF\n\n# Create bootstrap.sh\ncat <<EOF >bootstrap.sh\n#!/bin/bash\n# Setup Autotools Enviroment\nset -euo pipefail\necho \"== BOOTSTRAPPING ==\"\n\n# Run autoreconf to generate configure script and Makefile.in files\necho \"Running autoreconf...\"\n[ -e configure ] || autoreconf -vim\n\n# Configure and build the project\necho \"Configuring and building the project...\"\n[ -e Makefile ] || ( ./configure && make )\nEOF\nchmod +x bootstrap.sh\n\n# Create build.sh\ncat <<EOF >build.sh\n#!/bin/bash\n# Run the main program\nset -euo pipefail\necho \"== BUILD AND RUN $PACKAGE_NAME ==\"\nmake\n./$PACKAGE_NAME\nif [ $? -eq 0 ]; then\n echo \"build completed.\"\nelse\n echo \"build failed.\"\n exit 1\nfi\nEOF\nchmod +x build.sh\n\n# Create test.sh\ncat <<EOF >test.sh\n#!/bin/bash\n# Run the unit test program\nset -euo pipefail\necho \"== BUILD AND RUN UNIT TEST ==\"\nmake check\n./unit_test\nif [ $? -eq 0 ]; then\n echo \"Unit tests passed successfully.\"\nelse\n echo \"Unit tests failed.\"\n exit 1\nfi\nEOF\nchmod +x test.sh\n\n# Create clean.sh\ncat <<EOF >clean.sh\n#!/bin/bash\n# Clean out everything as much as possible\nset -euo pipefail\necho \"== CLEANING ==\"\nmake clean\nmake maintainer-clean\n# Extra cleaning is possible if inside a git repo\nif git rev-parse --is-inside-work-tree > /dev/null 2>&1; then\n echo \"Using .gitignore in an active git repo to clean out autotool files and directories\"\n git clean -Xdf\nfi\nEOF\nchmod +x clean.sh\n\n# Create .gitignore\ncat <<EOF >.gitignore\n# http://www.gnu.org/software/automake\n\nMakefile.in\n/ar-lib\n/mdate-sh\n/py-compile\n/test-driver\n/ylwrap\n.deps/\n.dirstamp\n\n# http://www.gnu.org/software/autoconf\n\nautom4te.cache\n/autoscan.log\n/autoscan-*.log\n/aclocal.m4\n/compile\n/config.cache\n/config.guess\n/config.h.in\n/config.log\n/config.status\n/config.sub\n/configure\n/configure.scan\n/depcomp\n/install-sh\n/missing\n/stamp-h1\n\n# https://www.gnu.org/software/libtool/\n\n/ltmain.sh\n\n# http://www.gnu.org/software/texinfo\n\n/texinfo.tex\n\n# http://www.gnu.org/software/m4/\n\nm4/libtool.m4\nm4/ltoptions.m4\nm4/ltsugar.m4\nm4/ltversion.m4\nm4/lt~obsolete.m4\n\n# Generated Makefile\n# (meta build system like autotools,\n# can automatically generate from config.status script\n# (which is called by configure script))\nMakefile\n\n# Generated from configure.ac by autoheader\nconfig_h.in\nsrc/config.h\nsrc/stamp-h1\n\n# Generated by autoreconf -i because of AC_CONFIG_AUX_DIR()\nbuild-aux/\nEOF\n\n# Check overall compilation flow\n./bootstrap.sh && ./build.sh && ./test.sh && ./clean.sh\n\necho \"== COMPLETE ==\"\necho \"Project '$PACKAGE_NAME' initialized. Run './bootstrap.sh' to set up the Autotools project.\"After running the provided script to set up a project using Autotools, some generated files such as aclocal.m4, configure, Makefile.in, and others may remain in the project directory even after cleaning with make clean and make maintainer-clean. These files are essential for the Autotools build system and are typically preserved as they may contain custom configurations or manual modifications made by developers.
I've added a check that would remove it if it's a git based project via the .gitignore file, however you can delete it from the script if you think you would be hand editing it as well.
\naclocal.m4 typically contains macros and definitions used during the configuration process. Developers often customize this file to include project-specific macros or to modify existing ones to fit their requirements.configure is a script generated by autoconf that is used to configure the build environment. It's often customized by developers to include specific configuration options or settings relevant to their project. Regenerating configure from scratch can be time-consuming and may discard customizations, so it's typically preserved during clean-up operations.Makefile.in files are templates generated by automake from Makefile.am files. While Makefile.in files are usually generated automatically, developers may make manual adjustments or additions to them to fine-tune the build process or include custom rules. Preserving these files ensures that these manual modifications are not lost.compile, depcomp, install-sh, and missing are auxiliary scripts and templates used by Autotools during the build process. Although they are generated by Autotools, developers may need to customize or modify them to accommodate specific project requirements. Therefore, they are also preserved after cleaning to ensure that any manual modifications are retained.By preserving these files, developers retain control over their project's configuration and build process, allowing for customization and flexibility.
\n", "date_published": "2024-04-11T00:00:00Z" }, { "id": "/blog/2024/04/06/inplace-upgrading-of-llamafiles-engine-bash-script/", "url": "/blog/2024/04/06/inplace-upgrading-of-llamafiles-engine-bash-script/", "title": "Inplace Upgrading Of Llamafiles Engine Bash Script", "content_html":"Been getting into LLMs and one thing I noticed being in Australia is internet speed still suck here compared to many other countries. Well in the meantime for the llamafile project, here is one useful linux bash script which may be useful for you who already downloaded a llamafile model a while ago, but want to take advantage of the new speedups that justine figured out for llamafile https://justine.lol/matmul/ .
\nThis script facilitates the repackaging and upgrading of llamafile archives generated by Llama.cpp. This is particularly useful for users with limited internet access, by preserving existing gguf and .arg settings while replacing the llamafile engine. This may break in the future if the llamafile contains more than just .gguf and .args but for now it shall do.
\nThis is also posted to gist in case anyone needs it.
\n#!/bin/bash\n# Llama.cpp Repackaging Script\n# This script facilitates the repackaging and upgrading of llamafile archives generated by Llama.cpp.\n# This is particularly useful for users with limited internet access, by preserving existing gguf and .arg settings while replacing the llamafile engine.\n#\n# Usage: llamafilerepack [-h] [-f] <old> <new>\n# -h: Display usage information.\n# -f: Skip Version Check.\n# -v: Verbose Mode\n# <old>: The name of the old llamafile archive to be upgraded.\n# <new>: The name of the new llamafile archive to be created.\n#\n# Example:\n# llamafilerepack old_llamafile new_llamafile\n# This command will upgrade the old_llamafile to a new llamafile named new_llamafile.\n#\n# Author: Brian Khuu\n# Date: 2023-04-06\n# https://briankhuu.com/blog/2024/04/06/inplace-upgrading-of-llamafiles-engine-bash-script/\nset -e\n\n# Function to display usage information\nprint_usage() {\n echo \"Usage: $0 [OPTION]... <old> <new>\"\n echo \"Upgrade llamafile archives.\"\n echo \"\"\n echo \"Options:\"\n echo \" -h, --help display this help and exit\"\n echo \" -f, --force skip version check\"\n echo \" -v, --verbose verbose mode\"\n echo \"\"\n echo \"Arguments:\"\n echo \" <old> the name of the old llamafile archive to be upgraded\"\n echo \" <new> the name of the new llamafile archive to be created\"\n echo \"\"\n echo \"Example:\"\n echo \" $0 old_llamafile new_llamafile\"\n echo \" This command will upgrade the old_llamafile to a new llamafile named new_llamafile.\"\n}\n\n# Parse command-line options\nwhile getopts \"hfv\" opt; do\n case $opt in\n h) \n print_usage\n exit 0 ;;\n f) \n force_upgrade=true\n echo \"Skipping version check.\" ;;\n v) \n verbose=true\n echo \"Verbose Output Mode.\" ;;\n esac\ndone\n\n\n# Shift the option parameters\nshift $((OPTIND -1))\n\n# Remove .llamafile extension from arguments if present\nold_llamafile=\"${1%.llamafile}\"\nif [ -z \"$2\" ]; then\n new_llamafile=\"${1%.llamafile}.updated\"\nelse\n new_llamafile=\"${2%.llamafile}\"\nfi\n\n# Obtain versions of old and new llamafiles\nold_llamafile_engine_version=$(./\"$old_llamafile\".llamafile --version)\nnew_llamafile_engine_version=$(/usr/local/bin/llamafile --version)\n\n# Check if llamafile has been upgraded\necho \"== Engine Version Check ==\"\necho \"Engine version from $old_llamafile: $old_llamafile_engine_version\"\necho \"Engine version from /usr/local/bin/llamafile: $new_llamafile_engine_version\"\nif [ \"$old_llamafile_engine_version\" = \"$new_llamafile_engine_version\" ] && [ \"$force_upgrade\" != \"true\" ]; then\n echo \"Upgrade not required. Exiting...\"\n exit 0\nfi\n\nif [ \"$verbose\" = \"true\" ]; then\n echo \"== Current Content ==\"\n zipinfo \"${old_llamafile}.llamafile\"\nfi\n\necho \"== Repackaging / Upgrading ==\"\ntempdir=$(mktemp -d)\necho \"extracting...\"\nunzip \"${old_llamafile}.llamafile\" -d ${tempdir}\necho \"repackaging...\"\ncp /usr/local/bin/llamafile \"${new_llamafile}.llamafile\"\n/usr/local/bin/zipalign -j0 \"${new_llamafile}.llamafile\" ${tempdir}/*.gguf ${tempdir}/.args\n\necho \"== Completed ==\"A while ago I was helping out with netguy's CITAQ H10 research found here. I was able to figure out to interface with the printer on it directly via the onboard internal serial port.
\nRecently however, I've been getting interested in creating some app for it and was checking if the web browser can still access modern websites. Much to my dismay, I discovered a significant hurdle: any websites utilizing Let's Encrypt SSL certificates were inaccessible.
\nThis got me trying to figure out how to update the Root CA certificates on the device, with the hope of enabling seamless access to Let's Encrypt-secured websites. This is some of the steps I had to do to get it working again by updating the built in root certificates to match the latest google android ca-certificates found in the latest android builds for newer devices.
\nFirst start by enabling Android dev mode by tapping Settings > About tablet > Build Number multiple times. Then install a terminal emulator android app and run start adbd command to start the adb daemon server. Then use ifconfig to find the ip address that this device is using.
Once you have got the device accessible over the network via adb, open up a shell terminal on your side... then update DEVICE_IPto match what the device ip is. You can then go though these steps below to download the latest CA certs then load it into the android device before rebooting. Once done, you should now be able to access let's encrypt protected websites.
# Pre Setup\nDEVICE_IP=192.168.152.248\n\n# Download the CA certificates archive\ncd /tmp/\nwget -O android-ca.tar.gz https://android.googlesource.com/platform/system/ca-certificates/+archive/refs/heads/main/files.tar.gz\n\n# Create a temporary directory to extract the certificates\nmkdir /tmp/cacerts\n\n# Extract the CA certificates to the temporary directory\ntar -xzvf android-ca.tar.gz -C /tmp/cacerts/\n\n# Connect to the device\nadb connect ${DEVICE_IP}:5555\n\n# Enter root mode (wait at least X seconds for adbd to restart into root mode)\nadb root\ntimeout 40 adb wait-for-any-device\n\n# Push the temporary directory containing the certificates to the device's storage\nadb shell mount -o rw,remount,rw /system\nadb push /tmp/cacerts/ /system/etc/security/\nadb shell mount -o ro,remount,ro /system\n\n# Sanity Check\nadb shell \"grep -C 0 'ISRG Root X1' /system/etc/security/cacerts/*.0\"\nadb shell \"grep -C 0 'ISRG Root X2' /system/etc/security/cacerts/*.0\"\n\n# Reboot\nadb rebootDid some exploration of a CITAQ H10-3 that I got from a friend who does not need it anymore for his shop.
\nI also contributed a few other useful informations like how to factory reset it, so if you need such information then head on to this Factory Reset Guide For CITAQ H10. I've also contributed other more detailed technical notes to this technical repository notes by netguy netguycode/citaq.
\nBelow is an exploration log of how the SDK and device work because in the future I may want to give a shot at writing an app for it. This doesn't quite fit into the above repository as it is more general notes and timeline of discoveries I found while exploring it and is a bit more disorganized (but is eventually cleaned up and entered into the repository). Still there are other useful notes that cannot be easily transferred and so may be of use to anyone still exploring this device as well so enjoy!
\n~/git/Citaq-H10-3/CitaqSDK/src/com/citaq/citaqfactory/PrintActivity.java\nPrintActivity.java)This button to print demo text will call either Command.getPrintDemoZH() and Command.getPrintDemo() from ./CitaqSDK/src/com/citaq/util/Command.java which would output a byte array of ESC/POS formatted text.
This is sent to printerWrite() in PrintActivity.java which calls mSendThread.addData() from public class SendThread extends Thread which would call either serialWrite() or usbWrite() to send the ESC/POS data to the internal printer.
Serial
\npublic class PrintActivity extends SerialPortActivity{\n\tprivate void initSerial(){\n\t\t\tmSerialPort = mApplication.getPrintSerialPort();\n\t\t\tmOutputStream = mSerialPort.getOutputStream();\n ... } ... } ...Where getPrintSerialPort() from ./CitaqSDK/src/com/citaq/citaqfactory/CitaqApplication.java uses SerialPort() from ./CitaqSDK/src/android_serialport_api/SerialPort.java
\tpublic SerialPort getPrintSerialPort() throws SecurityException, IOException, InvalidParameterException {\n\t\tif (mSerialPort == null) {\n\t\t\t/* Open the serial port */\n\t\t\tmSerialPort = new SerialPort(new File(\"/dev/ttyS1\"), 115200, 0, true);\n\t\t}\n\t\treturn mSerialPort;\n\t}Where
\n\tpublic SerialPort(File device, int baudrate, int flags, boolean flowCon)But the main point to learn from the above function is that the internal serial port we should be using to talk to the internal printer is:
\n/dev/ttyS1The test page for this led bar main business logic page is at ./CitaqSDK/src/com/citaq/citaqfactory/LedActivity.java
Which essentally calls functions like trunOnRedRight() which is from
./CitaqSDK/src/com/citaq/util/LEDControl.java\nThe virtual gpio file that this function writes is dependent on cpu type (different board revision?)
\nThis is determined via getCpuHardware() which calls a linux command cat /proc/cpuinfo that dumps the board hardware info and scans for lines starting with Hardware: and grab the hardware ID after it.
| getCpuHardware() Recognised Board Type | \nhardware ID string (/proc/cpuinfo) | \n
|---|---|
| SMDKV210 | \nSMDKV210 | \n
| RK3188 | \nRK30BOARD | \n
| RK30BOARD | \nSUN50IW1P1 | \n
| MSM8625Q | \nQRD MSM8625Q SKUD | \n
| RK3368 | \nRK3368 | \n
Fortunately as shown in trunOnRedRight()... in both CPU/board models, you just need to write 1 to turn led on or 0 to turn led off as shown in trunOnRedRight(). As for what files should be written to based on board type, there is some clues based on what trunOnRedRight() and trunOnBlueRight()
/sys/class/gpio/gpio190/value/sys/class/gpio/gpio172/value/sys/class/gpio/gpio124/value/sys/class/gpio/gpio106/valueThere is also MainBoardUtil.MSM8625Q referenced in trunOnRedRight() to control the led bar, but instead of control via linux gpio virual files interface... it is via calling isRedlightOn() function contained within a JNI (Java Native Interface) libarary from /CitaqSDK/libs/x86/libposctrl_jni.so. This fits my experience when working with Qualcomm SoC in that they don't typically give you datasheets for direct access to the gpio memory map as those tend to be behind NDAs for some reason...
As for other boards/cpu mentioned above, there is no led reference to it... so its likely an older model that may not have an led bar.
\nBut anyway for the context of this repository this does not matter. We got what we needed for system speccing now.
\nIn ./CitaqSDK/src/com/citaq/citaqfactory/CitaqApplication.java we see
| serial port getter name | \nSerial Port Devices | \nBaud | \nFlow Control | \n
|---|---|---|---|
| getPrintSerialPort() | \n'/dev/ttyS1` | \n115200 | \ntrue | \n
| getPrintSerialPortMT() | \n'/dev/ttyMT0` | \n115200 | \ntrue | \n
| getMSRSerialPort() | \n'/dev/ttyS2` | \n19200 | \nfalse | \n
| getCtmDisplaySerialPort() | \n'/dev/ttyS3` | \n9600 | \nfalse | \n
| getMSRSerialPort_S4() | \n'/dev/ttyS4` | \n19200 | \nfalse | \n
So let's at least annotate this for documentation
\n(Note: My best guess is that MSR means Magnetic Stripe Reader in the context of Point Of Sales equiment)
\n| CitaqApplication.java func() | \nSerial Port Devices | \nBaud | \nFlow Control | \nNote On Usage | \n
|---|---|---|---|---|
| getPrintSerialPort() | \n'/dev/ttyS1` | \n115200 | \ntrue | \nInternal Thermal Printer | \n
| getPrintSerialPortMT() | \n'/dev/ttyMT0` | \n115200 | \ntrue | \nUnknown Usage | \n
| getMSRSerialPort() | \n'/dev/ttyS2` | \n19200 | \nfalse | \nMagnetic Stripe Reader via serial port | \n
| getCtmDisplaySerialPort() | \n'/dev/ttyS3` | \n9600 | \nfalse | \nCustomer Display facing serial port. Used by FSK Caller ID and PD (ESC/POS Printer Device) example in POSFactory app | \n
| getMSRSerialPort_S4() | \n'/dev/ttyS4` | \n19200 | \nfalse | \nMagnetic Stripe Reader via serial port | \n
I'm not sure which one would control the serial port that is externally accessible from the CITAQ H10-3
\nEnable Android dev mode by tapping Settings > About tablet > Build Number multiple times.\nThen install a terminal emulator android app and run start adbd command to start the adb daemon server.\nThen use ifconfig to find the ip address that this device is using.
Then on the PC type these command (Replace ${IP_ADDRESS} with the ip address of the device)
sudo apt install adb\nadb connect ${IP_ADDRESS}:5555\nadb shellThen within the adb shell I ran /proc/cpuinfo and dumped the content here:
shell@rk3368:/ $ cat /proc/cpuinfo\nprocessor\t: 0\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 1\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 2\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 3\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 4\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 5\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 6\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nprocessor\t: 7\nBogoMIPS\t: 48.00\nFeatures\t: fp asimd evtstrm aes pmull sha1 sha2 crc32\nCPU implementer\t: 0x41\nCPU architecture: AArch64\nCPU variant\t: 0x0\nCPU part\t: 0xd03\nCPU revision\t: 3\n\nHardware\t: rockchip,rk3368\nRevision\t: 0000\nSerial\t\t: 3omdcoosnxpb7jmo\n\nDid a bit of test if I could simplify getCpuHardware() with pure shell commands avaliable in android shell.
Found this shell command works well.
\ncat /proc/cpuinfo | grep 'Hardware' | cut -d':' -f2 | cut -d',' -f2 | tr -d '[:space:]' | tr '[:lower:]' '[:upper:]'So given /proc/cpuinfo file where one of the line is: Hardware: rockchip,rk3368 this is the breakdown of the above command.
cat /proc/cpuinfo: Reads the input line from /proc/cpuinfo.grep 'Hardware': Searches for lines containing the text "Hardware"cut -d':' -f2: Splits the line at the colon (":") delimiter and selects the second field, which is " rockchip,rk3368" (with a leading space).cut -d',' -f2: Splits the text at the comma (",") delimiter and selects the second field, which is "rk3368" (without any spaces).tr -d '[:space:]': Removes any remaining spaces, resulting in "rk3368."tr '[:lower:]' '[:upper:]': Converts the text to uppercase, producing the final output: "RK3368."So, the command successfully processes the input line "Hardware: rockchip,rk3368" and outputs "RK3368" as the hardware identifier, which you could try to detect via getCpuHardware().contains('RK3368').
With this insight, we could simplify getCpuHardware() from the SDK into something like this
\n String getCpuHardware() {\n try {\n Process process = Runtime.getRuntime().exec(\"cat /proc/cpuinfo | grep 'Hardware' | cut -d':' -f2 | cut -d',' -f2 | tr -d '[:space:]' | tr '[:lower:]' '[:upper:]'\");\n BufferedReader reader = new BufferedReader(new InputStreamReader(process.getInputStream()));\n\t\t\treturn reader.readLine();\n } catch (IOException | InterruptedException e) {\n e.printStackTrace();\n }\n return \"Unknown\";\n }or in bash script function if you somehow need it...
\nfunction getCpuHardware { cat /proc/cpuinfo | grep 'Hardware' | cut -d':' -f2 | cut -d',' -f2 | tr -d '[:space:]' | tr '[:lower:]' '[:upper:]'; }\ngetCpuHardware # call get cpu hardware checkCitaq can supply firmware up to Androiv v6.0 for Citaq H10-3 as of 2023-09-11.
\nOften the examples and experiments I've done is via bash commands so best to know what I can use.\nAndroid uses toybox and busybox for shell utils, but does not have all the typical commands of a full desktop linux OS.
\nFor future reference here it is:
\nroot@rk3368:/ # toybox\nacpi base64 basename blkid blockdev bzcat cal cat chattr chcon chgrp\nchmod chown chroot cksum clear cmp comm cp cpio cut date dd df dirname\ndmesg dos2unix du echo egrep env expand expr fallocate false fgrep\nfind free freeramdisk fsfreeze getenforce getprop grep groups head\nhelp hostname hwclock id ifconfig inotifyd insmod install kill killall\nln load_policy logname losetup ls lsattr lsmod lsusb makedevs md5sum\nmkdir mkfifo mknod mkswap mktemp modinfo more mount mountpoint mv\nnbd-client nc netcat netstat nice nl nohup od partprobe paste patch\npgrep pidof pivot_root pkill pmap printenv printf pwd pwdx readlink\nrealpath renice restorecon rev rfkill rm rmdir rmmod route runcon\nsed seq setenforce setprop setsid sha1sum sleep sort split stat strings\nswapoff swapon switch_root sync sysctl tac tail tar taskset tee time\ntimeout top touch tr traceroute traceroute6 true truncate tty umount\nuname uniq unix2dos usleep vconfig vmstat wc which whoami xargs yes\n\nroot@rk3368:/sdcard # busybox\nBusyBox v1.22.1 (2014-11-27 12:30:44 CST) multi-call binary.\nBusyBox is copyrighted by many authors between 1998-2012.\nLicensed under GPLv2. See source distribution for detailed\ncopyright notices.\n\nUsage: busybox [function [arguments]...]\n or: busybox --list\n or: function [arguments]...\n\n\tBusyBox is a multi-call binary that combines many common Unix\n\tutilities into a single executable. Most people will create a\n\tlink to busybox for each function they wish to use and BusyBox\n\twill act like whatever it was invoked as.\n\nCurrently defined functions:\n\t[, [[, ar, arp, ash, awk, base64, basename, bash, beep, blkid,\n\tblockdev, bootchartd, bunzip2, bzcat, bzip2, cal, cat, catv, chat,\n\tchattr, chgrp, chmod, chown, chpst, chroot, chrt, chvt, cksum, clear,\n\tcmp, comm, cp, cpio, crond, crontab, cttyhack, cut, dc, dd, deallocvt,\n\tdepmod, devmem, df, diff, dirname, dmesg, dnsd, dos2unix, dpkg,\n\tdpkg-deb, du, dumpkmap, echo, ed, egrep, env, envdir, envuidgid,\n\texpand, expr, fakeidentd, false, fbset, fbsplash, fdflush, fdformat,\n\tfdisk, fgconsole, fgrep, find, findfs, flash_lock, flash_unlock,\n\tflashcp, flock, fold, free, freeramdisk, fstrim, fsync, ftpd, ftpget,\n\tftpput, fuser, getopt, grep, gunzip, gzip, halt, hd, hdparm, head,\n\thexdump, httpd, hwclock, ifconfig, ifdown, ifup, init, inotifyd,\n\tinsmod, install, iostat, ip, ipaddr, ipcalc, iplink, iproute, iprule,\n\tiptunnel, klogd, less, linuxrc, ln, loadkmap, losetup, lpd, lpq, lpr,\n\tls, lsattr, lsmod, lsof, lspci, lsusb, lzcat, lzma, lzop, lzopcat,\n\tmakedevs, makemime, man, md5sum, mdev, mesg, mkdir, mkfifo, mknod,\n\tmkswap, mktemp, modinfo, modprobe, more, mount, mpstat, mv, nanddump,\n\tnbd-client, nc, netstat, nice, nmeter, nohup, od, openvt, patch, pidof,\n\tping, pipe_progress, pkill, pmap, popmaildir, poweroff, powertop,\n\tprintenv, printf, ps, pscan, pstree, pwd, pwdx, raidautorun, rdev,\n\treadlink, readprofile, realpath, reboot, reformime, renice, reset,\n\tresize, rev, rm, rmdir, rmmod, route, rpm, rpm2cpio, rtcwake,\n\trun-parts, runsv, runsvdir, rx, script, scriptreplay, sed, sendmail,\n\tseq, setconsole, setkeycodes, setlogcons, setserial, setsid, setuidgid,\n\tsh, sha1sum, sha256sum, sha3sum, sha512sum, showkey, sleep, smemcap,\n\tsoftlimit, sort, split, start-stop-daemon, strings, stty, sum, sv,\n\tsvlogd, switch_root, sync, sysctl, tac, tail, tar, tcpsvd, tee, telnet,\n\ttelnetd, test, tftp, tftpd, time, timeout, top, tr, traceroute, true,\n\tttysize, tunctl, tune2fs, udhcpc, udpsvd, umount, uname, uncompress,\n\tunexpand, uniq, unix2dos, unlzma, unlzop, unxz, unzip, uptime, usleep,\n\tuudecode, uuencode, vconfig, vi, volname, watch, wc, wget, which,\n\twhoami, whois, xargs, xz, xzcat, yes, zcat\nA good reference for all commands across android version is https://android.googlesource.com/platform/system/core/+/master/shell_and_utilities/README.md
\n", "date_published": "2023-09-12T00:00:00Z" }, { "id": "/blog/2022/03/17/cheap-quadrocopter-toy/", "url": "/blog/2022/03/17/cheap-quadrocopter-toy/", "title": "The Fascination of Mini Quadrocopters", "content_html":"Just recently got my hands on a really tiny quadrocopter. It's very cool, especially how they managed to get everything to such a tiny form factor. This is no doubt in part of using the PCBs as part of the support structure.
\nThis wouldn't be possible without MEMS technologies that you find in a smart phone like accelerometers and gyroscope, in miniaturising components that use to be rather bulky and expensive to use.
\nThe major ICs onboards are:
\nIt's expected it would use a more beefy ARM processor than something like an AVR, since it is doing a closed loop feedback (PID?) control of 4 motors at the same time.
\nMINI54ZAN\n415AC\n2412B048\n-ZZ _ARM_\nhttp://www.digikey.com.au/product-detail/en/MINI54ZAN/MINI54ZAN-ND/2786710
\nhttp://media.digikey.com/pdf/Data%20Sheets/Nuvoton%20PDFs/Mini51_Br.pdf
\n\n+ Core\n - ARM Cortex-M0 core runs up to 50 MHz\n - One 24-bit system timer\n - Support low power sleep mode\n - Single-cycle 32-bit hardware multiplier\n - NVIC for the 32 interrupt inputs, each with 4-levels of priority\n - Support Serial Wire Debug (SWD) interface and 2 watchpoints/4 breakpoints\n+ Memory\n - 32K/64K/128K bytes flash memory for program memory\n (APROM) (128K bytes supports NUC100 Medium Density only)\n - 4K bytes flash memory for loader memory (LDROM)\n - Configurable data flash address and size for 128K bytes system,\n fixed 4K bytes data flash (DataFlash) for the 32K bytes and 64K bytes system\n - 4K/8K/16K bytes embedded SRAM (16K bytes supports NUC100\n Medium Density only)\n - Support PDMA mode\n+ Clock Control\n - Flexible selection from different clock sources\n - Build-in 22.1184 MHz high speed oscillator (trimmed to 1%) for\n system operation, and low power 10 KHz low speed oscillator\n for Watchdog timer and Wake-up operation\n - Support one PLL, up to 50 MHz, for high performance system operation\n - External 4 ~ 24 MHz high speed crystal input for precise timing operation\n - External 32.768 KHz low speed crystal input for RTC function\n and low power system operation\n+ Timers\n - Support 4 sets of 32-bit timers with 24-bit up-timer and one 8-bit pre-scale counter\n - Independent clock source for each timer\n - Provide one-shot, periodic, toggle and continuous counting\n operation modes (NUC100 Medium Density supports one-shot and periodic mode only)\n - Support event counting function (NUC100 Low Density only)\n+ PWM\n - Built-in up to four 16-bit PWM generators provide eight PWM\n outputs or four complementary paired PWM outputs\n - Each PWM generator equipped with one clock source selector,\n one clock divider, one 8-bit pre-scale and one Dead-Zone\n generator for complementary paired PWM\n - Up to eight 16-bit digital capture timers (shared with PWM\n timers) provide eight rising/falling capture inputs\n - Support capture interrupt\n+ ADC\n - 12-bit SAR ADC with 600K SPS\n - Up to 8-ch single-end input or 4-ch differential input\n - Single scan/single cycle scan/continuous scan\n - Each channel with individual result register\n - Scan on enabled channels\n - Threshold voltage detection\n - Conversion start by software programming or external input\n - Support PDMA mode\n+ Communication Interface\n - Maximum 3 UARTs, up to 1 Mbit/s with flow control\n - Maximum 4 SPIs, up to 16 MHz (Master@5V), 10 MHz (Salve)\n - 2 I2Cs\n - Support IrDA (SIR) function\n - Support RS485\n+ I2S\n - Interface with external audio CODEC\n - Operate as either master or slave mode\n - Capable of handling 8-, 16-, 24- and 32-bit word sizes\n - Support mono and stereo audio data\n+ Analog Comparator\n - Up to two analog comparators\n - External input or internal bandgap voltage selectable at\n negative node\n - Interrupt when compare result change\n+ RTC\n - Support software compensation by setting frequency compensate register (FCR)\n - Support RTC counter (second, minute, hour) and calendar counter (day, month, year)\n - Support alarm registers (second, minute, hour, day, month, year)\n+ EBI Bus (External bus interface supports NUC100 Low Density 64-pin package only)\n - Accessible space: 64K bytes in 8-bit mode or 128K bytes in 16-bit mode\n - Support 8-/16-bit data width\n - Support byte write in 16-bit data width mode\n+ Brownout Detector\n - With 4 levels: 4.5V / 3.8V / 2.7V / 2.2V\n - Support brownout interrupt and reset option\n+ GPIOs\n - Up to 80 general-purpose I/O (GPIO) pins\n - Four I/O modes: Quasi bi-direction, Push-Pull output, Open-Drain output, Input only with high impendence\n - TTL/Schmitt trigger input selectable\n - All GPIO pins can be configured as interrupt source with\n edge/level setting\n+ Built-in LDO for Wide Operating Voltage Range\n - 2.5V to 5.5V\n+ Operating Temperature\n - - 40oC ~ 85oC\n+ Packages (RoHS)\n - LQFP48 (7x7mm)\n - LQFP64 (10x10mm)\n\nI recognize this! It's an invensense MPU 6050! A 6 axis MPU (3 axis accerometer + 3 axis gyro)
\nINVENSENSE\nMPU-6050C\nD36138-B1\nEL 1411 E\nhttp://www.invensense.com/mems/gyro/documents/PS-MPU-6000A-00v3.4.pdf
\nThis appears to be a radio chip, due to it's proximity to the antenna
\nBEKEN\nBK2423\nB54144C\nhttp://www.inhaos.com/uploadfile/otherpic/BK2423%20Datasheet%20v2.0.pdf
\nBEKEN BK2423:\n\n\nLow Power High Performance 2.4 GHz GFSK Transceiver \n\n\n2400-2483.5 MHz ISM band operation:\n? Support 250Kbps, 1Mbps and 2 Mbps air data rate\n? Programmable output power\n? Low power consumption\n? Tolerate +/- 60ppm 16 MHz crystal\n? Variable payload length from 1 to 32bytes\n? Automatic packet processing\n? 6 data pipes for 1:6 star networks\n? 1.9V to 3.6V power supply\n? 4-pin SPI interface with maximum 8 MHz clock rate\n? Compact 20-pin 3x3 or 4x4mm QFN package \n\nWhat would be interesting, is if the quadrocopter can be reprogrammed to add other motions besides the 360 flip in one of it's auto acrobatic stunts button (one press and it does a flip in air).
\nEither way, it shows how far we have come since the first toy helicopters a few years ago (2015)
\nBTW: in jekyll I had a problem with unicode causing problems with page generation here. Solved it by stripping all non unicode via [^\\x00-\\x7F]+ regex expression. Thanks ProGM from http://stackoverflow.com/questions/20889996/notepad-how-to-remove-all-non-ascii-characters-with-regex
I attended a day presentation called 'Rockwell Automation University' where they showed some interesting development in the field of Industrial Automation. They are really pushing for integrating factories into the internet via the internet to enable new data analytic opportunities. Here is a few quick notes I made of some of the key interesting things I noted on the day.
\n\nUsually when you think about Machine Learning, you would usually think about cloud based software crunching data and spitting out results. However what's interesting is that Rockwell has opted for a AI module that fits right into a PLC.
\nSearching online, it's called Project Sherlock; and the idea is that it is a device that sits on the PLC backplane, monitoring the datastream and detecting the various condition of the machinery.
\nBased on the data it then creates a predictive model of what it thinks is a working PLC system condition. It is then able to continuously monitor after training, alerting the user if there is an anomaly.
\nThe main selling point according to Rockwell is that it is easier for non data scientist or field engineers to implement machine learning on the factory floor to detect failing machinery before the machine shuts down as well as the anomaly type. Example provided was monitoring a motor vibration to see if the motor has a loose or fracturing bearing.
\nImplementing the machine learning right at the PLC level, but not having it directly interact with the PLC is smart. If you remember the PetNet cloud outage incident, you realise that there is an importance from a risk-limiting perspective to not rely on the stability of remote connection. In the PetNet case, there was no local intelligence in the food schedule of the pet feeder, it was all online. Thus when there was an outage, the pet did not get fed.
\nhttps://www.theguardian.com/technology/2016/jul/27/petnet-auto-feeder-glitch-google
\nThus by implementing the AI module in the factory floor rather than purely the cloud, there is an inbuilt resilience to the system to allow the factory to function, even if disconnected from the internet. But at the same time, also allow for more advance analytics that are not connection stability sensitive (e.g. Long term mean time to failure prediction)
\nGood for simple machine learning problems that is linear in nature.
\n|* *\n| *--| *\n| * | *\n| *-| *\n| *---| *\n| *\n+--------------------\n|* *\n| * ---------------->| *\n| * |<---------------*\n| * ----------->| *\n| * |<-- *\n| *\n+--------------------\nIt is a IIoT concept where given enough sensors is integrated into the factories and connected to the cloud, it would allow for predictive models to get advance enough that it is able to have an accurate enough conceptual state of the factory floor. Maybe you could describe it as the factory or the company being able to be virtually introspective of themselves. (e.g. How humans know where their limbs are.)
\nOne example given is the tracking of a steel core though a steel mill. Being able to model a virtual representation of the product, would allow for triggering other factory processes based on the state of the product itself. (For example how much the steel core has cooled down since forging). (e.g. Having an IR camera monitor the heat outside of the product and thus know the spread of the heat inside the product)
\nThis is as opposed to current factory process of simply waiting a fixed amount of time, which may be inaccurate due to variation in core material properties.
\nDefine the Problem space --> Get data --> explore the data for insights --> prep data ---> create model --> gather recommended actions
\nDescriptive --> Diagnostic --> Predictive --> Prescriptive
\n| Descriptive --> Diagnostic | \nPredictive --> Prescriptive | \n
|---|---|
| Historical | \nFuture | \n
| Basic Analytics | \nAdvance Analytics | \n
Rockwell Thin Manager is intended to be installed on the factory server rack and allows for the centralisation of various factory interfaces together in one thinclient framework. (E.g. IP cameras, HMD, remote desktops).
\nThe server connects to various thin client terminals or android tablets, allowing for updating the server itself to upgrade all the thinclients, which would allow for easier security patching of the network and reduced attack surface for the factory.
\nThe Thin Manager thin client remote operating system allow for sharing multiple virtual screens, so you can have different apps on different screens. E.g. monitoring a camera feed, while also checking the PLC's HMD display of various valves state in the machinery.
\nEach terminal has two screens, one for the terminal specific interfaces, as well as a switchable screen for user specific displays that can be authenticated by fingerprint or RFID badge (e.g. Different screen for the floor manager vs the floor sparkie)
\nThese two interfaces in the terminal screen are classified as:
\nThin Manager is intended to be vendor agnostic, allowing for other companies to connect their device to Thin Manger via website, HMD, Remote Desktop Protocols or webcam.
\nDC Drive Waveform\n\n (B)\n /|\n.......| |........(C)\n | \\\n---- / \\--------\n \\-/\n (A)\nCommon fix...
\nA while ago, I went online and purchased a couple of old gameboy camera carts,\nI found that it had a bunch of old images taken by the previous owner.\nGot me thinking that we really should try to save all these images.\nThus to assist with this, I written a way to extract images from these old cameras,\nthat can be done on the cheap via an arduino, a link cable and a PC.
\nBeen a bit too busy to do a writeup, but now its ready at least to view.
\nThe full writeup is located in the project page, along with images that I\nhave extracted from the device. (As well as the JS gameboy printer hex to\nimage decoder)
\n\nhttps://github.com/mofosyne/arduino-gameboy-printer-emulator
\n", "date_published": "2017-10-07T20:59:00Z" }, { "id": "/blog/2017/09/30/electronex_show/", "url": "/blog/2017/09/30/electronex_show/", "title": "Tips On Testing From Electronex", "content_html":"During electronex, I've made some notes on good designs shown below. These are good tips in general to keep in mind.:
\nLow BOM cost does not always lead to low product cost. Don't forget cost of setup/testing/design etc...
\nMust design for testing in the beginning of the design process or it will be harder to test later on.
\nBuilt in self test can be useful in the right circumstances, so reserve some extra gpios/adc if possible for it.
\nScored really cheap from ebay. Wonder whats inside, and if it can be reprogrammed at all?
\n![\"packaging\"](\"iTagPackaging.jpg\")
![\"Front](\"iTagFront.jpg\")
![\"No](\"iTagNoBatt.jpg\")
![\"Battery](\"iTagBattCase.jpg\")
![\"Button](\"iTagButtonPCB.jpg\")
![\"PCB](\"iTagPCBcloseup.jpg\")
![\"Annotate](\"iTagPCBannotated.jpg\")
BLE micro controller
\nThere appears to be some unused pins on one side of this mcu. But datasheet is hard to come by. Does anyone know what chip this is?
\nPush Button (only one here)
\nThis allow for testing the buzzer.
\npolarity is marked. as BZ+ and BZ-
\nMT-8530 peizo buzzer.
\nThis is no connected directly to the microcontroller like in simple musical greeting cards.
\nInstead it is most likely connected to
\nThis is the microcontroller as mentioned above. I think it is called "ST17H25", but cannot find datasheet.
\nI initially thought this is an LDO stepping the battery voltage from 3V (coin cell voltage) to something like 2V or 1.8V.
\nHowever on checking the device, it did not appear to function as one.
\nAfter further studying of the pcb, I think it is most likely a mosfet gate. Since it uses only one resistor to what is likely the gate of the mosfet (resistor connected to uC).
\nWell it usally blinks to be discovered. Is connected to the PWM testpad (which is connected to uC).
\nBattery Positive
\nBattery Negative. Also GND ground level.
\nA diode that is placed essentally electrically across the buzzer. Which is most likely to dissipate the built up energy of the buzzer, when the mosfet driver is suddenly switched off duing a buzzer PWM cycle.
\nThe BLE microcontroller runs on 12Mhz
\nWell as a tag, it works alright. But as a hackable platform, it's not that great. Datasheet is unknown. Would be good to understand it's protocol thought.
\n", "date_published": "2015-10-27T02:08:20Z" }, { "id": "/blog/2015/07/11/v2.0-avr-register-macros/", "url": "/blog/2015/07/11/v2.0-avr-register-macros/", "title": "V2.0 AVR Convenient Register Macros for digital pins (for at least atmega family)", "content_html":"Ninja edit: I probbly should reworded with a name that properly specifies that this is mostly useful for manipulating digital pins only.
\nThis is the second iteration of the saner bitfield project that you can find in this page.
\nUnlike the first one, where an AVR IO register getter and setter are #define seperately. '\nIn this implementation, a single generic getter and setters was created.
This means instead of having to use only the registers supported by the macro SET_DDR or SET_PORT like below:
// Example blink code for Arduino UNO 16MHz ( atmega328P ) \n#define F_CPU 16000000UL // For delay.h to function\n#include <avr/io.h> // PIN, DDR, PORT defs\n#include <util/delay.h> //_delay_ms()\n#include \"./AVRAugment_io.h\"\n#define LED13 B5 // Only need to change this to swap pins\n#define DDR_13\tSET_DDR( LED13, 0xFF ) //IN=0x00, OUT=0xFF\n#define ON_13\tSET_PORT( LED13, 0xFF ) //LOW=0x00, HIGH=0xFF\n#define OFF_13\tSET_PORT( LED13, 0x00 ) //LOW=0x00, HIGH=0xFF\nint main(void)\n{\n\tDDR_13;\n\tON_13;\n\twhile(1)\n\t{\n\t\t//_delay_ms(2000);\n\t\tOFF_13;\n\t\t//_delay_ms(2000);\n\t\tON_13;\n\t}\n}You would be able to just use a single SET_REG macros.
\n// Example blink code for Arduino UNO 16MHz (atmega328p)\n#define F_CPU 16000000UL // For delay.h to function\n#include <avr/io.h> // PIN, DDR, PORT defs\n#include <util/delay.h> //_delay_ms()\n#include "./AVRAugment_io.h"\n##define LED13 B5 // Only need to change this to swap pins\n#define DDR_13\tSET_REG( DDR, LED13, 0xFF ) //IN=0x00, OUT=0xFF\n#define ON_13\tSET_REG( PORT, LED13, 0xFF ) //LOW=0x00, HIGH=0xFF\n#define OFF_13\tSET_REG( PORT, LED13, 0x00 ) //LOW=0x00, HIGH=0xFF\nint main(void)\n{\n\tDDR_13;\n\tON_13;\n\twhile(1)\n\t{\n\t\t_delay_ms(2000);\n\t\tOFF_13;\n\t\t_delay_ms(2000);\n\t\tON_13;\n\t}\n}\nHow does SET_REG( DDR, B5, 0xFF ) get decoded by the macro in AVRAugment_io.h
This section defines the SET_REG( REG_NAME , PIN , VALUE ) macro
\n// SINGLE BIT BITFIELD MASK ( Usally defined in atmel studio toolchain )\n// #define _BV(bit) (1 << (bit))\n\n// Enforce input to be either 0xFF or 0x00 (Since if people use arduino constants of HIGH --> 0x1 . Then it wont be 0xFF)\n#define SET_REG_VAL_CHK(VALUE) ( (VALUE>0) ? (0xFF) : (0x00) )\n\n//SET REGISTER\n // (1). Allows external #define to de-tokenize\n#define SET_REG( REG_NAME , PIN , VALUE ) R1_SET_REG( REG_NAME , PIN , VALUE ) \n // Seperate letters and numbers. Via first the `##` concat operation, and then detokanizing the PIN_LETTER and PIN_NUMBER (e.g. B1_LETTER --> B )\n#define R1_SET_REG( REG_NAME , PIN , VALUE ) R2_SET_REG( REG_NAME , PIN, PIN##_LETTER, PIN##_NUMBER, VALUE ) \n#define R2_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE ) R3_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE )\n // Now we can use the SET() macro (written by David Jahshan )\n#define R3_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE ) SET( REG_NAME##LETTER\t,\tPIN##_BITMASK\t,\tSET_REG_VAL_CHK(VALUE)\t)\nThe above macros will have a concat operation that rely on the pregenerated list below, to seperate the letters and number from "B5" into "B" and "5".
\n //Pxn: B4\n #define B4_BITMASK _BV(PB4)\n #define B4_LETTER B\n #define B4_NUMBER 4\n\n //Pxn: B5\n #define B5_BITMASK _BV(PB5)\n #define B5_LETTER B\n #define B5_NUMBER 5\n\n //Pxn: B6\n #define B6_BITMASK _BV(PB6)\n #define B6_LETTER B\n #define B6_NUMBER 6\nIt is then eventally sent to this section for actual decoding
\n//// From David Jahshan's SET and GET macro\n// This will not accept letter+number reference, must give PORT and MASK reference\n// e.g. SET_REGISTER( PORTA, _BV(PA6), 0xFF);\n#define SET(REGISTER,MASK,VALUE)\tREGISTER = ((MASK & VALUE) | (REGISTER & ~MASK))\n#define GET(REGISTER,MASK)\t\t\tREGISTER & MASK\nThus SET_REG( DDR, B5, 0xFF ) would get decoded as:
SET_REG( DDR, LED13, 0xFF )\n--> R1_SET_REG( DDR, B5, 0xFF )\n--> R2_SET_REG( DDR, B5, B5_LETTER, B5_NUMBER, 0xFF)
\n--> R3_SET_REG( DDR, PIN, B, 5, 0xFF )\n--> SET( DDRB, B5_BITMASK, SET_REG_VAL_CHK(0xFF) )
SET( DDRB, B5_BITMASK, (0xFF>0?0xFF:0x00) )\n--> SET( DDRB, _BV(PB5), (0xFF>0?0xFF:0x00) )\n--> SET( DDRB, 0x00010000, (0xFF>0?0xFF:0x00) )
\nThus the SET() Macro's form:\nREGISTER = (MASK & VALUE) | (REGISTER & ~MASK))\n--> DDRB = ( 0x00010000 & (0xFF>0?0xFF:0x00) ) | ( DDRB & ~0x00010000 ))
\nOptimized ( Since (0xFF>0?0xFF:0x00) == 0xFF == 0x11111111):\n--> DDRB = ( 0x00010000 & 0xFF ) | ( DDRB & ~0x00010000 ))\n--> DDRB = ( 0x00010000 ) | ( DDRB & ~0x00010000 ))\n--> DDRB = 0x00010000 | DDRB
\nNote: Optimization above, only works if VALUE=0xFF since setting values to high is of this form. Where setting bits is via VAR = VAR | MASK.\nIf VALUE = 0x00 then VARIABLE = VARIABLE & ~MASK is required, leading to DDRB = 0x00010000 | DDRB. Where clearing bits is var VAR = VAR & ~MASK.
So in summary SET_REG( DDR, B5, 0xFF ) means:
DDRB = ( 0x00010000 & 0xFF ) | ( DDRB & ~0x00010000 ))
\nMuch easier to understand this macro. As opposed to the bit manipulation?
\nUnlike say, arduino. This is still relatively low level code, with just macros. This allows for more effective compiler optimization.
\nAlso less abstraction than arduino. While this means a bit less portability than arduino. It is not much more work to change pins if you have already macrotized it like #define LEDPIN B5.
This macro is taking advantage of atmel's naming consistancy for both the register's macro name (e.g DDRx ), and the corresponding bit position (e.g. Pxn).
This approach only lets you edit one bit at a time. I think I really should give it a better name instead, that is more reflective of what it actually capable of.
\nWould SET_REGBIT, be a better name for this?
\nYou are still abstracting yourself away from the hardware.
\nMaybe instead of using Pxn to get the bitmask, I perhaps should really be using something like _BV(DDxn), as I recall that avr/iom328p.h used in toolchain for atmega328p looks like:
#define DDRB _SFR_IO8(0x04)\n#define DDB0 0\n#define DDB1 1\n#define DDB2 2\n#define DDB3 3\nThis might help guard against any weirdness where Pxn does not correspond to DDxn ( PB5 =/= _BV(DDB5) ). But I'll need to know if I should be paranoid enough to take that extra step in making the code a bit more complex to handle such edge cases.
// Generated @ Sat 11-07-2015 03:17AM 48sec\n/*\n TITLE: AVR Augmentation for io.h\n Purpose: Increase portability, Readability, Save time\n AUTHOR: Brian Khuu\n Version: V2.0\n Objective of V2:: \n To basically allow for flexible usage of registers beyond whatever is defined in this.\n e.g.\n Instead of: SET_PORT( B1, 0xFF) --> Sets bit 1 @ PORTB to 1\t\n Want something like: SET_REG(PORT, B1, OxFF) \n This method is more intuitive as well. But works only if the naming convention by Atmel remains consistent in this format::\n Register Location: < REGISTER TYPE NAME (e.g. DDR ) > < REGISTER LETTER > ( e.g. DDRB )\n Pin Naming: < REGISTER LETTER > < Pin Number >\n\n Thus what I would need to generate in masses is like this::\n #define B1_BITMASK PB1\n #define B1_NUMBER 1\n #define B1_LETTER B\n Assumption:\n That you are using io.h (For avr MCU) and\n that it splits IOs into banks of Port letters each with an word sized of pin numbers\n e.g. ( PA5 -> Port A pin 5 . Is a macro within io.h )\n Port letters Supported: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z\n Pin numbers Supported: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16\n\n Also assumes that Pxn is defined, and that registers are named like DDRx or PINx or PORTx etc... (x=letter, n=number)\n\n cite: initial inspiration from cinderblock "[CODE] [C] Simplifying PORT and DDR #defines for Portability\n http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=73829\n cite: "GET" and "SET" macros from David Jahshan's game_console Template\n\n Example blink code for the arduino UNO in C located in bottom of this header file\n*/\n\n// These accept letter + number reference only.\n// e.g. for PA5 -> SET_PORT(A5,0xFF)\n// ( R_ was a cinderblock suggestion, to allow for nested concat operations) \n\n// SINGLE BIT BITFIELD MASK ( Usally defined in atmel studio toolchain )\n// #define _BV(bit) (1 << (bit))\n\n// Enforce input to be either 0xFF or 0x00 (Since if people use arduino constants of HIGH --> 0x1 . Then it wont be 0xFF)\n#define SET_REG_VAL_CHK(VALUE) ( (VALUE>0) ? (0xFF) : (0x00) )\n\n//SET REGISTER\n // (1). Allows external #define to de-tokenize\n#define SET_REG( REG_NAME , PIN , VALUE ) R1_SET_REG( REG_NAME , PIN , VALUE ) \n // Seperate letters and numbers. Via first the `##` concat operation, and then detokanizing the PIN_LETTER and PIN_NUMBER (e.g. B1_LETTER --> B )\n#define R1_SET_REG( REG_NAME , PIN , VALUE ) R2_SET_REG( REG_NAME , PIN, PIN##_LETTER, PIN##_NUMBER, VALUE ) \n#define R2_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE ) R3_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE )\n // Now we can use the SET() macro (written by David Jahshan )\n#define R3_SET_REG( REG_NAME , PIN, LETTER, NUMBER, VALUE ) SET( REG_NAME##LETTER\t,\tPIN##_BITMASK\t,\tSET_REG_VAL_CHK(VALUE)\t)\n\n//GET REGISTER ( Similar method as SET REGISTER)\n#define GET_REG( REG_NAME , PIN ) R1_GET_REG( REG_NAME , PIN )\n#define R1_GET_REG( REG_NAME , PIN ) R2_SET_REG( REG_NAME , PIN, PIN##LETTER, PIN##NUMBER )\n#define R2_GET_REG( REG_NAME , PIN, LETTER, NUMBER ) R3_GET_REG( REG_NAME , PIN, LETTER, NUMBER ) \n#define R3_GET_REG( REG_NAME , PIN, LETTER, NUMBER ) SET( REG_NAME##LETTER\t,\tPIN##_BITMASK\t)\n\n//// From David Jahshan's SET and GET macro\n// This will not accept letter+number reference, must give PORT and MASK reference\n// e.g. SET_REGISTER( PORTA, _BV(PA6), 0xFF);\n#define SET(REGISTER,MASK,VALUE)\tREGISTER = ((MASK & VALUE) | (REGISTER & ~MASK))\n#define GET(REGISTER,MASK)\t\t\tREGISTER & MASK\n\n// Originally from Steve Karg in http://stackoverflow.com/questions/47981/how-do-you-set-clear-and-toggle-a-single-bit-in-c-c\n// This is included as reference. And also it's handy occationally.\n//Mask\n#define SETMASK(VARIABLE,MASK)\t\tVARIABLE = VARIABLE | MASK\n#define CLEARMASK(VARIABLE,MASK)\tVARIABLE = VARIABLE & ~MASK\n#define TOGGLEMASK(VARIABLE,MASK)\tVARIABLE = VARIABLE ^ MASK\n#define CHECKMASK(VARIABLE,MASK)\tVARIABLE & MASK\n//Single bit\n#define SETBIT(VARIABLE,b)\t\t\t((VARIABLE) |= (1<<(b)))\n#define CLEARBIT(VARIABLE,b)\t\t((VARIABLE) &= ~(1<<(b)))\n#define FLIPBIT(VARIABLE,b)\t\t\t((VARIABLE ^= (1<<(b)))\n#define CHECKBIT(VARIABLE,b)\t\t((VARIABLE) & (1<<(b)))\n\n\n// ~~~~~~~~~~ Pin Letter and Number references ~~~~~~~~~~\n\n// In _BV(PA1) the PA1 represents the bit position of the port in relation to the DDR,PORT,PIN\n//(e.g. DDRA,PORTA,PINA) registers, etc...\n// Where did PA1 etc... come from? It came from the AVR toolchain.\n// It is first either directly defined as Pxn or PORTxn (e.g. in iom328p.h ), but they are essentally equivalent values\n// as seen in portpins.h which fills in either Pxn or PORTxn with the missing value from the other one.\n// TL;DR: PA1 <--> PORTA1 . Both ultimately sourced from hardware header file like iom328p.h (8-gnu-toolchain\\include)\n\n\n//## Pin Letter:A\n\n //Pxn: A0\n #define A0_BITMASK _BV(PA0)\n #define A0_LETTER A\n #define A0_NUMBER 0\n\n //Pxn: A1\n #define A1_BITMASK _BV(PA1)\n #define A1_LETTER A\n #define A1_NUMBER 1\n\n //Pxn: A2\n #define A2_BITMASK _BV(PA2)\n #define A2_LETTER A\n #define A2_NUMBER 2\n\n //Pxn: A3\n #define A3_BITMASK _BV(PA3)\n #define A3_LETTER A\n #define A3_NUMBER 3\n\n //Pxn: A4\n #define A4_BITMASK _BV(PA4)\n #define A4_LETTER A\n #define A4_NUMBER 4\n\n //Pxn: A5\n #define A5_BITMASK _BV(PA5)\n #define A5_LETTER A\n #define A5_NUMBER 5\n\n //Pxn: A6\n #define A6_BITMASK _BV(PA6)\n #define A6_LETTER A\n #define A6_NUMBER 6\n\n //Pxn: A7\n #define A7_BITMASK _BV(PA7)\n #define A7_LETTER A\n #define A7_NUMBER 7\n\n //Pxn: A8\n #define A8_BITMASK _BV(PA8)\n #define A8_LETTER A\n #define A8_NUMBER 8\n\n //Pxn: A9\n #define A9_BITMASK _BV(PA9)\n #define A9_LETTER A\n #define A9_NUMBER 9\n\n //Pxn: A10\n #define A10_BITMASK _BV(PA10)\n #define A10_LETTER A\n #define A10_NUMBER 10\n\n //Pxn: A12\n #define A12_BITMASK _BV(PA12)\n #define A12_LETTER A\n #define A12_NUMBER 12\n\n //Pxn: A13\n #define A13_BITMASK _BV(PA13)\n #define A13_LETTER A\n #define A13_NUMBER 13\n\n //Pxn: A14\n #define A14_BITMASK _BV(PA14)\n #define A14_LETTER A\n #define A14_NUMBER 14\n\n //Pxn: A15\n #define A15_BITMASK _BV(PA15)\n #define A15_LETTER A\n #define A15_NUMBER 15\n\n //Pxn: A16\n #define A16_BITMASK _BV(PA16)\n #define A16_LETTER A\n #define A16_NUMBER 16\n\n\n//## Pin Letter:B\n\n //Pxn: B0\n #define B0_BITMASK _BV(PB0)\n #define B0_LETTER B\n #define B0_NUMBER 0\n\n //Pxn: B1\n #define B1_BITMASK _BV(PB1)\n #define B1_LETTER B\n #define B1_NUMBER 1\n\n //Pxn: B2\n #define B2_BITMASK _BV(PB2)\n #define B2_LETTER B\n #define B2_NUMBER 2\n\n //Pxn: B3\n #define B3_BITMASK _BV(PB3)\n #define B3_LETTER B\n #define B3_NUMBER 3\n\n //Pxn: B4\n #define B4_BITMASK _BV(PB4)\n #define B4_LETTER B\n #define B4_NUMBER 4\n\n //Pxn: B5\n #define B5_BITMASK _BV(PB5)\n #define B5_LETTER B\n #define B5_NUMBER 5\n\n //Pxn: B6\n #define B6_BITMASK _BV(PB6)\n #define B6_LETTER B\n #define B6_NUMBER 6\n\n //Pxn: B7\n #define B7_BITMASK _BV(PB7)\n #define B7_LETTER B\n #define B7_NUMBER 7\n\n //Pxn: B8\n #define B8_BITMASK _BV(PB8)\n #define B8_LETTER B\n #define B8_NUMBER 8\n\n //Pxn: B9\n #define B9_BITMASK _BV(PB9)\n #define B9_LETTER B\n #define B9_NUMBER 9\n\n //Pxn: B10\n #define B10_BITMASK _BV(PB10)\n #define B10_LETTER B\n #define B10_NUMBER 10\n\n //Pxn: B12\n #define B12_BITMASK _BV(PB12)\n #define B12_LETTER B\n #define B12_NUMBER 12\n\n //Pxn: B13\n #define B13_BITMASK _BV(PB13)\n #define B13_LETTER B\n #define B13_NUMBER 13\n\n //Pxn: B14\n #define B14_BITMASK _BV(PB14)\n #define B14_LETTER B\n #define B14_NUMBER 14\n\n //Pxn: B15\n #define B15_BITMASK _BV(PB15)\n #define B15_LETTER B\n #define B15_NUMBER 15\n\n //Pxn: B16\n #define B16_BITMASK _BV(PB16)\n #define B16_LETTER B\n #define B16_NUMBER 16\n\n\n//## Pin Letter:C\n\n //Pxn: C0\n #define C0_BITMASK _BV(PC0)\n #define C0_LETTER C\n #define C0_NUMBER 0\n\n //Pxn: C1\n #define C1_BITMASK _BV(PC1)\n #define C1_LETTER C\n #define C1_NUMBER 1\n\n //Pxn: C2\n #define C2_BITMASK _BV(PC2)\n #define C2_LETTER C\n #define C2_NUMBER 2\n\n //Pxn: C3\n #define C3_BITMASK _BV(PC3)\n #define C3_LETTER C\n #define C3_NUMBER 3\n\n //Pxn: C4\n #define C4_BITMASK _BV(PC4)\n #define C4_LETTER C\n #define C4_NUMBER 4\n\n //Pxn: C5\n #define C5_BITMASK _BV(PC5)\n #define C5_LETTER C\n #define C5_NUMBER 5\n\n //Pxn: C6\n #define C6_BITMASK _BV(PC6)\n #define C6_LETTER C\n #define C6_NUMBER 6\n\n //Pxn: C7\n #define C7_BITMASK _BV(PC7)\n #define C7_LETTER C\n #define C7_NUMBER 7\n\n //Pxn: C8\n #define C8_BITMASK _BV(PC8)\n #define C8_LETTER C\n #define C8_NUMBER 8\n\n //Pxn: C9\n #define C9_BITMASK _BV(PC9)\n #define C9_LETTER C\n #define C9_NUMBER 9\n\n //Pxn: C10\n #define C10_BITMASK _BV(PC10)\n #define C10_LETTER C\n #define C10_NUMBER 10\n\n //Pxn: C12\n #define C12_BITMASK _BV(PC12)\n #define C12_LETTER C\n #define C12_NUMBER 12\n\n //Pxn: C13\n #define C13_BITMASK _BV(PC13)\n #define C13_LETTER C\n #define C13_NUMBER 13\n\n //Pxn: C14\n #define C14_BITMASK _BV(PC14)\n #define C14_LETTER C\n #define C14_NUMBER 14\n\n //Pxn: C15\n #define C15_BITMASK _BV(PC15)\n #define C15_LETTER C\n #define C15_NUMBER 15\n\n //Pxn: C16\n #define C16_BITMASK _BV(PC16)\n #define C16_LETTER C\n #define C16_NUMBER 16\n\n\n//## Pin Letter:D\n\n //Pxn: D0\n #define D0_BITMASK _BV(PD0)\n #define D0_LETTER D\n #define D0_NUMBER 0\n\n //Pxn: D1\n #define D1_BITMASK _BV(PD1)\n #define D1_LETTER D\n #define D1_NUMBER 1\n\n //Pxn: D2\n #define D2_BITMASK _BV(PD2)\n #define D2_LETTER D\n #define D2_NUMBER 2\n\n //Pxn: D3\n #define D3_BITMASK _BV(PD3)\n #define D3_LETTER D\n #define D3_NUMBER 3\n\n //Pxn: D4\n #define D4_BITMASK _BV(PD4)\n #define D4_LETTER D\n #define D4_NUMBER 4\n\n //Pxn: D5\n #define D5_BITMASK _BV(PD5)\n #define D5_LETTER D\n #define D5_NUMBER 5\n\n //Pxn: D6\n #define D6_BITMASK _BV(PD6)\n #define D6_LETTER D\n #define D6_NUMBER 6\n\n //Pxn: D7\n #define D7_BITMASK _BV(PD7)\n #define D7_LETTER D\n #define D7_NUMBER 7\n\n //Pxn: D8\n #define D8_BITMASK _BV(PD8)\n #define D8_LETTER D\n #define D8_NUMBER 8\n\n //Pxn: D9\n #define D9_BITMASK _BV(PD9)\n #define D9_LETTER D\n #define D9_NUMBER 9\n\n //Pxn: D10\n #define D10_BITMASK _BV(PD10)\n #define D10_LETTER D\n #define D10_NUMBER 10\n\n //Pxn: D12\n #define D12_BITMASK _BV(PD12)\n #define D12_LETTER D\n #define D12_NUMBER 12\n\n //Pxn: D13\n #define D13_BITMASK _BV(PD13)\n #define D13_LETTER D\n #define D13_NUMBER 13\n\n //Pxn: D14\n #define D14_BITMASK _BV(PD14)\n #define D14_LETTER D\n #define D14_NUMBER 14\n\n //Pxn: D15\n #define D15_BITMASK _BV(PD15)\n #define D15_LETTER D\n #define D15_NUMBER 15\n\n //Pxn: D16\n #define D16_BITMASK _BV(PD16)\n #define D16_LETTER D\n #define D16_NUMBER 16\n\n\n//## Pin Letter:E\n\n //Pxn: E0\n #define E0_BITMASK _BV(PE0)\n #define E0_LETTER E\n #define E0_NUMBER 0\n\n //Pxn: E1\n #define E1_BITMASK _BV(PE1)\n #define E1_LETTER E\n #define E1_NUMBER 1\n\n //Pxn: E2\n #define E2_BITMASK _BV(PE2)\n #define E2_LETTER E\n #define E2_NUMBER 2\n\n //Pxn: E3\n #define E3_BITMASK _BV(PE3)\n #define E3_LETTER E\n #define E3_NUMBER 3\n\n //Pxn: E4\n #define E4_BITMASK _BV(PE4)\n #define E4_LETTER E\n #define E4_NUMBER 4\n\n //Pxn: E5\n #define E5_BITMASK _BV(PE5)\n #define E5_LETTER E\n #define E5_NUMBER 5\n\n //Pxn: E6\n #define E6_BITMASK _BV(PE6)\n #define E6_LETTER E\n #define E6_NUMBER 6\n\n //Pxn: E7\n #define E7_BITMASK _BV(PE7)\n #define E7_LETTER E\n #define E7_NUMBER 7\n\n //Pxn: E8\n #define E8_BITMASK _BV(PE8)\n #define E8_LETTER E\n #define E8_NUMBER 8\n\n //Pxn: E9\n #define E9_BITMASK _BV(PE9)\n #define E9_LETTER E\n #define E9_NUMBER 9\n\n //Pxn: E10\n #define E10_BITMASK _BV(PE10)\n #define E10_LETTER E\n #define E10_NUMBER 10\n\n //Pxn: E12\n #define E12_BITMASK _BV(PE12)\n #define E12_LETTER E\n #define E12_NUMBER 12\n\n //Pxn: E13\n #define E13_BITMASK _BV(PE13)\n #define E13_LETTER E\n #define E13_NUMBER 13\n\n //Pxn: E14\n #define E14_BITMASK _BV(PE14)\n #define E14_LETTER E\n #define E14_NUMBER 14\n\n //Pxn: E15\n #define E15_BITMASK _BV(PE15)\n #define E15_LETTER E\n #define E15_NUMBER 15\n\n //Pxn: E16\n #define E16_BITMASK _BV(PE16)\n #define E16_LETTER E\n #define E16_NUMBER 16\n\n\n//## Pin Letter:F\n\n //Pxn: F0\n #define F0_BITMASK _BV(PF0)\n #define F0_LETTER F\n #define F0_NUMBER 0\n\n //Pxn: F1\n #define F1_BITMASK _BV(PF1)\n #define F1_LETTER F\n #define F1_NUMBER 1\n\n //Pxn: F2\n #define F2_BITMASK _BV(PF2)\n #define F2_LETTER F\n #define F2_NUMBER 2\n\n //Pxn: F3\n #define F3_BITMASK _BV(PF3)\n #define F3_LETTER F\n #define F3_NUMBER 3\n\n //Pxn: F4\n #define F4_BITMASK _BV(PF4)\n #define F4_LETTER F\n #define F4_NUMBER 4\n\n //Pxn: F5\n #define F5_BITMASK _BV(PF5)\n #define F5_LETTER F\n #define F5_NUMBER 5\n\n //Pxn: F6\n #define F6_BITMASK _BV(PF6)\n #define F6_LETTER F\n #define F6_NUMBER 6\n\n //Pxn: F7\n #define F7_BITMASK _BV(PF7)\n #define F7_LETTER F\n #define F7_NUMBER 7\n\n //Pxn: F8\n #define F8_BITMASK _BV(PF8)\n #define F8_LETTER F\n #define F8_NUMBER 8\n\n //Pxn: F9\n #define F9_BITMASK _BV(PF9)\n #define F9_LETTER F\n #define F9_NUMBER 9\n\n //Pxn: F10\n #define F10_BITMASK _BV(PF10)\n #define F10_LETTER F\n #define F10_NUMBER 10\n\n //Pxn: F12\n #define F12_BITMASK _BV(PF12)\n #define F12_LETTER F\n #define F12_NUMBER 12\n\n //Pxn: F13\n #define F13_BITMASK _BV(PF13)\n #define F13_LETTER F\n #define F13_NUMBER 13\n\n //Pxn: F14\n #define F14_BITMASK _BV(PF14)\n #define F14_LETTER F\n #define F14_NUMBER 14\n\n //Pxn: F15\n #define F15_BITMASK _BV(PF15)\n #define F15_LETTER F\n #define F15_NUMBER 15\n\n //Pxn: F16\n #define F16_BITMASK _BV(PF16)\n #define F16_LETTER F\n #define F16_NUMBER 16\n\n\n//## Pin Letter:G\n\n //Pxn: G0\n #define G0_BITMASK _BV(PG0)\n #define G0_LETTER G\n #define G0_NUMBER 0\n\n //Pxn: G1\n #define G1_BITMASK _BV(PG1)\n #define G1_LETTER G\n #define G1_NUMBER 1\n\n //Pxn: G2\n #define G2_BITMASK _BV(PG2)\n #define G2_LETTER G\n #define G2_NUMBER 2\n\n //Pxn: G3\n #define G3_BITMASK _BV(PG3)\n #define G3_LETTER G\n #define G3_NUMBER 3\n\n //Pxn: G4\n #define G4_BITMASK _BV(PG4)\n #define G4_LETTER G\n #define G4_NUMBER 4\n\n //Pxn: G5\n #define G5_BITMASK _BV(PG5)\n #define G5_LETTER G\n #define G5_NUMBER 5\n\n //Pxn: G6\n #define G6_BITMASK _BV(PG6)\n #define G6_LETTER G\n #define G6_NUMBER 6\n\n //Pxn: G7\n #define G7_BITMASK _BV(PG7)\n #define G7_LETTER G\n #define G7_NUMBER 7\n\n //Pxn: G8\n #define G8_BITMASK _BV(PG8)\n #define G8_LETTER G\n #define G8_NUMBER 8\n\n //Pxn: G9\n #define G9_BITMASK _BV(PG9)\n #define G9_LETTER G\n #define G9_NUMBER 9\n\n //Pxn: G10\n #define G10_BITMASK _BV(PG10)\n #define G10_LETTER G\n #define G10_NUMBER 10\n\n //Pxn: G12\n #define G12_BITMASK _BV(PG12)\n #define G12_LETTER G\n #define G12_NUMBER 12\n\n //Pxn: G13\n #define G13_BITMASK _BV(PG13)\n #define G13_LETTER G\n #define G13_NUMBER 13\n\n //Pxn: G14\n #define G14_BITMASK _BV(PG14)\n #define G14_LETTER G\n #define G14_NUMBER 14\n\n //Pxn: G15\n #define G15_BITMASK _BV(PG15)\n #define G15_LETTER G\n #define G15_NUMBER 15\n\n //Pxn: G16\n #define G16_BITMASK _BV(PG16)\n #define G16_LETTER G\n #define G16_NUMBER 16\n\n\n//## Pin Letter:H\n\n //Pxn: H0\n #define H0_BITMASK _BV(PH0)\n #define H0_LETTER H\n #define H0_NUMBER 0\n\n //Pxn: H1\n #define H1_BITMASK _BV(PH1)\n #define H1_LETTER H\n #define H1_NUMBER 1\n\n //Pxn: H2\n #define H2_BITMASK _BV(PH2)\n #define H2_LETTER H\n #define H2_NUMBER 2\n\n //Pxn: H3\n #define H3_BITMASK _BV(PH3)\n #define H3_LETTER H\n #define H3_NUMBER 3\n\n //Pxn: H4\n #define H4_BITMASK _BV(PH4)\n #define H4_LETTER H\n #define H4_NUMBER 4\n\n //Pxn: H5\n #define H5_BITMASK _BV(PH5)\n #define H5_LETTER H\n #define H5_NUMBER 5\n\n //Pxn: H6\n #define H6_BITMASK _BV(PH6)\n #define H6_LETTER H\n #define H6_NUMBER 6\n\n //Pxn: H7\n #define H7_BITMASK _BV(PH7)\n #define H7_LETTER H\n #define H7_NUMBER 7\n\n //Pxn: H8\n #define H8_BITMASK _BV(PH8)\n #define H8_LETTER H\n #define H8_NUMBER 8\n\n //Pxn: H9\n #define H9_BITMASK _BV(PH9)\n #define H9_LETTER H\n #define H9_NUMBER 9\n\n //Pxn: H10\n #define H10_BITMASK _BV(PH10)\n #define H10_LETTER H\n #define H10_NUMBER 10\n\n //Pxn: H12\n #define H12_BITMASK _BV(PH12)\n #define H12_LETTER H\n #define H12_NUMBER 12\n\n //Pxn: H13\n #define H13_BITMASK _BV(PH13)\n #define H13_LETTER H\n #define H13_NUMBER 13\n\n //Pxn: H14\n #define H14_BITMASK _BV(PH14)\n #define H14_LETTER H\n #define H14_NUMBER 14\n\n //Pxn: H15\n #define H15_BITMASK _BV(PH15)\n #define H15_LETTER H\n #define H15_NUMBER 15\n\n //Pxn: H16\n #define H16_BITMASK _BV(PH16)\n #define H16_LETTER H\n #define H16_NUMBER 16\n\n\n//## Pin Letter:I\n\n //Pxn: I0\n #define I0_BITMASK _BV(PI0)\n #define I0_LETTER I\n #define I0_NUMBER 0\n\n //Pxn: I1\n #define I1_BITMASK _BV(PI1)\n #define I1_LETTER I\n #define I1_NUMBER 1\n\n //Pxn: I2\n #define I2_BITMASK _BV(PI2)\n #define I2_LETTER I\n #define I2_NUMBER 2\n\n //Pxn: I3\n #define I3_BITMASK _BV(PI3)\n #define I3_LETTER I\n #define I3_NUMBER 3\n\n //Pxn: I4\n #define I4_BITMASK _BV(PI4)\n #define I4_LETTER I\n #define I4_NUMBER 4\n\n //Pxn: I5\n #define I5_BITMASK _BV(PI5)\n #define I5_LETTER I\n #define I5_NUMBER 5\n\n //Pxn: I6\n #define I6_BITMASK _BV(PI6)\n #define I6_LETTER I\n #define I6_NUMBER 6\n\n //Pxn: I7\n #define I7_BITMASK _BV(PI7)\n #define I7_LETTER I\n #define I7_NUMBER 7\n\n //Pxn: I8\n #define I8_BITMASK _BV(PI8)\n #define I8_LETTER I\n #define I8_NUMBER 8\n\n //Pxn: I9\n #define I9_BITMASK _BV(PI9)\n #define I9_LETTER I\n #define I9_NUMBER 9\n\n //Pxn: I10\n #define I10_BITMASK _BV(PI10)\n #define I10_LETTER I\n #define I10_NUMBER 10\n\n //Pxn: I12\n #define I12_BITMASK _BV(PI12)\n #define I12_LETTER I\n #define I12_NUMBER 12\n\n //Pxn: I13\n #define I13_BITMASK _BV(PI13)\n #define I13_LETTER I\n #define I13_NUMBER 13\n\n //Pxn: I14\n #define I14_BITMASK _BV(PI14)\n #define I14_LETTER I\n #define I14_NUMBER 14\n\n //Pxn: I15\n #define I15_BITMASK _BV(PI15)\n #define I15_LETTER I\n #define I15_NUMBER 15\n\n //Pxn: I16\n #define I16_BITMASK _BV(PI16)\n #define I16_LETTER I\n #define I16_NUMBER 16\n\n\n//## Pin Letter:J\n\n //Pxn: J0\n #define J0_BITMASK _BV(PJ0)\n #define J0_LETTER J\n #define J0_NUMBER 0\n\n //Pxn: J1\n #define J1_BITMASK _BV(PJ1)\n #define J1_LETTER J\n #define J1_NUMBER 1\n\n //Pxn: J2\n #define J2_BITMASK _BV(PJ2)\n #define J2_LETTER J\n #define J2_NUMBER 2\n\n //Pxn: J3\n #define J3_BITMASK _BV(PJ3)\n #define J3_LETTER J\n #define J3_NUMBER 3\n\n //Pxn: J4\n #define J4_BITMASK _BV(PJ4)\n #define J4_LETTER J\n #define J4_NUMBER 4\n\n //Pxn: J5\n #define J5_BITMASK _BV(PJ5)\n #define J5_LETTER J\n #define J5_NUMBER 5\n\n //Pxn: J6\n #define J6_BITMASK _BV(PJ6)\n #define J6_LETTER J\n #define J6_NUMBER 6\n\n //Pxn: J7\n #define J7_BITMASK _BV(PJ7)\n #define J7_LETTER J\n #define J7_NUMBER 7\n\n //Pxn: J8\n #define J8_BITMASK _BV(PJ8)\n #define J8_LETTER J\n #define J8_NUMBER 8\n\n //Pxn: J9\n #define J9_BITMASK _BV(PJ9)\n #define J9_LETTER J\n #define J9_NUMBER 9\n\n //Pxn: J10\n #define J10_BITMASK _BV(PJ10)\n #define J10_LETTER J\n #define J10_NUMBER 10\n\n //Pxn: J12\n #define J12_BITMASK _BV(PJ12)\n #define J12_LETTER J\n #define J12_NUMBER 12\n\n //Pxn: J13\n #define J13_BITMASK _BV(PJ13)\n #define J13_LETTER J\n #define J13_NUMBER 13\n\n //Pxn: J14\n #define J14_BITMASK _BV(PJ14)\n #define J14_LETTER J\n #define J14_NUMBER 14\n\n //Pxn: J15\n #define J15_BITMASK _BV(PJ15)\n #define J15_LETTER J\n #define J15_NUMBER 15\n\n //Pxn: J16\n #define J16_BITMASK _BV(PJ16)\n #define J16_LETTER J\n #define J16_NUMBER 16\n\n\n//## Pin Letter:K\n\n //Pxn: K0\n #define K0_BITMASK _BV(PK0)\n #define K0_LETTER K\n #define K0_NUMBER 0\n\n //Pxn: K1\n #define K1_BITMASK _BV(PK1)\n #define K1_LETTER K\n #define K1_NUMBER 1\n\n //Pxn: K2\n #define K2_BITMASK _BV(PK2)\n #define K2_LETTER K\n #define K2_NUMBER 2\n\n //Pxn: K3\n #define K3_BITMASK _BV(PK3)\n #define K3_LETTER K\n #define K3_NUMBER 3\n\n //Pxn: K4\n #define K4_BITMASK _BV(PK4)\n #define K4_LETTER K\n #define K4_NUMBER 4\n\n //Pxn: K5\n #define K5_BITMASK _BV(PK5)\n #define K5_LETTER K\n #define K5_NUMBER 5\n\n //Pxn: K6\n #define K6_BITMASK _BV(PK6)\n #define K6_LETTER K\n #define K6_NUMBER 6\n\n //Pxn: K7\n #define K7_BITMASK _BV(PK7)\n #define K7_LETTER K\n #define K7_NUMBER 7\n\n //Pxn: K8\n #define K8_BITMASK _BV(PK8)\n #define K8_LETTER K\n #define K8_NUMBER 8\n\n //Pxn: K9\n #define K9_BITMASK _BV(PK9)\n #define K9_LETTER K\n #define K9_NUMBER 9\n\n //Pxn: K10\n #define K10_BITMASK _BV(PK10)\n #define K10_LETTER K\n #define K10_NUMBER 10\n\n //Pxn: K12\n #define K12_BITMASK _BV(PK12)\n #define K12_LETTER K\n #define K12_NUMBER 12\n\n //Pxn: K13\n #define K13_BITMASK _BV(PK13)\n #define K13_LETTER K\n #define K13_NUMBER 13\n\n //Pxn: K14\n #define K14_BITMASK _BV(PK14)\n #define K14_LETTER K\n #define K14_NUMBER 14\n\n //Pxn: K15\n #define K15_BITMASK _BV(PK15)\n #define K15_LETTER K\n #define K15_NUMBER 15\n\n //Pxn: K16\n #define K16_BITMASK _BV(PK16)\n #define K16_LETTER K\n #define K16_NUMBER 16\n\n\n//## Pin Letter:L\n\n //Pxn: L0\n #define L0_BITMASK _BV(PL0)\n #define L0_LETTER L\n #define L0_NUMBER 0\n\n //Pxn: L1\n #define L1_BITMASK _BV(PL1)\n #define L1_LETTER L\n #define L1_NUMBER 1\n\n //Pxn: L2\n #define L2_BITMASK _BV(PL2)\n #define L2_LETTER L\n #define L2_NUMBER 2\n\n //Pxn: L3\n #define L3_BITMASK _BV(PL3)\n #define L3_LETTER L\n #define L3_NUMBER 3\n\n //Pxn: L4\n #define L4_BITMASK _BV(PL4)\n #define L4_LETTER L\n #define L4_NUMBER 4\n\n //Pxn: L5\n #define L5_BITMASK _BV(PL5)\n #define L5_LETTER L\n #define L5_NUMBER 5\n\n //Pxn: L6\n #define L6_BITMASK _BV(PL6)\n #define L6_LETTER L\n #define L6_NUMBER 6\n\n //Pxn: L7\n #define L7_BITMASK _BV(PL7)\n #define L7_LETTER L\n #define L7_NUMBER 7\n\n //Pxn: L8\n #define L8_BITMASK _BV(PL8)\n #define L8_LETTER L\n #define L8_NUMBER 8\n\n //Pxn: L9\n #define L9_BITMASK _BV(PL9)\n #define L9_LETTER L\n #define L9_NUMBER 9\n\n //Pxn: L10\n #define L10_BITMASK _BV(PL10)\n #define L10_LETTER L\n #define L10_NUMBER 10\n\n //Pxn: L12\n #define L12_BITMASK _BV(PL12)\n #define L12_LETTER L\n #define L12_NUMBER 12\n\n //Pxn: L13\n #define L13_BITMASK _BV(PL13)\n #define L13_LETTER L\n #define L13_NUMBER 13\n\n //Pxn: L14\n #define L14_BITMASK _BV(PL14)\n #define L14_LETTER L\n #define L14_NUMBER 14\n\n //Pxn: L15\n #define L15_BITMASK _BV(PL15)\n #define L15_LETTER L\n #define L15_NUMBER 15\n\n //Pxn: L16\n #define L16_BITMASK _BV(PL16)\n #define L16_LETTER L\n #define L16_NUMBER 16\n\n\n//## Pin Letter:M\n\n //Pxn: M0\n #define M0_BITMASK _BV(PM0)\n #define M0_LETTER M\n #define M0_NUMBER 0\n\n //Pxn: M1\n #define M1_BITMASK _BV(PM1)\n #define M1_LETTER M\n #define M1_NUMBER 1\n\n //Pxn: M2\n #define M2_BITMASK _BV(PM2)\n #define M2_LETTER M\n #define M2_NUMBER 2\n\n //Pxn: M3\n #define M3_BITMASK _BV(PM3)\n #define M3_LETTER M\n #define M3_NUMBER 3\n\n //Pxn: M4\n #define M4_BITMASK _BV(PM4)\n #define M4_LETTER M\n #define M4_NUMBER 4\n\n //Pxn: M5\n #define M5_BITMASK _BV(PM5)\n #define M5_LETTER M\n #define M5_NUMBER 5\n\n //Pxn: M6\n #define M6_BITMASK _BV(PM6)\n #define M6_LETTER M\n #define M6_NUMBER 6\n\n //Pxn: M7\n #define M7_BITMASK _BV(PM7)\n #define M7_LETTER M\n #define M7_NUMBER 7\n\n //Pxn: M8\n #define M8_BITMASK _BV(PM8)\n #define M8_LETTER M\n #define M8_NUMBER 8\n\n //Pxn: M9\n #define M9_BITMASK _BV(PM9)\n #define M9_LETTER M\n #define M9_NUMBER 9\n\n //Pxn: M10\n #define M10_BITMASK _BV(PM10)\n #define M10_LETTER M\n #define M10_NUMBER 10\n\n //Pxn: M12\n #define M12_BITMASK _BV(PM12)\n #define M12_LETTER M\n #define M12_NUMBER 12\n\n //Pxn: M13\n #define M13_BITMASK _BV(PM13)\n #define M13_LETTER M\n #define M13_NUMBER 13\n\n //Pxn: M14\n #define M14_BITMASK _BV(PM14)\n #define M14_LETTER M\n #define M14_NUMBER 14\n\n //Pxn: M15\n #define M15_BITMASK _BV(PM15)\n #define M15_LETTER M\n #define M15_NUMBER 15\n\n //Pxn: M16\n #define M16_BITMASK _BV(PM16)\n #define M16_LETTER M\n #define M16_NUMBER 16\n\n\n//## Pin Letter:N\n\n //Pxn: N0\n #define N0_BITMASK _BV(PN0)\n #define N0_LETTER N\n #define N0_NUMBER 0\n\n //Pxn: N1\n #define N1_BITMASK _BV(PN1)\n #define N1_LETTER N\n #define N1_NUMBER 1\n\n //Pxn: N2\n #define N2_BITMASK _BV(PN2)\n #define N2_LETTER N\n #define N2_NUMBER 2\n\n //Pxn: N3\n #define N3_BITMASK _BV(PN3)\n #define N3_LETTER N\n #define N3_NUMBER 3\n\n //Pxn: N4\n #define N4_BITMASK _BV(PN4)\n #define N4_LETTER N\n #define N4_NUMBER 4\n\n //Pxn: N5\n #define N5_BITMASK _BV(PN5)\n #define N5_LETTER N\n #define N5_NUMBER 5\n\n //Pxn: N6\n #define N6_BITMASK _BV(PN6)\n #define N6_LETTER N\n #define N6_NUMBER 6\n\n //Pxn: N7\n #define N7_BITMASK _BV(PN7)\n #define N7_LETTER N\n #define N7_NUMBER 7\n\n //Pxn: N8\n #define N8_BITMASK _BV(PN8)\n #define N8_LETTER N\n #define N8_NUMBER 8\n\n //Pxn: N9\n #define N9_BITMASK _BV(PN9)\n #define N9_LETTER N\n #define N9_NUMBER 9\n\n //Pxn: N10\n #define N10_BITMASK _BV(PN10)\n #define N10_LETTER N\n #define N10_NUMBER 10\n\n //Pxn: N12\n #define N12_BITMASK _BV(PN12)\n #define N12_LETTER N\n #define N12_NUMBER 12\n\n //Pxn: N13\n #define N13_BITMASK _BV(PN13)\n #define N13_LETTER N\n #define N13_NUMBER 13\n\n //Pxn: N14\n #define N14_BITMASK _BV(PN14)\n #define N14_LETTER N\n #define N14_NUMBER 14\n\n //Pxn: N15\n #define N15_BITMASK _BV(PN15)\n #define N15_LETTER N\n #define N15_NUMBER 15\n\n //Pxn: N16\n #define N16_BITMASK _BV(PN16)\n #define N16_LETTER N\n #define N16_NUMBER 16\n\n\n//## Pin Letter:O\n\n //Pxn: O0\n #define O0_BITMASK _BV(PO0)\n #define O0_LETTER O\n #define O0_NUMBER 0\n\n //Pxn: O1\n #define O1_BITMASK _BV(PO1)\n #define O1_LETTER O\n #define O1_NUMBER 1\n\n //Pxn: O2\n #define O2_BITMASK _BV(PO2)\n #define O2_LETTER O\n #define O2_NUMBER 2\n\n //Pxn: O3\n #define O3_BITMASK _BV(PO3)\n #define O3_LETTER O\n #define O3_NUMBER 3\n\n //Pxn: O4\n #define O4_BITMASK _BV(PO4)\n #define O4_LETTER O\n #define O4_NUMBER 4\n\n //Pxn: O5\n #define O5_BITMASK _BV(PO5)\n #define O5_LETTER O\n #define O5_NUMBER 5\n\n //Pxn: O6\n #define O6_BITMASK _BV(PO6)\n #define O6_LETTER O\n #define O6_NUMBER 6\n\n //Pxn: O7\n #define O7_BITMASK _BV(PO7)\n #define O7_LETTER O\n #define O7_NUMBER 7\n\n //Pxn: O8\n #define O8_BITMASK _BV(PO8)\n #define O8_LETTER O\n #define O8_NUMBER 8\n\n //Pxn: O9\n #define O9_BITMASK _BV(PO9)\n #define O9_LETTER O\n #define O9_NUMBER 9\n\n //Pxn: O10\n #define O10_BITMASK _BV(PO10)\n #define O10_LETTER O\n #define O10_NUMBER 10\n\n //Pxn: O12\n #define O12_BITMASK _BV(PO12)\n #define O12_LETTER O\n #define O12_NUMBER 12\n\n //Pxn: O13\n #define O13_BITMASK _BV(PO13)\n #define O13_LETTER O\n #define O13_NUMBER 13\n\n //Pxn: O14\n #define O14_BITMASK _BV(PO14)\n #define O14_LETTER O\n #define O14_NUMBER 14\n\n //Pxn: O15\n #define O15_BITMASK _BV(PO15)\n #define O15_LETTER O\n #define O15_NUMBER 15\n\n //Pxn: O16\n #define O16_BITMASK _BV(PO16)\n #define O16_LETTER O\n #define O16_NUMBER 16\n\n\n//## Pin Letter:P\n\n //Pxn: P0\n #define P0_BITMASK _BV(PP0)\n #define P0_LETTER P\n #define P0_NUMBER 0\n\n //Pxn: P1\n #define P1_BITMASK _BV(PP1)\n #define P1_LETTER P\n #define P1_NUMBER 1\n\n //Pxn: P2\n #define P2_BITMASK _BV(PP2)\n #define P2_LETTER P\n #define P2_NUMBER 2\n\n //Pxn: P3\n #define P3_BITMASK _BV(PP3)\n #define P3_LETTER P\n #define P3_NUMBER 3\n\n //Pxn: P4\n #define P4_BITMASK _BV(PP4)\n #define P4_LETTER P\n #define P4_NUMBER 4\n\n //Pxn: P5\n #define P5_BITMASK _BV(PP5)\n #define P5_LETTER P\n #define P5_NUMBER 5\n\n //Pxn: P6\n #define P6_BITMASK _BV(PP6)\n #define P6_LETTER P\n #define P6_NUMBER 6\n\n //Pxn: P7\n #define P7_BITMASK _BV(PP7)\n #define P7_LETTER P\n #define P7_NUMBER 7\n\n //Pxn: P8\n #define P8_BITMASK _BV(PP8)\n #define P8_LETTER P\n #define P8_NUMBER 8\n\n //Pxn: P9\n #define P9_BITMASK _BV(PP9)\n #define P9_LETTER P\n #define P9_NUMBER 9\n\n //Pxn: P10\n #define P10_BITMASK _BV(PP10)\n #define P10_LETTER P\n #define P10_NUMBER 10\n\n //Pxn: P12\n #define P12_BITMASK _BV(PP12)\n #define P12_LETTER P\n #define P12_NUMBER 12\n\n //Pxn: P13\n #define P13_BITMASK _BV(PP13)\n #define P13_LETTER P\n #define P13_NUMBER 13\n\n //Pxn: P14\n #define P14_BITMASK _BV(PP14)\n #define P14_LETTER P\n #define P14_NUMBER 14\n\n //Pxn: P15\n #define P15_BITMASK _BV(PP15)\n #define P15_LETTER P\n #define P15_NUMBER 15\n\n //Pxn: P16\n #define P16_BITMASK _BV(PP16)\n #define P16_LETTER P\n #define P16_NUMBER 16\n\n\n//## Pin Letter:Q\n\n //Pxn: Q0\n #define Q0_BITMASK _BV(PQ0)\n #define Q0_LETTER Q\n #define Q0_NUMBER 0\n\n //Pxn: Q1\n #define Q1_BITMASK _BV(PQ1)\n #define Q1_LETTER Q\n #define Q1_NUMBER 1\n\n //Pxn: Q2\n #define Q2_BITMASK _BV(PQ2)\n #define Q2_LETTER Q\n #define Q2_NUMBER 2\n\n //Pxn: Q3\n #define Q3_BITMASK _BV(PQ3)\n #define Q3_LETTER Q\n #define Q3_NUMBER 3\n\n //Pxn: Q4\n #define Q4_BITMASK _BV(PQ4)\n #define Q4_LETTER Q\n #define Q4_NUMBER 4\n\n //Pxn: Q5\n #define Q5_BITMASK _BV(PQ5)\n #define Q5_LETTER Q\n #define Q5_NUMBER 5\n\n //Pxn: Q6\n #define Q6_BITMASK _BV(PQ6)\n #define Q6_LETTER Q\n #define Q6_NUMBER 6\n\n //Pxn: Q7\n #define Q7_BITMASK _BV(PQ7)\n #define Q7_LETTER Q\n #define Q7_NUMBER 7\n\n //Pxn: Q8\n #define Q8_BITMASK _BV(PQ8)\n #define Q8_LETTER Q\n #define Q8_NUMBER 8\n\n //Pxn: Q9\n #define Q9_BITMASK _BV(PQ9)\n #define Q9_LETTER Q\n #define Q9_NUMBER 9\n\n //Pxn: Q10\n #define Q10_BITMASK _BV(PQ10)\n #define Q10_LETTER Q\n #define Q10_NUMBER 10\n\n //Pxn: Q12\n #define Q12_BITMASK _BV(PQ12)\n #define Q12_LETTER Q\n #define Q12_NUMBER 12\n\n //Pxn: Q13\n #define Q13_BITMASK _BV(PQ13)\n #define Q13_LETTER Q\n #define Q13_NUMBER 13\n\n //Pxn: Q14\n #define Q14_BITMASK _BV(PQ14)\n #define Q14_LETTER Q\n #define Q14_NUMBER 14\n\n //Pxn: Q15\n #define Q15_BITMASK _BV(PQ15)\n #define Q15_LETTER Q\n #define Q15_NUMBER 15\n\n //Pxn: Q16\n #define Q16_BITMASK _BV(PQ16)\n #define Q16_LETTER Q\n #define Q16_NUMBER 16\n\n\n//## Pin Letter:R\n\n //Pxn: R0\n #define R0_BITMASK _BV(PR0)\n #define R0_LETTER R\n #define R0_NUMBER 0\n\n //Pxn: R1\n #define R1_BITMASK _BV(PR1)\n #define R1_LETTER R\n #define R1_NUMBER 1\n\n //Pxn: R2\n #define R2_BITMASK _BV(PR2)\n #define R2_LETTER R\n #define R2_NUMBER 2\n\n //Pxn: R3\n #define R3_BITMASK _BV(PR3)\n #define R3_LETTER R\n #define R3_NUMBER 3\n\n //Pxn: R4\n #define R4_BITMASK _BV(PR4)\n #define R4_LETTER R\n #define R4_NUMBER 4\n\n //Pxn: R5\n #define R5_BITMASK _BV(PR5)\n #define R5_LETTER R\n #define R5_NUMBER 5\n\n //Pxn: R6\n #define R6_BITMASK _BV(PR6)\n #define R6_LETTER R\n #define R6_NUMBER 6\n\n //Pxn: R7\n #define R7_BITMASK _BV(PR7)\n #define R7_LETTER R\n #define R7_NUMBER 7\n\n //Pxn: R8\n #define R8_BITMASK _BV(PR8)\n #define R8_LETTER R\n #define R8_NUMBER 8\n\n //Pxn: R9\n #define R9_BITMASK _BV(PR9)\n #define R9_LETTER R\n #define R9_NUMBER 9\n\n //Pxn: R10\n #define R10_BITMASK _BV(PR10)\n #define R10_LETTER R\n #define R10_NUMBER 10\n\n //Pxn: R12\n #define R12_BITMASK _BV(PR12)\n #define R12_LETTER R\n #define R12_NUMBER 12\n\n //Pxn: R13\n #define R13_BITMASK _BV(PR13)\n #define R13_LETTER R\n #define R13_NUMBER 13\n\n //Pxn: R14\n #define R14_BITMASK _BV(PR14)\n #define R14_LETTER R\n #define R14_NUMBER 14\n\n //Pxn: R15\n #define R15_BITMASK _BV(PR15)\n #define R15_LETTER R\n #define R15_NUMBER 15\n\n //Pxn: R16\n #define R16_BITMASK _BV(PR16)\n #define R16_LETTER R\n #define R16_NUMBER 16\n\n\n//## Pin Letter:S\n\n //Pxn: S0\n #define S0_BITMASK _BV(PS0)\n #define S0_LETTER S\n #define S0_NUMBER 0\n\n //Pxn: S1\n #define S1_BITMASK _BV(PS1)\n #define S1_LETTER S\n #define S1_NUMBER 1\n\n //Pxn: S2\n #define S2_BITMASK _BV(PS2)\n #define S2_LETTER S\n #define S2_NUMBER 2\n\n //Pxn: S3\n #define S3_BITMASK _BV(PS3)\n #define S3_LETTER S\n #define S3_NUMBER 3\n\n //Pxn: S4\n #define S4_BITMASK _BV(PS4)\n #define S4_LETTER S\n #define S4_NUMBER 4\n\n //Pxn: S5\n #define S5_BITMASK _BV(PS5)\n #define S5_LETTER S\n #define S5_NUMBER 5\n\n //Pxn: S6\n #define S6_BITMASK _BV(PS6)\n #define S6_LETTER S\n #define S6_NUMBER 6\n\n //Pxn: S7\n #define S7_BITMASK _BV(PS7)\n #define S7_LETTER S\n #define S7_NUMBER 7\n\n //Pxn: S8\n #define S8_BITMASK _BV(PS8)\n #define S8_LETTER S\n #define S8_NUMBER 8\n\n //Pxn: S9\n #define S9_BITMASK _BV(PS9)\n #define S9_LETTER S\n #define S9_NUMBER 9\n\n //Pxn: S10\n #define S10_BITMASK _BV(PS10)\n #define S10_LETTER S\n #define S10_NUMBER 10\n\n //Pxn: S12\n #define S12_BITMASK _BV(PS12)\n #define S12_LETTER S\n #define S12_NUMBER 12\n\n //Pxn: S13\n #define S13_BITMASK _BV(PS13)\n #define S13_LETTER S\n #define S13_NUMBER 13\n\n //Pxn: S14\n #define S14_BITMASK _BV(PS14)\n #define S14_LETTER S\n #define S14_NUMBER 14\n\n //Pxn: S15\n #define S15_BITMASK _BV(PS15)\n #define S15_LETTER S\n #define S15_NUMBER 15\n\n //Pxn: S16\n #define S16_BITMASK _BV(PS16)\n #define S16_LETTER S\n #define S16_NUMBER 16\n\n\n//## Pin Letter:T\n\n //Pxn: T0\n #define T0_BITMASK _BV(PT0)\n #define T0_LETTER T\n #define T0_NUMBER 0\n\n //Pxn: T1\n #define T1_BITMASK _BV(PT1)\n #define T1_LETTER T\n #define T1_NUMBER 1\n\n //Pxn: T2\n #define T2_BITMASK _BV(PT2)\n #define T2_LETTER T\n #define T2_NUMBER 2\n\n //Pxn: T3\n #define T3_BITMASK _BV(PT3)\n #define T3_LETTER T\n #define T3_NUMBER 3\n\n //Pxn: T4\n #define T4_BITMASK _BV(PT4)\n #define T4_LETTER T\n #define T4_NUMBER 4\n\n //Pxn: T5\n #define T5_BITMASK _BV(PT5)\n #define T5_LETTER T\n #define T5_NUMBER 5\n\n //Pxn: T6\n #define T6_BITMASK _BV(PT6)\n #define T6_LETTER T\n #define T6_NUMBER 6\n\n //Pxn: T7\n #define T7_BITMASK _BV(PT7)\n #define T7_LETTER T\n #define T7_NUMBER 7\n\n //Pxn: T8\n #define T8_BITMASK _BV(PT8)\n #define T8_LETTER T\n #define T8_NUMBER 8\n\n //Pxn: T9\n #define T9_BITMASK _BV(PT9)\n #define T9_LETTER T\n #define T9_NUMBER 9\n\n //Pxn: T10\n #define T10_BITMASK _BV(PT10)\n #define T10_LETTER T\n #define T10_NUMBER 10\n\n //Pxn: T12\n #define T12_BITMASK _BV(PT12)\n #define T12_LETTER T\n #define T12_NUMBER 12\n\n //Pxn: T13\n #define T13_BITMASK _BV(PT13)\n #define T13_LETTER T\n #define T13_NUMBER 13\n\n //Pxn: T14\n #define T14_BITMASK _BV(PT14)\n #define T14_LETTER T\n #define T14_NUMBER 14\n\n //Pxn: T15\n #define T15_BITMASK _BV(PT15)\n #define T15_LETTER T\n #define T15_NUMBER 15\n\n //Pxn: T16\n #define T16_BITMASK _BV(PT16)\n #define T16_LETTER T\n #define T16_NUMBER 16\n\n\n//## Pin Letter:U\n\n //Pxn: U0\n #define U0_BITMASK _BV(PU0)\n #define U0_LETTER U\n #define U0_NUMBER 0\n\n //Pxn: U1\n #define U1_BITMASK _BV(PU1)\n #define U1_LETTER U\n #define U1_NUMBER 1\n\n //Pxn: U2\n #define U2_BITMASK _BV(PU2)\n #define U2_LETTER U\n #define U2_NUMBER 2\n\n //Pxn: U3\n #define U3_BITMASK _BV(PU3)\n #define U3_LETTER U\n #define U3_NUMBER 3\n\n //Pxn: U4\n #define U4_BITMASK _BV(PU4)\n #define U4_LETTER U\n #define U4_NUMBER 4\n\n //Pxn: U5\n #define U5_BITMASK _BV(PU5)\n #define U5_LETTER U\n #define U5_NUMBER 5\n\n //Pxn: U6\n #define U6_BITMASK _BV(PU6)\n #define U6_LETTER U\n #define U6_NUMBER 6\n\n //Pxn: U7\n #define U7_BITMASK _BV(PU7)\n #define U7_LETTER U\n #define U7_NUMBER 7\n\n //Pxn: U8\n #define U8_BITMASK _BV(PU8)\n #define U8_LETTER U\n #define U8_NUMBER 8\n\n //Pxn: U9\n #define U9_BITMASK _BV(PU9)\n #define U9_LETTER U\n #define U9_NUMBER 9\n\n //Pxn: U10\n #define U10_BITMASK _BV(PU10)\n #define U10_LETTER U\n #define U10_NUMBER 10\n\n //Pxn: U12\n #define U12_BITMASK _BV(PU12)\n #define U12_LETTER U\n #define U12_NUMBER 12\n\n //Pxn: U13\n #define U13_BITMASK _BV(PU13)\n #define U13_LETTER U\n #define U13_NUMBER 13\n\n //Pxn: U14\n #define U14_BITMASK _BV(PU14)\n #define U14_LETTER U\n #define U14_NUMBER 14\n\n //Pxn: U15\n #define U15_BITMASK _BV(PU15)\n #define U15_LETTER U\n #define U15_NUMBER 15\n\n //Pxn: U16\n #define U16_BITMASK _BV(PU16)\n #define U16_LETTER U\n #define U16_NUMBER 16\n\n\n//## Pin Letter:V\n\n //Pxn: V0\n #define V0_BITMASK _BV(PV0)\n #define V0_LETTER V\n #define V0_NUMBER 0\n\n //Pxn: V1\n #define V1_BITMASK _BV(PV1)\n #define V1_LETTER V\n #define V1_NUMBER 1\n\n //Pxn: V2\n #define V2_BITMASK _BV(PV2)\n #define V2_LETTER V\n #define V2_NUMBER 2\n\n //Pxn: V3\n #define V3_BITMASK _BV(PV3)\n #define V3_LETTER V\n #define V3_NUMBER 3\n\n //Pxn: V4\n #define V4_BITMASK _BV(PV4)\n #define V4_LETTER V\n #define V4_NUMBER 4\n\n //Pxn: V5\n #define V5_BITMASK _BV(PV5)\n #define V5_LETTER V\n #define V5_NUMBER 5\n\n //Pxn: V6\n #define V6_BITMASK _BV(PV6)\n #define V6_LETTER V\n #define V6_NUMBER 6\n\n //Pxn: V7\n #define V7_BITMASK _BV(PV7)\n #define V7_LETTER V\n #define V7_NUMBER 7\n\n //Pxn: V8\n #define V8_BITMASK _BV(PV8)\n #define V8_LETTER V\n #define V8_NUMBER 8\n\n //Pxn: V9\n #define V9_BITMASK _BV(PV9)\n #define V9_LETTER V\n #define V9_NUMBER 9\n\n //Pxn: V10\n #define V10_BITMASK _BV(PV10)\n #define V10_LETTER V\n #define V10_NUMBER 10\n\n //Pxn: V12\n #define V12_BITMASK _BV(PV12)\n #define V12_LETTER V\n #define V12_NUMBER 12\n\n //Pxn: V13\n #define V13_BITMASK _BV(PV13)\n #define V13_LETTER V\n #define V13_NUMBER 13\n\n //Pxn: V14\n #define V14_BITMASK _BV(PV14)\n #define V14_LETTER V\n #define V14_NUMBER 14\n\n //Pxn: V15\n #define V15_BITMASK _BV(PV15)\n #define V15_LETTER V\n #define V15_NUMBER 15\n\n //Pxn: V16\n #define V16_BITMASK _BV(PV16)\n #define V16_LETTER V\n #define V16_NUMBER 16\n\n\n//## Pin Letter:W\n\n //Pxn: W0\n #define W0_BITMASK _BV(PW0)\n #define W0_LETTER W\n #define W0_NUMBER 0\n\n //Pxn: W1\n #define W1_BITMASK _BV(PW1)\n #define W1_LETTER W\n #define W1_NUMBER 1\n\n //Pxn: W2\n #define W2_BITMASK _BV(PW2)\n #define W2_LETTER W\n #define W2_NUMBER 2\n\n //Pxn: W3\n #define W3_BITMASK _BV(PW3)\n #define W3_LETTER W\n #define W3_NUMBER 3\n\n //Pxn: W4\n #define W4_BITMASK _BV(PW4)\n #define W4_LETTER W\n #define W4_NUMBER 4\n\n //Pxn: W5\n #define W5_BITMASK _BV(PW5)\n #define W5_LETTER W\n #define W5_NUMBER 5\n\n //Pxn: W6\n #define W6_BITMASK _BV(PW6)\n #define W6_LETTER W\n #define W6_NUMBER 6\n\n //Pxn: W7\n #define W7_BITMASK _BV(PW7)\n #define W7_LETTER W\n #define W7_NUMBER 7\n\n //Pxn: W8\n #define W8_BITMASK _BV(PW8)\n #define W8_LETTER W\n #define W8_NUMBER 8\n\n //Pxn: W9\n #define W9_BITMASK _BV(PW9)\n #define W9_LETTER W\n #define W9_NUMBER 9\n\n //Pxn: W10\n #define W10_BITMASK _BV(PW10)\n #define W10_LETTER W\n #define W10_NUMBER 10\n\n //Pxn: W12\n #define W12_BITMASK _BV(PW12)\n #define W12_LETTER W\n #define W12_NUMBER 12\n\n //Pxn: W13\n #define W13_BITMASK _BV(PW13)\n #define W13_LETTER W\n #define W13_NUMBER 13\n\n //Pxn: W14\n #define W14_BITMASK _BV(PW14)\n #define W14_LETTER W\n #define W14_NUMBER 14\n\n //Pxn: W15\n #define W15_BITMASK _BV(PW15)\n #define W15_LETTER W\n #define W15_NUMBER 15\n\n //Pxn: W16\n #define W16_BITMASK _BV(PW16)\n #define W16_LETTER W\n #define W16_NUMBER 16\n\n\n//## Pin Letter:X\n\n //Pxn: X0\n #define X0_BITMASK _BV(PX0)\n #define X0_LETTER X\n #define X0_NUMBER 0\n\n //Pxn: X1\n #define X1_BITMASK _BV(PX1)\n #define X1_LETTER X\n #define X1_NUMBER 1\n\n //Pxn: X2\n #define X2_BITMASK _BV(PX2)\n #define X2_LETTER X\n #define X2_NUMBER 2\n\n //Pxn: X3\n #define X3_BITMASK _BV(PX3)\n #define X3_LETTER X\n #define X3_NUMBER 3\n\n //Pxn: X4\n #define X4_BITMASK _BV(PX4)\n #define X4_LETTER X\n #define X4_NUMBER 4\n\n //Pxn: X5\n #define X5_BITMASK _BV(PX5)\n #define X5_LETTER X\n #define X5_NUMBER 5\n\n //Pxn: X6\n #define X6_BITMASK _BV(PX6)\n #define X6_LETTER X\n #define X6_NUMBER 6\n\n //Pxn: X7\n #define X7_BITMASK _BV(PX7)\n #define X7_LETTER X\n #define X7_NUMBER 7\n\n //Pxn: X8\n #define X8_BITMASK _BV(PX8)\n #define X8_LETTER X\n #define X8_NUMBER 8\n\n //Pxn: X9\n #define X9_BITMASK _BV(PX9)\n #define X9_LETTER X\n #define X9_NUMBER 9\n\n //Pxn: X10\n #define X10_BITMASK _BV(PX10)\n #define X10_LETTER X\n #define X10_NUMBER 10\n\n //Pxn: X12\n #define X12_BITMASK _BV(PX12)\n #define X12_LETTER X\n #define X12_NUMBER 12\n\n //Pxn: X13\n #define X13_BITMASK _BV(PX13)\n #define X13_LETTER X\n #define X13_NUMBER 13\n\n //Pxn: X14\n #define X14_BITMASK _BV(PX14)\n #define X14_LETTER X\n #define X14_NUMBER 14\n\n //Pxn: X15\n #define X15_BITMASK _BV(PX15)\n #define X15_LETTER X\n #define X15_NUMBER 15\n\n //Pxn: X16\n #define X16_BITMASK _BV(PX16)\n #define X16_LETTER X\n #define X16_NUMBER 16\n\n\n//## Pin Letter:Y\n\n //Pxn: Y0\n #define Y0_BITMASK _BV(PY0)\n #define Y0_LETTER Y\n #define Y0_NUMBER 0\n\n //Pxn: Y1\n #define Y1_BITMASK _BV(PY1)\n #define Y1_LETTER Y\n #define Y1_NUMBER 1\n\n //Pxn: Y2\n #define Y2_BITMASK _BV(PY2)\n #define Y2_LETTER Y\n #define Y2_NUMBER 2\n\n //Pxn: Y3\n #define Y3_BITMASK _BV(PY3)\n #define Y3_LETTER Y\n #define Y3_NUMBER 3\n\n //Pxn: Y4\n #define Y4_BITMASK _BV(PY4)\n #define Y4_LETTER Y\n #define Y4_NUMBER 4\n\n //Pxn: Y5\n #define Y5_BITMASK _BV(PY5)\n #define Y5_LETTER Y\n #define Y5_NUMBER 5\n\n //Pxn: Y6\n #define Y6_BITMASK _BV(PY6)\n #define Y6_LETTER Y\n #define Y6_NUMBER 6\n\n //Pxn: Y7\n #define Y7_BITMASK _BV(PY7)\n #define Y7_LETTER Y\n #define Y7_NUMBER 7\n\n //Pxn: Y8\n #define Y8_BITMASK _BV(PY8)\n #define Y8_LETTER Y\n #define Y8_NUMBER 8\n\n //Pxn: Y9\n #define Y9_BITMASK _BV(PY9)\n #define Y9_LETTER Y\n #define Y9_NUMBER 9\n\n //Pxn: Y10\n #define Y10_BITMASK _BV(PY10)\n #define Y10_LETTER Y\n #define Y10_NUMBER 10\n\n //Pxn: Y12\n #define Y12_BITMASK _BV(PY12)\n #define Y12_LETTER Y\n #define Y12_NUMBER 12\n\n //Pxn: Y13\n #define Y13_BITMASK _BV(PY13)\n #define Y13_LETTER Y\n #define Y13_NUMBER 13\n\n //Pxn: Y14\n #define Y14_BITMASK _BV(PY14)\n #define Y14_LETTER Y\n #define Y14_NUMBER 14\n\n //Pxn: Y15\n #define Y15_BITMASK _BV(PY15)\n #define Y15_LETTER Y\n #define Y15_NUMBER 15\n\n //Pxn: Y16\n #define Y16_BITMASK _BV(PY16)\n #define Y16_LETTER Y\n #define Y16_NUMBER 16\n\n\n//## Pin Letter:Z\n\n //Pxn: Z0\n #define Z0_BITMASK _BV(PZ0)\n #define Z0_LETTER Z\n #define Z0_NUMBER 0\n\n //Pxn: Z1\n #define Z1_BITMASK _BV(PZ1)\n #define Z1_LETTER Z\n #define Z1_NUMBER 1\n\n //Pxn: Z2\n #define Z2_BITMASK _BV(PZ2)\n #define Z2_LETTER Z\n #define Z2_NUMBER 2\n\n //Pxn: Z3\n #define Z3_BITMASK _BV(PZ3)\n #define Z3_LETTER Z\n #define Z3_NUMBER 3\n\n //Pxn: Z4\n #define Z4_BITMASK _BV(PZ4)\n #define Z4_LETTER Z\n #define Z4_NUMBER 4\n\n //Pxn: Z5\n #define Z5_BITMASK _BV(PZ5)\n #define Z5_LETTER Z\n #define Z5_NUMBER 5\n\n //Pxn: Z6\n #define Z6_BITMASK _BV(PZ6)\n #define Z6_LETTER Z\n #define Z6_NUMBER 6\n\n //Pxn: Z7\n #define Z7_BITMASK _BV(PZ7)\n #define Z7_LETTER Z\n #define Z7_NUMBER 7\n\n //Pxn: Z8\n #define Z8_BITMASK _BV(PZ8)\n #define Z8_LETTER Z\n #define Z8_NUMBER 8\n\n //Pxn: Z9\n #define Z9_BITMASK _BV(PZ9)\n #define Z9_LETTER Z\n #define Z9_NUMBER 9\n\n //Pxn: Z10\n #define Z10_BITMASK _BV(PZ10)\n #define Z10_LETTER Z\n #define Z10_NUMBER 10\n\n //Pxn: Z12\n #define Z12_BITMASK _BV(PZ12)\n #define Z12_LETTER Z\n #define Z12_NUMBER 12\n\n //Pxn: Z13\n #define Z13_BITMASK _BV(PZ13)\n #define Z13_LETTER Z\n #define Z13_NUMBER 13\n\n //Pxn: Z14\n #define Z14_BITMASK _BV(PZ14)\n #define Z14_LETTER Z\n #define Z14_NUMBER 14\n\n //Pxn: Z15\n #define Z15_BITMASK _BV(PZ15)\n #define Z15_LETTER Z\n #define Z15_NUMBER 15\n\n //Pxn: Z16\n #define Z16_BITMASK _BV(PZ16)\n #define Z16_LETTER Z\n #define Z16_NUMBER 16\n\n\n\n\n// ~~~~~~~~~ EXAMPLE ~~~~~~~~~~~\n/*\n\n\n// Example blink code for Arduino UNO 16MHz (atmega328p)\n#define F_CPU 16000000UL // For delay.h to function\n#include <avr/io.h> // PIN, DDR, PORT defs\n#include <util/delay.h> //_delay_ms()\n#include "./AVRAugment_io.h"\n##define LED13 B5 // Only need to change this to swap pins\n#define DDR_13\tSET_REG( DDR, LED13, 0xFF ) //IN=0x00, OUT=0xFF\n#define ON_13\tSET_REG( PORT, LED13, 0xFF ) //LOW=0x00, HIGH=0xFF\n#define OFF_13\tSET_REG( PORT, LED13, 0x00 ) //LOW=0x00, HIGH=0xFF\nint main(void)\n{\n\tDDR_13;\n\tON_13;\n\twhile(1)\n\t{\n\t\t_delay_ms(2000);\n\t\tOFF_13;\n\t\t_delay_ms(2000);\n\t\tON_13;\n\t}\n}\n\n\n*/\nThis is just a note for me to recall on how or what really happens in coding an AVR program:
\n\nx= register letter (e.g. DDRA DDRB etc... )\n\nDDRx :~ Data Direction Register (read/write)\n : Defines if pin is output=1 or input=0\n\nPORTx :~ Pin Output Mode Register (read/write)\n : If input then\n - pullup=1 floating=0\n : If output then\n - high=1 low=0\n\nPINx :~ Pin INput register (read only)\n : sense @ pin: 1=highIn 0=lowIn\n\nHow are port registers location defined? e.g. What does PORTD refer to?
In atmel studio 6 in this location:
\nC:\\Program Files (x86)\\Atmel\\Atmel Toolchain\\AVR Assembler\\Native\\2.1.1175\\avrassembler\\include
You have an entry in file m328def.inc like:
\n...\n.equ\tPORTD\t= 0x0b\n.equ\tDDRD\t= 0x0a\n.equ\tPIND\t= 0x09\n.equ\tPORTC\t= 0x08\n.equ\tDDRC\t= 0x07\n.equ\tPINC\t= 0x06\n.equ\tPORTB\t= 0x05\n.equ\tDDRB\t= 0x04\n.equ\tPINB\t= 0x03\n...\nWhich defines the IO register pointers in AVR memory.
\n.equ ?ALSO: http://www.atmel.com/webdoc/avrassembler/avrassembler.wb_directives.html
\nAll assembler directives have names that begin with a period (`.'). The rest of the name is letters, usually in lower case.
\nThe EQU directive assigns a value to a label. This label can then be used in later expressions. A label assigned to a value by the EQU directive is a constant and can not be changed or redefined.
\nVery similar to #define, but can only be defined once.
\nSeems to be similar to : http://tigcc.ticalc.org/doc/gnuasm.html#SEC86
\nBut I think the AVR assembler is a modified version of GCC to accept .equ symbol = expression instead/inaddition? to .equ symbol, expression (Maybe someone can clarify this?)
API :~ application programming interfaces define interfaces between program
\nABI :~ application binary interface (ABI) is the interface between two program modules
\nBtw Whats in ' #include <avr/io.h> ' ?\nAns: The compiler and the IDE will include in this location, the officially atmel recognized definition e.g."avr/iom328p.h - definitions for ATmega328P"
\n/* $Id: iom328p.h 2444 2014-08-11 22:10:47Z joerg_wunsch $ */\n\n/* avr/iom328p.h - definitions for ATmega328P. */\n\n/* This file should only be included from <avr/io.h>, never directly. */\n\n#ifndef _AVR_IO_H_\n# error \"Include <avr/io.h> instead of this file.\"\n#endif\n\n#ifndef _AVR_IOXXX_H_\n# define _AVR_IOXXX_H_ \"iom328p.h\"\n#else\n# error \"Attempt to include more than one <avr/ioXXX.h> file.\"\n#endif\n\n\n#ifndef _AVR_IOM328P_H_\n#define _AVR_IOM328P_H_ 1\n\n/* Registers and associated bit numbers */\n\n#define PINB _SFR_IO8(0x03)\n#define PINB0 0\n#define PINB1 1\n#define PINB2 2\n#define PINB3 3\n#define PINB4 4\n#define PINB5 5\n#define PINB6 6\n#define PINB7 7\n\n#define DDRB _SFR_IO8(0x04)\n#define DDB0 0\n#define DDB1 1\n#define DDB2 2\n#define DDB3 3\n\netc...\nI see the above is probbly just for AVR Studio with their AVR Assembler.
\nFor arduino, their source code is a bit different in terms of how it references ports in a chip, using AVR-GCC.
\ne.g. You find that in:
\nC:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr\\avr\\include\\avr
They would define a memmory mapped register as:
\n\n#ifndef _AVR_ATmega32U6_H_\n#define _AVR_ATmega32U6_H_ 1\n\n\n/* Registers and associated bit numbers. */\n\n#define PINA _SFR_IO8(0x00)\n#define PINA0 0\n#define PINA1 1\n#define PINA2 2\n#define PINA3 3\n#define PINA4 4\n#define PINA5 5\n#define PINA6 6\n#define PINA7 7\n\n#define DDRA _SFR_IO8(0x01)\n#define DDA0 0\n#define DDA1 1\n#define DDA2 2\n#define DDA3 3\n#define DDA4 4\n#define DDA5 5\n#define DDA6 6\n#define DDA7 7\n\nusing this cryptic _SFR_IO8 function. But actually, it is not a function, it is a directive.
\nAs shown in
\nThe _SFR_IO8() converts the I/O address to the memory address. It is a macro that returns a byte of data at an address of io_addr + __SFR_OFFSET.
The _SFR_IO8() is defined in hardware/tools/avr/avr/include/avr/sfr_defs.h as below.
\n#define _SFR_IO8(io_addr) _MMIO_BYTE((io_addr) + __SFR_OFFSET)\n#define __SFR_OFFSET 0x20\nAdding __SFR_OFFSET to io_addr, then calls _MMIO_BYTE().\nThe use of io_addr + __SFR_OFFSET makes more sense when you see this link http://www.protostack.com/blog/2010/12/avr-memory-architecture/
The memmory stucture of AVR is like this
\n\n# FLASH (16 Bits wide) (start at 0x000, ends at FLASHEND )\n * Application \n - Flash section ( Read while Write )\n - Optional Flash Section (No Read while Write)\n * Optional Bootloader\n\n# Ram (8bit wide)\n 0x0000 : 32 General Purpose Registers\n 0x0020 : 64 I/O Registers ( THIS IS WHAT __SFR_OFFSET refers to ) \n <---- (AKA THIS IS THE SPECIAL FUNCTION REGISTER!)\n 0x0060 : 160 Extended I/O Registers\n 0x0100 : Internal Ram (Accessable for variables etc...)\n RAMEND : End of internal Ram\n RAMEND+1: External RAM\n 0xFFFF : Max memmory address.\n\n# EEPROM ( 8 bit wide) ( start at 0x000, ends at EEPROMEND )\n\nSo that should give you an idea, of what exactly is going on... At least for AVR-GCC (and AVR Assembler too)
\nhttp://gcc.gnu.org/wiki/avr-gcc
\nhttp://stackoverflow.com/questions/23457389/avr-assembler-define-vs-equ-is-it-the-same
\nhttp://www.atmel.com/Images/doc1022.pdf - AVR Assembler User Guide\n(By Atmel)
\nhttp://www.atmel.com/Images/avr_3_04.pdf
\nHad quite a close call with bricking my OpenPGP card which is specifically V2.0 .
\nTo make it easier for those doing this in windows (mostly for myself). I made a batchfile that types the right commands into gpg to do a full factory reset of your OpenPGP card (Only tested on V2.0 btw, not V2.1 or V1.0), using codes from other sites (however most didn't work, except this one after some corrections).
\n\n@echo off\ncd ./script\necho Type "I know what I am doing" if you want to reset card: \nset /p word="passphrase: " %=%\n\nSET TRIGWORD=I know what I am doing\n\nIF "%word%" == "%TRIGWORD%" (gpg-connect-agent < openpgpcard_resetfile.scd) ELSE (echo incorrect passphrase)\n\nPAUSE\n/echo PURPOSE: To reset openpgp card (tested on V2.0 cards)\n/echo to use (openpgpcard_resetfile.scd), type: gpg-connect-agent < openpgpcard_resetfile.scd\nscd reset\nscd serialno undefined\nscd apdu 00 A4 04 00 06 D2 76 00 01 24 01\nscd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 81 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40\nscd apdu 00 20 00 83 08 40 40 40 40 40 40 40 40\nscd apdu 00 e6 00 00\nscd reset\nscd serialno undefined\nscd apdu 00 A4 04 00 06 D2 76 00 01 24 01\nscd apdu 00 44 00 00\n/echo Card has been reset to factory defaults \n/bye\nThe issue is that many examples out there does not specify version, and the troublesome thing is that what may work on V1.0 may not work in V2.0
\nAlso even when i got the correct set of codes, you must avoid trailing spaces when copying the apdu codes (Otherwise scd will get confused).
\nOnce that is solved, it was just a matter of writing a batch file to make sure it works.
\n", "date_published": "2015-02-28T01:32:00Z" }, { "id": "/blog/2015/02/24/gpg_gpa-and-a-openpgp-smartcard/", "url": "/blog/2015/02/24/gpg_gpa-and-a-openpgp-smartcard/", "title": "gpg+gpa and a openpgp smartcard", "content_html":"This is an ongoing log of setting up, installing and then using an open sourced privacy suite.
\nKeyserver entries. You can find my latest one under mofosyne in
\nThe OpenGPG smartcard is not as easy as you think to reinstall: Instruction coming up for openpgp card V2.0 factory reset process.
\nI did manage to get it to install, and work. But GPA (GUI for GPG) is really quite unstable, requiring a reset of computer sometimes\nto deal with the card not being read by GPA.
\nNow my concern is how to write emails and use it in an easy manner.
\n", "date_published": "2015-02-24T19:35:00Z" }, { "id": "/blog/2015/02/13/6x6-tap-code-experimentation/", "url": "/blog/2015/02/13/6x6-tap-code-experimentation/", "title": "6x6 tap code experimentation", "content_html":"Tap codes has a pretty cool history, you can read more about it in the wikipedia entry for tap codes. A minor issue is that the C and K in the 5x5 tap codes are mushed together. What if we extend the table to 6x6. And what if we arrange it in different ways. Here is just some experimentations to that reguards.
\nFeel free to use it. Please do let me know how you find it. It's not ment to be a serious form of communication. But it is easy to explain (not sure if any easier to master compared to morse code).
\n12,000\tE\t\t\t\t| 2,500\tF\n9,000\tT\t\t\t\t| 2,000\tW, Y\n8,000\tA, I, N, O, S\t| 1,700\tG, P\n6,400\tH\t\t\t\t| 1,600\tB\n6,200\tR\t\t\t\t| 1,200\tV\n4,400\tD\t\t\t\t| 800\tK\n4,000\tL\t\t\t\t| 500\tQ\n3,400\tU\t\t\t\t| 400\tJ, X\n3,000\tC, M\t\t\t| 200\tZ\nSOURCE: What is the freqency of the letters of the alphabet in english
\nTap the number of rows, then tap the number of columns
\n\t\n\t Non Standard 6x6 Tap Code ( Arranged by frequency of letters )\n\t\n\t | 1 | 2 | 3 | 4 | 5 | 6 |\n\t---|---|---|---|---|---|---|\n\t 1 | E | A | O | D | F | Z |\n\t 2 | T | N | R | M | B | X | \n\t 3 | I | H | C | P | J | 3 |\n\t 4 | S | U | G | Q | 2 | 6 | \n\t 5 | L | Y | K | 1 | 5 | 8 |\n\t 6 | W | V | 0 | 4 | 7 | 9 |\n\n\n\n\t Non Standard 6x6 Tap Code ( Arranged by Alphanumerical Order )\n\n\t | 1 | 2 | 3 | 4 | 5 | 6 |\n\t---|---|---|---|---|---|---|\n\t 1 | A | B | C | D | E | F | \n\t 2 | G | H | I | J | K | L |\n\t 3 | M | N | O | P | Q | R |\n\t 4 | S | T | U | V | W | X |\n\t 5 | Y | Z | 0 | 1 | 2 | 3 | \n\t 6 | 4 | 5 | 6 | 7 | 8 | 9 |\n\t\n\n\n\t Non Standard 6x6 Tap Code EXTENDED PROSIGNS ( Arranged by Alphanumerical Order )\n\n\t | 1 | 2 | 3 | 4 | 5 | 6 |\n\t---|---|---|---|---|---|---|\n\t 1 | A | B | C | D | E | F | \n\t 2 | G | H | I | J | K | L |\n\t 3 | M | N | O | P | Q | R |\n\t 4 | S | T | U | V | W | X |\n\t 5 | Y | Z | 0 | 1 | 2 | 3 | \n\t 6 | 4 | 5 | 6 | 7 | 8 | 9 |\n\t 7 |EOW|ERR|ITT|SS |UND|WAT|\n\t \n\t EOW : END OF WORK\n\t ERR : ERROR\n\t ITT : Invitation To Transmit\n\t SS : Starting signal\n\t UND : Understood\n\t WAT : Wait\n\n\n\t Non Standard 6x6 Tap Code EXTENDED PUNCTUATIONS ( Arranged by Alphanumerical Order )\n\n\t | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |\n\t---|---|---|---|---|---|---|---|---|---|\n\t 1 | A | B | C | D | E | F | . | ( | + |\n\t 2 | G | H | I | J | K | L | , | ) | - |\n\t 3 | M | N | O | P | Q | R | ? | & | _ |\n\t 4 | S | T | U | V | W | X | ' | : | " |\n\t 5 | Y | Z | 0 | 1 | 2 | 3 | ! | ; | $ |\n\t 6 | 4 | 5 | 6 | 7 | 8 | 9 | / | = | @ |\n\t\n\n\n\t Non Standard 6x6 Tap Code EXTENDED PUNCTUATIONS & PROSIGNS\n\t ( Arranged by Alphanumerical Order )\n\n\t | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |\n\t---|---|---|---|---|---|---|---|---|---|\n\t 1 | A | B | C | D | E | F | . | ( | + |\n\t 2 | G | H | I | J | K | L | , | ) | - |\n\t 3 | M | N | O | P | Q | R | ? | & | _ |\n\t 4 | S | T | U | V | W | X | ' | : | " |\n\t 5 | Y | Z | 0 | 1 | 2 | 3 | ! | ; | $ |\n\t 6 | 4 | 5 | 6 | 7 | 8 | 9 | / | = | @ |\n\t 7 |EOW|ERR|ITT|SS |UND|WAT|\n\t \n\t EOW : END OF WORK\n\t ERR : ERROR\n\t ITT : Invitation To Transmit\n\t SS : Starting signal\n\t UND : Understood\n\t WAT : Wait\t\n\nIn general however, from what I read online, it's still easier to learn morse code. (But this is easier to explain to newbies, with a reference sheet).
\n", "date_published": "2015-02-13T21:13:00Z" }, { "id": "/blog/2015/02/12/making-a-smartcard-reader-more-portable/", "url": "/blog/2015/02/12/making-a-smartcard-reader-more-portable/", "title": "making a smartcard reader more portable", "content_html":"Got a Smart Card Reader (Gemalto IDBridge CT30) for really cheap, but is frankly just too large. Would be nice to shrink it.
\nIt has usb and serial capability. But I have no idea what's the pinout for the serial line version.
\n\nPINOUT OF THE GEMALTO ID\n\t\n\tUSB CABLE to smartcard reader: \n\t[ 1:NC | 2:USB_D+_GREEN | 3:USB_D-_WHITE | 4:5V_VCC \n\t| 5:NC | 6:NC | 7:NC | 8:GND ]\n\t\n\t __ ___________________ __\n\t| |_| [1|2|3|4|5|6|7|8] |_| |\n\t| |\n\t| ([ 4.0Mhz Crystal ]) |\n\t| |\n\t| | | | | | | | | | | | | |\n\t| |-----------------------| |\n\t| | [ST] GEMPLUS | |\n\t| | GEMTWIN200G | |\n\t| | SAZ1 9907JVP | |\n\t| | MYS 99644 | |\n\t| |-----------------------| |\n\t| | | | | | | | | | | | | |\n\t| |\n\t| |\n\t| |\n\t| |\n\t| |\n\t|-----------------------------|\n\t\n\t\n\tC1:VCC C2:RST C3:CLK C4:NC\n\tC5:NC C6:IO C7:NC C8:VSS/GND\n\t __ ___________________ __\n\t| |_| |_| |\n\t| |\n\t| |C D| |\n\t| |A E| |\n\t| | | |R T| |\n\t| | | |D E| |\n\t| | | | C| |\n\t| | | | T| |\n\t| [C1][C2][C3][C4]| |\n\t| |\n\t| [C8][C7][C6][C5]| |\n\t| | | |\n\t| | | |\n\t| | | |\n\t| | | |\n\t| | | |\n\t| | | |\n\t| |\n\t|-----------------------------|\nSince I will be using the ID-000 smartcard form factor, I will need to short circuit the card detect function. Which doesn't matter since I will always be plugging in a single smartcard
\n", "date_published": "2015-02-12T20:11:00Z" }, { "id": "/blog/2015/01/14/css-style-for-ascii-art/", "url": "/blog/2015/01/14/css-style-for-ascii-art/", "title": "css style for ascii-art", "content_html":"In order to make ascii art nicer to look at, I was experimenting with some CSS. While I thought to make a dedicated generator in javascript, I luckly found that there is an easier way to do so in CSS. Originally I did the css styling for reddit as can be seen in this post. Since it works well there, I decided to try it out for my site.
\n __ __ _____ ____ _____ ___ _ _ _ _ ____ \n( \\/ )( _ )( ___)( _ )/ __)( \\/ )( \\( )( ___)\n ) ( )(_)( )__) )(_)( \\__ \\ \\ / ) ( )__) \n(_/\\/\\_)(_____)(__) (_____)(___/ (__) (_)\\_)(____)Above banner ascii text "mofosyne" was generated from this banner generator
\nTo get this style, just read on.
\n\nWhile it looks very nice for many ascii-arts, it really does mess up any textual data within the art, and make it much harder to read. So best practice is to just restrict this style to ascii-arts only, and to exclude any "ascii-diagrams".
\nHere is an example of an ascii-diagrams that is messed up when this style is applied.
\n _________________________________________________________________\n\t|\t\t\t\t \t__________\t\t\t\t\t\t\t\t\t|\n\t|\t\t\t\t\t|\t\t |\t\t\t\t\t\t\t\t\t|\n\t|\t|\t\t\t\t| EEPROM |\t\t\t(RX)\t\t(VCC)\t\t|\n\t|\t|___\t\t\t|________|\t\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t_________________\t\t(GPIO0)\t\t(RESET)\t\t|\n\t|\t|___\t|\t|\t\t\t\t|\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t|\tESP8266\t\t|\t\t(GPIO2)\t\t(CH_PD)\t\t|\n\t|\t|___\t|\t| Wifi+ARM_MCU |\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t|_______________|\t\t(GND)\t\t(TX)\t\t|\n\t|\t|_______|__\t\t\t\t\t\t\t\t\t\t\t\t\t|\n\t|_______________________________________________________________|\n\t\n\tRX\t\t:\tUART Receive Pin (Connects to TX of other device)\n\tVCC\t\t:\t3.3V Upper Power rail (Input power)\n\tGPIO0\t:\tGeneral Purpose Input Output (0)\n\tRESET\t:\tReset Device\n\tCH_P2\t:\tGeneral Purpose Input Output (2)\n\tCH_PD\t:\tChip Enable Pin (pull high)\n\tGND\t\t:\t0V Power Ground\n\tTX\t\t:\tUART Transmit Pin (Connects to RX of other device)Here is the CSS style to place in your css file.
\n/*\nDiagram and ASCII ART styling for Jekyll (and other markdown parser that appends a .language- prefix)\n*/\n\n.language-ascii-art {\n display: inline-block; \n font-family: "Lucida Console", Monaco, monospace;\n letter-spacing: -0.2em;\n line-height: 0.8em;\n text-shadow: 0 0 5px rgba(100,100,100,0.5);\n}\n\n.language-ascii-noshadows {\n display: inline-block; \n font-family: "Lucida Console", Monaco, monospace;\n letter-spacing: -0.2em;\n line-height: 0.8em;\n}\n\nSo now when you type in a fenced block that specifies "ascii-art" as the syntax highlighting option, it will be styled. This code will have ".language-ascii-art" as it's class name. And thus will be styled as an ascii-art.
\nascii-art \t\t\t /\\_/\\ \t\t____/ o o \\ \t /~____ =-= / \t (______)__m_m) \t
ascii-art-noshadows \t\t\t /\\_/\\ \t\t____/ o o \\ \t /~____ =-= / \t (______)__m_m) \t
Will turn into
\n /\\_/\\\n ____/ o o \\\n /~____ =-= /\n (______)__m_m)and if you don't like drop shadows (as requested by tom4000 from hackernews ):
\n /\\_/\\\n ____/ o o \\\n /~____ =-= /\n (______)__m_m)This ascii-art CSS styling snippet is public domain. Just use it how you wish.
\nNeed to use one for subreddit? Use this style:
\n/*\n CSS for nicer looking ascii art in reddit\n Demo: http://www.reddit.com/r/textfiles/comments/2s9ybk/random_ascii_art/\n*/\ncode {\n display:inline-block; \n font-family:"Lucida Console", Monaco, monospace ;\n letter-spacing: -0.2em;\n line-height: 0.8em;\n text-shadow: 0 0 5px rgba(100,100,100,0.5);\n}\nThis ascii-art CSS styling snippet is public domain. Just use it how you wish.
\n.language-ascii-art-blur {\n color: transparent; /*hide the text this time*/\n display: inline-block; \n font-family: "Lucida Console", Monaco, monospace;\n letter-spacing: -0.3em;\n line-height: 0.6em;\n text-shadow: 0 0 4px #000000;\n}\nThus:
\ni`it)v|[[[[(//s+)`(-\\\\/JJgbdd@@@@@@@dmKK(c!(/-[2=/cct/!-v\\!_L\\)|\n]-!/(!-)\\L\\)v|c5(!,!Ldd@@@@@@@@@@@@@@@@@@@dK/]!c\\\\\\v|i\\/cT\\v((c-\n]!`/v\\//(-|t\\VvcL!m@@@@@M@@@@@@@@@@@@@@@@@@@@bLt\\\\|)c/2-vv)/it\\.\n--/-,\\,\\v\\,|)/v/m@@@@@@K@@@@@@@@@@@@@@@@@@@@@@@bK!v!-( )-!.[/cT\n//.\\--'--|-/c(e@@@@@@@DD@@@@@@@@@@@@@@@@@@@@@@@@@@s\\\\\\\\-||/v!c\\.\n-,-|\\`||\\-\\/id@@@@@@@@N@@@@@@@@@@@@@@@@@@@@@@@@@@@@b.),`-,-/c-`i\n!,\\!-!-!'!-!d@@@@@@@P[+~**AAA@@@@@@@@@@@@@@@@@@@@@@@b/./`c-/.\\7-\n--'.-- -/,id@@@*P!` \\'Z8@@@@@@@@@@@@@@@@@@@@@i.\\\\'.\\.c\n',`,`\\'-,-J@@5`- -- `-iYA@@@@@@@@@@b@@@@@@@@@_\\-|-\\c-\n'. -.,`/.G@@K- ` - )7KM@@@@@@@@@@@@@@@@@@@c-----/\n- `- --i@@Ai -!ZZ@@@@@@@@@@@@@@@@@@@b! \\`|-`\n `-,'- G@@@[, '.D8K@@@@@@@@@@@@@@@@@@@[/-,-/.\n-` .-/v@@@A) -)ZdMd@@@@@@@@@@@@@@@@@@\\' _\\\n- ` ,iVJ@@@! '-!(K5K@@@@@@@@@@@@@@@@@@[(/s[.\n - i\\G@@@Z- ' ! -i55ZZ@@@@@@@@@@@@@@@@@)(4)`\n , -|b@@@@!\\ ' ` |-tYG@@@@@@@@@@@@@@@@XNYZ-\n tt@@@@A-, ' `)(d@@@@@@@@@@@@@@@@D)8A[\n )8@@@@@\\ ,-'-/Kd@@@@@@@@@@@@@@@@@KD@[\n ]]Z@@@@d|- ,ii.c,, -.icLZKK@@@@@@8@K@@@@@@@@@(@8[\n KN8@@@@@( .i!vGG_ J4Kb8ZKb@bbK@d@88@@@@@@@b@@@@@@@@@@dK@-\n )/8K@@@K@b@dP~~~T4( Jd@@7`___s@M@@@@MM8d@@@d@@@@@@@@@@@@LM8[\n\\!48@K@@@@8@@d*@@@bVi bAKLY~~@@@@@@*ff/\\NM8@@@@@@@@@@@@@@@db@[\n,\\\\Kb@@@d@.~t` !*~!`. -MA) '~'.).` `,'K@@@@@@@@@@@@@@@@@AKb[\n,`8M@@@@@@ -`,,gvZ`` A//- ..c\\+\\` i]d@@@@@@M@@@@@@@@@@@8[\ni\\@8@K@@@D \\!' !iZ8@@@8A@@@@@8d@b@@@8M[\ne8d5@@@@@@ '!- '-)8@@@@@@@@@@@@@@@@@@M8i\n8dZ8@M@@@@- v , ,\\tK@@@@@@@@@@@@A@@@@@@Z2|\n@b@AK@@@b@[ // cctbA@@@AK@@d@@d@@@K@@@bmi\n@@8@M@8@@@P- -=/. /iD8d@@@@@@@@@@@@@@A@@@d@@[\n@8@@@MA@@@@\\- . _)g2i -((dKK@@@@@d@@@@d@@K@@@@@@K[\n@@@bAK@@K@@)i 'c,,Kb@@bK )X)Kb@M@@d@@@Mb@@A@d@@@@@@8@[\n@K@b@@@@A@AA/i- ~M@@@@Mc .,\\c=)D8d@@b@@@d@@@@@@@@@@8d@@A[\n@@@@Mb@@@@@@('c\\` PPK((,i]v|-\\-v)8XNAdMK@@@@@@@b@@MK@A@@@@@[\n@@8@@MK@d@A@L!--c)s_, ,(ZsbLb@\\`- .-N]/KM@@@@@@@d@@@A@@@@@@@@d@[\n@@Kb@@@K@b@@@/- !''~~Vff*N5f -` -,\\))KK@@@@@@@MK@@d@@@M8d@b@@@[\n@b@@@KAK@@@@@@2-- ,,_JJ/i)/- |/v)NK@8d@@@@@@@@@@8@@@@@@@@M@K[\n@@8d@K@@@b@@@@@d!, 'VV\\)\\\\)\\7(-)4Jb@8@A@@@K@d@@@@@@@8@@@@@@@@[\nM@@@@8@@K@Kb@@@d@v. `-\\\\/v)88b@M@A@K@@M@@@A@@M@8@@A@d@8@M[\nZb@d@M@K@@@@@@@@@@m -)!/stbb@b@@A@b@@@@@Kb@@@@@@@b@@@K@@@[\nK@@d@@@@@d@M@8@@@@@Ks ,-/vJD@@8d@K@@@@@@8@@@@@@@@@@MK@@@b@@M@[\ntN@b@@d@d@M@@@@@@@@@@LL4JKd@A@@d@@K@@@@MK@@@@8@@@@@@@@@@@b@@@@@[\n)NM@8b@@A@@@A@@@@@@@@@@@@@@A@@A@@8@@K@d@@@@M@@K@@K@A@@@8@@M@@@@[\n(tMM@@@d@@M8@@@@A@@@@A@@@A@@@@@@@@@A@@@@8b@@8d@@@@@@@@@@@@@@@@M[\ntNZ@@K@@@d@@@@A@@@@@8@@@/4N@@8@b@@d@@M@8@MK@M8@K@@@@@@d@@@@@@@@[\nM/KA8@@@MA@@@M@@@@@@@@@@[|t*Z@N@@@@8@@M8ZAZZ@M@@@A@d@@@@@K@@@d@[\nbYJ4M@@@@@@A@@@@@@@@@@@@D.\\'(YKKZD@8dK@5A84YZ@dM@@@@@@@@@@@@d@@[\nK5dM8@8d@d@@@@@@@@8@@@@@@..-!/))ZK5AK4)AY(/XY/Z@@@A@@@d@@@M@@@@[\nY8dNA@@AK@@d@@@b@@@@@@@@@L,-,\\!]]\\X(5)Z/7c\\\\t5/K@@@@@@@@b@@@@@@[\n8M8@@@A@@@A@@8@@@@@@@@@KDLt! !,-|t'(-\\\\!,\\/,\\!ZJG@@@d@Md@@@G@@@[source: http://www.chris.com/ascii/index.php?art=art%20and%20design/mona%20lisa
\nThis preserves the look of ASCII text. But with the additional retro benifit of replicating the "bleed-in" effect that larger characters has (which ASCII artist in the past probbly exploited in CRT screens to give the image a "filled in" look).
\nFor Jekyll (using "ascii-art-glow")
\n.language-ascii-art-glow {\n font-family: monospace;\n text-shadow: 0 0 20px , 0 0 40px, 0 0 80px , 0 0 100px;\n}\nFor subreddit in reddit:
\ncode {\n font-family: monospace;\n text-shadow: 0 0 20px , 0 0 40px, 0 0 80px , 0 0 100px;\n}\n\nPros: More faithful to the original effect in CRT monitors that artist in the old days exploited. Normal non art text embedded within the ASCII-art is readable.
\nCons: Is not as pretty as the previous suggestion in here . Also it requires a dark background on light text to work best.
\n╔═ comhack@Cerberus 10:49 PM \n╚═══ ~-> ssh -p xxxx comhack@xx.xxx.xxx.xxx\n\n^[[H^[[2J\n _____ .__ .____ .__\n / _ \\_______ ____ | |__ | | |__| ____ __ _____ ___\n / /_\\ \\_ __ \\_/ ___\\| | \\ | | | |/ \\| | \\ \\/ /\n/ | \\ | \\/\\ \\___| Y \\ | |___| | | \\ | /> <\n\\____|__ /__| \\___ >___| / |_______ \\__|___| /____//__/\\_ \\\n \\/ \\/ \\/ \\/ \\/ \\/\n \n\nOS: Archlinux \\s Kernel: \\r Processor: \\m Terminal: \\l Users: \\u\n\ncomhack@xx.xxx.xxx.xxx's password: For more information about how artist and game makers exploted the glow effect of CRT, an interesting article here can be read:
\nWhat a Wonder is a Terrible Monitor — December 4, 2012\n( http://ascii.textfiles.com/archives/3786 )
\n.--. /\\ ____\n'--' /__\\ (^._.^)~ <(o.o )>\n\n.g@8g. db\n'Y8@P' d88b\n\n:$#$: \"4b. ':.\n:$#$: \"4b. ':.To install node.js go to http://nodejs.org/ and install the latest copy of node.js .
\nC:\\Windows\\System32>npm install\nError: ENOENT, stat 'C:\\Users\\<Your User Account Name>\\AppData\\Roaming\\npm'\nError: EPERM, open 'C:\\Windows\\System32\\npm-debug.log'\nIf you get this error, it means that this folder C:\\Users\\<Your User Account Name>\\AppData\\Roaming\\npm just plain doesn't exist and you should feel bad. Actually, just create that folder, and you will be good to go.
=====================
\nTo make life with node.js easier, you should really spend some time to understand how to use a package manager. Below is some commands you should note, especially when starting a project.
\nOn start of a node.js project. Type npm init on the root of your project folder. .
So how do you start a node.js project folder?
\nOn the root folder of a node.js project you should type npm init.
npm init\n:\t It will ask you a set of questions, e.g. versionm description, entry point (like main() in C, but "int.js" etc...) ,, git repot, etc.... Once you answer the question, it will show a prevew of the content of the package.json
This will generate a package configeration file that might look like:
\n{\n "name": "javascripting",\n "version": "1.0.0",\n "description": "",\n "main": "introduction.js",\n "scripts": {\n "test": "echo \\"Error: no test specified\\" && exit 1"\n },\n "author": "",\n "license": "ISC"\n}\nUnlike other languages like say python. In node.js installing a package will be local only to the folder itself, it's locally scoped (like in python virtural enviroment). So installing a package in one folder, does not mean it will be present in another. This might seem annoying now, but it makes versioning easier
\nSo with the example of the package 'exampleProj', how do you install or uninstall temporarily for a project (Temporary, in the sense that it is not recorded as a dependency in project.json)?
\nnpm install exampleProj\n:\tThis command will do a local install to a folder
npm uninstall exampleProj\n:\tThis command will do a local install to a folder
You will be using these above commands for temporary development work.
\nSo when you actually do want to record a dependency (so that it will be autoinstalled on npm install command). Then you will be using the --save switch in npm.
npm install exampleProj --save\n:\tThis command will install and record the dependency to project.json
npm install exampleProj@3.2.3 --save\n:\tThis command is similar to above, but is restricted to a version.
npm uninstall exampleProj --save\n:\tThis command will uninstall and record the removal of the dependency to project.json
npm install\n:\tThis command will read the dependency tag for package version, and install all missing packages that is necessary to make the project work quickly. You will be using this for deployment of code to clients etc...
npm uninstall\n:\tThis command will read the dependency tag for package version, and remove all installed packages that matches these dependencies.
npm outsdated\n: \tThis is for keeping track of versining and if we should upgrade any of the dependenceies.
\n", "date_published": "2015-01-10T11:32:00Z" }, { "id": "/blog/2015/01/02/reverse-engineering-rrd-102-v2.0-fm-radio-module-with-rds-decoding-capability/", "url": "/blog/2015/01/02/reverse-engineering-rrd-102-v2.0-fm-radio-module-with-rds-decoding-capability/", "title": "Reverse Engineering RRD-102 V2.0 FM Radio Module With RDS decoding capability", "content_html":"To solve the issue of not knowing what song was playing over the radio, I am looking to create an FM display that shows a log of the (Radio Data System) RDS signal that is included in all broadcast FM stations (Incidentally short news, song title, station names, can be found via RDS). Looking at ebay for a cheap radio module, I came across this radio module ( PCB model RRD-102 V2.0) that breaks out the relevant pins of the RDA5807M Broadcast FM radio tuner IC. I chose this chip because it has RDS decoding capability baked into the device itself already (greatly reducing the amount of work needed to decode the RDS signal).
\nUnfortunately like many things in life, you do get what you pay for. This module did not come with any documentations (unlike the TEAxxx module which cost a bit more, but have bigger community support around it). At the very least, the datasheet for this device can be found (you can contact me for it, or check if I included it in this page), which shows the pinout of the actual chip itself.
\nUsing the pinouts from the datasheet, I was able to trace out which wires goes where, and below you can see the resulting pinout for this module. I am also able to confirm that the I2C pins labels are correct, as I am able to interface with it via the BUS_PIRATE electronic tool.
\nIf you are looking for the pinout, you can find it here below. Do note that SDIO==SDA and SCLK==SCK (since they are both I2C pins). Also make sure to place a pull up resistor for each I2C pins. Lastly note that this is a 3.0V device (so 3.3V VCC input will work well, but a 5V input will kill it)
\nNext step now, is to communicate with the module, but that is a story for another time.
\nPlease comment below or email me if you found this useful!
\n\n\nnote: N/C ~= Unconnected Pins\n\n\t\t\t\t{FRONT}\n\n -------------------------------------\n\t|\t\t\t\t\t\t\t\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t1)-SDIO\t\t\t\t\t FM-Aerial-(10\n\t|\t\t|\t|\t|\t|\t|\t\t\t|\n\t|\t\t-----------------\t\t\t|\n\t2)-SCLK\t|\t\t\t\t|\t\tN/C-(9\n\t|\t\t| RDA5807M \t\t|\t\t\t|\n\t|\t\t| Broadcast\t\t|\t\t\t|\n\t3)-N/C\t| FM Tuner \t\t|\t ROUT-(8\n\t|\t\t-----------------\t\t\t|\n\t|\t\t|\t|\t|\t|\t|\t\t\t|\n\t4)-N/C\t\t\t\t\t\t LOUT-(7\n\t|\t\t\t\t\t\t\t\t\t|\n\t|\t\t---------------------\t\t|\n\t5)-VCC\t| 32.768Mhz Crystal\t|\tGND-(6\n\t|\t\t---------------------\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t-------------------------------------\n\n\n\t\t\t\t{BACK}\n\t\t\t\t\n\t-------------------------------------\n\t|\t\t\t\t\t\t\t\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t)\t\t\t\t\t\t\t\t\t(\n\t|\t\t\tRRD-102\t\t\t\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t)\t\t\t\t\t\t\t\t\t(\n\t|\t\t\tVer: 2.01\t\t\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t)\t\t\t\t\t\t\t\t\t(\n\t|\t\t\t\t\t\t\t\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t)\t\t\t\t\t\t\t\t\t(\n\t|\t\t\t\t\t\t\t\t\t|\n\t|\t\t---------------------\t\t|\n\t)\t\t| 32.768Mhz Crystal\t|\t\t(\n\t|\t\t---------------------\t\t|\n\t|\t\t\t\t\t\t\t\t\t|\n\t-------------------------------------\n\t\n\n?\n General\t\t\t\t\tProtocol interaction\n ---------------------------------------------------------------------------\n ?\tThis help\t\t\t(0)\tList current macros\n =X/|X\tConverts X/reverse X\t\t(x)\tMacro x\n ~\tSelftest\t\t\t[\tStart\n #\tReset the BP \t\t\t]\tStop\n $\tJump to bootloader\t\t{\tStart with read\n &/%\tDelay 1 us/ms\t\t\t}\tStop\n a/A/@\tAUXPIN (low/HI/READ)\t\t"abc"\tSend string\n b\tSet baudrate\t\t\t123\n c/C\tAUX assignment (aux/CS)\t\t0x123\n d/D\tMeasure ADC (once/CONT.)\t0b110\tSend value\n f\tMeasure frequency\t\tr\tRead\n g/S\tGenerate PWM/Servo\t\t/\tCLK hi\n h\tCommandhistory\t\t\t\\\tCLK lo\n i\tVersioninfo/statusinfo\t\t^\tCLK tick\n l/L\tBitorder (msb/LSB)\t\t-\tDAT hi\n m\tChange mode\t\t\t_\tDAT lo\n o\tSet output type\t\t\t.\tDAT read\n p/P\tPullup resistors (off/ON)\t!\tBit read\n s\tScript engine\t\t\t:\tRepeat e.g. r:10\n v\tShow volts/states\t\t;\tBits to read/write e.g. 0x55;2\n w/W\tPSU (off/ON)\t\t<x>/<x= >/<0>\tUsermacro x/assign x/list all\nHiZ>P\nCommand not used in this mode\nHiZ>m4\nSet speed:\n 1. ~5KHz\n 2. ~50KHz\n 3. ~100KHz\n 4. ~400KHz\n\n(1)>1\nReady\nI2C>0\nWRITE: 0x00 ACK \n\n(1)>3\nDisplay format set\nI2C>(1)\nSearching I2C address space. Found devices at:\nWarning: *Short or no pull-up \n\nI2C>P\nPull-up resistors ON\nWarning: no voltage on Vpullup pin\nI2C>(1)\nSearching I2C address space. Found devices at:\nWarning: *Short or no pull-up \n\nI2C>P\nPull-up resistors ON\nWarning: no voltage on Vpullup pin\nI2C>v\nPinstates:\n1.(BR)\t2.(RD)\t3.(OR)\t4.(YW)\t5.(GN)\t6.(BL)\t7.(PU)\t8.(GR)\t9.(WT)\t0.(Blk)\nGND\t3.3V\t5.0V\tADC\tVPU\tAUX\tSCL\tSDA\t-\t-\nP\tP\tP\tI\tI\tI\tI\tI\tI\tI\t\nGND\t0.00V\t0.00V\t0.00V\t0.00V\tL\tL\tL\tL\tL\t\nI2C>P\nPull-up resistors ON\nWarning: no voltage on Vpullup pin\nI2C>?\n General\t\t\t\t\tProtocol interaction\n ---------------------------------------------------------------------------\n ?\tThis help\t\t\t(0)\tList current macros\n =X/|X\tConverts X/reverse X\t\t(x)\tMacro x\n ~\tSelftest\t\t\t[\tStart\n #\tReset the BP \t\t\t]\tStop\n $\tJump to bootloader\t\t{\tStart with read\n &/%\tDelay 1 us/ms\t\t\t}\tStop\n a/A/@\tAUXPIN (low/HI/READ)\t\t"abc"\tSend string\n b\tSet baudrate\t\t\t123\n c/C\tAUX assignment (aux/CS)\t\t0x123\n d/D\tMeasure ADC (once/CONT.)\t0b110\tSend value\n f\tMeasure frequency\t\tr\tRead\n g/S\tGenerate PWM/Servo\t\t/\tCLK hi\n h\tCommandhistory\t\t\t\\\tCLK lo\n i\tVersioninfo/statusinfo\t\t^\tCLK tick\n l/L\tBitorder (msb/LSB)\t\t-\tDAT hi\n m\tChange mode\t\t\t_\tDAT lo\n o\tSet output type\t\t\t.\tDAT read\n p/P\tPullup resistors (off/ON)\t!\tBit read\n s\tScript engine\t\t\t:\tRepeat e.g. r:10\n v\tShow volts/states\t\t;\tBits to read/write e.g. 0x55;2\n w/W\tPSU (off/ON)\t\t<x>/<x= >/<0>\tUsermacro x/assign x/list all\nI2C>W\nPOWER SUPPLIES ON\nI2C>v\nPinstates:\n1.(BR)\t2.(RD)\t3.(OR)\t4.(YW)\t5.(GN)\t6.(BL)\t7.(PU)\t8.(GR)\t9.(WT)\t0.(Blk)\nGND\t3.3V\t5.0V\tADC\tVPU\tAUX\tSCL\tSDA\t-\t-\nP\tP\tP\tI\tI\tI\tI\tI\tI\tI\t\nGND\t3.24V\t4.80V\t0.00V\t3.22V\tL\tH\tH\tH\tH\t\nI2C>v\nPinstates:\n1.(BR)\t2.(RD)\t3.(OR)\t4.(YW)\t5.(GN)\t6.(BL)\t7.(PU)\t8.(GR)\t9.(WT)\t0.(Blk)\nGND\t3.3V\t5.0V\tADC\tVPU\tAUX\tSCL\tSDA\t-\t-\nP\tP\tP\tI\tI\tI\tI\tI\tI\tI\t\nGND\t3.29V\t4.80V\t0.00V\t3.31V\tL\tH\tH\tH\tH\t\nI2C>(1)\nSearching I2C address space. Found devices at:\n0b00100000(0b00010000 W) 0b00100001(0b00010000 R) 0b00100010(0b00010001 W) 0b00100011(0b00010001 R) 0b11000000(0b01100000 W) 0b11000001(0b01100000 R) \n\n\nSince we got the pinouts, we could perhaps use these ready made libs etc...
\nThis is useful for those who is seeking a way to interface directly to a Posiflex PP7000II, with a micro controller. This was done by looking at the pcb board of the usb printer adapter for the Posiflex PP7000II printer. Read this if you have a similar printer, and you are hoping to interface to it via say an arduino, or a PIC, or AVR, or even a raspberry pi.
\nOn the PCB board, the main component that does the serial to usb conversion is the "FTDI FT232BM 518-1" chip. I previously tried to get the adapter to work normally, but however the driver for the printer was too old, and the manufacture no longer supplies the driver for it. This would usually mean that this printer would go to the landfill, but aside from the driver issue, it was a perfectly good working printer (Which is quite a shame that manufactures would create products that they would eventually render as obsolete, forcing it into the landfill. I'm looking at you ink jet manufactures).
\nAnyway straight to business. Here is the results by tracing the pinouts from the FT232BM converter ICs to the header pins that connects to the printer.
\nGND = 0V\nVCC = 5V\nTxD = Printer Transmit Pin\nRxD = Printer Recieve Pin\nDSR = Data Set Ready\nRTS = Ready TO Send\nRST = RESET ( i think...)\n\n{ Pins from printer facing upwards }\n| GND | GND | GND | VCC | VCC |\n| RST# | DSR# | RTS# | TxD | RxD | \n\n`````\n\n\n```\nGND = 0V\nVCC = 5V\nTxD = Adapter Transmit Pin\nRxD = Adapter Recieve Pin\n\n{ Pins from adapter to slot into printer adapter port}\n| GND | GND | GND | VCC | VCC |\n| RST# | DTR# | CTS# | RxD | TxD | \n\n```\n\n```\nDTR - Data Terminal Ready\nDSR - Data Set Ready\nRTS - Request To Send\nCTS - Clear To Send\n\nRTS --> CTS\n\nDTR --> DSR\n```\n\n\n\n## Raw Reverse Engineering log: \n\n```\nInterface is a serial 5V pinout, which is shown in the back already.\n\nCurrently using an FTDI chip to make it work. Via Hercules SETUP utility by HW-group.com\n\nSerial setup as 19200 baud, 8 bits, no parity, with RTS/CTS handshake, at Mode Free.\n\nSuspected to accept ESC / POS commands\n\ne.g.\n\nPrint text:\n0x1B , "@Hello World" :- Prints Hello World, auto wordwrap\n\n0x1B , "@Hello World", 0x0A :- Gets a "Hello World" text printed in the thermal paper and then increment paper.\n\n0x1B , "-@Hello World", 0x0A :- Gets an UNDERLINED "Hello World" text printed on next line feed.\n\n0x1D, B, 0x1B, "Black or White", 0x0A :- Creates a black and white print of "Black or White"\n\nFEED paper:\n0x0A :- Moves the thermal paper up once.\n\nBeep:\n0x1B, o :- Beeps a sound using the internal speaker in printer\n\nCut Paper:\n0x1D, V, 0 :- Auto feeds 1 inch and then, Full Cut (Reverts to partial cut if full cut cannot be done)\n0x1D, V, 1 :- Auto feeds 1 inch then, Partial cut\n\n\n----------\n\n0x1B :- Hex ASCII code for Escape command\n0x0A :- Hex ASCII code for Line Feed\n0x1D :- Hex ASCII code for GS control character (Group Separator)\n@ :- ASCII command char for printing a line of text\n\n=-----\n\nhttp://support.epostraders.co.uk/support-files/documents/21/XRx-PP7000-II-PP7000IIU_Technical_Information.pdf\n\nhttp://printarduino.blogspot.com.au/2010/02/arduino-and-thermal-printers.html\n\nhttp://content.epson.de/fileadmin/content/files/RSD/downloads/escpos.pdf pg 6\n\nhttp://support.epson.ru/products/manuals/000350/part1.pdf\n\nhttp://nicholas.piasecki.name/blog/2009/12/sending-a-bit-image-to-an-epson-tm-t88iii-receipt-printer-using-c-and-escpos/\n \n\n-------------\n\nOn installing an ESC/POS driver for this serial printer\n\nhttp://www.kbytes.co.uk/Articles.asp?articleid=58 - installing generic drivers\n\nTrying out EPSOM> EPSOM ESC/P Standard 10 V4 Class driver\n\n-------\n```Was working on improving this jekyll blog, when I cam across the issue of truncating blog post for the front page view.
\nBy default it only shows the first paragraph with ``. However I wanted to show pictures. Thus...
\nThere is 3 approaches I could have done here.
\n\nLimit post by number of words. But this may cut off html tags, thus messing up the presentation. {{ post.content | truncatewords: 50 }} or you could try stripping html, but you lose images. which is unacceptable to me. {{ post.content | strip_html | truncatewords: 50 }}
Truncate by paragraph like shown in this stack overflow page. This is not as bad, but it lack the ability to control presentation.
\n\n{%- set truncatedContent = '' %}\n{%- set paragraphs = post.content | split:'</p>' %}\n{%- for paragraph in paragraphs limit:N %}\n\t{{ truncatedContent | append: paragraph }}\n\t{{ truncatedContent | append: '</p>' }}\n{%- endfor %}\n\nTruncate by splitting at <!--more--> (which is how wordpress typically does things). Here is an example from http://mikeygee.com/blog/truncate.html :
\n{%- for post in site.posts limit:10 %}\n\t<div class="post-preview">\n\t\t<h2><a href="{{ post.url }}">{{ post.title }}</a></h2>\n\t\t<div class="post-date">{{ post.date | date: "%B %d, %Y" }}</div>\n\t\t{{ post.content | split:'<!--break-->' | first }}\n\t\t{%- if post.content contains '<!--break-->' %}\n\t\t\t<a href="{{ post.url }}">read more</a>\n\t\t{%- endif %}\n\t</div>\n\t<hr>\n{%- endfor %}\n\nI chose option 3, since it gives most flexibility. However my issue with this previous code is that it doesn't stick to the standard of wordpress using <!--more--> as the tag. Also if I forget to place the <!--more--> tag, then the entire post just gets dumped into the front page. This is undesirable. Thus the code was customised as shown below to correct for this issue.
If the <!--more--> tag is detected, then an excerpt based on <!--more--> is used. If <!--more--> is not detected then by default the first paragraph is used instead.
\n{%- if post.content contains '<!--more-->' %}\n\t{{ post.content | split:'<!--more-->' | first }}\n{%- else %}\n\t{{ post.excerpt }}\n{%- endif %}\n\t<a href="{{ post.url }}">read more</a>\n\nIf you like this, then dont forget to credit the modification to me, and the original code to mikeygee http://mikeygee.com/blog/truncate.html .
\nReference:
\nGot some barcode scanner off ebay. It's the usb type 1d barcode scanner. Model type MJ-4209 .\n![\"A](\"/projects/barcode_scanner/MJ-4209_scanner_small.JPG\")
It came with a manual full of barcodes that allows for scanning it to set settings.
\nOne of it was for version control. Which when scanned gave:
\nMJ_tech V3.00 2014/03/01\nIf you need a copy of the manual, here it is:
\nIf you need the pinout, for the scanner, then here it is as well from the datasheet for MJ-4209
\nInteresting side note to observe:
\nCAT5 ETHERNET CABLE:\nPin Number\tStrand color\n1\torange stripe\n2\torange\n3\tgreen stripe\n4\tblue*\n5\tblue stripe*\n6\tgreen\n7\tbrown stripe*\n8\tbrown*\n\nEthernet Pinout Front View: \n ______________________ \n / \\ \n / \\ \n+--------------------------+\n| 8 7 6 5 4 3 2 1 |\n| |\n+-----+ +-----+\n +--------------+ \n\nSRC: \n* http://www.gnswireless.com/bulk_cat5e_ethernet_cable.htm\n* http://www.cscape.net/modplugstandard.htmlThis two will allow you to interface with the device using a normal Ethernet cable modified to tap into those pins (remember to ensure the RX and TX lines are not twisted).
\nIf an Ethernet cable has the correct configuration, we can save time by just using the colours. Recall the pinout for both the scanner and Ethernet. So when combined:
\nEthernet cable pinout Vs scanner pinout:\n(Ethernet uses 8pin, scanner port uses 10pin\n\n EthPin# | Eth Cable colour | ScanPin# | scanner pin function\n-----------------------------------------------------------\n\t\t\t\t\t\t\t|\t1\t\t|\t NC\n\t1\t |\torange stripe\t|\t2\t\t|\t +5V\n\t2 |\torange\t\t\t|\t3\t\t|\t GND\n\t3 |\tgreen stripe\t|\t4\t\t|\t RXD\n\t4 |\tblue*\t\t\t|\t5\t\t|\t NC\n\t5 |\tblue stripe*\t|\t6\t\t|\t NC\n\t6 |\tgreen\t\t\t|\t7\t\t|\t NC\n\t7 |\tbrown stripe*\t|\t8\t\t|\t RTS\n\t8 |\tbrown*\t\t\t|\t9\t\t|\t TXD\n\t\t\t\t\t\t\t|\t10\t\t|\t CTS\nSo judging from the pinout. The standard Ethernet cable can connect pretty much everything, except for the CTS line. (Luckily) This will not matter for our purpose, as I plan to just use 5V,GND,RX & TX lines only, using software flow control.
\nThus using typical Ethernet cable would be wired as this:
\nStripedOrange == 5V | Orange == GND | GreenStripe == RXD | Brown = TXD
\nI got a spare ethernet cable, I got an FTDI FT232RL SERIAL/USB dongle, and I got a scanner.
\nSo, basically, I cut the ethernet cable in half (using the above cable colour direction as a guide), wired the RX to the TX of the dongle and the TX to the RX of the dongle. Hooked up the power supply rails. Plug the serial/usb dongle, and boot up a serial console.
\n|\tETHERNET CABLE\t\t|\t\t|\tSERIAL TO USB\t\t|\n| Connected to MJ-4209\t|\t\t|\tConverter\t\t\t|\n| 1D Barcode Scanner\t|\t\t|\tFT232RL (By FTDI)\t|\n|=======================|\t\t|=======================|\n|\t\t\t\t\t\t|\t\t|\t\t\t\t\t\t|\n|\tStripedOrange | +5V |:-----:| +5V |\tPower Rail Upper|\n|\tOrange \t\t | GND |:-----:| GND | Power Ground\t|\n|\t\t\t\t\t\t|\t\t|\t\t\t\t\t\t|\n|\tGreenStripe\t | RXD |:- -:| RXD | Serial Receive\t|\n|\t\t\t\t\t\t| \\ /\t|\t\t\t\t\t\t|\n|\t\t\t\t\t\t|\tX <--crossover (not joined)\t|\n|\t\t\t\t\t\t| / \\\t|\t\t\t\t\t\t|\n|\tBrown\t\t | TXD |:- -:| TXD | Serial Transmit\t|\n\nWhen done, it shall look like this:
\n![\"A](\"/projects/barcode_scanner/1D_scanner_to_FTDIdongle.jpg\")
Now, I set the scanner to "UART 9600, NO, 8, 1" ( Using the document manual called "Manual Guide" that you can find in this page).
\nAfter that, when I scan the MJ_tech demo barcode, it actually showed up! However, it didn't have newline inbetween, so hard to tell which is a new barcode. So in the "Data Edit Setting" I switch the scanner to use "CR+Skip" \\r\\n, but you could also use\n"skip" \\n, or TAB \\t. Depends on how you code the destination microprocessor's firmware (Or PC etc...).
This is what it looks like when you use CR \\r only:
MJ_techMJ_techMJ_techMJ_tech\nThus in general, you would prefer to use either "skip" \\n or "CR+Skip" \\r\\n
MJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nMJ_tech\nSo that's it! You got it interfacing over UART! (Oh and btw, I used the Arduino serial console to talk to the FT232RL. It was set to 9600 baud, set to "Both NL & CR" )
\nIt means you could potentially hook this to a microcontroller, or an arduino project, since you now know the pinout of the serial uart cable for this scanner.
\nWhat can you do with this capability? Well how about this idea. Automated inventory management on the cheap etc...
\nLet me know if this is helpful to you on the comments below XD
\nHere are the characteristics from the same datasheet:
\nNet weight : 115 g\nMaterial : ABS+PC\nVoltage : 5 V +/- 10%\nCurrent:110mA , idle 10mA\nColor: gray, black\n\nPerformance Characteristics::\n\nScanner type:\t\t bi-directional\nLight source:\t\t 650nm Visible laser diode\nScanning Rate:\t\t 100 scans per second\nScanning distance:\t 2.5mm-600mm\nScanning scope:\t\t 18CM\nPrint contrast:\t\t 25% minimum reflective difference\n①Roll(tilt):\t\t +/- 30degrees\n②Pitch:\t\t\t\t +/- 45 degrees\n③Skew(yaw):\t\t\t +/- 60 degrees\nDecodeCapability:\tUPC/EAN, UPC/EANwithsupplementalsCode128, UCC/EAN128, Code39Code39FullASCII, Code128FullASCII, Codabar, Interleaved2of5, Code93, MSI, Code11, ISBN, ISSN, china post code, etc\nBit error rate:\t\t 1/500million\nResolution:\t\t\t 4mil(0.1mm)\nTip :\t\t\t\t buzzer and led\nScanning mode :\t\t Press button, Automatic continuous scan Auto-induction,\nWorking times of button :\t 3 million times\nWorking hours of laser:\t\t 10000hours\nInterfaces supported:\t\t RS232,keyboard wedge, USB.\nCable length:\t\t\t\t 2M\n\nUser Environment::\n\nWorking temperature:\t 0oC-45oC\nStorage temperature:\t -400oC-60oC\nRelative humidity:\t\t 5%-95%(Non-condensing)\nAnti-shock design:\t\t withstand 1.8M drops\nAmbient light immunity:\t immune to direct exposure of normal office and factory lighting conditions, As well as direct exposure to sunlight.\n\nRegulatory::\n\nElectrostatic discharge:\t certified to ±15KV air discharge and ±8KV of contact discharge\nEMI/RFI:\t\t\t\t\t FCC Part 15 Class B,European Union EMC Directive,Taiwan EMC,CE\nLaser safety:\t\t\t\t CDRH Class II,IEC Class 2\nenvironmental protection:\t certified to RoHS directive 2002/95/EEC\nRelated:
\nJust found out about this really curious piece of kit. It is a tiny chip with an embedded ARM microprocessor and a wifi stack all miniturised into one tiny surface mount chip. Cheap to boot too!
\n\nRight now, I am just learning how to use it. So my first configuration is to hook the module up to a serial dongle.
\n\n\n\nThe Seeed tutorial is written for the version 1 module with a 57600 baud rate serial link. The version 2 module that is currently shipping runs at 115200 bps.
\n
\nThis is what my module looks like. You can get it cheap from ebay\nThe newer module has LEDs near the antenna\n\n _________________________________________________________________\n\t|\t\t\t\t \t__________\t\t\t\t\t\t\t\t\t|\n\t|\t\t\t\t\t|\t\t |\t\t\t\t\t\t\t\t\t|\n\t|\t|\t\t\t\t| EEPROM |\t\t\t(RX)\t\t(VCC)\t\t|\n\t|\t|___\t\t\t|________|\t\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t_________________\t\t(GPIO0)\t\t(RESET)\t\t|\n\t|\t|___\t|\t|\t\t\t\t|\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t|\tESP8266\t\t|\t\t(GPIO2)\t\t(CH_PD)\t\t|\n\t|\t|___\t|\t| Wifi+ARM_MCU |\t\t\t\t\t\t\t\t|\n\t|\t____|\t|\t|_______________|\t\t(GND)\t\t(TX)\t\t|\n\t|\t|_______|__\t\t\t\t\t\t\t\t\t\t\t\t\t|\n\t|_______________________________________________________________|\n\t\n\tRX\t\t:\tUART Receive Pin (Connects to TX of other device)\n\tVCC\t\t:\t3.3V Upper Power rail (Input power)\n\tGPIO0\t:\tGeneral Purpose Input Output (0)\n\tRESET\t:\tReset Device\n\tCH_P2\t:\tGeneral Purpose Input Output (2)\n\tCH_PD\t:\tChip Enable Pin (pull high)\n\tGND\t\t:\t0V Power Ground\n\tTX\t\t:\tUART Transmit Pin (Connects to RX of other device)\n\t\n\t\nFeel free to copy and reuse this diagram. Just remember to credit me. ( briankhuu.com )\n\tSo far I have wired it up, but suspect the board is using a higher firmware version and thus require CH_PD to be tied to 3.3V VCC. However no dice, but the LEDs on the modules started flashing randomly, as well as the serial dongle... on both RX and TX, even when I'm not sending any characters. The output is garbage regardless of baud rate.
\nI think the issue here, is that this is a big of a power hog and the FTDI chip included is not powerful enough to power it. So you'll want to hook a dedicated linear voltage regulator (or boost/buck regulators if you can afford to).
\n\n+------------+ \n| XX | \n| XX XX | \n| XX | \n+------------+ \n| | \n| LM39401T | \n| 3.3V LDO | \n| (LM3940) | \n| | \n+-+---++---+-+ \n || || || \n || || ||<----+ 3.3v output \n || || \n || ||<--------+ 0v Ground (Gnd)\n || \n ||<------------+ 5v - 3.3v Input \nNow when I plug it in, the board starts to light up more brightly.
\nOpening up the arduino serial console on 9600 bps as my baud rate setting. (seems that 115200 bps just get garbage characters. This also includes 57600 bps ). Seems that newer modules are distributed with slow serial links by default. I have a feeling it's popularity with the maker community that is full of Arduino users may have something to do with it.
\nAs soon as I pull the RESET pin of the ESP8266 down to ground and release it. This is what I got:
\n<\n[System Ready, Vendor:www.ai-thinker.com]\nNot sure what the initial garbage data means, but at least it seems the serial link to the module is now operational.
\nHere we try out AT+RST for resetting board, and AT+CWMODE for checking wifi mode.
AT+RST\n\n\nOK\nc_ÇÏRSöfJSúfJ[úfì\n[System Ready, Vendor:www.ai-thinker.com]\nAT+CWMODE\n\nno this fun\n"no this fun" ... huh? well that's kind of a funny response. I guess that means we are not connected to anything. Which is true.
\nSo what's my firmware version number? Use AT+GMR
AT+GMR\n\n0018000902\nAT+GMR\n: Show firmware version
\nAT+RST\n: restarts module
\nAT+CWMODE=3\n: Change working mode to mode 3. This stands for AP+STA (Access Point Station)
\nAT+CWLAP\n: Find and list wifi spots
\nAT+CIFSR\n: Show IP address assigned to the module by the router
\nAT+CWJAP="SSID NAME", "PASSWORD"\n: Connect to said access point
\nAT+CWJAP=?\n: Check if connected successfully
\nAT+CWJAP?\n: Same as AT+CWJAP=? but for some modules where the other command doesn't work.
AT+CIPMUX=1\n: Allow for multiple connections
\nAT+CIPSTART=4,"TCP","192,168.1.104",9999\n: connect to remote TCP server @ 192,168.1.104 (E.g. your PC)\n: Port number 9999
\nAT+CIPMODE=1\n: Optional switch into data transmission mode
\nAT+CIPSEND=4,5\n: Send data via channel 4, 5 bytes length. Auto unlinks, when no data is being transmitted.\n: e.g. Serial.print("AT+CIPSEND=");
\nAT+CIPSEND=5\n: Send data via channel 5 bytes length. Auto unlinks, when no data is being transmitted.
\ne.g. To send the header "GET / HTTP/1.0\\r\\n" lets start by connecting to server
\nAT+CIPMUX=0 \nOK \n\nAT+CIPSTART="TCP","173.194.123.5",80 \nOK Linked \nNow start sending msg to server. There is 15 chars (or bytes) in "GET / HTTP/1.0\\r\\n"
\nAT+CIPSEND=16\nNow send the data after waiting for the > character
> <-- wait for this character to come in
Then send this response (remember \\r and \\n are both single characters)
GET / HTTP/1.0\\r\\n
AT+CIPSERVE=1,9999\n: =1 means enable, =0 means disable\n: setup TCP server on port 9999
\nAT+CIFSR\n: Check module IP address
\nHaven't yet connected this device to a router, but that's pretty much the next step. Being able to see a wifi network is pretty cool already.
\nReferences
\nBtw http://www.instructables.com/id/Guino-Dashboard-for-your-Arduino/?ALLSTEPS is pretty cool. It's a GUI dashboard for your arduino. Very handy for debugging.
\n", "date_published": "2014-12-01T14:54:00Z" }, { "id": "/blog/2014/11/24/algorithmic-javascript-playground-toy/", "url": "/blog/2014/11/24/algorithmic-javascript-playground-toy/", "title": "Algorithmic Javascript Playground Toy", "content_html":"Here is a collection of javascript programming toys for you to try out. (heck you can even download it), where you can create algorithmic art using code. It was developed when I found that you can actually read the content of a url after the # sign.
Direct link to folder: link
\nurlhashloader.html : First file written. It's just a simple read and display kind of thing. Quite simply it is a platform for enabling remixable content shared via data embedded in the hash fields of urls (via javascript). E.g. shareable algorithmic music Feel free to remix and reuse, but please leave credit.
\nimageGen.html : This is a simple black and white image generator, with some gradient capability. It was my second experiment.
\nimageAlgoGen.html : This is a remixable algorithmic image generator.
\nalgoCanvasPlayer.html : This is a remixable algorithmic animation generator. Uses similar codes to imageAlgoGen but includes a t for time variable, which allows for animated scenes.
\nalgoMusicPlayer.html : Lets you play any algorithmic music. E.g. Try "Math.round(255 * Math.random());" . A test tone is played when this page is opened. ( 8Khz )
\nHow does this 'save/load' to url work? If you look at the codes below from urlhashloader, it should make sense.
\nEssentially the informations after the hash in the url is stored in window.location.hash . It is exposed to javascript to enable the back button of a browser to work, even for a fully javascript based website. E.g. Facebook uses it so that you can still go back to a particular page in the site, even if it is dynamically loaded via javascript.
So what this script does, is first loads the hash content to a variable named hash. It is then saved to a global container via document.getElementById("hashContent").value. This is how we "load url hash" process.
Do note that you cannot change the window.location.hash in the url field without having to refresh the page. This is why we have the loadHash() function, to change window.location.hash first, and then reload the entire page. This is how we "save url hash", since the url is now updated (because we refreshed the page) and thus is now copyable by the user.
\nJust note that there is an issue of firefox converting %25 to %%, which messes the encoding up. Thus until it is fixed, I am using a hack to work around it.
Here is something you might find interesting. This is a HTML5 text to speech shoutbox . This works best for chrome browser, and is a recent addition to HTML5. This is quite a useful little program that you might want to know better. It's more of a toy at the moment, but I'm sure you can still find use for it.
\nDEMO: http://briankhuu.com/shoutbox/shoutbox_TTS.html
\nSource Code: http://briankhuu.com/shoutbox/src/
\n\nVersion list:\nV7 - reducing polling, and ability to turn off TTS\nV6 - Shows last updated\nV5 - Fixed crash when not find TTS\nV4 - Generate time elapsed since last post\nV3 - Limit number of stored post to 100 posts.\nV2 - Generate last updated status image\nV1 - Start of first working shoutbox
\nThis is a mish mash of various codes to make a good platform for semi real time speech synth chatroom (Which would be good for web radio etc...)
\nMashup of codes by Brian Khuu (briankhuu.com) 2014
\nUsage:\nPlace these files into a properly configered php webserver in /shoutbox/ folder (script must be able to create files). Then run either shoutbox.html for a low speed shoutbox (updates every 10 sec), and shoutbox_TTS.html for a highspeed shoutbox(3 sec update) with Text To Speech of any incoming messages.
\nConcept:\nTo possibly allow for semi-realtime conversation without having to read the messages. E.g. hosting a radio interview behind TOR
\nUSES CODES FROM:
\nHMTL5 Speech Synthsis API:\nMashed up by Brian Khuu briankhuu.com
\nhttp://updates.html5rocks.com/2014/01/Web-apps-that-talk---Introduction-to-the-Speech-Synthesis-API
\nLifted codes and styling from:
\nHTML code is very simple and comes from : http://instantchatbox.net/
\nThe licence for the javascript used above is :\n/***************************\n/\n//@Author: Adrian "yEnS" Mato Gondelle & Ivan Guardado Castro
\n//@website: www.yensdesign.com
\n//@email: yensamg@gmail.com
\n//@license: Feel free to use it, but keep this credits please!\n/***************************/
\nFor the backend, I used:
\nSIMPLE PHP GUESTBOOK v1.0 by Pasi Havia (roomeo@yahoo.com)
\nINSTALL NOTES
\n1. Unzip guestbook.zip\n2. Transfer all unzipped files to your webserver\n3. Change guestbook.txt file attributes so that it is writable by public. For example 'chmod 646 guestbook.txt'.\n4. You are ready to use! Just make a link to readbook.php or to addbook.php from your webpage.
\nThis guestbook is distributed under GPL license.
\nPasi Havia, 2nd April 2003
\nDiff-PDF (click here to go to the download page) is a very useful command line tool for comparing pdfs. Only issue is that there is a lack of GUI frontend to use this. This is quite annoying for occasional usage of this program, especially for the average user.
\n\nThus for anybody who really really needs this feature quickly, here is a good stopgap measure for those in windows. For linux users, it shouldn't be too hard to modify.
\nIt is a python script that ask for two files via GUI and runs it in diff-pdf. To use it, just drop it in the same folder as the binaries, and execute the script.
\n#### GUI FRONTEND SCRIPT FOR DIFF-PDF (guiDiffPDF) ####\n## Author: Brian Khuu 2014 briankhuu.com\n## Description: This script will ask you for two files,\n## and then open a visual mode diff.\n## In other platform, just change diff-pdf.exe\n## Install: Place in same location as diff-pdf.exe\n## Don't forget to put it in system path for handy access!\n## Tested: On windows 8 with python V3.1\n## Dependency: diff-pdf.exe @ https://github.com/vslavik/diff-pdf\nimport tkinter, sys\nimport tkinter.filedialog #https://mail.python.org/pipermail/python-list/2010-April/574512.html\n\nprogramPath = \"diff-pdf.exe\" ## FOR WINDOWS ONLY, MODIFY THIS IF IN... SAY LINUX\n\n## START GUI ##\nroot = tkinter.Tk() # open and start tkinter object\nroot.withdraw() # hide the root window\n## save sys.argv arguments (As file dialog changes it...) ##\noptArgV = sys.argv[1:] # optional ArgV.\n\n## ASK USER WHICH TWO FILES TO COMPARE ##\nfilePath1 = tkinter.filedialog.askopenfilename(title=\"Open First PDF - 1\")\nprint (\"pdf1: \"+filePath1+\"\\n\") #Display first filepath\nfilePath2 = tkinter.filedialog.askopenfilename(title=\"Open Second PDF - 2\")\nprint (\"pdf1: \"+filePath2+\"\\n\") #Display second filepath\n\n## Run the command line instruction ##\nfrom subprocess import check_output\nif ( len(optArgV) > 0 ): # pass though argument to diff-pdf.exe\n print( \"ARGUMENTS: \"+\" \".join(optArgV)+\"\\n\" )\n command = programPath+\" \"+\" \".join(optArgV)+\" \\\"\"+filePath1+\"\\\" \\\"\"+filePath2+\"\\\"\"\nelse: # Otherwise default to visual diff\n command = programPath+\" --view \\\"\"+filePath1+\"\\\" \\\"\"+filePath2+\"\\\"\"\nprint(\">> \"+command+\"\\n\")\nprint( check_output( command , shell=True) )\n\ninput(\"Press Enter to continue...\")Posted the solution also to https://github.com/vslavik/diff-pdf/issues/14
\n", "date_published": "2014-11-24T22:48:00Z" }, { "id": "/blog/2014/11/24/now-using-jekyll/", "url": "/blog/2014/11/24/now-using-jekyll/", "title": "Now Using Jekyll", "content_html":"It has been a while since this website has been updated. Previously I written custom PHP files to iterate over my blog post and display it using markdown to html converter (ParseDown). Maintaining it has become a hassle however, and thus I'm converting the site into Jekyll which is a static site generator (and thus no PHP needed). Of which the biggest advantage for me, is that the output is in simple HTML. Thus it is much more secure than coding a dynamic site to avoid holes that allows for malicious code to enter.
\n\nIt will take some time to get used to, as well as setting the whole system up.
\nThese are the two links I used to understand how to install jekyll in windows. Unfortunately, it is not as easy to setup in windows compared to linux. This is since you also need to install the windows ruby devkit installer as well standard ruby.
\nIn addition you need to install rogue gem install rouge before inserting highlighter: rouge in _config.yml
Let me know if you need a step by step script. But the links above should be good enough.
\nAlso, am using a modified version of the rakefiles below here. Very useful stuff:
\nBtw here is what my config looks like, hopefully this helps:
\n# Site settings\ntitle: Brian Khuu\nemail: mofosyne@gmail.com\ndescription: > # this means to ignore newlines until "baseurl:"\nMy name is Brian, I like coding, pixel arts, and electronics!\nbaseurl: "" # the subpath of your site, e.g. /blog/\nurl: "http://briankhuu.com" # the base hostname & protocol for your site\ntwitter_username: mofosyne\ngithub_username: mofosyne\nreddit_username: mofosyne
\n# Build settings\nhighlighter: rouge\npermalink: /blog/:categories/:year/:month/:day/:title.html\nmarkdown: redcarpet
\nBy default kramdown is chosen. But since I'm used to github style markdown, I chose to use redcarpet instead (which is also natively supported, so use that too!). Also rouge syntax highlighter is chosen, since the default setting doesn't work for windows.
\n(Just rememeber to install it via gem install rouge )
Sometimes you just gotta switch the date to an older time because a program checks for that. Well maybe this might be handy for you, if you are a windows 7 user:
\nJust copy the below code and name the file as tempdateset.bat. So when you click on it, you have a 10 sec window to activate the program and let it check the date before launching whatever program it is. Cheers.
@ECHO off\nECHO Temporary Date setter\nECHO Designed for windows 7. Run this as admin. \n\nset BEFOREDATE=%date:~4,10%\ndate 01-03-07\n\nECHO Now manually launch whatever you need before we revert back to the correct time.\n\nTIMEOUT 10\ndate %BEFOREDATE%\nECHO Date reverted\nTIMEOUT 5\nHoped it was helpful! Let me know if it works or doesn't work.
\n", "date_published": "2014-11-24T00:00:00Z" }, { "id": "/blog/2014/06/30/More_Exploration_Of_The_TL-WR703N/", "url": "/blog/2014/06/30/More_Exploration_Of_The_TL-WR703N/", "title": "More Exploration Of The TL-WR703N", "content_html":"This is a continuation of the experiment with TL-WR703n (Starting from the The_TL-WR703N_piratebox_exploration post) http://wiki.openwrt.org/toh/tp-link/tl-wr703n
\n![Image of the PCB][pcb]
\nJust remembered I got Tera Terminal, and if I remember, it should support ymodem
\nPreviously tried TFTP method:
\nhornet> tftpboot 0x81000000 openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin\nhornet> erase 0x9f020000 +0x3c0000\nhornet> cp.b 0x81000000 0x9f020000 0x3c0000\nhornet> bootm 9f020000
\nNow crafting up a process in Uboot after tpl at the "autoboot at 1 sec" or something
hornet> erase 0x9f020000 +0x3c0000\nhornet> loadb 0x81000000\n#\n# OVER HERE WE SEND VIA KERMIT\n#\nhornet> cp.b 0x81000000 0x9f020000 0x3c0000\nhornet> bootm 9f020000
\nMy interpretation of above
\nhornet> erase from 0x9f020000 to +0x3c0000\nhornet> loadb prepare to load to ram using kermit starting from 0x81000000\n#\n# OVER HERE WE SEND VIA KERMIT\n#\nhornet> cp.b copy from ram startng at 0x81000000 to flash mem position 0x9f020000 to 0x3c0000\nhornet> bootm start booting at 9f020000
\nSooo in the bit inbetween for Kermit serial modem (According to http://wiki.openwrt.org/doc/howto/generic.flashing.serial ) once all is setup, in tera term, go to file>Transfer>Kermit>Send and send openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin
\ndammit... no kermit mode?
\nPreviously i used a usb to ethernet adaptor on windows 8, but that was bunk.\nWhat ended up working, was to do the same process of using tftp on an older laptop with windows XP (possibly because it has a crappier protection system)\nWell that was interesting... At least I am back to square 1 rather than -1 or 1/0
\nSo lesson. Choose a laptop with embedded ethernet (or pick a good ethernet to usb adaptor). Or alternatively, learn linux lol. Or choose a board with a less stripped down uboot (or even better, with onboard web failsafe)
\nyea ya I know it was annoying to recover from this error, but I did get it back to normal.
\nSo I followed the previous attempt I did, of installing generic openwrt firmware, then the usb driver to mount the usb, before following the piratebox instruction more carefully.
\nBtw this method of installing usb support on generic unmodified openwrt firmware is recommeneded in http://daviddarts.com/piratebox-diy-openwrt/ . (But is rather outdated)
\nopkg update\nopkg install kmod-usb-uhci\ninsmod usbcore ## may return: file exists\ninsmod uhci\nopkg install kmod-usb-ohci ## may return: up to date.\ninsmod usb-ohci
\nAs usual the piratebox image installed now, but somehow doesn't run. Bah.
\nJust found https://github.com/pepe2k/u-boot_mod & https://forum.openwrt.org/viewtopic.php?id=43237 it has web based failsafe, this is definitely needed by me to avoid having to go though tftp again.
\nroot@OpenWrt:/# cat /proc/mtd\ndev: size erasesize name\nmtd0: 00020000 00010000 "u-boot"\nmtd1: 000ecf04 00010000 "kernel"\nmtd2: 002e30fc 00010000 "rootfs"\nmtd3: 000e0000 00010000 "rootfs_data"\nmtd4: 00010000 00010000 "art"\nmtd5: 003d0000 00010000 "firmware"\nroot@OpenWrt:/#
\nSo the uboot partition is at 0x20000 (128 KiB) and has size of 0x1000(64 KiB).
\nSoo lets craft a command to insert the modified firmware:
\nhornet> tftpboot 0x81000000 uboot_for_tl-wr703n.bin\nhornet> erase 0x9F000000 +0x10000\nhornet> cp.b 0x81000000 0x9F000000 0x10000\nhornet> #bootm 9f020000
\nCheck flash memory before rebooting
\nhornet> md 0x9F000000 #check flash\nhornet> md 0x81000000 #check memory we copied from\\
\nAfter that reboot and hope it all goes well. Well the answer is that it did. Now it's harder to brick :D . And I have given up on running piratebox on this dammn thing. Ah well, at least until I understand embedded linux more.
So anyhow to access the web failsafe in this modified firmware, just go to the Uboot console, and then type 'httpd'. It will then specify the IP address you have to connect to. Just connect to it at port 80, and you can take over from there :D (might need to set a static address e.g. 192.168.1.100 )
\nWell for my use, here is what you run after installing a generic image to get at least usb and internet running for opkg etc... (http://wiki.openwrt.org/doc/uci) :
\n# Connect the ethernet to the internet first!\n# /etc/config/network modification to connect to dhcp\n# 'uci show network' will show what values can be changed\nuci set network.lan.proto=dhcp\nuci commit\n/etc/init.d/network reload\n# Install latest squashfs-sysupgrade.bin\n# This updates BusyBox v1.19.4 & OpenWrt ATTITUDE ADJUSTMENT (12.09, r36088)\n# to BusyBox v1.22.1 & BARRIER BREAKER (Bleeding Edge, r41391)\ncd /tmp\nwget http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-sysupgrade.bin\nsysupgrade openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-sysupgrade.bin\nreboot\n# Install usb support\nopkg update\nopkg install kmod-usb-storage block-mount block-hotplug kmod-fs-ext4 kmod-fs-vfat kmod-nls-cp437 kmod-nls-iso8859-1\nmkdir -p /mnt/usb\nmount -t vfat /dev/sda1 /mnt/usb\n#\n#src luci http://downloads.openwrt.org/kamikaze/8.09.2/ar71xx/packages/\nopkg update\nopkg install luci
\nSo now that would be my base system! Oh.... and I had to remove usb support if I wanted luci, 4 megs is not alot (remove all packages via 'firstboot' command).
\nSo whats my IP? http://www.cyberciti.biz/faq/how-to-find-out-the-ip-address-assigned-to-eth0-and-display-ip-only/
\nroot@OpenWrt:/# /sbin/ifconfig\nbr-lan Link encap:Ethernet HWaddr EC:17:2F:F0:7A:B4\ninet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0\ninet6 addr: fe80::ee17:2fff:fef0:7ab4/64 Scope:Link\ninet6 addr: fd78:a0fe:50cd::1/60 Scope:Global\nUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1\nRX packets:685 errors:0 dropped:0 overruns:0 frame:0\nTX packets:119 errors:0 dropped:0 overruns:0 carrier:0\ncollisions:0 txqueuelen:0\nRX bytes:77032 (75.2 KiB) TX bytes:12528 (12.2 KiB)
\neth0 Link encap:Ethernet HWaddr EC:17:2F:F0:7A:B4\nUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1\nRX packets:4658 errors:0 dropped:0 overruns:0 frame:0\nTX packets:470 errors:0 dropped:0 overruns:0 carrier:0\ncollisions:0 txqueuelen:1000\nRX bytes:550387 (537.4 KiB) TX bytes:44507 (43.4 KiB)\nInterrupt:4\n... etc...
\nWell, its... hard to tell. So I went to /etc/config/network and remove the 'type' bridge line. However even then luci didn't load. so thats when I realized that the daemon for uhttpd is not on. http://wiki.openwrt.org/doc/howto/luci.essentials
\nThese two commands took care of the rest.
\n/etc/init.d/uhttpd start # Start uhttpd that holds luci\n/etc/init.d/uhttpd enable # Enable start on every reboot
\nNow the system works
\nUser: root\npassword: password\nYea... very secure lol
\nSo now that I got a pretty general router... I've no idea what I'm suppose to do with it now that I won't install piratebox on it. Plus with luci, there is not a lot of flash memory to play with, so any future project will still need to done via CMD (or having an external flash drive). Sooo yea, it has luci GUI, and could potentially act as a remote serial access terminal over wifi, so that's cool but I think that's enough for me today. All this note will be of assistance to any of you guys who are still new to this, and may need some ideas on how to get started. (Plus is a good reference for me later on!)
\nCheers.
\n(LUCI GUI) Status\nSystem\nHostname\tOpenWrt\nModel\tTP-LINK TL-WR703N v1\nFirmware Version\t OpenWrt Barrier Breaker r41391 / LuCI Trunk (svn-r10375)\nKernel Version\t3.10.44\nLocal Time\tMon Jun 30 11:08:42 2014\nUptime\t0h 30m 49s\nLoad Average\t0.09, 0.18, 0.12\nMemory\nTotal Available\t\n16260 kB / 28844 kB (56%)\nFree\t\n7952 kB / 28844 kB (27%)\nCached\t\n6716 kB / 28844 kB (23%)\nBuffered\t\n1592 kB / 28844 kB (5%)\nNetwork\nIPv4 WAN Status\t\neth0\tType: dhcp\nAddress: 192.168.0.9\nNetmask: 255.255.255.0\nGateway: 192.168.0.1\nDNS 1: 192.168.0.1\nConnected: 0h 8m 31s
\nJust extra notes for myself:
\nAccording to http://blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:serial_port_loading_files
\n# Loading with the kermit protocol\nbfin> loadb [load address] [baud rate]
\n# Loading with the y-modem protocol\nbfin> loady [load address] [baud rate]
\nAccording to http://eduunix.ccut.edu.cn/index2/html/linux/O'Reilly%20-%20Building%20Embedded%20Linux%20Systems/belinuxsys-CHP-9-SECT-5.html
\naskenv - get environment variables from stdin\nautoscr - run script from memory\nbase - print or set address offset\nbdinfo - print Board Info structure\nbootm - boot application image from memory\nbootp - boot image via network using BootP/TFTP protocol\nbootd - boot default, i.e., run 'bootcmd'\ncmp - memory compare\nconinfo - print console devices and informations\ncp - memory copy\ncrc32 - checksum calculation\ndate - get/set/reset date & time\ndhcp - invoke DHCP client to obtain IP/boot params\ndiskboot- boot from IDE device\necho - echo args to console\nerase - erase FLASH memory\nflinfo - print FLASH memory information\ngo - start application at address 'addr'\nhelp - print online help\nide - IDE sub-system\niminfo - print header information for application image\nloadb - load binary file over serial line (kermit mode)\nloads - load S-Record file over serial line\nloop - infinite loop on address range\nmd - memory display\nmm - memory modify (auto-incrementing)\nmtest - simple RAM test\nmw - memory write (fill)\nnm - memory modify (constant address)\nprintenv- print environment variables\nprotect - enable or disable FLASH write protection\nrarpboot- boot image via network using RARP/TFTP protocol\nreset - Perform RESET of the CPU\nrun - run commands in an environment variable\nsaveenv - save environment variables to persistent storage\nsetenv - set environment variables\nsleep - delay execution for some time\ntftpboot- boot image via network using TFTP protocol\nand env variables ipaddr and serverip\nversion - print monitor version\n? - alias for 'help'
\nLinks to note
\nhttp://code.kliu.org/hashcheck/ - hash check from explorer, sounds useful
\nhttp://code.kliu.org/cmdopen/ - "Open Command Prompt" menu item to the context menus (right-click menus) in Windows Explorer... Very useful!
\n[pcb]: data:image/jpg;base64,/9j/4AAQSkZJRgABAQEASABIAAD/4QJMRXhpZgAATU0AKgAAAAgABwEaAAUAAAABAAAAYgEbAAUAAAABAAAAagEoAAMAAAABAAIAAAExAAIAAAAOAAAAcgITAAMAAAABAAEAAIdpAAQAAAABAAAAgIglAAQAAAABAAABXAAAAAAAAABIAAAAAQAAAEgAAAABcGFpbnQubmV0IDQuMAAAC4gnAAMAAAABAfwAAJAAAAcAAAAEMDIyMJADAAIAAAAUAAABCpAEAAIAAAAUAAABHpEBAAcAAAAEAQIDAJIKAAUAAAABAAABMqAAAAcAAAAEMDEwMKABAAMAAAABAAEAAKACAAQAAAABAAAHoKADAAQAAAABAAAMwKAFAAQAAAABAAABOgAAAAAyMDE0OjA2OjMwIDIxOjM0OjIzADIwMTQ6MDY6MzAgMjE6MzQ6MjMAAAABcQAAAGQAAgABAAIAAAAEUjk4AAACAAcAAAAEMDEwMAAAAAAAAAAAAAoAAAACAAAABgAAAdoAAQACAAAAAlMAAAAAAgAFAAAAAwAAAeAAAwACAAAAAkUAAAAABAAFAAAAAwAAAfgABQABAAAAAQAAAAAABgAFAAAAAQAAAhAABwAFAAAAAwAAAhgAEgACAAAABwAAAjAAHQACAAAACwAAAjgAAAAAMiwyLDAAAAAAJQAAAAEAAAAvAAAAAQAAWH4AAAPoAAAAkAAAAAEAAAAyAAAAAQAAXCAAAAPoAABr0AAAA+gAAAALAAAAAQAAACIAAAABAAAAFgAAAAFXR1MtODQAADIwMTQ6MDY6MzAAAP/bAEMALyAjKSMdLykmKTUyLzhHdkxHQUFHkGdtVXarlrOwqJalorzU/+W8yP/LoqXr/+7///////+24v/////////////bAEMBMjU1Rz5HikxMiv/CpcL////////////////////////////////////////////////////////////////////AABEIAK4AyAMBIgACEQEDEQH/xAAfAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgv/xAC1EAACAQMDAgQDBQUEBAAAAX0BAgMABBEFEiExQQYTUWEHInEUMoGRoQgjQrHBFVLR8CQzYnKCCQoWFxgZGiUmJygpKjQ1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4eLj5OXm5+jp6vHy8/T19vf4+fr/xAAfAQADAQEBAQEBAQEBAAAAAAAAAQIDBAUGBwgJCgv/xAC1EQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFRB2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2dri4+Tl5ufo6ery8/T19vf4+fr/2gAMAwEAAhEDEQA/AK287dvanxS4O1unaoqO9AFwHBqQHiokO5QaevSgB+O9KKFoxj60ATxPxtP4VHcRYUsOmKZU0b+YpRuuKAM5f9UarN1rQ+ybH2vlgfQ4qvJblWPysF9aAI4WA4NPNRbcU8cigCM8NUinNIVyKRDg4NAFqF+cGnSxj8DUKcEGrYHmJxQBRXMT1oQOBz2NV5Y9w9xTLdiG2H8KANQUvWoonyMd6lXpQAlFKetJQAlZl2nlzZHAPNahqtdReZEfUcigBsM+9ATRVS3fDbexooAhNCDLjNSTLhyQOD0qKgCz5qgkEYxUikMAR0qn1NXLBPMbBHA5NAFqGHcNzcCpDJChxxn6ZqO6nwfLU49TWeJSj5wDj1oA0ftMH+RR9pgHt+FZLSZbg0D5+KANb7VCe+aDcQHrj8RWZCD5ir6nqKmuI/Lk4ORnvQBb8y0P8Kf980brX+6n/fNZygZ4pC5VsCgDTza/3V/75o/0Q/wJ/wB81mbz61YlQLKyjOBQBczbdlX8qcHgHTA/Cs2RiqBgx64pQzD7zH86ANHdCT0B/CkAt85CLn6VRErKxTdkEA08McUAX1CE8AZp2MVQEjKQc1djbcgPegBab0olfZg+tM3gigCTNNbpTd9LuFAGZdJ5cxx0PIoq1eJvjJ7iigBjKGUg1ScYOKuioZkGNwoAgrU09QtuW9TWYK1LX/jx/A0AUJpCWLHPJqu5J71PI+Rg9KrEkE4oAQVJGdufcYqIHJqXHyjHWgCSPkKR1U4P0/zmrd1FtJbt/wDWqmAYQHbqegqaS7aUEFeDj8KAI0QB/vfhURIA6c1Mq/vj7DB+uKhVwM5GaAHoMgH3q5PxcSHrgf4CqkbBj0OM1cukZZyT91qAISm5dvPDAn8qbM/yhh1LY/QVIHKMSDgY+aqbsTgZ4HSgCVsn67RTzJ5ZAINRRucH1GMVJMNyBh1oAlVw33lI+taMQwgrKj/j38HFadsSYFJoAjvThF+tVleptSOET61SVuetAFneaej1ADkU5TzQBYbDKQehopoooArRPvHuKfgEdKrMDG+R0NWEYMoIoAgkj2c9q0LT/jy/OqsilgMVbtBi0I+tAGdKq44PNVicE1PLn0NRL96gBmOc1O4QooQk+uaFQMMml2KD8vX0oATIIAJHC4H500DCk4709woBPT2zTBNxtxxQAoyJDznPelC/OMd6JBsKnOM0i538UAOjTa4A55zWtKVAbzMEdhWVhgzMelSFzgZJoAbOxdyeACeg6VAVz2qZiM9OaekWVyTQBXX5Vb8KmgfdlSBTpUUrsUc9TSRrtPoRQA4eWJcScL6DvWlERsAVSF7ZqkYUfBPOe9XYRiIA9uKAKmqnCR/Ws9WrVvhkJVVVFAESNUyHNWY1UDJAAqQqMdKAK4PFFCRlmPOBnAooAhdNwwahjPlOVNTxPvT3pk6ZGe4oAlHSrcH+oP41n27ZBU9q0Lf/AFJ/GgDLlc4xmq565qxKqY6nNViME0AWEbK0gAPpyKSI/Link4446UAV5R82R0NInygt37U6RsSEdqRgTGO+O9ACPI0mNx6U+JiHFQjpUqffX8KALkiDa+Wxg5HvUAmC5BB5qVyFkP8ADnuXxVWQ/vD06/WgCYXAzkgnjHanx3CAckj61VpZDnHOePXNAFwOPM4HUZyO9RoQZTn3ptu2XwPT0oHyybvegDRG3jb0qxH9wVnRzKB346VoREmNSeM0AV77ov41XTrVi+/g/GqylQeo/OgC2mPL+bGPepD0qus8QXBcY+tONzHj74/OgB2RsGP71FUvPJc7TxmigCNCY5MNwO9WSAeaS7hx8wpkD5XaTyKAI2HlSZHStK1YNBkd81UdQwwasWIItyD2Y0AZ0qt2BxUB61bkY4xniqzgliRQAnbrzUsYZxkc461CVwBzz6VLCcAjJFADJIzvPFNVWGRg4ParEkhxg849KckabAWGSR60AVTGc8DB/nTolYyDAyR2qSTCNgAU5VLDeoGelAEjNhuCAcYOG21Vm++T/XNWHkKk7icdtuBVeTlm+tADe1K/OP8AHNN9qkcgqMZ49QKACFijZFTRhCxMhIHtVqyije2DuoJBPNTCKHGdinHXigCmVhC/ebr09q04yrICvTHFUbtQsgAAxiprMf8A6hQBDqpwI/xrNbg1o6t0j/GqtvCs27OeKAK9CnDVfFlH70v2KP3oAijAyD2oqdbcKMA8UUAWmAdSKzpFMMuccVas5t67WPI/Wn3MXmp7igCJcMoI6GrVsP3R+tZ9vJtJRvwrRg/1Z+tAGXJ/Wos8nnmp5vu9Mc1XPGTigCRQMDd1pHAXkHmkRxjt+NDFSeaAHD5iGOKlC7uQqke5qKNwp4bGKXziABuGKAFmUryVAz6UiOEBBGfSlMiNwWpu8LLvzz15oAAGIzg49aawBGMDNWPN3I27A3egqMpwGz1oAgK80+NfnHFDDnNPTaSOu7NAF+y/492HoTUgxGfmHB5B9DTLQfuG+pqQ/cHGPagCtc9Uz/dqWz7028+8v0p9mODQBDqnSP8AGobH+OpdU6R/jUVj0f60AW++KUjApP4vwpT0FACUUUUAZ2TDIGWtONxIgYVRdNy4pLSbypNjdDQA+7i2NvUcHrVyxffb5PXNKyB0IboaS0Qxwsp/vH+VAGdOxIxVck8ircmwAnBzVVjyaAGKSDxTxzTQMjrSr1oAXoaKXHFJjmgBCMUdqVhzikNAEoBG3bk+uRxT2DBRu6HkU5TmHOBxxTlWSSI7VBVepoAjVCVyFJHrTXjZBnBA9amhlATYTgdaSWQMNvQZ60AW7DP2Y+uan2kjvnNVYCVTERBPeg3To5EnA7ECgB92OU+lPtOhqvJOspUcls4AxVuGMoOvWgCpqnSP8aisfuv9al1U48v8aopK6D5TigDU75orL+1TA/e/SpVuJDzuoAv0VDG28dTmigBjLg+xqGZONwq3jIxUZXAwaAJLSfzF2t1FXF5U1j8wShl6VqQSB1BHQ0AZ0qnJHeqrdc1o3cREmR0bmqki84HagCIJn+IU8Rf7QpyxEgnHA70sakkACgBBEc43fpStCU74/CpWXa2Byak2AQncvU8GgCoIh/ez+FIYuM5/SrcUYY4wKZs+bGOlAEedqbAcjr0pUleMFVbAbqKlliwEYKOetPSHfGw2jdjigCoKASGBB5qaNCDggflVpQP7i5+lAEEbhFA35PoDimHPzlgeehNXV2D+Bfyp7wxyoRtA9wKAK1pEdx3oMEZBq9UcQwoQ9VqSgDM1dhujX0BNUFbPHep79/NnZh0HAqoODQBKy5HFJE2Dg9Kch3Clkj4yKALCEg5FFRwvn5T1ooAvpyKHTIyKrmRophn7hq2CCMjmgCrIm5cU20l8t9hPXpU8gwf5VUnTB3CgDWIWZNrVUezYH5eRTrWXzIwe44NOnmkiUMMEd80AAgb7OY8c5zRFAUYHHSmx3jOucLnvTjcuOmKAFe3LSFsdTTmhLQ7MY5zVWW9mQ8BcfShL6Vx/CCPagC1HCUYHH60025LlvU1Wku7gcqRj6VCdQuP7w/KgDSeIvGq8cGlijMZ7Vmf2hcf3h/3yKfFfyscMwz9BQBcW3KvuGOuak2Sbt3y5xiqn2qX+9+go+0zf3v0FAFoxMWzxmnorL16VSFxN/e/QUG5mH8f6CgDQ4HNVp5g6skZ9iRVN5ZJBhnJFEZ2tn86AIXjIODVd0Kn2rXaMSKCOtVZIgwIPWgCkjbW9qtrjHHIqsylTg1JC+PlNABLHt+ZelFWMZGD0NFAEske+Mjv2qGGZom8t+mfyqYucdKqXJy4PtQBoP8y8VAw3Ag02zkLDaewqZlG760AVYJPJmw3Toa0WAdcHkEVn3CDbuqxZyl49p/h70AVTut5iD2qyMFc9qW9jDR7u6/rVe1kOCp7UAPkj3ArVQExP9OtX3qvcrwHHWgBwIIBHQ1XlTa3HSn27E/LST5Dcnj0oAhxQOCD3o71Y+z8DDUASRuHUEde9SAcVDFGYyec5qUHmgAxTiuRzR3oNAERGDR3p7DIplAFi2kwdp6GnzRc7hVUcVagmLDa1AFSeLevHUVUxg1sSRA8jg1n3EYHzD8aAFhk3Daeo/Wiqykg5HUUUAf/Z
\n", "date_published": "2014-06-30T11:10:50Z" }, { "id": "/blog/2014/06/28/parsedownRender_V2/", "url": "/blog/2014/06/28/parsedownRender_V2/", "title": "Parsedown Render V2", "content_html":"Here is version two of the parsedown based general .md file viewer
\nThis time I added support for Math Jax, which will make it easier for me to post documents marked in LaTeX and ASCIIMaths. Which is very useful! Especially for future collaboration or documentation efforts.
\n\n<?php\n/*\nProject: parsedown Render\nCoder: Brian Khuu briankhuu.com\nVERSION: v2.0 (MathJax and raw view support now)\nPurpose: To allow for displaying of .md file transparently to visitors via http://parsedown.org and mod_rewrite\nUsage: Place this file (parsedownRender.php) in your root directory and add these lines below to your .htaccess file\n\t\t<IfModule mod_rewrite.c>\n\t\tRewriteEngine On\n\t\tRewriteCond %{REQUEST_URI} ^(.*)\\.md [NC]\n\t\tRewriteRule . /parsedownRender.php?file=%{REQUEST_URI}&%{QUERY_STRING} [L]\n\t\t</IfModule>\n\t*/\n$file = \"./\".$_GET[\"file\"]; // 'file' => /md/test.md\n$css = isset($_GET['css']) ? htmlspecialchars($_GET['css']) : \"http://kevinburke.bitbucket.org/markdowncss/markdown.css\";\n$viewMode = isset($_GET['view']) ? htmlspecialchars($_GET['view']) : \"\";\nif ( $viewMode == \"raw\"){ echo file_get_contents($file); exit(); }\nfunction parsedownInclude($f){\n\trequire_once 'Parsedown.php';\n\t$Parsedown = new Parsedown();\n\techo is_readable($f) ? $Parsedown->text(file_get_contents($f)) : \"File Not Found: \".htmlspecialchars($f);\n}\n?>\n<!DOCTYPE html>\n<head>\n\t<link rel=\"stylesheet\" type=\"text/css\" href=\"<?php echo $css ?>\" />\n\t<script type=\"text/javascript\" src=\"http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-MML-AM_HTMLorMML\"></script>\n</head>\n<body>\n<?php parsedownInclude($file); echo \"<hr><a href='?view=raw'>VIEW RAW</a>\"; ?>\n</body>\n</html>Testing mathjax rendering support for this page. This is the code inserted on the top of each page.
\n\n\nI decided on using mathjax cdn since it is likely to be precached by the cdn in multiple websites, meaning faster load time. Plus it means MathJax will always be up to date. I also decided to choose both ASCIIMath and Tex/LaTeX support since both have suitable use case (One for quick and dirty notation, and the other for clean mathamatical notations).
\nThe settings I chose according to MathJax\nTeX-MML-AM_HTMLorMML.js\nAllows math to be specified in TeX, LaTeX, MathML, or AsciiMath notation, with the AMSmath and AMSsymbols packages included, producing output using MathML if the browser supports it sufficiently, and HTML-with-CSS otherwise.
\nHere is some test Math Jax stuff
\nInline math/tex:
\n\n\nDisplayed math/tex:
\n\n\nInline math/asciimath:
\n\n\nDisplayed math/asciimath:
\n\nLooks like I was mistaken, you are not forced to use the unwieldy html tags to declare if a text should be considered math or not.
\nIn http://docs.mathjax.org/en/latest/tex.html read under the heading "TeX and LaTeX math delimiters". For Tex and LaTeX, the delimiters are
\nLaTeX Inline Mode:
\n\\(...\\)
\nLaTeX Display Mode:
\n\\[...\\]
\nTeX Mode(unverified, may need ""):
\n$$...$$
\nASCIIMath Mode (Note: Backtick located next to "1" or "!" key:
\n`...`
\nLaTeX Inline Mode:\n\\(...\\)\nLaTeX Display Mode:\n\\[...\\]\nTeX Mode(unverified, may need ""):\n$$...$$\nASCIIMath Mode (Note: Backtick located next to "1" or "!" key:\n`...`
\nNote: For some reason, the Math Jax document specifies (...) & [...]\nbut that does not work for me... document needs updating?\nP.s. ("" is needed if running mathjaxs after markdown parser, since there is special significance to "`" and ""
\nOh and btw if you type "_" in math mode, youw will actually need to escape it too, like below\ne.g. "
\n\\( \\Gamma g_{th} = \\alpha_i + \\frac{1}{2L} ln[\\frac{1}{R_1 R_2}] \\)
\nAs a signoff, here is a random equation (see if you can recognize it :p )
\n\\( \\Gamma g_{th} = \\alpha_i + \\frac{1}{2L} ln[\\frac{1}{R_1 R_2}] \\)
\n$$ a=b $$
\n`x^2 /7`
\np.s. I think I know why "" needs to be added in most cases. It's because the markdown parser treats "" and ` as special characters, and thus needs to be escaped.
\n", "date_published": "2014-06-28T14:24:23Z" }, { "id": "/blog/2014/06/28/The_TL-WR703N_piratebox_exploration/", "url": "/blog/2014/06/28/The_TL-WR703N_piratebox_exploration/", "title": "The TL-WR703N piratebox exploration", "content_html":"Today, just trying again at configuring a pirate box in TL-WR703N. A while ago, I got it working for a while, but then the Sandisk 16gig somehow ended up dying. Haven't touched it since. Now just trying to see what can be done with it, and if I can reinstall it (on a 4gig flash drive, Sandisk nonetheless)
\nSerial: 11520 baud
\nUseful to note that if you stuff things up in OpenWrt for TL-WR703N that you can revert the damage via typing\nopenwrt reset -r mtd -r erase rootfs_data
\nAlso soldered into TL-WR703N, is a stereo plug that is acting as a cheap way to implement a TTL logic level UART port for interfacing with the board's linux console terminal over serial (via Putty).
\nTRS Plug (What I chose, based on most common configuration I seen online)\n(Remember that Tx->Rx and Rx->Tx)
\nPLUG SIDE (To USB to serial converter\nTIP , RING , SLEEVE\nTxd , Rxd , Ground
\nPORTSIDE (wired to board UART)\nTIP , RING , SLEEVE\nRxd , Txd , Ground
\nHaving bit of difficulty in getting the usb to mount, possibly due to the need to install usb mounting package. But to install packages, I need an internet connection :/ . Well my router has DHCP, so we can go from there (Static IPs are bloody annoying).
\nNotice specifically that I switched the option for 'proto' to 'dhcp'
\nroot@OpenWrt:/etc# cat /etc/config/network\nconfig interface 'loopback'\noption ifname 'lo'\noption proto 'static'\noption ipaddr '127.0.0.1'\noption netmask '255.0.0.0'
\nconfig interface 'lan'\noption ifname 'eth0'\noption type 'bridge'\noption proto 'dhcp'\noption ipaddr '192.168.1.1'\noption netmask '255.255.255.0'
\nroot@OpenWrt:/etc# /etc/init.d/\nboot dnsmasq firewall rcS telnet usb\ncron done led sysctl ubus watchdog\ndefconfig dropbear network sysntpd umount\nroot@OpenWrt:/etc# /etc/init.d/network\nSyntax: /etc/init.d/network [command]
\nAvailable commands:\nstart Start the service\nstop Stop the service\nrestart Restart the service\nreload Reload configuration files (or restart if that fails)\nenable Enable service autostart\ndisable Disable service autostart
\nroot@OpenWrt:/etc# /etc/init.d/network reload\n[ 4768.420000] br-lan: port 1(eth0) entered disabled state\n[ 4768.450000] device eth0 left promiscuous mode\n[ 4768.450000] br-lan: port 1(eth0) entered disabled state\n[ 4768.450000] eth0: link down\n[ 4768.480000] device eth0 entered promiscuous mode\n'radio0' is disabled\n[ 4769.250000] eth0: link up (100Mbps/Full duplex)\n[ 4769.250000] br-lan: port 1(eth0) entered forwarding state\n[ 4769.250000] br-lan: port 1(eth0) entered forwarding state\n'radio0' is disabled\n'radio0' is disabled\nroot@OpenWrt:/etc# [ 4771.250000] br-lan: port 1(eth0) entered forwarding state
\nTIP: Control z will quit any program you are running at the moment in command line.
\nroot@OpenWrt:/etc# ping google.com\nPING google.com (74.125.237.96): 56 data bytes\n64 bytes from 74.125.237.96: seq=0 ttl=55 time=27.968 ms\n64 bytes from 74.125.237.96: seq=1 ttl=56 time=31.212 ms\n64 bytes from 74.125.237.96: seq=2 ttl=56 time=30.802 ms\n^Z[3]+ Stopped ping google.com\nroot@OpenWrt:/etc#
\nI already installed OpenWrt, and based on tl-wr703n#flashing page in openwrt wiki, you need to flash a factory and then a sysupgrade. I was pretty confused on the difference between the two until stitch626 in https://forum.openwrt.org/viewtopic.php?id=34572 pointed this out from the FAQ.
\nWhat is the difference between the different image formats?\na factory image is one built for the bootloader flasher or stock software flasher\na sysupgrade image (previously named trx image) is designed to be flashed from within openwrt itself
\nWhat this means, is that I have already installed the 'factory' replacement image, my best guess is that it holds the openwrt fail safes etc... think of it as the 'openwrt BIOS'.
\nWhich means, what I really should be doing, is updating the sysupgrade image of the system.
\ncd /tmp\nwget http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-sysupgrade.bin\nsysupgrade openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-sysupgrade.bin\nreboot
\nhmmm... It seems that a fresh install of openwrt does not include usb support (needed to install piratebox install script in usb drive). Looking at http://en.code-bude.net/2013/02/16/how-to-increase-storage-on-tp-link-wr703n-with-extroot/\nTrying 'ls /dev/sd*` shows no directory or file, indicating no flash drive mounted.
\n#Update package list\nopkg update\n#Install USB storage support\nopkg install kmod-usb-storage
\nin http://wiki.openwrt.org/doc/howto/usb.storage
\nopkg update\nopkg install kmod-usb-storage block-mount block-hotplug kmod-fs-ext4 kmod-fs-vfat kmod-nls-cp437 kmod-nls-iso8859-1\nmkdir -p /mnt/usb\nmount -t vfat /dev/sda1 /mnt/usb
\nDon't forget to type reboot after installing usb support, otherwise you gonna go crazy. ( opkg install kmod-scsi-generic may also be required... not sure)
Somehow after following the pirate box instruction, I got it stuck in a autoreset loop during the install process. http://piratebox.cc/openwrt:diy\n(edit: Okay, so I am an idiot, I forgot one critical instruction to place a modified “*squashfs-factory.bin” on the root directory of the flash drive)
\nU-Boot 1.1.4 (Feb 28 2012 - 11:58:24)
\nAP121 (ar9330) U-boot
\nDRAM: 32 MB\nled turning on for 1s...\nid read 0x100000ff\nflash size 4194304, sector count = 64\nFlash: 4 MB\nUsing default environment
\nIn: serial\nOut: serial\nErr: serial\nNet: ag7240_enet_initialize...\nNo valid address in Flash. Using fixed address\nNo valid address in Flash. Using fixed address\n: cfg1 0x5 cfg2 0x7114\neth0: 00:03:7f:09:0b:ad\nag7240_phy_setup\neth0 up\n: cfg1 0xf cfg2 0x7214\neth1: 00:03:7f:09:0b:ad\nathrs26_reg_init_lan\nATHRS26: resetting s26\nATHRS26: s26 reset done\nag7240_phy_setup\neth1 up\neth0, eth1\nAutobooting in 1 seconds\n## Booting image at 9f020000 ...\nUncompressing Kernel Image ... Too big uncompressed streamLZMA ERROR 1 - must RESET
\nTyped tpl very quickly after Autobooting in 1 seconds is shown, getting me into some sort of failsafe of failsafes. (I suspect it is a CFE (Common Firmware Environment) command line http://wiki.openwrt.org/doc/techref/bootloader/cfe )
U-Boot 1.1.4 (Feb 28 2012 - 11:58:24)
\nAP121 (ar9330) U-boot
\nDRAM: 32 MB\nled turning on for 1s...\nid read 0x100000ff\nflash size 4194304, sector count = 64\nFlash: 4 MB\nUsing default environment
\nIn: serial\nOut: serial\nErr: serial\nNet: ag7240_enet_initialize...\nNo valid address in Flash. Using fixed address\nNo valid address in Flash. Using fixed address\n: cfg1 0x5 cfg2 0x7114\neth0: 00:03:7f:09:0b:ad\nag7240_phy_setup\neth0 up\n: cfg1 0xf cfg2 0x7214\neth1: 00:03:7f:09:0b:ad\nathrs26_reg_init_lan\nATHRS26: resetting s26\nATHRS26: s26 reset done\nag7240_phy_setup\neth1 up\neth0, eth1\nAutobooting in 1 seconds\nhornet> help\n? - alias for 'help'\nbootm - boot application image from memory\ncp - memory copy\nerase - erase FLASH memory\nhelp - print online help\nmd - memory display\nmm - memory modify (auto-incrementing)\nmtest - simple RAM test\nmw - memory write (fill)\nnm - memory modify (constant address)\nprintenv- print environment variables\nprogmac - Set ethernet MAC addresses\nreset - Perform RESET of the CPU\nsetenv - set environment variables\ntftpboot- boot image via network using TFTP protocol\nversion - print monitor version
\nAfter getting an TFTP client and following http://forums.openpilot.org/blog/52/entry-92-unbrick-wr703n-wifi-router/ http://www.tricksguide.com/how-to-setup-a-tftp-server-tftpd32-windows.html
\nUsing http://www.rfactory.org/OpenWRT/download/ipscan.exe to scan for the ip of the device.
\nThis is all confusing and not working... On checking http://staticky.com/ar725w.html for a different device, I saw something simular using tftp only
\ntftp 8A800000 openwrt.bin\nprotect off BC450000 BC7DFFFF\nerase BC450000 BC7DFFFF\ncp.b 8A800000 BC450000 $(filesize)\nbootm
\nThe author has a nice description of what the above does "This downloads the firmware image to RAM (which begins at 0x80000000), unprotects the safe area of the flash chip, erases said flash space and then copies (writes) onto the flash chip from the RAM image. The bootm command boots the image in 0xBC450000 by default. It is also useful for booting an uImage in memory, like the kernel+initramfs images that OpenWRT can build. In that case, something like bootm 8a800000 works."
\nThis makes more sense on how the below lines of commands in http://forums.openpilot.org/blog/52/entry-92-unbrick-wr703n-wifi-router/ works.
\nhornet> tftpboot 0x81000000 openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin\nhornet> erase 0x9f020000 +0x3c0000\nhornet> cp.b 0x81000000 0x9f020000 0x3c0000\nhornet> bootm 9f020000
\nOkay I think this is using Das U-boot bootloader. I could try uploading over serial, but man... there is no good kermit or ymodem programs for windows (Haven't yet transitined to linux yet D: )
\nhttp://www.jackslab.org/?portfolio=u-boot-quick-start
\nOoooh so there is more commands under Uboot e.g. tftp http://support.atmel.no/knowledgebase/avr32studiohelp/com.atmel.avr32.tool.ngw100/html/u_boot_command_reference.html
\nAhhh screw this... I think trying to get this working over tftp under windows is screwed up... I'll shelve this, until maybe I find a kermit serial modem thing in python or something
\n", "date_published": "2014-06-28T13:40:21Z" }, { "id": "/blog/2014/06/15/parsedown_include/", "url": "/blog/2014/06/15/parsedown_include/", "title": "Parsedown Include", "content_html":"You might find this useful. It's a way to include a markdown file as if you were doing a PHP include() command, into your page. This would make for easier modification of your webpage by separating the text from the layout. This requires that you already have Parsedown.php from parsedown.org.
\nfunction parsedownInclude($f){\nrequire_once 'Parsedown.php';\n$Parsedown = new Parsedown();\necho is_readable($f) ? $Parsedown->text(file_get_contents($f)) : "File Not Found".htmlspecialchars($f);\n}
\n\nLet me know if it has been of assistance to you!
\n", "date_published": "2014-06-15T00:00:00Z" }, { "id": "/blog/2014/06/15/parsedownRender/", "url": "/blog/2014/06/15/parsedownRender/", "title": "Parsedown Render", "content_html":"Here is a parsedownRender.php file for you to easily present your markdown files (e.g. test.md ). Let me know if it was helpful!
\n\n<?php\n/*\nCoder: Brian Khuu briankhuu.com\nPurpose: To allow for displaying of .md file transparently to visitors via http://parsedown.org and mod_rewrite\nUsage: Place this file (parsedownRender.php) in your root directory and add these lines below to your .htaccess file\n\n\t<IfModule mod_rewrite.c>\n\tRewriteEngine On\n\tRewriteCond %{REQUEST_URI} ^(.*)\\.md\n\tRewriteRule . /parsedownRender.php?css=/css/markdown1.css&file=%{REQUEST_URI} [L]\n\t</IfModule>\n\n\t*/\n$file = \"./\".$_GET[\"file\"]; // 'file' => /md/test.md\n$css = ( $_GET['css']!=\"\" ) ? htmlspecialchars($_GET['css']) : \"/css/style.css\";\n\nfunction parsedownInclude($f){\n\trequire_once 'Parsedown.php';\n\t$Parsedown = new Parsedown();\n\techo is_readable($f) ? $Parsedown->text(file_get_contents($f)) : \"File Not Found: \".htmlspecialchars($f);\n}\n?>\n<!DOCTYPE html>\n<head><link rel=\"stylesheet\" type=\"text/css\" href=\"<?php echo $css ?>\" /></head>\n<body>\n<?php parsedownInclude($file) ?>\n</body>\n</html>Let me know if it helped you!
\n", "date_published": "2014-06-15T00:00:00Z" }, { "id": "/blog/2014/06/15/flatfile_blog_done/", "url": "/blog/2014/06/15/flatfile_blog_done/", "title": "Flat File Blog Done", "content_html":"Finally got the minimalistic flatfile blogging system completed.
\nEssentally all the post in my blog is organized as flat files in a folder called /blog/ they are all named in this format:
\n[ISO8601 timedate]+[optional "_"or" "]+[title of post]+ [file extension ".txt" ".md"]
\nRegular expression used to extract these information is "/(?P
This is the first test post for this minimalistic blog. First overhaul of the website in a while. This time most of the code from skeleton HTML/CSS framework was removed( www.getskeleton.com ), only kept bit of formatting (because too lazy to remove it, and their font choice are still pretty good). Still keeping the scrolling effect as that is still very nice to look at.
\nEdit: There has been some modifications to this website using jekyll, so it's much different now. Thus the old about text is out of date. Here is what it said.
\nThis page is designed to be visually minimalistic. For the scrolling to link anchor, I used this jquery tutorial found in this link. The parallax background was done by using this tutorial in this link (but modified to support multiple background elements, try scrolling the page)
\nThis is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at jekyllrb.com
\nYou can find the source code for the Jekyll new theme at: github.com/jglovier/jekyll-new
\nYou can find the source code for Jekyll at github.com/jekyll/jekyll
\n", "date_published": "2014-06-14T00:00:00Z" } ] }