Frequently asked questions

In agent banking, a GPS tracker is usually a USB GPS receiver plugged into the agent's computer. It reads satellite signals and passes the position to the banking application, which stores the coordinates with each transaction. The RAIVENS USB GPS receiver needs no SIM card or data plan of its own, so the bank gets an independent location for every withdrawal, deposit or inquiry made at a BC or CSP point.

Geo-tagging proves that a transaction happened at the agent's registered location. Banks use it to spot agents working from unregistered places, to investigate disputes and suspected fraud with evidence, to support audits and to map where their agent network is active. A USB GPS receiver from Raivens gives each BC point this evidence automatically, without asking the agent to type an address or relying on coarse internet-based location.

Plug the receiver into a free USB port, then download and install the driver for your receiver version from the Raivens support page. Windows will list the receiver as a COM port. Select that port in your banking or kiosk application and keep the receiver near a window or under open sky. The first position fix usually arrives within a minute, after which the application reads location continuously.

GPS signals are weak inside buildings, so placement matters. A receiver on a windowsill or near an outside wall usually gets a fix, and a USB extension cable can bring it closer to the sky in deeper rooms. Metal roofs, basements and thick concrete can block signals completely, so test the position once during installation. The Raivens support team can advise on placement for difficult sites.

Raivens has produced its USB GPS receiver in versions 4.0, 5.0 and 8.0. Each connects over USB, appears as a COM port and outputs standard NMEA location data, so applications written for one version can usually read the others. Drivers differ by version, so download the one that matches your device. For new deployments, the sales team will recommend a version for your operating system and quantities.

A vehicle GPS tracker has its own SIM card and sends its location to a server by itself. A USB GPS receiver has no SIM; it gives position data to the computer it is plugged into, and the banking application decides what to store and send. That makes the Raivens receiver simple to deploy at BC points, with no extra data plan, while every transaction record still carries a verified location.

Yes. Every receiver has a unique serial number that is recorded from factory testing through dispatch. Banks and BC network managers can map each serial to an agent, follow self-test results and handle complaints, returns and replacements device by device. The same records feed the lifecycle and monitoring dashboards in the Raivens hardware and software platform for banks and BCs, so the whole device fleet stays visible in one place.

Yes. Raivens supplies USB GPS receivers in volume to banks, BCs and agent-banking networks, with serial-number records, dispatch tracking and after-sales support. Bulk orders can include installation guidance for agents, driver packages for your IT team and integration help for your banking application. Share your quantity, operating system and delivery locations through the contact page to receive a quotation.

In banking, a handheld POS machine lets an agent or field officer deliver branch services away from the branch. Typical services are cash deposit and withdrawal, balance inquiry, mini statements, account opening, bill payments and loan collections, each confirmed with a printed receipt. The RAIVENS Handheld POS runs the bank's or BC's own Android app and adds card, NFC and fingerprint options, so one device covers most agent-banking services.

Yes, on models fitted with the optional fingerprint sensor. The sensor captures the customer's fingerprint for national ID-based biometric authentication, which many agent-banking services use instead of cards or PINs. Where a terminal has no built-in sensor, an external USB fingerprint scanner can connect over OTG. Raivens supplies both options and the SDK your app needs to call the sensor and receive a secure capture.

Depending on model and payment app, the terminal reads chip and magnetic-stripe cards, accepts contactless cards and phones over NFC, and scans or displays QR codes for instant QR payments such as UPI, PIX, PayNow and similar real-time payment schemes. The bank or payment processor decides which schemes are switched on. Raivens configures the hardware options to match the services you plan to offer.

Yes. The terminal runs Android, so your existing agent or merchant app can run on it after integration with the device SDK for the printer, card reader, scanner and fingerprint sensor. Raivens can preload the app before dispatch, lock the terminal to permitted apps only and help your developers test on sample units. Custom app development is also available if you do not have an app yet.

