Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 435
» Latest member: J_Smitty
» Forum threads: 432
» Forum posts: 2,187

Full Statistics

Latest Threads
Used Pins
Forum: Hardware
Last Post: Armin@netPI
January-14th-2021, 06:36 AM
» Replies: 3
» Views: 372
190 times higher enduranc...
Forum: Hardware
Last Post: Armin@netPI
January-12th-2021, 01:19 PM
» Replies: 2
» Views: 163
docker.service start fail...
Forum: Software
Last Post: Armin@netPI
January-11th-2021, 01:16 PM
» Replies: 11
» Views: 850
Hardware watchdog in a co...
Forum: Hardware
Last Post: Armin@netPI
January-7th-2021, 07:53 AM
» Replies: 0
» Views: 85
[SOLVED] Use larger SD-Ca...
Forum: Hardware
Last Post: Armin@netPI
January-7th-2021, 06:13 AM
» Replies: 9
» Views: 804
MySQL database
Forum: Software
Last Post: Armin@netPI
January-7th-2021, 05:34 AM
» Replies: 6
» Views: 110
InfluxDB, Node-RED and Gr...
Forum: Projects
Last Post: Armin@netPI
January-6th-2021, 02:36 PM
» Replies: 0
» Views: 86
Programming NPIX modules
Forum: Software
Last Post: Armin@netPI
January-4th-2021, 08:54 PM
» Replies: 0
» Views: 50
OpenVPN container
Forum: Software
Last Post: Armin@netPI
January-3rd-2021, 12:13 PM
» Replies: 0
» Views: 44
netPI RTE + remote access...
Forum: Hardware
Last Post: Armin@netPI
December-24th-2020, 01:43 PM
» Replies: 1
» Views: 145

 
  Usage of Fieldbus in and out and FRAM read and write nodes
Posted by: Schranz - November-1st-2017, 11:07 AM - Forum: Software - Replies (8)

Is there an image which includes both Fieldbus and FRAM nodes?
hilschernetpi/netpi-nodered-fieldbus
hilschernetpi/netpi-nodered-fram


  NPIX board outline
Posted by: Armin@netPI - November-1st-2017, 07:16 AM - Forum: Hardware - Replies (2)

netPI's pluggable advanced networking modules are called NPIX which stands for NetPI eXtension modules. The interface is like the HAT interface you know from Raspberry already but provides signals from the network controller SoC netX additionally (netX communication was not established yet in any of Hilscher NPIX designs).

A standard plastic 52 pin mPCIe socket provides the physical contact between netPI's motherboard and the plugin modules. The mPCIe socket was selected cause it is delivering the appropriate number of signals. It is not providing a real mPCIe signal bus! Due to its popularity you'll find socket and connector in any PCB board design software's library. The whole PCB has roughly a size of 4 cm x 4,5 cm and its board outline can be found as appendix to this topic.



Attached Files
.pdf   NPIX board outline.pdf (Size: 89 KB / Downloads: 29)

  Power loss and removing power
Posted by: Armin@netPI - October-31st-2017, 07:25 AM - Forum: Hardware - Replies (3)

netPI does not have a physical reset button. The official method to shutdown the device is clicking "shutdown" within "Control Panel" management tile under the tab "System". The shutdown will take about 10 seconds and is finished when netPI's heartbeat LED "ACT" goes on for a second first and finally remains off forever. Only in this state it is allowed to remove netPI from its power source. This ensures there are no more write accesses to the SD card media that could else easily damage the file system when interrupted during an active write.

On the other hand, a power loss or an intended/unintended remove from power source cannot be controlled and can happen at any time still. netPI's industrial grade SD card supports a mechanism called Data Clone System (DCS) to prevent data corruption during active writes. DCS holds the data to be written in a second clone buffer always. On every power cycle the card checks the last written target block's data against the buffer. If different it re-writes it and solves the problem. This mechanism vastly reduce the risk of a damaged file system.


  Access netPI via Firefox Browser times out
Posted by: Armin@netPI - October-30th-2017, 08:37 PM - Forum: Software - No Replies

