Remote AI teams blog

Community Updates

This section shares updates from Remote AI Teams programs, community activities, and training groups. Content may include progress updates, project milestones, and examples of learning and participation across our teams and partner platforms.

This is part two of my journey through North Queensland with Rusel, a traditional Aboriginal knowledge holder who knows literally hundreds of healing plants. His people have used them for centuries β€” some are backed by science, many haven't been tested yet.

Out on Country I introduced him to a basic AI I'd trained in GPT. The AI was 'role-playing' as a cultural researcher in a community, carefully asking about plants and taking notes. The point? To show how Remote AI Teams can help preserve and share traditional knowledge β€” on terms set by the community.


🌿 Fuel Check Request: Palmerville to Darwin Field Trip β€” April/May 2026

Updated for community feedback

Route map β€” Townsville to Palmerville to Darwin via the Savannah Way

Remote AI Teams is preparing for our upcoming field trip from Townsville through Palmerville and across to Darwin. Because fuel availability can change quickly in remote areas, we’re asking locals, travellers, station contacts, and anyone familiar with the route to help us confirm current fuel access.

What we need to know: Are the fuel stops marked on our route currently operating, and are there any restrictions, outages, road impacts, or places where travellers should ring ahead before relying on fuel?

The mission: Work alongside Western Yalanji traditional owners at Palmerville Station to document specialised bush food plants β€” including Kakadu plum, spinifex, and other species with medicinal and nutritional potential β€” using AI-powered field scanning and DNA/soil sampling kits.

The route: Starting from Townsville, the team will travel via the Peninsula Developmental Road to Palmerville Station for a 14-day deep dive, then head west along the Savannah Way through to Darwin β€” covering approximately 5,560 km of remote and regional travel.

If you’ve driven this route recently, please comment below with:

Remote AI Teams β€” Training AI in Remote Australia

Share fuel info or route advice

Tap a route stop below. We’ll connect each stop to your latest fuel-price screenshots and trip notes as you send them through.

Remote AI Teams field trip route map

Cairns

Cairns is now on the route map as the first working fuel stop. I can usually source public web data here, then you can fill in the remote gaps from your phone app.

Fuel prices are guidance only. Public web sources may be delayed or incomplete, especially in remote areas. Confirm locally before travel.

AI fuel strategy β€” unleaded trip plan to Darwin

This version now assumes the vehicle arrives empty in Cairns, fills a full 180 L of unleaded before departure, and only shows the confirmed places where fuel is actually planned to be bought.

180 LTotal usable fuel capacity
UnleadedFuel type for this trip
23 L/100 kmTowing consumption used for planning
30 LSafety reserve used in planning
Cairns β€” full starting fill before departure
Ravenshoe β€” first practical top-up
Georgetown β€” major western Queensland refuel
Normanton β€” important confirmed top-up before the longer Gulf leg
Burketown β€” critical remote refuel before the uncertain stretch
Robinson River β€” confirmed bridge fuel point
Borroloola β€” major refill before the NT leg
Jabiru β€” optional top-up if using the active route before Darwin

How this corrected model works: This section now focuses only on the places where fuel is actually recommended to be bought. It removes minor route points and non-essential stops, and keeps the plan centred on the practical top-up decisions needed to get to Darwin safely.

  • Start with a full fill in Cairns
  • Use unleaded only for this model
  • Show only the stops where fuel is actually planned to be purchased
  • Exclude uncertain fuel points such as Hells Gate
  • Keep the plan readable as a real buying strategy, not a route dump