No. The terminal connects over 4G mobile data with a SIM card, so agents can work in markets, villages and homes without Wi-Fi. At a counter with Wi-Fi it can switch to the local network. Receipt printing works without a connection, while whether transactions can be queued offline depends on the banking app. Raivens helps match SIM, network and app settings to your coverage.

Each terminal has a unique serial number recorded from factory test to dispatch and mapped to an agent and SIM. App updates and configuration changes can be pushed remotely, and complaints, returns and replacements are tracked by serial number. Raivens can connect this to its lifecycle management and monitoring dashboards, so operations teams see every terminal's status, location and service history in one view.

The built-in printer uses standard thermal paper rolls, typically 58 mm wide, which need no ink or ribbon. Thermal receipts suit transaction slips, mini statements and collection receipts. Store rolls away from heat and direct sunlight, because thermal paper darkens when warm. Raivens can advise on roll sizes for your model and on printing longer documents, such as account statements, through the agent app.

A payment soundbox is a small connected speaker that announces each digital payment as it is credited. The customer scans a QR code and pays from their app, the bank's server sends a message to the soundbox, and the device speaks the amount aloud. The RAIVENS Payment Soundbox also shows the QR code and amount on its display and connects over 4G or Wi-Fi, with a rechargeable battery for counters without power.

The soundbox announces any payment that the bank or payment processor confirms to it. That covers instant QR payments such as UPI, PIX, PayNow and similar real-time payment schemes, and it can cover card or wallet payments when the backend sends a notification. Raivens connects the device to the bank's notification service or provides a cloud service for it, so the deploying bank decides which schemes to enable.

Some customers show an edited screenshot or a fake message instead of paying. A soundbox reduces that risk because it speaks only when the payment server confirms that money has been credited to the merchant's account. The customer's phone plays no part in the announcement. With the RAIVENS Payment Soundbox on the counter, staff can rely on what they hear and keep serving without opening a banking app.

The soundbox speaks English and multiple local languages, and the merchant or bank can choose the language per device. Voice packs are stored on the device and can be updated over the air, so a bank can add a language or change its wording across a whole fleet. Raivens can also prepare custom prompts, such as a bank's own greeting or brand name, on request.

Battery life depends on how many payments are announced, the volume, the network type and screen use. The soundbox is designed for long battery life and speaks low-battery and charging alerts, so the merchant knows when to recharge it over USB. Ask Raivens for typical figures for each model, based on the daily payment volume you expect, before planning a large rollout.

Yes. Each soundbox has a unique serial number that is mapped to a merchant or agent account. Configuration, language, voice packs and firmware can be changed over the air, and every device reports its battery and network status. Raivens links these records to its device lifecycle and monitoring tools, so complaints, replacements and returns are traced by serial number across the whole fleet.

Yes. Besides QR payments, the soundbox can announce agent-banking events such as cash withdrawals, cash deposits, balance inquiries, money transfers, bill payments and failed transactions. It can also guide customers with spoken prompts, for example asking them to place a finger on the scanner or confirming that authentication succeeded. Raivens configures the prompt set with the bank or BC so it matches each service offered at the counter.

A biometric device in banking captures a physical trait, usually a fingerprint, and sends it securely to an authentication service that confirms who the customer is. Banks and agents use it in place of cards, PINs or paper documents for cash withdrawals, deposits, account opening and KYC. Raivens makes optical fingerprint scanners, with iris and face options, that connect over USB or OTG.

Yes. The scanners connect to Android phones, tablets and handheld POS terminals through a USB OTG port and draw power from the host, so no separate power supply is needed. On Windows PCs they connect over a standard USB port. Raivens provides Android and Windows SDKs and a secure capture service, so one integration approach covers desktop BC points and mobile agents.

