Deprecated: Return type of AWeberCollection::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 246

Deprecated: Return type of AWeberCollection::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 252

Deprecated: Return type of AWeberCollection::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 244

Deprecated: Return type of AWeberCollection::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 245

Deprecated: Return type of AWeberCollection::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 267

Deprecated: Return type of AWeberCollection::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 275

Deprecated: Return type of AWeberCollection::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 271

Deprecated: Return type of AWeberCollection::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 283

Deprecated: Return type of AWeberCollection::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 279

Deprecated: Return type of AWeberCollection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php on line 293

Deprecated: Return type of AWeberEntryDataArray::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 22

Deprecated: Return type of AWeberEntryDataArray::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 26

Deprecated: Return type of AWeberEntryDataArray::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 30

Deprecated: Return type of AWeberEntryDataArray::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 36

Deprecated: Return type of AWeberEntryDataArray::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 18

Deprecated: Return type of AWeberEntryDataArray::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 44

Deprecated: Return type of AWeberEntryDataArray::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 52

Deprecated: Return type of AWeberEntryDataArray::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 48

Deprecated: Return type of AWeberEntryDataArray::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 56

Deprecated: Return type of AWeberEntryDataArray::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_entry_data_array.php on line 40

Deprecated: Return type of Wppr_Recursive_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/wp-product-review/class-wppr-recursive-filter.php on line 51

Deprecated: Return type of Wppr_Recursive_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/wp-product-review/class-wppr-recursive-filter.php on line 40

Deprecated: version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/wp-product-review/vendor/codeinwp/themeisle-sdk/load.php on line 31

Deprecated: version_compare(): Passing null to parameter #2 ($version2) of type string is deprecated in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/wp-product-review/vendor/codeinwp/themeisle-sdk/load.php on line 36

Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/amazon-auto-links/include/core/main/option/AmazonAutoLinks_Option.php on line 779

Deprecated: dirname(): Passing null to parameter #1 ($path) of type string is deprecated in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/amazon-auto-links/include/core/component/template/option/AmazonAutoLinks_TemplateOption.php on line 378

Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/formatting.php on line 2827

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-content/plugins/blossomthemes-email-newsletter/includes/libs/aweber/aweber_collection.php:2) in /home/u276665811/domains/massimopetrossi.com/public_html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1769
{"id":330,"date":"2019-01-30T12:48:57","date_gmt":"2019-01-30T11:48:57","guid":{"rendered":"https:\/\/blog.massimopetrossi.com\/?p=330"},"modified":"2019-04-17T00:10:56","modified_gmt":"2019-04-16T22:10:56","slug":"usare-il-cellulare-ovunque-cosa-significa-resistenza-certificata-ip68","status":"publish","type":"post","link":"https:\/\/blog.massimopetrossi.com\/senza-categoria\/usare-il-cellulare-ovunque-cosa-significa-resistenza-certificata-ip68\/","title":{"rendered":"Usare il cellulare ovunque: cosa significa “Resistenza certificata IP68”?"},"content":{"rendered":"\n
\"I<\/figure><\/div>\n\n\n\n

Una delle ultime frontiere da abbattere \u00e8 poter utilizzare i propri dispositivi digitali in ogni circostanza, con ogni condizione meteorologica, in ogni situazione.<\/p>\n\n\n\n

Naturalmente, la vita quotidiana non porta chiunque a vivere esperienze estreme, perci\u00f2 qualcuno potrebbe sentirsi non interessato al fatto che il suo smartphone sia impermeabile: non faccio immersioni subacquee, che me ne importa?<\/p>\n\n\n\n

In realt\u00e0, la certificazione IP<\/a><\/strong> per uno smartphone non vuol dire che posso usare sott’acqua il telefonino<\/em>, ma molto di pi\u00f9: in effetti, la Marcatura Internazionale di Protezione (IP67 IP68) mi garantisce che acqua e polvere non possono entrare nel mio taccuino digitale,<\/em> danneggiandolo in modo a volte irreparabile.<\/p>\n\n\n\n

Con i costi vertiginosi che questi dispositivi hanno quando li si acquista, e visti i costi di riparazioni dovuto al pensare che “tanto a me non accadr\u00e0 mai”…<\/p>\n\n\n\n

In realt\u00e0, tutti viviamo e lavoriamo in ambienti polverosi o “bagnati”, e ci portiamo il telefonino in bagno o in cucina: luoghi in cui siamo cos\u00ec abituati a polveri (farine alimentari, pulviscolo domestico) e liquidi (acqua, latte, sughi, caff\u00e8…) che non li consideriamo come rischiosi.<\/p>\n\n\n\n

\"Samsung<\/figure>\n\n\n\n

Ho visto nella mia esperienza di contatto con il pubblico telefonini da cestinare dopo aver preso un acquazzone, telefonini volati nella tazza del cesso, telefoni scivolati da una tasca in una pozzanghera, telefoni “pucciati” nel cappuccino… La fortuna \u00e8 cieca ma la sf…ortuna<\/em> ci vede benissimo: come scriveva Arthur Bloch, se qualcosa potr\u00e0 andar male, andr\u00e0 male<\/a><\/em>, causando il maggior numero possibile di danni. Beh, allora vale davvero la pena pretendere di avere dispositivi pi\u00f9 resistenti, ed ecco che IP67 o IP68 diventano una sigla importante da conoscere, per capire da cosa il nostro smartphone \u00e8 protetto.<\/p>\n\n\n\n

In fondo al post aggiungo un breve riassunto tratto dalla tabella consultabile su Wikipedia<\/a>. <\/p>\n\n\n\n

Intanto, vi faccio pensare ad un’altra cosa: esiste una lunga serie di problemi a schermi di telefonini dovuti (secondo i produttori, vedi Apple e Samsung<\/a>) a “eccessiva pressione esercitata sul dispositivo<\/em>“… che per\u00f2, dalle dichiarazioni dei proprietari, altro non hanno fatto che tenerli nella propria borsa e l\u00ec trasportarli durante la loro giornata..<\/p>\n\n\n\n

Una simpatica descrizione (anche molto puntuale) si trova anche su FiveStarsPC<\/a><\/p>\n\n\n\n

Significato della codifica IP<\/h3>\n\n\n\n

La codifica, istituita dalla norma EN60529<\/strong> recepita dalla norma del Comitato Elettrotecnico Italiano<\/a> CEI70-1<\/strong>, \u00e8 la seguente: <\/p>\n\n\n\n

IPXXab <\/strong><\/p>\n\n\n\n

Al termine fisso IP<\/em> seguono due cifre e due lettere opzionali. <\/p>\n\n\n\n

La prima cifra va da 0 a 6 e indica il livello di protezione che l’involucro fornisce contro l’accesso di parti pericolose (e.s., conduttori elettrici, parti mobili) e l’ingresso di oggetti solidi estranei.<\/p>\n\n\n\n

La seconda cifra va da 0 a 9 e indica il livello di protezione che l’involucro fornisce contro l’accesso di liquidi.<\/p>\n\n\n\n

Ricordiamoci sempre che “impermeabile” (waterproof<\/em>) non vuol dire “subacqueo” (water resistant<\/em>)! Quindi per esempio: <\/p>\n\n\n\n