Fuel stop Distance to next planned top-up Fuel needed for next leg Recommended purchase Estimated cost Why buy here
Cairns 417 km 95.9 L 180.0 L full fill $404.82 Best starting fill before leaving the major supply area
Ravenshoe 265 km 61.0 L 61.0 L $136.34 First practical top-up after departure without cluttering the plan with minor stops
Georgetown 370 km 85.1 L 85.1 L $209.35 Major confirmed top-up before the longer western run
Normanton 350 km 80.5 L 80.5 L $231.03 Important confirmed top-up even though pricing is higher
Burketown 440 km 101.2 L 101.2 L $306.53 Critical remote fuel point before the uncertain stretch
Robinson River 160 km 36.8 L 36.8 L $95.31 Confirmed bridge stop replacing uncertain options like Hells Gate
Borroloola 720 km 165.6 L 150.0 L $337.50 Major remote refill before the longest Northern Territory stretch
Jabiru 255 km 58.6 L 58.6 L $124.11 Optional final top-up if that route is being used before Darwin
Darwin Destination β€” No planned purchase $0.00 End of the trip model
Current estimated unleaded fuel spend to Darwin: $1,844.99

This version now reads as a practical refuelling plan: only the recommended top-up stops are shown, with estimated litres, costs, and the reason each stop is included.

Comments are open below. You do not need to sign in, but submissions are reviewed before appearing so we can keep the information useful and spam-free.

No sign-in required. Comments are moderated before they appear publicly.

Approved comments

No public comments yet.

Trip planning β€” drive days and sampling days

This revised draft treats the route as a proper plant research trip rather than a straight run to Darwin. It now alternates more clearly between driving days and sampling days, while also showing the approximate kilometres covered on each movement day.

Plant research link: Field updates and plant intelligence work can be fed into MyTurboBot so readers can follow the broader plant research direction behind this trip.

Field systems overview: This trip is also being used to run a dedicated mobile field-data system built around Starlink and an onboard Mac mini. The Mac mini will operate as a secure local research hub with its own internal hard drive and its own internal LLM so drone footage, plant samples, mapping outputs, and field notes can be stored directly during the journey. While Starlink will be used whenever possible, the Mac mini provides the local locked-down copy of the expedition data so research is retained even when internet coverage is limited.

~12 daysCurrent working estimate to Darwin
300–400 kmPreferred drive-day window
1 daySampling / testing between travel legs
FlexibleCan stretch or shorten to suit fuel and camp

Day 1 β€” Cairns to Ravenshoe (~140 km)

Working plan: Fuel up in Cairns and make the first shorter move toward Ravenshoe.

Fuel / camp position: Full starting fill in Cairns, refill water tanks where possible before departure, then roadside or remote mobile camp in the Ravenshoe corridor.

Field focus: Settle into the trip, begin fuel sample collection, and watch the roadside for early plant zones worth logging. This opening leg also sets up the 4T AI-driven drone program, with plant signatures being prepared for later aerial mapping flights over target zones.

Reference points to plan ahead: Ravenshoe sits near upland Tablelands country with access toward the Jirrbal area and nearby park/forest zones such as Tully Falls / Koombooloomba country. This makes it a useful early contact point for public-land checks and Traditional Owner awareness before sampling.

Systems check: Confirm Starlink is running, the Mac mini is powered and operational while driving, and log the day’s connection speeds and system performance.

Day 2 β€” Ravenshoe field day

Working plan: Hold in the Ravenshoe / upland area for a dedicated sampling and testing day.

Fuel / camp position: Stay camped in the same local working area.

Field focus: In the Ravenshoe upland zone, start by identifying useful high-rainfall and tableland species that may differ from the drier western country further ahead. Record photos, notes, scans, sample locations, and update MyTurboBot with plant research observations from the field. This day is about building a reference base for how plant communities change as the trip moves west.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. At lighter loads it appears to run at roughly 0.67 litres per hour (about 6 L over 9 hours), so an 8 hour field day should still be counted carefully against the main fuel reserves.

Reference points to plan ahead: Use Ravenshoe as the contact base for nearby public forest and national-park access enquiries, with attention to Jirrbal country and any local permissions or restrictions that may apply before entering specific work zones.

Systems check: Confirm Starlink remains active in camp, the Mac mini is collecting trip data locally, confirm Basecamp access is available, and record any working upload or sync speeds achieved in the area.

Day 3 β€” Ravenshoe to Georgetown (~265 km)

Working plan: Top up at Ravenshoe and continue toward Georgetown.