Fingerprint is the usual first choice because it is fast and familiar. Iris works better for people whose fingerprints are worn by manual labor, age or skin conditions, and it avoids contact. Face capture suits hygiene-sensitive sites and assisted verification where the authentication service supports it. A common approach is fingerprint scanners at every point, with iris units as a fallback. Raivens can supply a mix to match your customer base.

It means the biometric data is protected from the moment of capture. A capture service tied to each scanner encrypts the fingerprint record and signs it with a device key, so the authentication server can confirm that it came from a known, registered scanner and was not replayed or altered. Raivens provides this service with its scanners and shares model-specific documentation for your authentication program.

Yes. Raivens supplies Windows and Android SDKs with sample code for device detection, fingerprint capture, quality checks and template or image output. Developers call the secure capture service from their banking, KYC or attendance application, and the encrypted result goes to their own authentication backend. Engineers are available to help with testing and troubleshooting during integration.

Yes. Through the SDK, the fingerprint scanners work with attendance software on Windows and Android, so branches, offices and field teams can record check-in and check-out with a fingerprint. This reduces proxy attendance and gives HR accurate time records. Raivens can supply scanners for an existing attendance system or build attendance software with dashboards as part of a custom project.

Requirements for biometric devices differ by country and by authentication program. Compliance documentation per model is available on request from Raivens, together with technical datasheets, so your IT or risk team can check a device against the rules that apply in your market before ordering in volume. Share your target program and use case when you ask, so the right model documentation is provided.

A BC point kit is the set of devices a Business Correspondent agent needs to offer banking services from a shop or kiosk. A typical RAIVENS BC point kit combines a USB GPS receiver for transaction geo-tagging, a fingerprint scanner for national ID-based authentication, a handheld POS or countertop terminal, and a receipt printer. Devices arrive configured, tested together and recorded by serial number, ready to map to an agent.

Yes. The GPS receiver outputs standard NMEA data over a COM port, the fingerprint scanners come with Windows and Android SDKs and a secure capture service, and the POS terminals run Android apps through a device SDK. Many banking applications can therefore use the kit with modest integration work. Raivens engineers support your developers during integration or build the missing pieces as custom software.

Device lifecycle management tracks every device from the factory to the end of its service life. Each unit's serial number is linked to its factory test results, dispatch record, the agent it was assigned to, self-test results, complaints, returns and replacements. Raivens keeps these records in one system, so banks and BCs can see where every device is, whether it works and why any unit came back.

The dashboard gives operations teams one view of the agent network. It typically shows active and inactive agents, transaction volumes and trends, geo-tagged transaction maps, device health and open complaints. Rules can flag exceptions, such as transactions recorded far from an agent's registered location or devices that stop reporting. Raivens configures the views and alerts to match your services and reporting needs.

Yes. Raivens builds agent apps, back-office portals, reports and integrations in-house, alongside the hardware. Because the same team designs the electronics, firmware, cloud platform and apps, custom features such as new device checks, service workflows or reports can be added without coordinating several vendors. Share your process and existing systems through the contact page to start a scoping discussion.

Yes. Every part of the kit is available on its own: USB GPS receivers, fingerprint scanners, handheld POS machines, payment soundboxes and the software modules. A network can start with one device type, such as GPS receivers for geo-tagging, and add lifecycle tracking or dashboards later. Raivens keeps the same serial-number records whichever combination you choose, so the fleet view stays complete.

The three evTor Powerpulse models differ mainly in output power. At full output, the 30 kW model delivers up to 15 kWh in 30 minutes, the 60 kW model up to 30 kWh and the 120 kW model up to 60 kWh. As a rule of thumb, 30 kW suits offices, hotels and retail parking, 60 kW suits malls and highway stops, and 120 kW suits bus depots and busy corridors. Raivens confirms the right mix after a site assessment.

CCS2 is the standard connector on these DC fast chargers. GB/T and other connector options are available for fleets and markets that use them, and the chargers use dual-connector designs, so each unit can be configured for the vehicles a site expects. Share the vehicle models and regions you serve, and Raivens will recommend the connector configuration for each charger before you order.

