We manufacture a wireless consumer therapy device — a handheld remote control that wirelessly operates two receiver units ("pods"). We need a licensed Professional Engineer with strong embedded-RF expertise to independently test, characterize, and document how the remote communicates with and selects between the pods, and to deliver a signed/stamped engineering report of the findings. This is an independent verification engagement. We have an internal understanding of how the system works, but we need it rigorously and impartially confirmed and documented to professional standards. We are looking for objective findings — we need the truth of how the device behaves, documented in a way that stands on its own. What we need verified The central technical question is how the system selects which pod acts on a given command. Specifically, we need you to determine and document whether: the remote transmits to each pod on its own dedicated RF frequency/channel; or the remote broadcasts over a shared, frequency-hopping link to all pods simultaneously, and each pod independently decides whether to act based on a device identifier (UID) contained in the data packet — i.e., selection occurs at the receiver, by address, not by frequency. We need the actual mechanism established with evidence, not assumed. Scope of work Identify the RF transceiver and microcontroller on the device and the protocol/architecture in use. Characterize the over-the-air RF behavior (center frequencies, channel usage, and whether/how the link frequency-hops) using appropriate instrumentation (e.g., SDR, spectrum analysis). Probe and document the control-level behavior — e.g., capturing the SPI bus between the MCU and the RF transceiver — to determine what the device does when a specific pod is selected (which registers are written: frequency/channel vs. address/UID). Determine how pods are distinguished from one another (frequency assignment vs. UID/address filtering at the receiver) and capture supporting evidence (frame/packet structure, transmit/receive logs across multiple sessions, with one pod active, then both). Establish whether the hopping sequence (if any) is shared across all pods or assigned per pod. Tie all findings to the specific production firmware version in the units tested, and document that version. Produce a clear, well-documented engineering report — methodology, equipment, settings, procedures, captures, and conclusions — signed and PE-stamped. Required qualifications Active US Professional Engineer (PE) license in Electrical Engineering (in good standing) — please state your license state(s) and number. A current stamp is mandatory; this is a hard requirement. Hands-on experience with embedded RF and proprietary (non-Bluetooth) wireless protocols — sub-GHz / 2.4 GHz transceivers, register-level configuration, frequency-hopping schemes. Experience with SDR capture (e.g., HackRF, USRP, BladeRF) and logic-analyzer / SPI bus probing (e.g., Saleae) for embedded systems. Ability to read a transceiver datasheet/register map and interpret device behavior from it. Experience producing formal, stamped engineering reports relied upon by third parties — clear, defensible, and standalone. Nice to have Prior reverse-engineering or protocol-characterization work on wireless consumer or medical devices. Experience working with overseas manufacturers, including reviewing materials under NDA. Deliverable A signed, PE-stamped engineering report documenting the methodology, evidence, and conclusions regarding the device's communication and pod-selection mechanism, tied to a specific production firmware version. Raw capture files and supporting data to accompany the report. To apply, please answer: Are you an actively licensed US PE in Electrical Engineering? State(s) and license number. Briefly describe your experience with embedded RF / proprietary wireless protocols and the instrumentation you'd use here. How would you determine whether a device assigns a dedicated frequency per receiver versus broadcasting on a shared hopping link and selecting by UID at the receiver? What's your approach and equipment? Have you produced stamped engineering reports that other parties relied on? Briefly describe. Estimated timeline and your rate structure.

We are a bootstrapped startup looking tor 6 to 8 years of experienced systems software engineer who will work directly with the cofounders and partner teams. Required skills include C++, IOT, Digital Twin, CUDA, Python, Cloud, Edge AI devices. Prefered skills: Would be nice to have experience working with NVIDIA edge devices, Agentic AI Frameworks, CI/CD pipeline deployments for embedded edge software, containerized edge deployments... Job is remote friendly for the right candidate.

We are seeking an experienced developer to create a customized Pi KVM (Keyboard, Video, Mouse) solution tailored to our specific needs. The ideal candidate will have a strong understanding of Raspberry Pi hardware and software, along with experience in video streaming and remote access protocols. Your expertise will help us implement a reliable and efficient KVM solution for our project. If you have a passion for innovative tech solutions and hands-on experience in building similar systems, we want to hear from you! The equipment we specialize in selling and service are Siemens Pet CT Scanners. Monitor Project 1. Monitor Power from Poser Monitor a. We use Elspec power monitors that use an older web based monitor for viewing. It also has a Modbus for gathering data. We need this data brought into the system for graphing and viewing. 2. Monitor Temp and humidity a. This monitor should show temp and humidity in each location visually for the tech. While also sending the data to the system for graphing. b. These should be plugged into a power source, they will get forgotten and not recharged or battery replaced by the tech. c. The main computer/PI will be 10-60 feet from each sensor, so the data transmission needs to be thought through with this in mind. Some area’s are also in rooms that are lead lined. 3. Monitor Chilled water Temp/Flow/Level. a. Chiller is located in the belly of the mobile. b. Fixed site should possibly be monitored also. c. Cold weather – the ambient temp in the belly should be monitored also and connected to a heater and turned on a certain temp. 4. Connection to Server/Cloud a. We should always want to go through the best and most reliable source. Either through wifi/Wired or Cell is that isn’t available. Both have issue. b. Cell has issues in certain locations, and some networks it is too diQicult and problematic for us to go through. 5. Connection for PiKVM a. We usually put a cell connection into the piKVM, but that is hard to share with other devices. b. It might be easier to go through the network/Cell for this device and have it share with the PiKVM. 6. Gathering of data from ICS a. Graphing data from these data points from the ICS i. QC’s ii. Gantry Temps iii. Establishing highs and lows for warnings b. Storage of backups c. Software loads for systems. 7. Sensitivity of power for system/ UPS