This issue is affecting web sites to be opened in Firefox Browser (e.g. netPI's web GUI landing page) if self-signed certificates are used. It can be encountered when the certificate has been replaced multiple times by Firefox with new same certificates that all have identical Subject/Issuer information. This is the case if you restore your  netPI to factory default and Firefox wants you to reaccept the untrusted certificate during the next browser session.

A way to correct this problem is to browse about:support in your Firefox address bar instead of an URL. Click then Open Folder under topic Profile Folder. Locate certx.db e.g. cert8.db in your file explorer and rename or delete it (e.g. “cert8.db.bak”). It may be necessary to have Firefox close to access the file.

Start your Firefox and visit netPI's landing page again and the problem is gone.


  [SOLVED] "Image unavailable" “no such image” message during deploy
Posted by: Armin@netPI - October-28th-2017, 06:27 AM - Forum: Software - Replies (3)

KWhenever an image is loaded from Docker Hub a certificate is exhanged between the device that pulls the image and the Docker site. This is because of security reasons. The certificate contains next to others also an information about when it was created and until it is valid. During the pulling process Docker Hub compares these times against its system time to release an image or not.

If now the expiration time - even if it is just a second - is in the past and signals the image certificate has expired an image cannot be loaded. So on netPI the same scenario happens if netPI's system time is not set up right and different to the actual time Docker Hub is referencing on ... an "image unavailable" message is reported in this case although available on Docker Hub. So make sure you manually set netPI's time correctly or setup an NTP server keeping an eye on the system time automatically.


  System software modifications
Posted by: Armin@netPI - October-28th-2017, 05:42 AM - Forum: Software - No Replies

By definition system software modifications by users are not possible on netPI. There is not even an SSH service or a shell running on it that could grant you access to the operating system level.

We simply see netPI as a Docker hosting platform having a "hardened" Linux environment as basis you can rely on where you contribute with your knowlegde in isolated software containers only. The concept follows the principle of "Open Innovation" with splitted tasks. netPI delivers the first half of work in hardware and basic software, you deliver the other with your dockerized software to complete with confidence.


  SD card durability
Posted by: Armin@netPI - October-27th-2017, 05:43 PM - Forum: Hardware - Replies (2)

Before you read on watch this story first: https://insideevs.com/news/376037/tesla-...ory-issue/

So categorize your (containerized) applications how write intensive they are and how they are stressing the non-volatile FLASH storage media used in embedded devices such as netPI.

Critical are those applications writing data at high frequency and volume like databases. But not only the applications could get critical:
Docker daemon for example logs all container's console outputs too. So if you have an application running at debug level maybe outputting tons of text information to the console (even no one would/could read it) will lead to a worn-out-effect easily too.

netPI includes an 8GB Industrial rated micro SD card of type MLC-NAND. Since January 2019 the SD card used comes from company SANDISK(Western Digital) named SDSDQAF3-008G-I. The most critical thing about a NAND FLASH memory is its finite number of erase/program cycles (P/E cycles) also referred to as "memory wear". The wear begins to deteriorate the integrity of the memory until it is becoming unusable in the end. The exceptional thing about netPI's 8GB Industrial SD card is that internally this card is based on an 128GB FLASH memory. The card's memory controller chip in front is just limiting the whole size to a 8GB big window available to the user. You see in the appended product brief that all cards of this type even if it's a 8,16,32,64 or 128GB size share all the same TBW (Terra Bytes Written) value of 384.

Where does this TBW value come from? MLC technology in general has a limit of around 3000 P/E cycles per flash block specified by the FLASH manufacturers used in an SD card (https://en.wikipedia.org/wiki/Write_amplification). The limit per block makes a NAND-flash endurance directly dependent on its overall size, so the bigger the more blocks,  the better. An auto-wear leveling mechanism in the card's memory controller ensures the next erase/program cycle is performed on another flash block and hence distributes them evenly across the medium. So the FLASH is 128GB effectively and the P/E is 3000. Both multiplied results in 384TBW.

10 years life time in theory: There is a MS Excel based lifetime calculator available (from Toshiba, appended) estimating the expected NAND flash life time in theory. Let's suppose you have 1MByte as amount of data to be written every second to netPI's 8GB SD card. Even if 8GB  are just visible internally there works an 128GB FLASH memory @ 3000 P/E cycle as you know now. The calculator comes to a lifetime  of 12.5 years.

Life time in practice: We made tests with the SDSDQAF3-008G-I SD card over 485 days. We brought the card to its limit at a incredible writing rate of 216GB/day and realized the first failure after writing 105TB of data. We wrote in chunks of 1GByte file sizes. So in theory there is 384TB possible but in practice we got less than a third. But where does this effect comes from? This comes from WAF and means write amplification factor Read on here for more information https://en.wikipedia.org/wiki/Write_amplification. So if you think writing 1GB results in writing exactly 1GB then this is ideal but you are wrong. A typical WAF value of an SD card is 3.

If you want to read more information about the SANDISK industrial SD cards read on here: https://static6.arrow.com/aropdfconversi...iginal.pdf

There are two methods in general to increase the durability using your own SD card with netPI:

  1. Increase the memory card size while the NAND technology remains the same (MLC). Rule of thumb: double size, double durability.
  2. Switch to memory cards based on a different NAND technology. Type "pSLC" has roughly 6x higher durability, type "SLC" has 30x higher durability compared to MLC
... so keep an eye on your applications.

Additional information:

You can read out useful information from your SD card in use if you call in a Linux terminal. Replace the ? (usually 7 on netPI) in the command line with the corresponding number found on your system

Code:
cd /sys/class/mmc_host/mmc0/mmc0:000?
echo "man:$(cat manfid) oem:$(cat oemid) name:$(cat name) hwrev:$(cat hwrev) fwrev:$(cat fwrev)"

Additionally there are userspace utils available in source code that can deliver further information than provided by default. Call the following commands in a terminal and you get a utility compiled named "mmc"

Code:
git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/cjb/mmc-utils/
cd mmc-utils
make install

Use "mmc" with the following command to read out "Card Specific Data" where the ? needs to be replaced with the corresponding number found on your system (typically 7 on netPI)

Code:
mmc csd read /sys/class/mmc_host/mmc0/mmc0:000?/
mmc cid read /sys/class/mmc_host/mmc0/mmc0:000?/
mmc scr read /sys/class/mmc_host/mmc0/mmc0:000?/



Attached Files
.xlsx   TOSHIBA NAND Llifetime Calculator March 2015.xlsx (Size: 15.12 KB / Downloads: 4)
.pdf   al-industrial-grade-sd-and-microsd-cards-wpb262-original.pdf (Size: 843.58 KB / Downloads: 9)

  Sealed microSD memory card (no more)
Posted by: Armin@netPI - October-27th-2017, 05:28 PM - Forum: Hardware - Replies (1)

If you open netPI's housing you will notice the micro SD memory card is irreversible glued to its socket. It cannot be removed or exchanged without destroying the device physically.

This measure is part of netPI's security concept and ensures nobody is able to manipulate the system software and guarantees you and us a constant system behaviour.


  netPI RTE 3 schematics
Posted by: Armin@netPI - October-27th-2017, 02:03 PM - Forum: Hardware - Replies (2)

For all those interested in netPI RTE 3 schematics find the correspondent document appended.

Since our netPI design partner company Element14 (Farnell Group) licensed the Raspberry Pi 3 schematics on non-disclosure provisions it is clear that the netPI document does of course not contain the Raspberry Pi 3 schematics part.



Attached Files
.pdf   P1651001.pdf (Size: 475.24 KB / Downloads: 73)

  System Software V1.1.3.0RC3 out now!
Posted by: hilscherforum_admin - Less than 1 minute ago - Forum: News - Replies (3)

Hi there,

yes this is correct. Since netPI - from the initial idea - is just a Docker host platform ready to deploy images/containers from a remote registry resource the image/container original should never be stored on netPI itself.

So even if the conainer are destroyed due to a software update - as you mention - the original containers are available on the registry still and can be pulled to netPI after the update.

Thx
Armin