Forums
New posts
Forum list
Search forums
What's new
New posts
New resources
Latest activity
Trending Threads
Resources
Latest reviews
Search resources
FarmTV
Farm Compare
Search
Tokens/Searches
Calendar
Upcoming Events
Members
Registered members
Current visitors
New Resources
New posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Forum list
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Farm Machinery
Precision Farming & GPS
iPad machine control
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="funtime" data-source="post: 1109642" data-attributes="member: 19352"><p>Cheers Andy although I've just seen Reed are now in charge hmmm.</p><p>Sleepy, I understand where your coming from there are a lot of advantages, broad devise compatibility being the main. I don't know much on HTML5 (web pages) but I understand the biggest constraint that make it less than ideal is having a devise powerful enough to process a glitzy webpage capable of working in a variety of different formats (screen sizes ect) and then continually transmit it, traditionally this would be expensive and fragile. Laptops, tablets ect have big processors for making things look nice for us. Most microprocessors don't because all they have to do is read some signals, process 'simple' code and switch a few switches, generally cheap and relatively robust. Things like the Raspberry Pi are changing this though they seem to be primarily capable of user interface but can also have control hardware added. Reaction speed should also be considered, there's quite a few processes involved, delay is not ideal with heavy machinery. </p><p>The beauty of the app is you can get the tablet to do all the graphical stuff and have a very light stream of data transmitting to and from a microprocessor eg. tank full, change rate to... ect. And then leave the microprocessor to run the implement. The other beauty is if the User Interface goes tit up which is the most likely bit to crash being by far the most complex, it doesn't take down the important bit that's doing the work.</p><p></p><p>From my basic understanding of Isobus it's very robust 'language' based upon Canbus which was designed for use in the automotive industry. The cable is a tad elaborate and expensive but your always going to have to run a power cable regardless. And there's little chance of interference. My problem with it is it's tied up by the big manufactures and it doesn't seem easy for the farm engineer to work on/ develop it.</p><p></p><p>That's my take on it, I could be feeding you a load of horse **** tho.</p></blockquote><p></p>
[QUOTE="funtime, post: 1109642, member: 19352"] Cheers Andy although I've just seen Reed are now in charge hmmm. Sleepy, I understand where your coming from there are a lot of advantages, broad devise compatibility being the main. I don't know much on HTML5 (web pages) but I understand the biggest constraint that make it less than ideal is having a devise powerful enough to process a glitzy webpage capable of working in a variety of different formats (screen sizes ect) and then continually transmit it, traditionally this would be expensive and fragile. Laptops, tablets ect have big processors for making things look nice for us. Most microprocessors don't because all they have to do is read some signals, process 'simple' code and switch a few switches, generally cheap and relatively robust. Things like the Raspberry Pi are changing this though they seem to be primarily capable of user interface but can also have control hardware added. Reaction speed should also be considered, there's quite a few processes involved, delay is not ideal with heavy machinery. The beauty of the app is you can get the tablet to do all the graphical stuff and have a very light stream of data transmitting to and from a microprocessor eg. tank full, change rate to... ect. And then leave the microprocessor to run the implement. The other beauty is if the User Interface goes tit up which is the most likely bit to crash being by far the most complex, it doesn't take down the important bit that's doing the work. From my basic understanding of Isobus it's very robust 'language' based upon Canbus which was designed for use in the automotive industry. The cable is a tad elaborate and expensive but your always going to have to run a power cable regardless. And there's little chance of interference. My problem with it is it's tied up by the big manufactures and it doesn't seem easy for the farm engineer to work on/ develop it. That's my take on it, I could be feeding you a load of horse **** tho. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Farm Machinery
Precision Farming & GPS
iPad machine control
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top