What we're building Third Rail is a phone case that zaps you when you blow past your daily pickup limit (thirdrailcase.com). I need the works-like prototype: an UNMODIFIED consumer TENS unit, triggered by an ESP32 over BLE, delivering the zap through copper-tape rails stuck to a standard phone case. Deliverables - ESP32 receives a BLE command (triggered from nRF Connect / LightBlue - no custom app needed) and fires the TENS unit's trigger via relay or optocoupler - TENS output routed to copper-tape rails on the case edges, where grip lands - Rails re-stickable so I can iterate on placement without you - Battery-powered and self-contained enough to demo in hand - Raw build footage: 10–20 short VERTICAL phone clips as you go (parts unboxing, wiring, first relay click, bench zap test, final assembly). Prop your phone up and hit record — no editing required, hands-only is fine. Clips are ours to use in marketing. - Short handover doc: wiring diagram, parts list + receipts, how to adjust/re-flash Hard requirements (acceptance criteria) 1. The TENS unit's output stage stays completely stock - no custom high-voltage circuitry anywhere in this build 2. The TENS unit must be a standard consumer retail unit (no kits, no bare modules) 3. Zap intensity is controlled ONLY on the TENS unit's own dial 4. Rails detach and re-stick without soldering 5. All parts and leftover materials transfer to me at handover Parts: you source them - up to $150 of the budget, receipts required (TENS unit ~$30, ESP32 dev board, relay/optocoupler module, basic case, copper tape, battery pack). Milestones (fixed price, $650) - M1 ($300): parts purchased (receipts) + video of the ESP32 firing the relay on BLE command, within 4 days of start - M2 ($350): assembled prototype + handover doc + all build clips. NYC is a plus for in-person handover; otherwise ship tracked + insured (shipping cost reimbursed with receipt) Timeline: 2 weeks from kickoff. Start date: roughly 1–2 weeks out. To apply: briefly describe how you'd trigger the zap while keeping the TENS output stage completely stock.

I am looking for an experienced RF/embedded systems engineer with expertise in proprietary 2.4 GHz wireless protocols, RF spectrum analysis, frequency hopping systems, and packet-level communications. I need an independent technical analysis of a wireless medical device system consisting of a remote controller and multiple wireless receiver units. The objective is to determine how the system actually operates, not to support any predetermined conclusion. Tasks include: • Review technical documentation and communication specifications. • Analyze RF behavior using spectrum analyzer data. • Determine actual operating frequencies and hopping behavior. • Determine whether receiver units share frequencies or use dedicated frequencies. • Determine whether receiver selection changes RF transmission behavior or only affects packet contents/identifiers. • Analyze packet structure, UID/device identification logic, synchronization behavior, and communication flow. • Review firmware/source code if available. • Create diagrams showing: * RF architecture * transmit/receive flow * packet flow * frequency usage * device selection process • Produce a written technical report explaining the actual communication architecture. Important: The analysis must be independent and objective. I am not looking for someone to advocate a position. I need a technically accurate description of how the system operates based on evidence, testing, and engineering analysis.

Seeking an expert mechatronics or robotics engineer to design and build a functional, 4-lever motorized flight simulator throttle prototype that will be integrated with commercial flight simulator software (X-Plane, MSFS, or similar). The project involves creating a realistic and durable throttle system for flight simulation, requiring precision and attention to detail. The ideal candidate will have experience in mechatronics and robotics, with a strong understanding of mechanical and electrical systems. The scope of work includes design and prototype build within 3 months.