Fuel / camp position: Top up at Ravenshoe, refill water tanks where available, then aim for a practical roadside camp near or before Georgetown depending on daylight.

Field focus: Continue fuel sample collection and watch for changing vegetation zones along the route.

Reference points to plan ahead: Georgetown becomes the next planning anchor for Gulf Savannah public land, regional reserves, and local community contact points before moving further west.

Systems check: Confirm the Mac mini remains operational during the drive, Starlink performance is logged where available, and the day’s data is safely stored to the internal field drive.

Day 4 β€” Georgetown field day

Working plan: Stay in the Georgetown region for a full fieldwork block.

Fuel / camp position: Hold camp near the Georgetown working area.

Field focus: In the Georgetown region, begin looking more seriously for drier-country medicinal plants including likely Gumbi Gumbi country and other species used in Indigenous healing practice. Record the exact tree or shrub position, environmental conditions, associated species, and any signs of bark, leaf, or antiseptic-use traditions that may need follow-up with local knowledge holders. Upload all mapped observations into MyTurboBot. This is also a key aerial AI modelling day, where the 4T drone can be flown over a broader 20 km area to test plant-signature recognition and support the mapping plan.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. At lighter loads it appears to run at roughly 0.67 litres per hour (about 6 L over 9 hours), so generator fuel use should be tracked carefully against the vehicle and reserve fuel plan.

Reference points to plan ahead: Georgetown should be treated as an advance contact point for nearby public-country access and regional landholder / community checks before moving toward the more remote Gulf sections.

Systems check: Confirm Starlink, the Mac mini, and the local LLM workflow are all active while field research is underway, note the speeds or offline performance being achieved, and confirm Basecamp login access is available.

Day 5 β€” Georgetown to Normanton (~300 km)

Working plan: Fuel up and move on toward Normanton.

Fuel / camp position: Top up in Georgetown if needed, refill water tanks before leaving town, then move through to Normanton and camp where the next western leg starts cleanly.

Field focus: Movement day with selective roadside checks for promising species and visible environmental changes.

Reference points to plan ahead: Normanton is important for Lower Gulf planning. Use it as a contact point for Gulf community links, ranger contacts, and public-land / native-title awareness before any nearby sampling work.

Systems check: Confirm the onboard Mac mini is still running continuously, that Starlink usage is being monitored, and that all movement-day data is being saved locally.

Day 6 β€” Normanton field day

Working plan: Stay around the Normanton area rather than pushing on immediately.

Fuel / camp position: Hold camp in a practical working area and prepare for the next western remote leg.

Field focus: Around Normanton and the Lower Gulf, pay attention to species and healing practices associated with bark, leaf wash, antiseptic soap trees, and medicinal eucalyptus uses. This is a good day to look for how local plant uses may shift with the Gulf conditions and to note any areas where elder guidance or community contact would be essential before further sampling. Update MyTurboBot with all mapped field notes, and use the 4T AI-driven drone to scan a wider aerial search zone for plant signatures that can be checked on the ground.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. At lighter loads it appears to run at roughly 0.67 litres per hour, so an 8 hour working day still needs to be counted so the main fuel reserves are not accidentally overcommitted.

Reference points to plan ahead: The Normanton / Karumba district intersects with important Gulf Aboriginal country. Treat this as a day for both fieldwork and checking the right community / ranger / land-contact pathways for any nearby plant work.

Systems check: Confirm Starlink and the Mac mini are functioning throughout the field day, tally the connection quality and speeds achieved while updating research records, and confirm Basecamp can be reached.

Day 7 β€” Normanton to Burketown (~380 km)

Working plan: Fuel up and continue toward Burketown.

Fuel / camp position: Fuel up at Normanton and/or Burketown based on range, refill water tanks where available, then roadside camp in a practical remote area before the uncertain stretch.

Field focus: Long movement day with opportunistic plant and route notes only where practical.

Reference points to plan ahead: Burketown is a key western Gulf contact point. Nearby references include Carpentaria Land Council networks and the broader Boodjamulla / Lawn Hill public-land context further inland for future planning.