DC charging time depends on the vehicle as much as the charger. The car's battery management system sets the power it accepts, and that power drops as the battery fills or when it is cold. As a guide, energy equals power multiplied by time, so a 60 kW charger running at full output adds up to 30 kWh in 30 minutes. Raivens can estimate session times for the vehicles in your fleet.

On evTor Powerpulse chargers, drivers start a session in one of three ways: tap an RFID card, use the mobile app, or scan a QR code. The 7-inch touchscreen then guides them through each step. Every session is recorded in the billing backend against that card, account or scan, so operators can apply tariffs and see energy use per driver or fleet. Raivens sets up the access methods during commissioning.

A DC fast charger needs a three-phase AC supply with enough spare capacity for its rated power, plus a margin for the site's other loads. A 120 kW unit, or several smaller chargers, may need a supply upgrade or a dedicated transformer. Raivens assesses the available capacity, expected traffic and parking layout first, then recommends power levels and charger count, so the site does not overload its connection.

Yes. Each DC fast charger connects to a remote monitoring and billing backend that shows charger status, active sessions, energy delivered and faults. Operators can review usage and spot problems without a site visit, which matters for highway locations and depots spread over a wide area. Raivens configures the backend during commissioning and supports it after go-live.

Grid connection and safety requirements for DC fast chargers differ by country and utility, so they are checked for each project. Compliance documentation per model is available on request. Raivens shares it during the project review, so your consultant, utility or local authority can confirm fit with local grid and safety rules before installation. Connector variants, such as GB/T, are also available on request.

Choosing an AC EV charger starts with the electrical supply and the vehicles. Homes with a single-phase connection typically use 3.3 to 7.4 kW chargers. Sites with three-phase power, such as offices, apartment car parks and hotels, can use 11 or 22 kW. The car's onboard charger caps the AC rate, so a higher-rated wallbox only helps vehicles that accept more power. Raivens recommends a rating after checking your supply and expected vehicles.

A 22 kW AC charger is faster only if the car's onboard charger accepts more than 7.4 kW. With AC charging, the vehicle converts alternating current to direct current itself, so its onboard charger sets the maximum rate. A car limited to 7.4 kW charges at the same speed on a 7.4 kW or a 22 kW wallbox. Raivens suggests matching the charger to the vehicles you expect, with some headroom for future models.

A socket charger has an untethered Type 2 outlet, and each driver plugs in their own cable. It suits shared sites such as offices and hotels, where vehicles and cables vary. A tethered charger has a cable fixed to the unit, so the driver only plugs into the car, which is convenient at home and for fleets. Raivens offers both versions of its AC EV chargers.

Yes. With load management, several AC chargers can share one building connection, because total charging demand stays within the capacity available on site. Scheduling can also move charging to off-peak hours. For apartments and offices that add chargers in stages, this can delay or avoid a supply upgrade. Raivens sets the load limits and schedules for each site during commissioning.

Raivens AC EV chargers support RFID cards and app control. Residents or staff authorize a session with a card or a phone, so only registered users can charge, and each session is linked to a user. Hotels can hand out RFID cards at check-in in the same way. Where energy must be billed per resident or tenant, pair the chargers with smart electricity meters from the same range.

Raivens AC EV chargers connect over Wi-Fi, 4G or Ethernet, depending on the model and the site. Wi-Fi suits homes, Ethernet suits buildings with wired networks, and 4G works in open car parks where neither reaches. A connection enables app control and remote management. The team helps choose the right option during the site check, before any hardware is ordered.

Choose AC where vehicles stay parked for hours, such as homes, offices, apartments and hotels. AC chargers cost less to install, and the long stay gives them time to charge. Choose DC where drivers need energy during a short stop, such as highways, fleet depots and bus depots. Many sites combine both, and Raivens builds both, so one supplier can cover the whole site.