I’m working on an early-stage startup concept in the counter-drone / critical infrastructure security space. The product is not drone jamming, takedown, spoofing, or mitigation. The concept is a civilian-compliant drone incident management platform that helps data centers, utilities, ports, stadiums, prisons, refineries, airports, and industrial campuses detect, document, and respond to unauthorized drone activity. I’m looking for a technical advisor with experience in one or more of the following areas: Counter-UAS / drone detection RF sensing or passive RF detection Radar systems Sensor fusion Computer vision / object detection Security camera systems Physical security technology Aerospace / unmanned systems Remote ID / drone telemetry Critical infrastructure security systems The goal is not to have you build the full product right now. I’m looking for a technical expert who can review the concept, help shape the MVP, identify technical risks, and advise on what would make the product credible to customers, investors, and pilot partners. The product vision is a software/workflow layer that connects to existing cameras, sensors, employee reports, Remote ID feeds where available, and security operations tools. The platform would help security teams determine whether a drone incident is real, assess risk, preserve evidence, create an incident timeline, and coordinate response. I’d like help answering questions such as: What sensor inputs should the MVP support first? What technical claims should we avoid making early? What is feasible for a software-first prototype? How should we think about false positives: birds, aircraft, weather, reflections, etc.? What would make a pilot technically credible? What metrics should we measure during field testing? What existing hardware or sensor vendors could we integrate with instead of building hardware ourselves? What architecture would make sense for an edge gateway + cloud dashboard model? What technical risks would investors or customers challenge us on? What technical talent would we eventually need to hire? Deliverables I’m looking for: 1–2 advisory calls Technical feasibility review MVP recommendations Sensor/integration recommendations List of technical risks and assumptions Suggested pilot metrics Recommended technical hiring profile Optional written summary after the call Please let me know: Your relevant background in drones, C-UAS, RF, radar, computer vision, sensor fusion, or security systems Whether you have experience with commercial, defense, or critical infrastructure customers Your availability for an initial advisory call Your hourly rate or fixed price for a concept review What information you would need from me before the call I’m looking for someone who can be direct, practical, and honest. I do not need hype. I need someone who can tell me what is technically realistic, what is risky, and what the first credible version of this product should look like.

We are seeking a skilled professional with experience in software development and electronic engineering, particularly in the MEDTECH field. The ideal candidate will have experience with Edge AI and a strong background in electronics and microcontroller programming.

Integrating a PIR sensor with a remote controller to turn on a Insta 360 camera for recording. ESP32 developer" or "Arduino sensor integration". This is to turn a Insta 360 camera into a type of trail camera.

What I need: I want a custom-built, fully working physical Skylanders portal that I can place real figures and traps on, that works with the Cemu emulator on my Windows PC. It must be detected by my computer as a genuine Skylanders portal (USB Vendor ID 0x1430, Product ID 0x0150) so the game treats it as real hardware. I am not interested in software-only emulation — I want real hardware with real, placeable figures. This is a recreation of the Skylanders: Trap Team "Traptanium" portal. It's a known, documented build (Raspberry Pi Pico + NFC reader + open-source firmware), so this is execution work, not research from scratch — I'll provide a detailed technical reference doc with the exact firmware repos, wiring, and USB protocol once we connect. The finished portal must include, like the original: An open surface to place multiple figures at once A separate trap slot Color (RGB) LEDs lighting the portal area A dedicated LED for the trap slot A working speaker for in-game audio A housing that can be opened to access the internal components for future repairs or upgrades (e.g., screwed or otherwise removable panel — not glued or permanently sealed shut) Suggested approach (you're welcome to propose better): Raspberry Pi Pico running TinyUSB-based portal firmware (e.g., the open-source PicoWPortal project), an MFRC522 reader for the main figure area, a second NFC reader for the trap slot, addressable RGB LEDs, a white trap-slot LED, and a small speaker + amp — all in a custom 3D-printed/fabricated housing. Deliverables: A working, assembled portal in a custom housing with all five features above functioning in-game. Proof it works — a short video showing a real figure and a trap being placed and recognized in Trap Team running in Cemu on Windows, plus the LEDs and speaker responding. A brief written note of the firmware/version used and how to re-flash it, so I can maintain it myself. What I'll provide: My real Skylanders figures/traps for testing (or I can dump and send the data — your call). My broken original portal as a layout/feel reference (photos or shipped). A detailed technical reference document (firmware, wiring, protocol, part numbers). Two things to be aware of before you bid (please address these in your proposal): The trap slot (second reader) and the speaker (USB audio passthrough) may require extending the firmware beyond a stock flash. Tell me whether you'll use existing firmware that supports these or whether you'll be writing/extending code, and price accordingly. The multi-figure read area needs a larger or custom-tuned 13.56 MHz antenna (a stock MFRC522 antenna only reads one small spot). Tell me how you'll handle reliable reads across the surface. Logistics: Tell me if you work remotely (I ship parts/figures) or are local to South Florida (Homestead/Miami). Please quote parts cost, labor, and turnaround separately. MILESTONES: Design sign-off — parts list, wiring plan, housing concept, and confirmation of trap-slot + audio approach. (small upfront %) Working electronics (no housing) — Pico enumerates as 1430:0150, main reader + trap reader recognized in Cemu, LEDs and speaker responding on the bench. (largest %) Final assembly + housing — everything integrated in the custom enclosure, acceptance test passed, proof video + re-flash notes delivered. (final %) Acceptance criteria With Trap Team running in Cemu on Windows: a real figure on the main surface appears in-game; a trap in the trap slot is recognized; portal RGB LEDs respond to in-game color/fades; the trap-slot LED lights when expected; the speaker produces in-game audio. Proof captured on video. I have conducted research and sourced the firmware and software needed. Just need someone to source and assemble the hardware.