Systems check: Confirm the Mac mini remains operational on the move, Starlink performance is tracked, all fuel, plant, and route data is being written to the internal drive, and Basecamp login is available if needed.

Day 8 β€” Burketown field day

Working plan: Use this as another dedicated field day before crossing the next remote section.

Fuel / camp position: Hold a mobile camp position in the Burketown working zone.

Field focus: In the Burketown working zone, compare Gulf-country plants against the earlier inland observations and watch for species tied to saline, floodplain, and hotter lowland conditions. This day should focus on finding locally useful medicinal or antiseptic species, marking tree positions, and taking small vacuum-sealed reference samples only where culturally and practically appropriate. Upload the latest findings into MyTurboBot. The 4T drone should also be flown here to map the area from the air and test whether the current plant-signature library is matching what is being found on the ground.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. Its draw at lighter loads appears to sit around 0.67 litres per hour, so fuel reserves should still be tracked carefully before the next remote movement.

Reference points to plan ahead: Burketown can be used as the last stronger Queensland planning point before pushing further into the Gulf crossing. Advance community and public-land enquiries should be lined up from here where possible.

Systems check: Confirm both Starlink and the Mac mini are stable during the field day, log what upload performance or local processing speed is being achieved, and confirm Basecamp access remains available.

Day 9 β€” Burketown to Robinson River / bridge camp (~300 km)

Working plan: Bridge through the uncertain section and use Robinson River as the confirmed fuel point.

Fuel / camp position: Use Robinson River as the bridge fuel point, refill water where practical, and camp in a mobile position that supports the Borroloola run.

Field focus: Focused route-control day with fuel comparison, country notes, and selective plant observation.

Reference points to plan ahead: Robinson River is an Aboriginal community reference point and should be treated carefully as a contact and permissions anchor rather than just a fuel stop.

Systems check: Confirm the Mac mini continues to hold the local research archive, Starlink performance is noted where possible, data is syncing or storing correctly during transit, and Basecamp is reachable for storage backup if required.

Day 10 β€” Robinson River / transition field day

Working plan: Hold position for another field and reset day before the next long movement.

Fuel / camp position: Maintain a simple remote roadside or mobile camp position.

Field focus: Use this transition day to consolidate plant records, fuel notes, testing work, and route planning while checking which species or medicine-related observations now need verification from local elders or community contacts. Make sure MyTurboBot is updated with the current plant research gathered so far.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. Even on transition days, if the system is run for testing or processing, its Yamaha fuel use still needs to be checked so it does not eat into the main trip reserves.

Reference points to plan ahead: Use this as a contact day for community awareness, local access considerations, and confirming the next safe movement toward Borroloola.

Systems check: Confirm Starlink remains available where possible, the Mac mini and onboard LLM are still operating correctly, and note the day’s practical field performance.

Day 11 β€” Robinson River to Borroloola (~350 km)

Working plan: Move through to Borroloola and set up for the Northern Territory leg.

Fuel / camp position: Major refill at Borroloola, refill water tanks at the same time, then camp to suit the next move toward Jabiru or the Darwin approach.

Field focus: Use the day mainly for movement, logistics, and preparing the next stage of plant research.

Reference points to plan ahead: Borroloola is a major NT planning anchor with clear Aboriginal-community context and links toward places such as Barranyi / North Island National Park and nearby Indigenous protected areas. It is a strong point to organise permissions and next-stage sampling contacts.

Systems check: Confirm the Mac mini is still running as the secure field-data hub, Starlink speeds are logged, all drone, plant, and route data is retained on the internal drive, and Basecamp can be accessed for uplink storage.

Day 12 β€” Borroloola field / decision day

Working plan: Use this day either as a final dedicated sampling day or as the decision point for the next push toward Jabiru and Darwin.

Fuel / camp position: Stay based from Borroloola or a nearby practical remote camp depending on the route choice.