A smart prepaid electricity meter measures energy use and runs on credit paid in advance, much like a prepaid phone plan. Users recharge remotely through an app or web portal, and the meter can disconnect supply through its built-in relay when credit runs out. Raivens builds single- and three-phase prepaid meters with RF, LoRa or 4G connectivity for apartments, hostels, malls and EV charging sites.

With remote recharge, the user adds credit in the mobile app or web portal, and the credit reaches the meter over its RF, LoRa or 4G link. If the relay had disconnected supply at zero credit, power can be restored once the recharge arrives. Nobody needs to visit the meter or a site office. Raivens sets up the app and portal for each site.

Multi-channel sub-metering uses one meter to measure several separate circuits. Raivens multi-channel meters handle up to 10 channels, so one device in an electrical panel can meter up to 10 shops, offices or charging bays. The result is fewer meters to install, fewer communication links to manage and one place to read every tenant's consumption, which suits malls and commercial buildings.

The right wireless link for smart meters depends on site layout. RF and LoRa suit buildings and campuses with many meters close together, since one network covers them all, and LoRa adds range for spread-out sites. 4G suits standalone meters, such as a single shop or a remote charging bay, because each meter connects directly over the cellular network. Raivens recommends the link after a site survey.

When prepaid credit reaches zero, the meter can disconnect supply through its built-in relay, depending on how the site is configured, and supply can be restored after a recharge. Site owners decide how disconnection is handled for their property. Users can see their balance in the app and recharge in time. Raivens configures these rules with the owner during commissioning.

Yes. Raivens smart meters raise tamper alerts and report them to the portal, so site managers can investigate quickly instead of discovering a loss at the next manual reading. Combined with remote readings and relay control, this helps protect revenue in rented rooms, hostels and shared buildings. Tamper detection details for each model are available on request.

Yes. A smart meter on each charging bay records the energy that bay uses, so a building can bill EV charging per bay, resident or tenant on prepaid or postpaid terms. Three-phase meters suit 11 and 22 kW AC chargers. Raivens builds both the meters and the chargers, so one team can plan metering and charging together.

Metering rules for smart electricity meters differ between countries and utilities, so requirements are reviewed for each project. Compliance documentation per model is available on request, along with details on accuracy, phase configuration and communication options. Ask Raivens early in the project, so your consultant can confirm fit with local grid and metering standards before installation begins.

A PLC data logger is a device that reads values from a programmable logic controller, such as machine status, counts, temperatures or alarms, and stores or forwards them for monitoring. The data logger from Raivens reads PLCs, energy meters and sensors over Modbus RTU or Modbus TCP and sends the data to cloud dashboards over 4G, Ethernet or Wi-Fi.

The Raivens data logger reads devices that communicate over Modbus RTU on RS485 or Modbus TCP on Ethernet. That covers many PLCs, energy meters, solar inverters, flow meters and sensor transmitters. Digital inputs capture run status and alarm contacts, and analog inputs read transmitters directly. Send a list of your devices and the values you need, and the team will confirm the register map and wiring.

Modbus RTU is the serial form of the protocol. It runs over RS485 wiring, where one master polls many devices on a single bus. Modbus TCP carries the same register model over Ethernet networks. Many sites use both, with older meters on RS485 and newer PLCs on Ethernet. The Raivens data logger reads both, so one gateway can cover a mixed panel.

The PLC & IoT data logger keeps reading your devices and stores the values in local memory. When the 4G, Ethernet or Wi-Fi link comes back, it uploads the buffered readings, so dashboards fill in without gaps. How long it can buffer depends on the model and the logging interval. Raivens sets the interval to balance storage with the detail each site needs.

The PLC & IoT data logger publishes data over MQTT or HTTP, two widely supported IoT protocols. It can feed the Raivens dashboards and, by arrangement, your own server or cloud platform. Share the platform you use during scoping, and the payload format and topics are agreed before installation, so your team receives data in the structure it expects.

