AutoForce - Intelligence

AutoForce –czyli czemu służy automatyczna regulacja nacisku redlic?

Gleby kamieniste potrzebują większego nacisku redlic, aby ziarno zostało umieszczone na tej samej głębokości. Gdyby nacisk redlic był zbyt mały, korpus redlicy pracowałby niespokojnie, a ziarna kiełkowałyby w różnym czasie i nierównomiernie.
Aby uniknąć zagęszczania gleby, pola o lekkich glebach lub gleby wrażliwe na nacisk wymagają mniejszego nacisku redlic. W tym przypadku zbyt duży nacisk redlic zagęszczałby glebę i spowalniał rozwój korzeni, mimo że wszystkie ziarna zostały wysiane na tej samej głębokości.
Rzadko zdarzają się pola jednorodne. Nacisk redlic należy dostosowywać do każdej sekcji pola.
Dlatego firma HORSCH opracowała automatyczną regulację nacisku redlic.

Czujnik ciśnienia AutoForce: ciężar jest rejestrowany przy użyciu technologii piezo (czujnik ciśnienia).

Jak pracuje AutoForce?

Szerokość roboczą maszyny można podzielić na 1, 2 lub 4 sekcje.
Ciśnienie mierzone jest na obu kołach podporowych za pomocą czujnika
System kontroluje ciśnienie cylindrów na równoległobokui reguluje go tak, aby ciężar na kołach podporowych był zawsze taki sam. Jest to możliwe dzięki konstrukcji Maestro,która pozwala na przenoszenie ciężaru na szynę siewną.
Nacisk redlic zmienia się wtedy automatycznie z 150 kg do 350 kg

Nazwa	cel	Czas życia	Typ	Dostawca
CookieConsent	Zapisz zgodę na używanie ciasteczek.	1 rok	HTML	Website
PHPSessID	Retains user states on all page requests	3 miesięcy	HTTP	php
fe_typo_user	This cookie is set by TYPO3 to uniquely identify a user. It offers the user better user guidance.	1 session	HTTP	TYPO3
be_typo_user	be_typo_user Is used to identify a backend session when a backend user logs into the TYPO3 backend or frontend.	1 session	HTTP	TYPO3
mtm_cookie_consent	Saves your consent to use matomo tracking.	1 session	HTTP	TYPO3
mtm_consent_removed	Saves your opt-out from tracking with Matomo.	1 miesiąc	HTTP	Matomo

Nazwa	cel	Czas życia	Typ	Dostawca
personalization_id	Marketing Used to determine the number of visitors who access our website via Twitter advertising content and can be used for targeted advertising.	2 lat	HTTP	Google Tag Manager / Twitter
ANID	Marketing Used to play out advertisements.	10 lat		Google
_fbc	Marketing / Tracking Used by Facebook to deliver a range of advertising products, such as real-time bidding from third parties.	3 miesięcy		Google Tag Manager / Facebook
datr	Marketing / Tracking Used to identify the web browser that connects to Facebook, irrespective of the logged-in user. This cookie plays a key role in Facebook’s security and integrity functions.	2 lat		Google Tag Manager / Facebook
fr	Marketing / Tracking Provides information to Facebook for linking the functionality of the social plugin. It sends information to Facebook irrespective of whether you have a Facebook account or are logged in to the social network.	3 miesięcy	HTML	Google Tag Manager / Facebook
sb	Marketing / Tracking Provides information to Facebook for linking the functionality of the social plugin. It sends information to Facebook irrespective of whether you have a Facebook account or are logged in to the social network.	3 miesięcy	HTML	Google Tag Manager / Facebook
_fbp	Marketing / Tracking Used by Facebook to display a range of advertising products, such as real-time bids from third-party advertisers.	7 dni	Pixel	Google Tag Manager / Facebook
_gcl_au	Marketing / Tracking Used by Google AdSense to learn about the effectiveness of advertising on websites that use their services.	1 dzień	HTML	Google Tag Manager / Google Ad
RUL	Marketing / Tracking Used by DoubleClick to determine whether website ads are displayed correctly.	1 rok		Google DoubleClick
IDE	Marketing / Tracking Contains a randomly generated user ID. Google uses this ID to identify users across different web sites and domains and display personalised advertising.	1 rok		Google DoubleClick
__adroll_fpc	Marketing / Tracking Used to identify visitors on repeat visits and across different devices. Allows the website to present relevant ads to the visitor.	1 session	HTTP	Adroll
NID	Marketing / Tracking Google’s cookies store information about user settings and information for Google services.	6 miesięcy		Google Ads Optimazation
__Secure-3PAPISID	Marketing / Functional Used for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	2 lat		Google
__Secure-3PSID	Marketing / Functional Used by Google for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	2 lat		Google
__Secure-3PSIDCC	Marketing / Functional Used by YouTube / Google for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	1 rok		YouTube / Google
CONSENT	Marketing / Functional Save CONSENT cookie settings.	10 lat		Google / YouTube
_ar_v4	Optimises ad delivery based on the combination of the user’s online behaviour and bids from advertisers to display user ads.	1 rok	HTTP	Google DoubleClick
MYSAPSSO2	Used for targeting to create a profile of the interests of website visitors and to display relevant, personalised Google advertising.	1 session		SAP

Nazwa	cel	Czas życia	Typ	Dostawca
_ga	Statistics Used to distinguish unique users by assigning a randomly generated number as a client identifier.	2 lat	HTML	Google Analytics
_ga_XXXXXXXXXX	Statistics Contains a unique identifier used by Google Analytics 4 to determine whether two different hits across browsing sessions belong to the same user.	2 lat	HTML	Google Analytics
_gid	Statistics Provides functionality for counting and tracking page views.	1 dzień	HTML	Google Analytics
1P_JAR	Statistics Used by Google to display personalised advertising on Google websites based on current search queries and previous interactions.	1 miesiąc		Google
_hjAbsoluteSessionInProgress	Statistics Used to detect the first page-view session of a user. It has a true/false value.	30 minuty		Hotjar
_hjFirstSeen	Statistics This cookie is set to identify a new user’s first session. It has a true/false value that specifies whether Hotjar has seen this user for the first time. It is used by recording filters to identify new user sessions.	1 session		Hotjar
_hjTLDTest	Statistics When the Hotjar script is executed, we try to determine the most generic cookie path to use in place of the hostname of the device hosting the page. This is done to allow cookies to be shared across subdomains (if applicable). To determine the most generic path, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	1 session		Hotjar
_hjid	Statistics Hotjar cookie that is set the first time a customer lands on a page running the Hotjar script. It is used to persist the Hotjar user ID, which is unique for this page, in the browser. This ensures that the behaviour on subsequent visits to the same page is assigned to the same user ID.	365 dni		Hotjar
_hjIncludedInPageviewSample	Statistics This cookie is set to tell Hotjar whether this user is included in the data sample defined by the site’s page-view limit.	30 minuty		Hotjar
_hjIncludedInSessionSample	Statistics This cookie is set to tell Hotjar whether this user is included in the data sample defined by the website’s daily session limit.	30 minuty		Hotjar
_pk_id	Statistics Saves a few user details such as the unique user ID.	13 miesięcy		Matomo
_pk_ses	Statistics Temporary cookie that temporarily stores data about a visit.	90 minuty		Matomo