Field focus: Around Borroloola and into the Northern Territory zone, the research priority should broaden toward species more likely to align with Kakadu plum country and other northern medicinal plant systems. This is also the place to prepare for direct discussions with local knowledge holders if available, especially around healing remedies, bark uses, soaps, and antiseptic plants. Update MyTurboBot with the latest field intelligence and decide whether the next day is another sampling block or a longer movement day. This is also a major aerial AI modelling opportunity where the 4T drone can load target plant signatures, fly up to a 20 km search area, and strengthen the mapping plan before the next movement.

Generator reminder: Allow for the Yamaha 2.4 kVA generator on field days. At lighter loads it appears to run at roughly 0.67 litres per hour, so this extra use should still be part of the daily fuel check so the main reserves remain protected.

Reference points to plan ahead: Treat Borroloola as the key place to confirm who should be contacted next for public-land, community, ranger, and protected-area access before the final northern run.

Systems check: Confirm Starlink, the Mac mini, and the local LLM remain operational before leaving the area, record the connection quality and system speeds achieved so far on the trip, and confirm Basecamp login is available before departure.

Current working trip estimate: About 12 days to Darwin when proper sampling days are included between drive legs

Aerial AI modelling with the 4T drone: At selected field days, the team will also deploy the 4T drone across working search areas of up to 20 km. The 4T is an AI-driven drone platform being developed to recognise specific plant signatures from the air. Before each flight, the relevant plant signatures and search targets are loaded into the system so the drone can help identify promising zones for ground follow-up, mapping, and upload into MyTurboBot. This helps show that the trip combines field botany, AI modelling, and aerial survey into one professional operating workflow.

This is the stronger working version so far. Next step is to tighten the exact kilometres, fuel-up quantities, and which sampling days should be locked in versus left flexible.

Estimated budget for the 12 day trip

This is a practical working budget based on the current 12 day trip model. It focuses on the three main cost items that are easiest to estimate in advance: vehicle fuel, generator fuel, and food for two people.

Budget item Working estimate How it was estimated
Main vehicle fuel $1,845 Based on the current working fuel plan across the route, including the confirmed fuel chain and remote top-up logic already mapped on this page.
Generator fuel $40–$60 Based on the Yamaha 2.4 kVA generator running at lighter load, roughly 0.67 L/hour. Across around 5 to 6 active field days at about 8 hours per day, this creates a modest but important extra fuel allowance.
Food for 2 people $550–$650 Assumes an initial Cairns shop of about $350 covering the first 7 days, then a more expensive remote top-up later in the trip to finish the 12 day run.
Miscellaneous trip costs $150–$300 Allows for small but realistic extras such as oil, gloves, ice, snacks, a hot meal on the road, and other minor field or travel purchases that tend to come up on remote runs.
Estimated 12 day trip budget: Approximately $2,585 to $2,855 based on current fuel, generator, food, and miscellaneous trip assumptions

This estimate is intentionally simple and public-facing. It gives readers a realistic overview without pretending the final trip cost is fixed. Remote food pricing, extra field days, or longer generator use could increase the budget, but this is the current working baseline.

Planning note: This trip-planning and budget model was designed by our local AI agent to help shape route logic, field operations, supply planning, and cost forecasting before departure.

Privacy policy

Please reach us at allan@remoteaiteams.com if you cannot find an answer to your question.

What Personal Data We Collect

1. What Personal Data We Collect, Why We Collect It, and How It Is Used

(I) When you browse or visit our website

Purpose: To improve the performance and security of our website; personalise your experience; remember settings; and analyse usage patterns.

(II) When you interact with Remote AI Teams through the website
(1) When you request a demonstration or make an inquiry

Personal Data We Collect: Full name; email address; country; company or organisation name; phone number; and any additional information you provide.

Purpose: To respond to your request; schedule a demo; provide further details about our AI-supported employment and training systems; or send marketing material (with consent).

(2) When you contact us for general support

Personal Data We Collect: Name; email address; company or community affiliation; job title (if provided); phone number; any information shared in your message.

Purpose: To assist with your enquiry, provide support, or respond to partnership or community engagement requests.