Usually not, if the PLC already supports Modbus. The data logger acts as a Modbus master and reads the values the PLC exposes in its registers. If a value you need is not mapped to a register, the PLC programmer may need to add it, which is typically a small change. Raivens reviews your PLC model and register list first and tells you whether any change is needed.

Factories use PLC and IoT data loggers to track machine status, production counts and energy per line. Utilities collect readings from remote meters and equipment over 4G. Water treatment plants log flow, level and pump status, with alerts when values leave their range. Solar plants read inverters and energy meters to monitor generation. Raivens supplies data loggers for each of these settings, with dashboards and alerts configured per site.

A GSM motor controller is a device that lets you switch a pump or motor on and off from a mobile phone over the cellular network, and check whether it is running. It saves trips to fields, wells and pump houses, especially at night or in bad weather. Raivens builds GSM and 4G controllers for single- and three-phase motors and pumps, used on farms and in water supply systems.

Yes. Raivens offers GSM/4G controllers for both single-phase and three-phase motors and pumps. Single-phase models suit domestic pumps and small farms, while three-phase models suit larger irrigation pumps, wells and water supply stations. Share the motor rating, supply details and how you want to control it, and the team will recommend the right controller for the job.

The Raivens wireless sensor range covers gas sensors for leak detection, temperature sensors for cold rooms, server rooms and warehouses, and door sensors for security and access monitoring. LoRa networks connect sensors spread across farms, campuses and industrial sites, and LOCKZEE smart alarms alert owners when a sensor triggers. Sensors for other measurements can be developed as custom projects.

LoRa is a long-range, low-power wireless technology for sending small amounts of data over distances that Wi-Fi cannot reach. It suits battery-powered sensors spread across farms, campuses, plants and large buildings, where running cables is impractical. Raivens sets up LoRa networks for sensor projects and can pair them with GSM/4G links where coverage requires it.

Yes. The in-house engineering team handles electronics and PCB design, embedded firmware, cloud platforms, and web and mobile apps, then manufactures and tests the product. Installation and after-sales support are available too. Working with one team from first prototype to production means fewer handoffs between vendors. Raivens has designed and built electronics in-house since 2012.

A short brief is enough to begin a custom IoT project: what the device must measure or control, where it will be installed, how it should connect (GSM/4G, Wi-Fi or LoRa), who will use the app and the expected quantities. Raivens then proposes an architecture and a plan for prototypes and production. Share the brief through the contact page to arrange a first call with the engineering team.

In a hotel, a service robot delivers room-service meals, towels, toiletries and other amenities from the kitchen or front desk to the guest's door. It can also welcome guests in the lobby and guide them to restaurants, meeting rooms or elevators. Guests can order from an in-room touchscreen, and the order becomes a robot task. Raivens configures routes, compartments and voice prompts for each property, so staff spend less time walking corridors.

Hospital delivery robots carry medicines, lab samples and supplies in lockable compartments that stay closed for the whole trip. Each compartment opens only for the intended recipient, with release options such as a PIN code or staff card. Every delivery is logged in the fleet dashboard with its time, route and recipient, which gives wards and labs a clear record. Raivens sets up who can load and open each compartment during deployment.

Each robot uses LiDAR and onboard sensors to build a map of the building, then plans its own routes, avoids people and obstacles, and slows down in zones you define, such as wards, lobbies or food courts. Navigation runs on a ROS 2 software stack. Raivens creates the maps during the site survey, and in most buildings no floor tape, rails or magnetic strips are needed. Maps can be updated when layouts change.

Yes, on request. Elevator and door integration lets a robot call an elevator, select the floor and pass through automatic doors without help, so one fleet can serve several floors, wards and wings. The right interface depends on the elevator and door controllers in your building, so Raivens checks them during the site survey and confirms the approach before deployment. Without integration, a robot can still serve a single floor.

Yes. On request, Raivens connects robots to hotel ordering and property management systems, hospital task and request systems, and the in-room guest touchscreen, so a new order or request becomes a robot task without manual entry. Delivery status can also flow back to your software. The scope of integration is agreed during planning and depends on the interfaces your current systems offer.

It depends on the number of deliveries per hour, the distance between stations, the number of floors and how many elevators the robots share. A small hotel or a single hospital wing may start with one robot, while larger sites run a fleet from one dashboard. Raivens estimates the fleet size from your delivery volumes during the site survey, and you can begin with a pilot before expanding.

After go-live, the fleet dashboard shows each robot's status, battery and alerts, and the Raivens support team handles software updates, map changes when layouts change, troubleshooting and repairs. Because the electronics, firmware and fleet software are developed in-house, issues go straight to the engineers who built the robot. Service requests can be raised through the support page or by email to support@raivens.com.

Raivens builds custom multirotor drones, including quadcopters, hexacopters and octocopters sized to the payload, flight time and site. Typical builds include thermal and zoom inspection drones for solar plants, power lines and telecom towers, mapping drones for surveys, day-and-night drones for security, agricultural drones for crop monitoring and, where rules allow, spraying, plus training and education drone kits. Each platform is built around its mission rather than adapted from a fixed model.

Yes. Custom payload integration covers the mount, vibration isolation, power supply, data connection and control from the ground station, followed by flight testing with the payload fitted. Common examples are thermal and zoom cameras, LiDAR scanners, multispectral cameras, gas sensors, loudspeakers and drop mechanisms. Share the payload's weight, size, power needs and data interface, and Raivens will confirm the airframe and the integration plan.

Drone rules differ by country and by use, and usually cover aircraft registration, pilot licensing, flight zones and permissions. Raivens builds each platform to operate within local aviation regulations and configures features such as geofencing, return-to-home and flight logs for each mission. Compliance documentation per model is available on request. Registering the aircraft, licensing pilots and obtaining flight permissions remain the operator's responsibility.

Solar inspection uses a multirotor carrying a thermal camera to find hot spots and failed cells, together with an RGB camera to record cracks, soiling and physical damage. Automated grid missions fly the same pattern on every visit, so results can be compared over time, and geotagged images help teams locate each faulty panel. Raivens matches camera resolution, flight time and mission planning to the size and layout of the plant.

Flight time depends on frame size, battery, payload weight, wind and temperature. As an indication, camera drones for inspection and mapping typically fly about 25 to 40 minutes per battery, while agricultural drones carrying liquid fly for shorter periods. Raivens sizes the battery and airframe to the mission and can supply spare battery sets and chargers so field teams can keep flying through a working day.

Agricultural drones fly over fields, orchards and plantations to map crop health with multispectral cameras, spot water stress, pests or disease early, and plan where inputs should go. Where local rules allow, spraying and spreading variants apply fertilizer or crop protection only where it is needed, which reduces waste and manual work. Raivens builds monitoring drones and, on request, application drones sized to the farm and the crop.

Yes. Training and education drone kits teach students how a drone is built, how its flight controller works, how to program simple missions and how to fly safely. They suit colleges, training institutes and school STEM labs, and they sit alongside the RAIVENS robotics and AI kits, with lesson plans by level. Older students can move from manual flying to coding autonomous missions.

Children can start learning AI ideas from about age 8, using games, image and sound recognition activities and block coding that need no prior experience. From around 11, they train simple models and build robot projects, and by 14 to 16 many are ready for machine-learning basics in Python. Raivens groups the curriculum into levels by age and experience, so each child starts at a suitable point and moves up as skills grow.

No coding experience is needed. Beginners start with visual, block-based tools and hands-on activities, so the focus is on ideas such as patterns, data and decisions rather than syntax. As students progress, they move to Python and work with real datasets and simple models. Raivens places new learners by age and experience, so a beginner and a child who already codes each get a suitable starting level.