(3) When you apply for a role or register as a worker

Personal Data We Collect: Name; email address; phone number; location; CV/resume; skills; previous work history; any additional details you provide.

Purpose: To evaluate your suitability for remote or AI-supported roles; to communicate during the recruitment or onboarding process; to build your agent and training profile.

How We Protect and Retain Your Personal Data

2. How We Protect and Retain Your Personal Data

2.1 Security β€” At Remote AI Teams, we take data protection seriously. We implement appropriate technical, administrative, and physical safeguards to protect your Personal Data against unauthorised access, alteration, disclosure, or destruction. These measures include encryption, access controls, secure hosting environments, and regular security assessments.

2.2 Retention of Your Personal Data β€” We retain Personal Data only for as long as necessary to fulfil the purposes for which it was collected, comply with legal obligations, resolve disputes, and enforce agreements. When Personal Data is no longer required, it is securely deleted or anonymised.

Engagement and Right of Use

Remote AI Teams – End User Agreement (EUA)

1. Engagement and Right of Use

Remote AI Teams grants the End User a limited, non-exclusive, non-transferable right to access and use the platform and associated services for the purposes of training, workforce participation, and related activities as described in the relevant program documentation.

2. Fees

Unless otherwise agreed in writing, access to training programs and platform tools may be subject to fees as outlined in the applicable program schedule or Exhibit A. Remote AI Teams reserves the right to adjust fees with reasonable notice.

3. Term

This Agreement commences on the date of acceptance and continues for the duration of the applicable program or until terminated by either party in accordance with these terms.

4. Warranties

Remote AI Teams provides the platform and services on an "as is" basis. While we endeavour to ensure reliability and accuracy, we do not warrant that the platform will be uninterrupted, error-free, or meet all specific requirements of the End User.

5. Liability

To the maximum extent permitted by law, Remote AI Teams shall not be liable for any indirect, incidental, special, or consequential damages arising from the use of, or inability to use, the platform or services.

6. Indemnification

The End User agrees to indemnify and hold harmless Remote AI Teams, its officers, employees, and agents from any claims, damages, or expenses arising from the End User's misuse of the platform or breach of this Agreement.

7. Support

Remote AI Teams will provide reasonable technical and program support during standard business hours. Support availability and response times may vary depending on the nature of the inquiry and program participation level.

8. AI-Generated Interactions

The platform may utilise AI-generated content, responses, and learning tools. These tools are designed to assist and support learning and communication. They do not replace human judgment, mentorship, or cultural authority. End Users acknowledge that AI outputs may contain inaccuracies and should be verified where appropriate.

9. Data Insights

Remote AI Teams may collect and analyse aggregated, de-identified usage data to improve platform performance, training outcomes, and service delivery. Individual Personal Data will be handled in accordance with our Privacy Policy.

10. Suspension

Remote AI Teams reserves the right to suspend or restrict access to the platform if the End User breaches this Agreement, engages in harmful conduct, or if required for maintenance, security, or legal compliance.

11. Confidentiality

Both parties agree to treat as confidential any proprietary or sensitive information disclosed during the course of participation. This obligation survives termination of this Agreement.

12. Third-Party Services

The platform may integrate with or link to third-party services. Remote AI Teams is not responsible for the content, privacy practices, or availability of third-party platforms.

13. Fair Use

End Users agree to use the platform and services in a fair and reasonable manner, consistent with their intended purpose. Excessive, automated, or abusive use may result in access restrictions.

14. Publicity

Remote AI Teams may reference the End User's participation in programs for promotional or reporting purposes, unless the End User opts out in writing. No personal identifying information will be used without consent.

15. General Terms

This Agreement constitutes the entire agreement between the parties regarding its subject matter. It is governed by the laws of Queensland, Australia. Any disputes shall be resolved through good faith negotiation before pursuing formal resolution.

Exhibit A β€” Program Schedule

Details of specific programs, fees, timelines, and deliverables are outlined in the applicable Program Schedule, which forms part of this Agreement when signed or accepted by both parties.