A school AI lab needs a classroom with enough power outlets, a reliable internet connection, computers or tablets, storage for kits and regular timetable slots. Raivens plans the layout, supplies the desktop AI learning robots and robotics kits, installs the software, trains the teachers and maps lessons to the school calendar. A lab can start small, with one class set, and expand as more grades join the program.

No. The program is designed for teachers from any subject who are willing to learn alongside their students. Teacher training covers the AI concepts, every hands-on project, how to run practical sessions and how to assess project work. Lesson plans and project guides support each session. Raivens also offers follow-up sessions when new levels or projects are introduced, so teachers keep building confidence through the school year.

AI ethics is part of every level, not a separate lecture. Younger children talk about when a computer's guess is wrong and why that matters. Older students test their own models for bias, discuss privacy when using photos and voice recordings, and debate where AI should and should not be used. Raivens builds these discussions into the projects themselves, so students learn to question AI systems as well as build them.

Yes. Lessons are organized by level and learning outcome, so they can be mapped to national curriculum frameworks for computing, science and technology. Schools can run the program as a timetabled subject, within existing computer classes or as an after-school club. On request, Raivens works with the school's academic team to map each lesson and to fit the program into the timetable and term calendar.

Yes. Workshops and holiday camps are short, project-based programs where children build a working AI project, such as an object-recognition game or a voice-controlled robot, and present it to parents at the end. They suit beginners and children who want to go further than their school lessons. Schools, learning centers and parents can contact Raivens to arrange a workshop or camp and choose the level and topics.

The beginner level, for ages about 8 to 10, pairs a robot car kit with basic sensors and drag-and-drop block coding. Early projects include an obstacle-avoiding car and a line follower, which teach sensing, logic and motor control. As skills grow, the learner adds sensor packs and an AI camera and moves on to Python. Raivens can suggest a starting kit based on the child's age and any coding experience.

The kits support block-based coding for beginners, Python for intermediate learners and C++ for advanced students and competition teams. Block coding builds logic without typing errors, Python introduces real syntax and data handling, and C++ gives precise control of motors and sensors on the microcontroller. Raivens provides project guides at each level, so students can move from blocks to text-based code step by step.

A robotics kit teaches how machines sense and move: students build a robot, connect motors and sensors, and program behaviors such as following a line or avoiding walls. An AI kit adds a camera module so the robot can recognize colors, faces, objects or gestures and decide what to do next. Raivens offers the AI camera as an add-on, so a school can start with robotics and add AI later.

Yes. Competition kits are built for common event formats such as line-following, maze solving, robot sumo and robot soccer, with spare-part options for practice and repairs. Advanced teams program them in Python or C++ to fine-tune speed and control. Rules on size, weight and parts differ between competitions, so Raivens can advise a school on which kit and configuration suit a given event.

A STEM lab package typically combines class sets of robot car kits and sensor packs, AI camera add-ons, drone kits, a curriculum by level, teacher training and lab setup. The exact mix depends on the grades involved, class sizes and the space available. Raivens plans each package with the school, so it can start with one class set and add kits, levels and competition gear as the program grows.

Yes. Sensor packs add distance, line-tracking, light, sound, temperature and motion sensors as projects become more ambitious, and the AI camera add-on brings vision projects to the robot car. Families and schools can add parts over time instead of replacing the whole kit. Raivens can confirm which add-ons fit each kit, and the support team can help if a part does not work as expected.

Yes. The kits are designed to work alongside the AI education program for kids, which covers computer vision, voice, machine-learning basics and AI ethics for ages about 8 to 16. Schools can run both in one lab, using the same robot cars, AI cameras and lesson plans across levels. Raivens trains teachers on the kits and the curriculum together, so hardware and lessons stay in step.