16 skills found
chrisneagu / FTC Skystone Dark Angels Romania 2020NOTICE This repository contains the public FTC SDK for the SKYSTONE (2019-2020) competition season. If you are looking for the current season's FTC SDK software, please visit the new and permanent home of the public FTC SDK: FtcRobotController repository Welcome! This GitHub repository contains the source code that is used to build an Android app to control a FIRST Tech Challenge competition robot. To use this SDK, download/clone the entire project to your local computer. Getting Started If you are new to robotics or new to the FIRST Tech Challenge, then you should consider reviewing the FTC Blocks Tutorial to get familiar with how to use the control system: FTC Blocks Online Tutorial Even if you are an advanced Java programmer, it is helpful to start with the FTC Blocks tutorial, and then migrate to the OnBot Java Tool or to Android Studio afterwards. Downloading the Project If you are an Android Studio programmer, there are several ways to download this repo. Note that if you use the Blocks or OnBot Java Tool to program your robot, then you do not need to download this repository. If you are a git user, you can clone the most current version of the repository: git clone https://github.com/FIRST-Tech-Challenge/SKYSTONE.git Or, if you prefer, you can use the "Download Zip" button available through the main repository page. Downloading the project as a .ZIP file will keep the size of the download manageable. You can also download the project folder (as a .zip or .tar.gz archive file) from the Downloads subsection of the Releases page for this repository. Once you have downloaded and uncompressed (if needed) your folder, you can use Android Studio to import the folder ("Import project (Eclipse ADT, Gradle, etc.)"). Getting Help User Documentation and Tutorials FIRST maintains online documentation with information and tutorials on how to use the FIRST Tech Challenge software and robot control system. You can access this documentation using the following link: SKYSTONE Online Documentation Note that the online documentation is an "evergreen" document that is constantly being updated and edited. It contains the most current information about the FIRST Tech Challenge software and control system. Javadoc Reference Material The Javadoc reference documentation for the FTC SDK is now available online. Click on the following link to view the FTC SDK Javadoc documentation as a live website: FTC Javadoc Documentation Documentation for the FTC SDK is also included with this repository. There is a subfolder called "doc" which contains several subfolders: The folder "apk" contains the .apk files for the FTC Driver Station and FTC Robot Controller apps. The folder "javadoc" contains the JavaDoc user documentation for the FTC SDK. Online User Forum For technical questions regarding the Control System or the FTC SDK, please visit the FTC Technology forum: FTC Technology Forum Release Information Version 5.5 (20200824-090813) Version 5.5 requires Android Studio 4.0 or later. New features Adds support for calling custom Java classes from Blocks OpModes (fixes SkyStone issue #161). Classes must be in the org.firstinspires.ftc.teamcode package. Methods must be public static and have no more than 21 parameters. Parameters declared as OpMode, LinearOpMode, Telemetry, and HardwareMap are supported and the argument is provided automatically, regardless of the order of the parameters. On the block, the sockets for those parameters are automatically filled in. Parameters declared as char or java.lang.Character will accept any block that returns text and will only use the first character in the text. Parameters declared as boolean or java.lang.Boolean will accept any block that returns boolean. Parameters declared as byte, java.lang.Byte, short, java.lang.Short, int, java.lang.Integer, long, or java.lang.Long, will accept any block that returns a number and will round that value to the nearest whole number. Parameters declared as float, java.lang.Float, double, java.lang.Double will accept any block that returns a number. Adds telemetry API method for setting display format Classic Monospace HTML (certain tags only) Adds blocks support for switching cameras. Adds Blocks support for TensorFlow Object Detection with a custom model. Adds support for uploading a custom TensorFlow Object Detection model in the Manage page, which is especially useful for Blocks and OnBotJava users. Shows new Control Hub blink codes when the WiFi band is switched using the Control Hub's button (only possible on Control Hub OS 1.1.2) Adds new warnings which can be disabled in the Advanced RC Settings Mismatched app versions warning Unnecessary 2.4 GHz WiFi usage warning REV Hub is running outdated firmware (older than version 1.8.2) Adds support for Sony PS4 gamepad, and reworks how gamepads work on the Driver Station Removes preference which sets gamepad type based on driver position. Replaced with menu which allows specifying type for gamepads with unknown VID and PID Attempts to auto-detect gamepad type based on USB VID and PID If gamepad VID and PID is not known, use type specified by user for that VID and PID If gamepad VID and PID is not known AND the user has not specified a type for that VID and PID, an educated guess is made about how to map the gamepad Driver Station will now attempt to automatically recover from a gamepad disconnecting, and re-assign it to the position it was assigned to when it dropped If only one gamepad is assigned and it drops: it can be recovered If two gamepads are assigned, and have different VID/PID signatures, and only one drops: it will be recovered If two gamepads are assigned, and have different VID/PID signatures, and BOTH drop: both will be recovered If two gamepads are assigned, and have the same VID/PID signatures, and only one drops: it will be recovered If two gamepads are assigned, and have the same VID/PID signatures, and BOTH drop: neither will be recovered, because of the ambiguity of the gamepads when they re-appear on the USB bus. There is currently one known edge case: if there are two gamepads with the same VID/PID signature plugged in, but only one is assigned, and they BOTH drop, it's a 50-50 chance of which one will be chosen for automatic recovery to the assigned position: it is determined by whichever one is re-enumerated first by the USB bus controller. Adds landscape user interface to Driver Station New feature: practice timer with audio cues New feature (Control Hub only): wireless network connection strength indicator (0-5 bars) New feature (Control Hub only): tapping on the ping/channel display will switch to an alternate display showing radio RX dBm and link speed (tap again to switch back) The layout will NOT autorotate. You can switch the layout from the Driver Station's settings menu. Breaking changes Removes support for Android versions 4.4 through 5.1 (KitKat and Lollipop). The minSdkVersion is now 23. Removes the deprecated LinearOpMode methods waitOneFullHardwareCycle() and waitForNextHardwareCycle() Enhancements Handles RS485 address of Control Hub automatically The Control Hub is automatically given a reserved address Existing configuration files will continue to work All addresses in the range of 1-10 are still available for Expansion Hubs The Control Hub light will now normally be solid green, without blinking to indicate the address The Control Hub will not be shown on the Expansion Hub Address Change settings page Improves REV Hub firmware updater The user can now choose between all available firmware update files Version 1.8.2 of the REV Hub firmware is bundled into the Robot Controller app. Text was added to clarify that Expansion Hubs can only be updated via USB. Firmware update speed was reduced to improve reliability Allows REV Hub firmware to be updated directly from the Manage webpage Improves log viewer on Robot Controller Horizontal scrolling support (no longer word wrapped) Supports pinch-to-zoom Uses a monospaced font Error messages are highlighted New color scheme Attempts to force-stop a runaway/stuck OpMode without restarting the entire app Not all types of runaway conditions are stoppable, but if the user code attempts to talk to hardware during the runaway, the system should be able to capture it. Makes various tweaks to the Self Inspect screen Renames "OS version" entry to "Android version" Renames "WiFi Direct Name" to "WiFi Name" Adds Control Hub OS version, when viewing the report of a Control Hub Hides the airplane mode entry, when viewing the report of a Control Hub Removes check for ZTE Speed Channel Changer Shows firmware version for all Expansion and Control Hubs Reworks network settings portion of Manage page All network settings are now applied with a single click The WiFi Direct channel of phone-based Robot Controllers can now be changed from the Manage page WiFi channels are filtered by band (2.4 vs 5 GHz) and whether they overlap with other channels The current WiFi channel is pre-selected on phone-based Robot Controllers, and Control Hubs running OS 1.1.2 or later. On Control Hubs running OS 1.1.2 or later, you can choose to have the system automatically select a channel on the 5 GHz band Improves OnBotJava New light and dark themes replace the old themes (chaos, github, chrome,...) the new default theme is light and will be used when you first update to this version OnBotJava now has a tabbed editor Read-only offline mode Improves function of "exit" menu item on Robot Controller and Driver Station Now guaranteed to be fully stopped and unloaded from memory Shows a warning message if a LinearOpMode exists prematurely due to failure to monitor for the start condition Improves error message shown when the Driver Station and Robot Controller are incompatible with each other Driver Station OpMode Control Panel now disabled while a Restart Robot is in progress Disables advanced settings related to WiFi direct when the Robot Controller is a Control Hub. Tint phone battery icons on Driver Station when low/critical. Uses names "Control Hub Portal" and "Control Hub" (when appropriate) in new configuration files Improve I2C read performance Very large improvement on Control Hub; up to ~2x faster with small (e.g. 6 byte) reads Not as apparent on Expansion Hubs connected to a phone Update/refresh build infrastructure Update to 'androidx' support library from 'com.android.support:appcompat', which is end-of-life Update targetSdkVersion and compileSdkVersion to 28 Update Android Studio's Android plugin to latest Fix reported build timestamp in 'About' screen Add sample illustrating manual webcam use: ConceptWebcam Bug fixes Fixes SkyStone issue #248 Fixes SkyStone issue #232 and modifies bulk caching semantics to allow for cache-preserving MANUAL/AUTO transitions. Improves performance when REV 2M distance sensor is unplugged Improves readability of Toast messages on certain devices Allows a Driver Station to connect to a Robot Controller after another has disconnected Improves generation of fake serial numbers for UVC cameras which do not provide a real serial number Previously some devices would assign such cameras a serial of 0:0 and fail to open and start streaming Fixes ftc_app issue #638. Fixes a slew of bugs with the Vuforia camera monitor including: Fixes bug where preview could be displayed with a wonky aspect ratio Fixes bug where preview could be cut off in landscape Fixes bug where preview got totally messed up when rotating phone Fixes bug where crosshair could drift off target when using webcams Fixes issue in UVC driver on some devices (ftc_app 681) if streaming was started/stopped multiple times in a row Issue manifested as kernel panic on devices which do not have this kernel patch. On affected devices which do have the patch, the issue was manifest as simply a failure to start streaming. The Tech Team believes that the root cause of the issue is a bug in the Linux kernel XHCI driver. A workaround was implemented in the SDK UVC driver. Fixes bug in UVC driver where often half the frames from the camera would be dropped (e.g. only 15FPS delivered during a streaming session configured for 30FPS). Fixes issue where TensorFlow Object Detection would show results whose confidence was lower than the minimum confidence parameter. Fixes a potential exploitation issue of CVE-2019-11358 in OnBotJava Fixes changing the address of an Expansion Hub with additional Expansion Hubs connected to it Preserves the Control Hub's network connection when "Restart Robot" is selected Fixes issue where device scans would fail while the Robot was restarting Fix RenderScript usage Use androidx.renderscript variant: increased compatibility Use RenderScript in Java mode, not native: simplifies build Fixes webcam-frame-to-bitmap conversion problem: alpha channel wasn't being initialized, only R, G, & B Fixes possible arithmetic overflow in Deadline Fixes deadlock in Vuforia webcam support which could cause 5-second delays when stopping OpMode Version 5.4 (20200108-101156) Fixes SkyStone issue #88 Adds an inspection item that notes when a robot controller (Control Hub) is using the factory default password. Fixes SkyStone issue #61 Fixes SkyStone issue #142 Fixes ftc_app issue #417 by adding more current and voltage monitoring capabilities for REV Hubs. Fixes a crash sometimes caused by OnBotJava activity Improves OnBotJava autosave functionality ftc_app #738 Fixes system responsiveness issue when an Expansion Hub is disconnected Fixes issue where IMU initialization could prevent Op Modes from stopping Fixes issue where AndroidTextToSpeech.speak() would fail if it was called too early Adds telemetry.speak() methods and blocks, which cause the Driver Station (if also updated) to speak text Adds and improves Expansion Hub-related warnings Improves Expansion Hub low battery warning Displays the warning immediately after the hub reports it Specifies whether the condition is current or occurred temporarily during an OpMode run Displays which hubs reported low battery Displays warning when hub loses and regains power during an OpMode run Fixes the hub's LED pattern after this condition Displays warning when Expansion Hub is not responding to commands Specifies whether the condition is current or occurred temporarily during an OpMode run Clarifies warning when Expansion Hub is not present at startup Specifies that this condition requires a Robot Restart before the hub can be used. The hub light will now accurately reflect this state Improves logging and reduces log spam during these conditions Syncs the Control Hub time and timezone to a connected web browser programming the robot, if a Driver Station is not available. Adds bulk read functionality for REV Hubs A bulk caching mode must be set at the Hub level with LynxModule#setBulkCachingMode(). This applies to all relevant SDK hardware classes that reference that Hub. The following following Hub bulk caching modes are available: BulkCachingMode.OFF (default): All hardware calls operate as usual. Bulk data can read through LynxModule#getBulkData() and processed manually. BulkCachingMode.AUTO: Applicable hardware calls are served from a bulk read cache that is cleared/refreshed automatically to ensure identical commands don't hit the same cache. The cache can also be cleared manually with LynxModule#clearBulkCache(), although this is not recommended. (advanced users) BulkCachingMode.MANUAL: Same as BulkCachingMode.AUTO except the cache is never cleared automatically. To avoid getting stale data, the cache must be manually cleared at the beginning of each loop body or as the user deems appropriate. Removes PIDF Annotation values added in Rev 5.3 (to AndyMark, goBILDA and TETRIX motor configurations). The new motor types will still be available but their Default control behavior will revert back to Rev 5.2 Adds new ConceptMotorBulkRead sample Opmode to demonstrate and compare Motor Bulk-Read modes for reducing I/O latencies. Version 5.3 (20191004-112306) Fixes external USB/UVC webcam support Makes various bugfixes and improvements to Blocks page, including but not limited to: Many visual tweaks Browser zoom and window resize behave better Resizing the Java preview pane works better and more consistently across browsers The Java preview pane consistently gets scrollbars when needed The Java preview pane is hidden by default on phones Internet Explorer 11 should work Large dropdown lists display properly on lower res screens Disabled buttons are now visually identifiable as disabled A warning is shown if a user selects a TFOD sample, but their device is not compatible Warning messages in a Blocks op mode are now visible by default. Adds goBILDA 5201 and 5202 motors to Robot Configurator Adds PIDF Annotation values to AndyMark, goBILDA and TETRIX motor configurations. This has the effect of causing the RUN_USING_ENCODERS and RUN_TO_POSITION modes to use PIDF vs PID closed loop control on these motors. This should provide more responsive, yet stable, speed control. PIDF adds Feedforward control to the basic PID control loop. Feedforward is useful when controlling a motor's speed because it "anticipates" how much the control voltage must change to achieve a new speed set-point, rather than requiring the integrated error to change sufficiently. The PIDF values were chosen to provide responsive, yet stable, speed control on a lightly loaded motor. The more heavily a motor is loaded (drag or friction), the more noticable the PIDF improvement will be. Fixes startup crash on Android 10 Fixes ftc_app issue #712 (thanks to FROGbots-4634) Fixes ftc_app issue #542 Allows "A" and lowercase letters when naming device through RC and DS apps. Version 5.2 (20190905-083277) Fixes extra-wide margins on settings activities, and placement of the new configuration button Adds Skystone Vuforia image target data. Includes sample Skystone Vuforia Navigation op modes (Java). Includes sample Skystone Vuforia Navigation op modes (Blocks). Adds TensorFlow inference model (.tflite) for Skystone game elements. Includes sample Skystone TensorFlow op modes (Java). Includes sample Skystone TensorFlow op modes (Blocks). Removes older (season-specific) sample op modes. Includes 64-bit support (to comply with Google Play requirements). Protects against Stuck OpModes when a Restart Robot is requested. (Thanks to FROGbots-4634) (ftc_app issue #709) Blocks related changes: Fixes bug with blocks generated code when hardware device name is a java or javascript reserved word. Shows generated java code for blocks, even when hardware items are missing from the active configuration. Displays warning icon when outdated Vuforia and TensorFlow blocks are used (SkyStone issue #27) Version 5.1 (20190820-222104) Defines default PIDF parameters for the following motors: REV Core Hex Motor REV 20:1 HD Hex Motor REV 40:1 HD Hex Motor Adds back button when running on a device without a system back button (such as a Control Hub) Allows a REV Control Hub to update the firmware on a REV Expansion Hub via USB Fixes SkyStone issue #9 Fixes ftc_app issue #715 Prevents extra DS User clicks by filtering based on current state. Prevents incorrect DS UI state changes when receiving new OpMode list from RC Adds support for REV Color Sensor V3 Adds a manual-refresh DS Camera Stream for remotely viewing RC camera frames. To show the stream on the DS, initialize but do not run a stream-enabled opmode, select the Camera Stream option in the DS menu, and tap the image to refresh. This feature is automatically enabled when using Vuforia or TFOD—no additional RC configuration is required for typical use cases. To hide the stream, select the same menu item again. Note that gamepads are disabled and the selected opmode cannot be started while the stream is open as a safety precaution. To use custom streams, consult the API docs for CameraStreamServer#setSource and CameraStreamSource. Adds many Star Wars sounds to RobotController resources. Added SKYSTONE Sounds Chooser Sample Program. Switches out startup, connect chimes, and error/warning sounds for Star Wars sounds Updates OnBot Java to use a WebSocket for communication with the robot The OnBot Java page no longer has to do a full refresh when a user switches from editing one file to another Known issues: Camera Stream The Vuforia camera stream inherits the issues present in the phone preview (namely ftc_app issue #574). This problem does not affect the TFOD camera stream even though it receives frames from Vuforia. The orientation of the stream frames may not always match the phone preview. For now, these frames may be rotated manually via a custom CameraStreamSource if desired. OnBotJava Browser back button may not always work correctly It's possible for a build to be queued, but not started. The OnBot Java build console will display a warning if this occurs. A user might not realize they are editing a different file if the user inadvertently switches from one file to another since this switch is now seamless. The name of the currently open file is displayed in the browser tab. Version 5.0 (built on 19.06.14) Support for the REV Robotics Control Hub. Adds a Java preview pane to the Blocks editor. Adds a new offline export feature to the Blocks editor. Display wifi channel in Network circle on Driver Station. Adds calibration for Logitech C270 Updates build tooling and target SDK. Compliance with Google's permissions infrastructure (Required after build tooling update). Keep Alives to mitigate the Motorola wifi scanning problem. Telemetry substitute no longer necessary. Improves Vuforia error reporting. Fixes ftctechnh/ftc_app issues 621, 713. Miscellaneous bug fixes and improvements. Version 4.3 (built on 18.10.31) Includes missing TensorFlow-related libraries and files. Version 4.2 (built on 18.10.30) Includes fix to avoid deadlock situation with WatchdogMonitor which could result in USB communication errors. Comm error appeared to require that user disconnect USB cable and restart the Robot Controller app to recover. robotControllerLog.txt would have error messages that included the words "E RobotCore: lynx xmit lock: #### abandoning lock:" Includes fix to correctly list the parent module address for a REV Robotics Expansion Hub in a configuration (.xml) file. Bug in versions 4.0 and 4.1 would incorrect list the address module for a parent REV Robotics device as "1". If the parent module had a higher address value than the daisy-chained module, then this bug would prevent the Robot Controller from communicating with the downstream Expansion Hub. Added requirement for ACCESS_COARSE_LOCATION to allow a Driver Station running Android Oreo to scan for Wi-Fi Direct devices. Added google() repo to build.gradle because aapt2 must be downloaded from the google() repository beginning with version 3.2 of the Android Gradle Plugin. Important Note: Android Studio users will need to be connected to the Internet the first time build the ftc_app project. Internet connectivity is required for the first build so the appropriate files can be downloaded from the Google repository. Users should not need to be connected to the Internet for subsequent builds. This should also fix buid issue where Android Studio would complain that it "Could not find com.android.tools.lint:lint-gradle:26.1.4" (or similar). Added support for REV Spark Mini motor controller as part of the configuration menu for a servo/PWM port on the REV Expansion Hub. Provide examples for playing audio files in an Op Mode. Block Development Tool Changes Includes a fix for a problem with the Velocity blocks that were reported in the FTC Technology forum (Blocks Programming subforum). Change the "Save completed successfully." message to a white color so it will contrast with a green background. Fixed the "Download image" feature so it will work if there are text blocks in the op mode. Introduce support for Google's TensorFlow Lite technology for object detetion for 2018-2019 game. TensorFlow lite can recognize Gold Mineral and Silver Mineral from 2018-2019 game. Example Java and Block op modes are included to show how to determine the relative position of the gold block (left, center, right). Version 4.1 (released on 18.09.24) Changes include: Fix to prevent crash when deprecated configuration annotations are used. Change to allow FTC Robot Controller APK to be auto-updated using FIRST Global Control Hub update scripts. Removed samples for non supported / non legal hardware. Improvements to Telemetry.addData block with "text" socket. Updated Blocks sample op mode list to include Rover Ruckus Vuforia example. Update SDK library version number. Version 4.0 (released on 18.09.12) Changes include: Initial support for UVC compatible cameras If UVC camera has a unique serial number, RC will detect and enumerate by serial number. If UVC camera lacks a unique serial number, RC will only support one camera of that type connected. Calibration settings for a few cameras are included (see TeamCode/src/main/res/xml/teamwebcamcalibrations.xml for details). User can upload calibration files from Program and Manage web interface. UVC cameras seem to draw a fair amount of electrical current from the USB bus. This does not appear to present any problems for the REV Robotics Control Hub. This does seem to create stability problems when using some cameras with an Android phone-based Robot Controller. FTC Tech Team is investigating options to mitigate this issue with the phone-based Robot Controllers. Updated sample Vuforia Navigation and VuMark Op Modes to demonstrate how to use an internal phone-based camera and an external UVC webcam. Support for improved motor control. REV Robotics Expansion Hub firmware 1.8 and greater will support a feed forward mechanism for closed loop motor control. FTC SDK has been modified to support PIDF coefficients (proportional, integral, derivative, and feed forward). FTC Blocks development tool modified to include PIDF programming blocks. Deprecated older PID-related methods and variables. REV's 1.8.x PIDF-related changes provide a more linear and accurate way to control a motor. Wireless Added 5GHz support for wireless channel changing for those devices that support it. Tested with Moto G5 and E4 phones. Also tested with other (currently non-approved) phones such as Samsung Galaxy S8. Improved Expansion Hub firmware update support in Robot Controller app Changes to make the system more robust during the firmware update process (when performed through Robot Controller app). User no longer has to disconnect a downstream daisy-chained Expansion Hub when updating an Expansion Hub's firmware. If user is updating an Expansion Hub's firmware through a USB connection, he/she does not have to disconnect RS485 connection to other Expansion Hubs. The user still must use a USB connection to update an Expansion Hub's firmware. The user cannot update the Expansion Hub firmware for a downstream device that is daisy chained through an RS485 connection. If an Expansion Hub accidentally gets "bricked" the Robot Controller app is now more likely to recognize the Hub when it scans the USB bus. Robot Controller app should be able to detect an Expansion Hub, even if it accidentally was bricked in a previous update attempt. Robot Controller app should be able to install the firmware onto the Hub, even if if accidentally was bricked in a previous update attempt. Resiliency FTC software can detect and enable an FTDI reset feature that is available with REV Robotics v1.8 Expansion Hub firmware and greater. When enabled, the Expansion Hub can detect if it hasn't communicated with the Robot Controller over the FTDI (USB) connection. If the Hub hasn't heard from the Robot Controller in a while, it will reset the FTDI connection. This action helps system recover from some ESD-induced disruptions. Various fixes to improve reliability of FTC software. Blocks Fixed errors with string and list indices in blocks export to java. Support for USB connected UVC webcams. Refactored optimized Blocks Vuforia code to support Rover Ruckus image targets. Added programming blocks to support PIDF (proportional, integral, derivative and feed forward) motor control. Added formatting options (under Telemetry and Miscellaneous categories) so user can set how many decimal places to display a numerical value. Support to play audio files (which are uploaded through Blocks web interface) on Driver Station in addition to the Robot Controller. Fixed bug with Download Image of Blocks feature. Support for REV Robotics Blinkin LED Controller. Support for REV Robotics 2m Distance Sensor. Added support for a REV Touch Sensor (no longer have to configure as a generic digital device). Added blocks for DcMotorEx methods. These are enhanced methods that you can use when supported by the motor controller hardware. The REV Robotics Expansion Hub supports these enhanced methods. Enhanced methods include methods to get/set motor velocity (in encoder pulses per second), get/set PIDF coefficients, etc.. Modest Improvements in Logging Decrease frequency of battery checker voltage statements. Removed non-FTC related log statements (wherever possible). Introduced a "Match Logging" feature. Under "Settings" a user can enable/disable this feature (it's disabled by default). If enabled, user provides a "Match Number" through the Driver Station user interface (top of the screen). The Match Number is used to create a log file specifically with log statements from that particular Op Mode run. Match log files are stored in /sdcard/FIRST/matlogs on the Robot Controller. Once an op mode run is complete, the Match Number is cleared. This is a convenient way to create a separate match log with statements only related to a specific op mode run. New Devices Support for REV Robotics Blinkin LED Controller. Support for REV Robotics 2m Distance Sensor. Added configuration option for REV 20:1 HD Hex Motor. Added support for a REV Touch Sensor (no longer have to configure as a generic digital device). Miscellaneous Fixed some errors in the definitions for acceleration and velocity in our javadoc documentation. Added ability to play audio files on Driver Station When user is configuring an Expansion Hub, the LED on the Expansion Hub will change blink pattern (purple-cyan) to indicate which Hub is currently being configured. Renamed I2cSensorType to I2cDeviceType. Added an external sample Op Mode that demonstrates localization using 2018-2019 (Rover Ruckus presented by QualComm) Vuforia targets. Added an external sample Op Mode that demonstrates how to use the REV Robotics 2m Laser Distance Sensor. Added an external sample Op Mode that demonstrates how to use the REV Robotics Blinkin LED Controller. Re-categorized external Java sample Op Modes to "TeleOp" instead of "Autonomous". Known issues: Initial support for UVC compatible cameras UVC cameras seem to draw significant amount of current from the USB bus. This does not appear to present any problems for the REV Robotics Control Hub. This does seem to create stability problems when using some cameras with an Android phone-based Robot Controller. FTC Tech Team is investigating options to mitigate this issue with the phone-based Robot Controllers. There might be a possible deadlock which causes the RC to become unresponsive when using a UVC webcam with a Nougat Android Robot Controller. Wireless When user selects a wireless channel, this channel does not necessarily persist if the phone is power cycled. Tech Team is hoping to eventually address this issue in a future release. Issue has been present since apps were introduced (i.e., it is not new with the v4.0 release). Wireless channel is not currently displayed for WiFi Direct connections. Miscellaneous The blink indication feature that shows which Expansion Hub is currently being configured does not work for a newly created configuration file. User has to first save a newly created configuration file and then close and re-edit the file in order for blink indicator to work. Version 3.6 (built on 17.12.18) Changes include: Blocks Changes Uses updated Google Blockly software to allow users to edit their op modes on Apple iOS devices (including iPad and iPhone). Improvement in Blocks tool to handle corrupt op mode files. Autonomous op modes should no longer get switched back to tele-op after re-opening them to be edited. The system can now detect type mismatches during runtime and alert the user with a message on the Driver Station. Updated javadoc documentation for setPower() method to reflect correct range of values (-1 to +1). Modified VuforiaLocalizerImpl to allow for user rendering of frames Added a user-overrideable onRenderFrame() method which gets called by the class's renderFrame() method. Version 3.5 (built on 17.10.30) Changes with version 3.5 include: Introduced a fix to prevent random op mode stops, which can occur after the Robot Controller app has been paused and then resumed (for example, when a user temporarily turns off the display of the Robot Controller phone, and then turns the screen back on). Introduced a fix to prevent random op mode stops, which were previously caused by random peer disconnect events on the Driver Station. Fixes issue where log files would be closed on pause of the RC or DS, but not re-opened upon resume. Fixes issue with battery handler (voltage) start/stop race. Fixes issue where Android Studio generated op modes would disappear from available list in certain situations. Fixes problem where OnBot Java would not build on REV Robotics Control Hub. Fixes problem where OnBot Java would not build if the date and time on the Robot Controller device was "rewound" (set to an earlier date/time). Improved error message on OnBot Java that occurs when renaming a file fails. Removed unneeded resources from android.jar binaries used by OnBot Java to reduce final size of Robot Controller app. Added MR_ANALOG_TOUCH_SENSOR block to Blocks Programming Tool. Version 3.4 (built on 17.09.06) Changes with version 3.4 include: Added telemetry.update() statement for BlankLinearOpMode template. Renamed sample Block op modes to be more consistent with Java samples. Added some additional sample Block op modes. Reworded OnBot Java readme slightly. Version 3.3 (built on 17.09.04) This version of the software includes improves for the FTC Blocks Programming Tool and the OnBot Java Programming Tool. Changes with verion 3.3 include: Android Studio ftc_app project has been updated to use Gradle Plugin 2.3.3. Android Studio ftc_app project is already using gradle 3.5 distribution. Robot Controller log has been renamed to /sdcard/RobotControllerLog.txt (note that this change was actually introduced w/ v3.2). Improvements in I2C reliability. Optimized I2C read for REV Expansion Hub, with v1.7 firmware or greater. Updated all external/samples (available through OnBot and in Android project folder). Vuforia Added support for VuMarks that will be used for the 2017-2018 season game. Blocks Update to latest Google Blockly release. Sample op modes can be selected as a template when creating new op mode. Fixed bug where the blocks would disappear temporarily when mouse button is held down. Added blocks for Range.clip and Range.scale. User can now disable/enable Block op modes. Fix to prevent occasional Blocks deadlock. OnBot Java Significant improvements with autocomplete function for OnBot Java editor. Sample op modes can be selected as a template when creating new op mode. Fixes and changes to complete hardware setup feature. Updated (and more useful) onBot welcome message. Known issues: Android Studio After updating to the new v3.3 Android Studio project folder, if you get error messages indicating "InvalidVirtualFileAccessException" then you might need to do a File->Invalidate Caches / Restart to clear the error. OnBot Java Sometimes when you push the build button to build all op modes, the RC returns an error message that the build failed. If you press the build button a second time, the build typically suceeds. Version 3.2 (built on 17.08.02) This version of the software introduces the "OnBot Java" Development Tool. Similar to the FTC Blocks Development Tool, the FTC OnBot Java Development Tool allows a user to create, edit and build op modes dynamically using only a Javascript-enabled web browser. The OnBot Java Development Tool is an integrated development environment (IDE) that is served up by the Robot Controller. Op modes are created and edited using a Javascript-enabled browser (Google Chromse is recommended). Op modes are saved on the Robot Controller Android device directly. The OnBot Java Development Tool provides a Java programming environment that does NOT need Android Studio. Changes with version 3.2 include: Enhanced web-based development tools Introduction of OnBot Java Development Tool. Web-based programming and management features are "always on" (user no longer needs to put Robot Controller into programming mode). Web-based management interface (where user can change Robot Controller name and also easily download Robot Controller log file). OnBot Java, Blocks and Management features available from web based interface. Blocks Programming Development Tool: Changed "LynxI2cColorRangeSensor" block to "REV Color/range sensor" block. Fixed tooltip for ColorSensor.isLightOn block. Added blocks for ColorSensor.getNormalizedColors and LynxI2cColorRangeSensor.getNormalizedColors. Added example op modes for digital touch sensor and REV Robotics Color Distance sensor. User selectable color themes. Includes many minor enhancements and fixes (too numerous to list). Known issues: Auto complete function is incomplete and does not support the following (for now): Access via this keyword Access via super keyword Members of the super cloass, not overridden by the class Any methods provided in the current class Inner classes Can't handle casted objects Any objects coming from an parenthetically enclosed expression Version 3.10 (built on 17.05.09) This version of the software provides support for the REV Robotics Expansion Hub. This version also includes improvements in the USB communication layer in an effort to enhance system resiliency. If you were using a 2.x version of the software previously, updating to version 3.1 requires that you also update your Driver Station software in addition to updating the Robot Controller software. Also note that in version 3.10 software, the setMaxSpeed and getMaxSpeed methods are no longer available (not deprecated, they have been removed from the SDK). Also note that the the new 3.x software incorporates motor profiles that a user can select as he/she configures the robot. Changes include: Blocks changes Added VuforiaTrackableDefaultListener.getPose and Vuforia.trackPose blocks. Added optimized blocks support for Vuforia extended tracking. Added atan2 block to the math category. Added useCompetitionFieldTargetLocations parameter to Vuforia.initialize block. If set to false, the target locations are placed at (0,0,0) with target orientation as specified in https://github.com/gearsincorg/FTCVuforiaDemo/blob/master/Robot_Navigation.java tutorial op mode. Incorporates additional improvements to USB comm layer to improve system resiliency (to recover from a greater number of communication disruptions). Additional Notes Regarding Version 3.00 (built on 17.04.13) In addition to the release changes listed below (see section labeled "Version 3.00 (built on 17.04.013)"), version 3.00 has the following important changes: Version 3.00 software uses a new version of the FTC Robocol (robot protocol). If you upgrade to v3.0 on the Robot Controller and/or Android Studio side, you must also upgrade the Driver Station software to match the new Robocol. Version 3.00 software removes the setMaxSpeed and getMaxSpeed methods from the DcMotor class. If you have an op mode that formerly used these methods, you will need to remove the references/calls to these methods. Instead, v3.0 provides the max speed information through the use of motor profiles that are selected by the user during robot configuration. Version 3.00 software currently does not have a mechanism to disable extra i2c sensors. We hope to re-introduce this function with a release in the near future. Version 3.00 (built on 17.04.13) *** Use this version of the software at YOUR OWN RISK!!! *** This software is being released as an "alpha" version. Use this version at your own risk! This pre-release software contains SIGNIFICANT changes, including changes to the Wi-Fi Direct pairing mechanism, rewrites of the I2C sensor classes, changes to the USB/FTDI layer, and the introduction of support for the REV Robotics Expansion Hub and the REV Robotics color-range-light sensor. These changes were implemented to improve the reliability and resiliency of the FTC control system. Please note, however, that version 3.00 is considered "alpha" code. This code is being released so that the FIRST community will have an opportunity to test the new REV Expansion Hub electronics module when it becomes available in May. The developers do not recommend using this code for critical applications (i.e., competition use). *** Use this version of the software at YOUR OWN RISK!!! *** Changes include: Major rework of sensor-related infrastructure. Includes rewriting sensor classes to implement synchronous I2C communication. Fix to reset Autonomous timer back to 30 seconds. Implementation of specific motor profiles for approved 12V motors (includes Tetrix, AndyMark, Matrix and REV models). Modest improvements to enhance Wi-Fi P2P pairing. Fixes telemetry log addition race. Publishes all the sources (not just a select few). Includes Block programming improvements Addition of optimized Vuforia blocks. Auto scrollbar to projects and sounds pages. Fixed blocks paste bug. Blocks execute after while-opModeIsActive loop (to allow for cleanup before exiting op mode). Added gyro integratedZValue block. Fixes bug with projects page for Firefox browser. Added IsSpeaking block to AndroidTextToSpeech. Implements support for the REV Robotics Expansion Hub Implements support for integral REV IMU (physically installed on I2C bus 0, uses same Bosch BNO055 9 axis absolute orientation sensor as Adafruit 9DOF abs orientation sensor). - Implements support for REV color/range/light sensor. Provides support to update Expansion Hub firmware through FTC SDK. Detects REV firmware version and records in log file. Includes support for REV Control Hub (note that the REV Control Hub is not yet approved for FTC use). Implements FTC Blocks programming support for REV Expansion Hub and sensor hardware. Detects and alerts when I2C device disconnect. Version 2.62 (built on 17.01.07) Added null pointer check before calling modeToByte() in finishModeSwitchIfNecessary method for ModernRoboticsUsbDcMotorController class. Changes to enhance Modern Robotics USB protocol robustness. Version 2.61 (released on 16.12.19) Blocks Programming mode changes: Fix to correct issue when an exception was thrown because an OpticalDistanceSensor object appears twice in the hardware map (the second time as a LightSensor). Version 2.6 (released on 16.12.16) Fixes for Gyro class: Improve (decrease) sensor refresh latency. fix isCalibrating issues. Blocks Programming mode changes: Blocks now ignores a device in the configuration xml if the name is empty. Other devices work in configuration work fine. Version 2.5 (internal release on released on 16.12.13) Blocks Programming mode changes: Added blocks support for AdafruitBNO055IMU. Added Download Op Mode button to FtcBocks.html. Added support for copying blocks in one OpMode and pasting them in an other OpMode. The clipboard content is stored on the phone, so the programming mode server must be running. Modified Utilities section of the toolbox. In Programming Mode, display information about the active connections. Fixed paste location when workspace has been scrolled. Added blocks support for the android Accelerometer. Fixed issue where Blocks Upload Op Mode truncated name at first dot. Added blocks support for Android SoundPool. Added type safety to blocks for Acceleration. Added type safety to blocks for AdafruitBNO055IMU.Parameters. Added type safety to blocks for AnalogInput. Added type safety to blocks for AngularVelocity. Added type safety to blocks for Color. Added type safety to blocks for ColorSensor. Added type safety to blocks for CompassSensor. Added type safety to blocks for CRServo. Added type safety to blocks for DigitalChannel. Added type safety to blocks for ElapsedTime. Added type safety to blocks for Gamepad. Added type safety to blocks for GyroSensor. Added type safety to blocks for IrSeekerSensor. Added type safety to blocks for LED. Added type safety to blocks for LightSensor. Added type safety to blocks for LinearOpMode. Added type safety to blocks for MagneticFlux. Added type safety to blocks for MatrixF. Added type safety to blocks for MrI2cCompassSensor. Added type safety to blocks for MrI2cRangeSensor. Added type safety to blocks for OpticalDistanceSensor. Added type safety to blocks for Orientation. Added type safety to blocks for Position. Added type safety to blocks for Quaternion. Added type safety to blocks for Servo. Added type safety to blocks for ServoController. Added type safety to blocks for Telemetry. Added type safety to blocks for Temperature. Added type safety to blocks for TouchSensor. Added type safety to blocks for UltrasonicSensor. Added type safety to blocks for VectorF. Added type safety to blocks for Velocity. Added type safety to blocks for VoltageSensor. Added type safety to blocks for VuforiaLocalizer.Parameters. Added type safety to blocks for VuforiaTrackable. Added type safety to blocks for VuforiaTrackables. Added type safety to blocks for enums in AdafruitBNO055IMU.Parameters. Added type safety to blocks for AndroidAccelerometer, AndroidGyroscope, AndroidOrientation, and AndroidTextToSpeech. Version 2.4 (released on 16.11.13) Fix to avoid crashing for nonexistent resources. Blocks Programming mode changes: Added blocks to support OpenGLMatrix, MatrixF, and VectorF. Added blocks to support AngleUnit, AxesOrder, AxesReference, CameraDirection, CameraMonitorFeedback, DistanceUnit, and TempUnit. Added blocks to support Acceleration. Added blocks to support LinearOpMode.getRuntime. Added blocks to support MagneticFlux and Position. Fixed typos. Made blocks for ElapsedTime more consistent with other objects. Added blocks to support Quaternion, Velocity, Orientation, AngularVelocity. Added blocks to support VuforiaTrackables, VuforiaTrackable, VuforiaLocalizer, VuforiaTrackableDefaultListener. Fixed a few blocks. Added type checking to new blocks. Updated to latest blockly. Added default variable blocks to navigation and matrix blocks. Fixed toolbox entry for openGLMatrix_rotation_withAxesArgs. When user downloads Blocks-generated op mode, only the .blk file is downloaded. When user uploads Blocks-generated op mode (.blk file), Javascript code is auto generated. Added DbgLog support. Added logging when a blocks file is read/written. Fixed bug to properly render blocks even if missing devices from configuration file. Added support for additional characters (not just alphanumeric) for the block file names (for download and upload). Added support for OpMode flavor (“Autonomous” or “TeleOp”) and group. Changes to Samples to prevent tutorial issues. Incorporated suggested changes from public pull 216 (“Replace .. paths”). Remove Servo Glitches when robot stopped. if user hits “Cancels” when editing a configuration file, clears the unsaved changes and reverts to original unmodified configuration. Added log info to help diagnose why the Robot Controller app was terminated (for example, by watch dog function). Added ability to transfer log from the controller. Fixed inconsistency for AngularVelocity Limit unbounded growth of data for telemetry. If user does not call telemetry.update() for LinearOpMode in a timely manner, data added for telemetry might get lost if size limit is exceeded. Version 2.35 (released on 16.10.06) Blockly programming mode - Removed unnecesary idle() call from blocks for new project. Version 2.30 (released on 16.10.05) Blockly programming mode: Mechanism added to save Blockly op modes from Programming Mode Server onto local device To avoid clutter, blocks are displayed in categorized folders Added support for DigitalChannel Added support for ModernRoboticsI2cCompassSensor Added support for ModernRoboticsI2cRangeSensor Added support for VoltageSensor Added support for AnalogInput Added support for AnalogOutput Fix for CompassSensor setMode block Vuforia Fix deadlock / make camera data available while Vuforia is running. Update to Vuforia 6.0.117 (recommended by Vuforia and Google to close security loophole). Fix for autonomous 30 second timer bug (where timer was in effect, even though it appeared to have timed out). opModeIsActive changes to allow cleanup after op mode is stopped (with enforced 2 second safety timeout). Fix to avoid reading i2c twice. Updated sample Op Modes. Improved logging and fixed intermittent freezing. Added digital I/O sample. Cleaned up device names in sample op modes to be consistent with Pushbot guide. Fix to allow use of IrSeekerSensorV3. Version 2.20 (released on 16.09.08) Support for Modern Robotics Compass Sensor. Support for Modern Robotics Range Sensor. Revise device names for Pushbot templates to match the names used in Pushbot guide. Fixed bug so that IrSeekerSensorV3 device is accessible as IrSeekerSensor in hardwareMap. Modified computer vision code to require an individual Vuforia license (per legal requirement from PTC). Minor fixes. Blockly enhancements: Support for Voltage Sensor. Support for Analog Input. Support for Analog Output. Support for Light Sensor. Support for Servo Controller. Version 2.10 (released on 16.09.03) Support for Adafruit IMU. Improvements to ModernRoboticsI2cGyro class Block on reset of z axis. isCalibrating() returns true while gyro is calibration. Updated sample gyro program. Blockly enhancements support for android.graphics.Color. added support for ElapsedTime. improved look and legibility of blocks. support for compass sensor. support for ultrasonic sensor. support for IrSeeker. support for LED. support for color sensor. support for CRServo prompt user to configure robot before using programming mode. Provides ability to disable audio cues. various bug fixes and improvements. Version 2.00 (released on 16.08.19) This is the new release for the upcoming 2016-2017 FIRST Tech Challenge Season. Channel change is enabled in the FTC Robot Controller app for Moto G 2nd and 3rd Gen phones. Users can now use annotations to register/disable their Op Modes. Changes in the Android SDK, JDK and build tool requirements (minsdk=19, java 1.7, build tools 23.0.3). Standardized units in analog input. Cleaned up code for existing analog sensor classes. setChannelMode and getChannelMode were REMOVED from the DcMotorController class. This is important - we no longer set the motor modes through the motor controller. setMode and getMode were added to the DcMotor class. ContinuousRotationServo class has been added to the FTC SDK. Range.clip() method has been overloaded so it can support this operation for int, short and byte integers. Some changes have been made (new methods added) on how a user can access items from the hardware map. Users can now set the zero power behavior for a DC motor so that the motor will brake or float when power is zero. Prototype Blockly Programming Mode has been added to FTC Robot Controller. Users can place the Robot Controller into this mode, and then use a device (such as a laptop) that has a Javascript enabled browser to write Blockly-based Op Modes directly onto the Robot Controller. Users can now configure the robot remotely through the FTC Driver Station app. Android Studio project supports Android Studio 2.1.x and compile SDK Version 23 (Marshmallow). Vuforia Computer Vision SDK integrated into FTC SDK. Users can use sample vision targets to get localization information on a standard FTC field. Project structure has been reorganized so that there is now a TeamCode package that users can use to place their local/custom Op Modes into this package. Inspection function has been integrated into the FTC Robot Controller and Driver Station Apps (Thanks Team HazMat… 9277 & 10650!). Audio cues have been incorporated into FTC SDK. Swap mechanism added to FTC Robot Controller configuration activity. For example, if you have two motor controllers on a robot, and you misidentified them in your configuration file, you can use the Swap button to swap the devices within the configuration file (so you do not have to manually re-enter in the configuration info for the two devices). Fix mechanism added to all user to replace an electronic module easily. For example, suppose a servo controller dies on your robot. You replace the broken module with a new module, which has a different serial number from the original servo controller. You can use the Fix button to automatically reconfigure your configuration file to use the serial number of the new module. Improvements made to fix resiliency and responsiveness of the system. For LinearOpMode the user now must for a telemetry.update() to update the telemetry data on the driver station. This update() mechanism ensures that the driver station gets the updated data properly and at the same time. The Auto Configure function of the Robot Controller is now template based. If there is a commonly used robot configuration, a template can be created so that the Auto Configure mechanism can be used to quickly configure a robot of this type. The logic to detect a runaway op mode (both in the LinearOpMode and OpMode types) and to abort the run, then auto recover has been improved/implemented. Fix has been incorporated so that Logitech F310 gamepad mappings will be correct for Marshmallow users. Release 16.07.08 For the ftc_app project, the gradle files have been modified to support Android Studio 2.1.x. Release 16.03.30 For the MIT App Inventor, the design blocks have new icons that better represent the function of each design component. Some changes were made to the shutdown logic to ensure the robust shutdown of some of our USB services. A change was made to LinearOpMode so as to allow a given instance to be executed more than once, which is required for the App Inventor. Javadoc improved/updated. Release 16.03.09 Changes made to make the FTC SDK synchronous (significant change!) waitOneFullHardwareCycle() and waitForNextHardwareCycle() are no longer needed and have been deprecated. runOpMode() (for a LinearOpMode) is now decoupled from the system's hardware read/write thread. loop() (for an OpMode) is now decoupled from the system's hardware read/write thread. Methods are synchronous. For example, if you call setMode(DcMotorController.RunMode.RESET_ENCODERS) for a motor, the encoder is guaranteed to be reset when the method call is complete. For legacy module (NXT compatible), user no longer has to toggle between read and write modes when reading from or writing to a legacy device. Changes made to enhance reliability/robustness during ESD event. Changes made to make code thread safe. Debug keystore added so that user-generated robot controller APKs will all use the same signed key (to avoid conflicts if a team has multiple developer laptops for example). Firmware version information for Modern Robotics modules are now logged. Changes made to improve USB comm reliability and robustness. Added support for voltage indicator for legacy (NXT-compatible) motor controllers. Changes made to provide auto stop capabilities for op modes. A LinearOpMode class will stop when the statements in runOpMode() are complete. User does not have to push the stop button on the driver station. If an op mode is stopped by the driver station, but there is a run away/uninterruptible thread persisting, the app will log an error message then force itself to crash to stop the runaway thread. Driver Station UI modified to display lowest measured voltage below current voltage (12V battery). Driver Station UI modified to have color background for current voltage (green=good, yellow=caution, red=danger, extremely low voltage). javadoc improved (edits and additional classes). Added app build time to About activity for driver station and robot controller apps. Display local IP addresses on Driver Station About activity. Added I2cDeviceSynchImpl. Added I2cDeviceSync interface. Added seconds() and milliseconds() to ElapsedTime for clarity. Added getCallbackCount() to I2cDevice. Added missing clearI2cPortActionFlag. Added code to create log messages while waiting for LinearOpMode shutdown. Fix so Wifi Direct Config activity will no longer launch multiple times. Added the ability to specify an alternate i2c address in software for the Modern Robotics gyro. Release 16.02.09 Improved battery checker feature so that voltage values get refreshed regularly (every 250 msec) on Driver Station (DS) user interface. Improved software so that Robot Controller (RC) is much more resilient and “self-healing” to USB disconnects: If user attempts to start/restart RC with one or more module missing, it will display a warning but still start up. When running an op mode, if one or more modules gets disconnected, the RC & DS will display warnings,and robot will keep on working in spite of the missing module(s). If a disconnected module gets physically reconnected the RC will auto detect the module and the user will regain control of the recently connected module. Warning messages are more helpful (identifies the type of module that’s missing plus its USB serial number). Code changes to fix the null gamepad reference when users try to reference the gamepads in the init() portion of their op mode. NXT light sensor output is now properly scaled. Note that teams might have to readjust their light threshold values in their op modes. On DS user interface, gamepad icon for a driver will disappear if the matching gamepad is disconnected or if that gamepad gets designated as a different driver. Robot Protocol (ROBOCOL) version number info is displayed in About screen on RC and DS apps. Incorporated a display filter on pairing screen to filter out devices that don’t use the “-“ format. This filter can be turned off to show all WiFi Direct devices. Updated text in License file. Fixed formatting error in OpticalDistanceSensor.toString(). Fixed issue on with a blank (“”) device name that would disrupt WiFi Direct Pairing. Made a change so that the WiFi info and battery info can be displayed more quickly on the DS upon connecting to RC. Improved javadoc generation. Modified code to make it easier to support language localization in the future. Release 16.01.04 Updated compileSdkVersion for apps Prevent Wifi from entering power saving mode removed unused import from driver station Corrrected "Dead zone" joystick code. LED.getDeviceName and .getConnectionInfo() return null apps check for ROBOCOL_VERSION mismatch Fix for Telemetry also has off-by-one errors in its data string sizing / short size limitations error User telemetry output is sorted. added formatting variants to DbgLog and RobotLog APIs code modified to allow for a long list of op mode names. changes to improve thread safety of RobocolDatagramSocket Fix for "missing hardware leaves robot controller disconnected from driver station" error fix for "fast tapping of Init/Start causes problems" (toast is now only instantiated on UI thread). added some log statements for thread life cycle. moved gamepad reset logic inside of initActiveOpMode() for robustness changes made to mitigate risk of race conditions on public methods. changes to try and flag when WiFi Direct name contains non-printable characters. fix to correct race condition between .run() and .close() in ReadWriteRunnableStandard. updated FTDI driver made ReadWriteRunnableStanard interface public. fixed off-by-one errors in Command constructor moved specific hardware implmentations into their own package. moved specific gamepad implemnatations to the hardware library. changed LICENSE file to new BSD version. fixed race condition when shutting down Modern Robotics USB devices. methods in the ColorSensor classes have been synchronized. corrected isBusy() status to reflect end of motion. corrected "back" button keycode. the notSupported() method of the GyroSensor class was changed to protected (it should not be public). Release 15.11.04.001 Added Support for Modern Robotics Gyro. The GyroSensor class now supports the MR Gyro Sensor. Users can access heading data (about Z axis) Users can also access raw gyro data (X, Y, & Z axes). Example MRGyroTest.java op mode included. Improved error messages More descriptive error messages for exceptions in user code. Updated DcMotor API Enable read mode on new address in setI2cAddress Fix so that driver station app resets the gamepads when switching op modes. USB-related code changes to make USB comm more responsive and to display more explicit error messages. Fix so that USB will recover properly if the USB bus returns garbage data. Fix USB initializtion race condition. Better error reporting during FTDI open. More explicit messages during USB failures. Fixed bug so that USB device is closed if event loop teardown method was not called. Fixed timer UI issue Fixed duplicate name UI bug (Legacy Module configuration). Fixed race condition in EventLoopManager. Fix to keep references stable when updating gamepad. For legacy Matrix motor/servo controllers removed necessity of appending "Motor" and "Servo" to controller names. Updated HT color sensor driver to use constants from ModernRoboticsUsbLegacyModule class. Updated MR color sensor driver to use constants from ModernRoboticsUsbDeviceInterfaceModule class. Correctly handle I2C Address change in all color sensors Updated/cleaned up op modes. Updated comments in LinearI2cAddressChange.java example op mode. Replaced the calls to "setChannelMode" with "setMode" (to match the new of the DcMotor method). Removed K9AutoTime.java op mode. Added MRGyroTest.java op mode (demonstrates how to use MR Gyro Sensor). Added MRRGBExample.java op mode (demonstrates how to use MR Color Sensor). Added HTRGBExample.java op mode (demonstrates how to use HT legacy color sensor). Added MatrixControllerDemo.java (demonstrates how to use legacy Matrix controller). Updated javadoc documentation. Updated release .apk files for Robot Controller and Driver Station apps. Release 15.10.06.002 Added support for Legacy Matrix 9.6V motor/servo controller. Cleaned up build.gradle file. Minor UI and bug fixes for driver station and robot controller apps. Throws error if Ultrasonic sensor (NXT) is not configured for legacy module port 4 or 5. Release 15.08.03.001 New user interfaces for FTC Driver Station and FTC Robot Controller apps. An init() method is added to the OpMode class. For this release, init() is triggered right before the start() method. Eventually, the init() method will be triggered when the user presses an "INIT" button on driver station. The init() and loop() methods are now required (i.e., need to be overridden in the user's op mode). The start() and stop() methods are optional. A new LinearOpMode class is introduced. Teams can use the LinearOpMode mode to create a linear (not event driven) program model. Teams can use blocking statements like Thread.sleep() within a linear op mode. The API for the Legacy Module and Core Device Interface Module have been updated. Support for encoders with the Legacy Module is now working. The hardware loop has been updated for better performance.
NICALab / SUPPORTAccurate denoising of voltage imaging data through statistically unbiased prediction, Nature Methods.
ccadic / SHARPIW0The SHARPIW0 carrier board has been designed to hold both a Raspberry(R) PI ZERO 2W or W + 2.7" (400x240) Sharp Memory Display. This display is capable of a fast refresh which allows the use of linux shells or display game images. The board also has 4 independently controlable LEDs you can switch on/off with classic GPIO commands (C++ or Python) The board also has 5 buttons you may also control via GPIO voltage detection (UP/Down voltage detection). You can use this board for gaming.
ssr-diaries / Development Of Autonomous Downscaled Model Car Using Neural Networks And Machine LearningMachine learning using convolution neural network Required: raspberry pi pi cam compatibile rc car motor driver l293d Please create the respective files: forward idle left right reverse optimized_thetas This project aims to build an autonomous rc car using supervised learning of a neural network with a single hidden layer. We have not used any Machine Learning libraries since we wanted to implement the neural network from scratch to understand the concepts better. We will be referring the DC motor controlling the left/right direction as the front motor and the motor controlling the forward/reverse direction as the back motor. Connect the BACK_MOTOR_DATA_ONE and BACK_MOTOR_DATA_TWO GPIO pins(GPIO17 and GPIO27) of the Raspberry Pi to the Input pins for Motor 1(Input 1, Input 2) and the BACK_MOTOR_ENABLE_PIN GPIO pin(GPIO22) to the Enable pin for Motor 1(Enable 1,2) in the L293D Motor Driver IC. Connect the Output pins for Motor 1(Output 1, Output 2) of the IC to the back motor. Connect the FRONT_MOTOR_DATA_ONE and FRONT_MOTOR_DATA_TWO GPIO pins(GPIO19 and GPIO26) of the Raspberry Pi to the Input pins for Motor 2(Input 3, Input 4) in the IC. Connect the Output pins for Motor 2(Output 3, Output 4) of the IC to the front motor. The PWM_FREQUENCY and INITIAL_PWM_DUTY_CYCLE represent the initial frequency and duty cycle of the PWM output. We have created five class labels namely forward, reverse, left, right and idle and assigned their expected values. All class labels would require a folder of the same name to be present in the current directory. The input images resize to the dimension of the IMAGE_DIMENSION tuple value during training. The LAMBDA and HIDDEN_LAYER_SIZE values represent the default lambda value and the number of nodes in the hidden layer while training the neural network. All these values are configurable in configuration.py. The images for training are captured using interactive_control_train.py, the car is controlled using the direction arrows and all the images are recorded in the same folder along with the corresponding key press. After segregating the images into their corresponding class folders, the neural network is trained using train.py which takes two optional arguments - lambda and hidden layer size; default values would be those specified in the configuration file. At the command prompt, run the following command Once we have the trained model, the RC car is run autonomously using autonomous.py which takes an optional argument for the trained model; default will use the latest model in the optimized_thetas folder. Please feel free to post your doubts on code through my linkedin link: edin.com/in/shreyas-ramachandran-srinivasan-565638117/ CONTROLLING THE CAR The controlling process consists of 4 parts: The sensor interface layer includes various programming modules worried about getting and time stamping all sensor information. The discernment layer maps sensor information into inward models. The essential module in this layer is the PI camera, which decides the vehicle's introduction and area. Two distinct modules enable auto to explore in view of ultrasonic sensor and the camera. A street discovering module utilizes the PI camera determined pictures to discover the limit of a street, so the vehicle can focus itself along the side. At last, a surface evaluation module separates parameters of the present street to determine safe vehicle speeds. The control layer is in charge of managing the controlling, throttle, and brake reaction of the vehicle. A key module is the way organizer, which sets the direction of the vehicle in controlling and speed space. The vehicle interface layer fills in as the interface to the robot's drive-by-wire framework. It contains all interfaces to the vehicle's brakes, throttle, and controlling wheel. It likewise includes the interface to the vehicle's server, a circuit that manages the physical capacity to a significant number of the framework segments. In the proposed system, the raspberry Pi is used to control the L293D board, which allows motors to be controlled through the raspberry pi through the pulses provided by it. Based on the images obtained, raspberry pi provides PWM pulses tocontrol the L293D controller. L293D is a 16 Pin Motor Driver IC as shown in Figure 9. This is designed to provide bidirectional drive currents at voltages from 5 V to 36 V. Fig 9 L293D Breakout Board It also allows the speed of the motor to be controlled using PWM. It’s a series of high and low. The Duration of high and low determine the voltage supplied to the motor and hence the speed of the motor. PWM Signals: The DC motor speed all in all is specifically relative to the supply voltage, so if lessen the voltage from 9 volts to 4.5 volts, then our speed turn out to be half of what it initially had. Yet, for changing the speed of a dc motor we can't continue changing the supply voltage constantly. The speed controller PWM for a DC motor works by changing the normal voltage provided to the motor.The input signals we have given to PWM controller may be a simple or computerized motion as per the outline of the PWM controller. The PWM controller acknowledges the control flag and modifies the obligation cycle of the PWM motion as indicated by the prerequisites. In these waves frequency is same but the ON and OFF times are different. Recharge power bank of any capacity, here, 2800 mAH is used (operating voltage of 5V DC), can be used to provide supply to central microcontroller. The microcontroller used will separate and supply the required amount of power to each hardware component. This battery power pack is rechargeable and can get charged and used again and again.
Neol00 / Edk2 Cix UnlockedCustom UEFI (EDK2) firmware for the Radxa Orion O6 single board computer (CIX CD8180 / Sky1 SoC). This firmware adds a BIOS settings menu for configuring OPP (Operating Performance Point) tables and TDP power caps, allowing per-domain frequency and voltage tuning without recompiling the BIOS image.
adamcohenlab / Invivo ImagingDenoising and Demixing Pipeline for in vivo Voltage Imaging Data (SGPMD-NMF)
caichangjia / VolPyVoltage imaging analysis in python
dan22h / OLED GaugeCode to drive a 4d systems uOLED 160 display module using an attiny84 or arduino for a car/automotive gauge. Sample images for Oil pressure, oil temp, voltage etc
bu-cisl / DeepVIDDeepVID: A Self-supervised Deep Learning Framework for Two-photon Voltage Imaging Denoising
bu-cisl / DeepVIDv2DeepVID v2: Self-Supervised Denoising with Decoupled Spatiotemporal Enhancement for Low-Photon Voltage Imaging
cellarium-ai / CellMincerCellMincer is a software package for self-supervised denoising of voltage imaging datasets
kushalkolar / Mesmerize Workshop Ccn 2022Materials related to the Mesmerize sections of the CCN 2022 Calcium & Voltage Imaging Workshop
jgamble77 / REST API<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>numResults</key> <integer>3040589</integer> <key>results</key> <array> <dict> <key>Source</key> <string>IMT</string> <key>DocumentID</key> <integer>5986181</integer> <key>SalesStatus</key> <string>Delete</string> <key>CoOpIndicator</key> <string>false</string> <key>NumberOfEngines</key> <integer>0</integer> <key>RegistrationCountryCode</key> <integer>0</integer> <key>Owner</key> <dict> <key>PartyId</key> <integer>63898</integer> </dict> <key>SalesRep</key> <dict> <key>PartyId</key> <integer>63899</integer> <key>Name</key> <string>Sander Bekkers</string> <key>Message</key> <string>The company for strong ships!</string> </dict> <key>CompanyName</key> <string>Breitner Yacht Brokers</string> <key>Office</key> <dict> <key>PostalAddress</key> <string>Breitnerlaan 14 Utrecht</string> <key>City</key> <string>Utrecht</string> <key>State</key> <string></string> <key>PostCode</key> <string>3582 HB</string> <key>Country</key> <string>NL</string> <key>Email</key> <string>info@breitnerbrokers.nl</string> <key>Phone</key> <string>+31(0)637139954</string> <key>Name</key> <string>Breitner Yacht Brokers</string> </dict> <key>LastModificationDate</key> <string>2018-02-18</string> <key>ItemReceivedDate</key> <string>2016-10-28</string> <key>Price</key> <string>62075.43 USD</string> <key>PriceHideInd</key> <false/> <key>EmbeddedVideoPresent</key> <false/> <key>BoatLocation</key> <dict> <key>BoatCityName</key> <string>Unknown</string> <key>BoatCountryID</key> <string>SE</string> <key>BoatStateCode</key> <string></string> </dict> <key>BoatCityNameNoCaseAlnumOnly</key> <string>Unknown</string> <key>MakeString</key> <string>Alistair Hunter</string> <key>MakeStringExact</key> <string>Alistair Hunter</string> <key>MakeStringNoCaseAlnumOnly</key> <string>Alistair Hunter</string> <key>ModelYear</key> <integer>1986</integer> <key>SaleClassCode</key> <string>Used</string> <key>Model</key> <integer>42</integer> <key>ModelExact</key> <integer>42</integer> <key>ModelNoCaseAlnumOnly</key> <integer>42</integer> <key>BoatCategoryCode</key> <string>Sail</string> <key>BoatName</key> <string>Fair Grace</string> <key>BoatNameNoCaseAlnumOnly</key> <string>Fair Grace</string> <key>BuilderName</key> <string></string> <key>DesignerName</key> <string></string> <key>CruisingSpeedMeasure</key> <string></string> <key>PropellerCruisingSpeed</key> <string></string> <key>MaximumSpeedMeasure</key> <string></string> <key>RangeMeasure</key> <string></string> <key>BridgeClearanceMeasure</key> <string></string> <key>BeamMeasure</key> <string>11 ft</string> <key>FreeBoardMeasure</key> <string></string> <key>CabinHeadroomMeasure</key> <string></string> <key>DryWeightMeasure</key> <string></string> <key>BallastWeightMeasure</key> <string></string> <key>DisplacementMeasure</key> <string></string> <key>DisplacementTypeCode</key> <string></string> <key>TotalEnginePowerQuantity</key> <string></string> <key>DriveTypeCode</key> <string></string> <key>BoatKeelCode</key> <string>Full Keel</string> <key>ConvertibleSaloonIndicator</key> <false/> <key>WindlassTypeCode</key> <string></string> <key>DeadriseMeasure</key> <string></string> <key>ElectricalCircuitMeasure</key> <string></string> <key>TrimTabsIndicator</key> <false/> <key>BoatHullMaterialCode</key> <string>Steel</string> <key>BoatHullID</key> <string></string> <key>StockNumber</key> <string></string> <key>NominalLength</key> <string>42 ft</string> <key>ListingTitle</key> <string>Offers wanted</string> <key>MaxDraft</key> <string>6.5 ft</string> <key>TaxStatusCode</key> <string>Paid</string> <key>IMTTimeStamp</key> <string>2018-02-18T08:42:27Z</string> <key>HasBoatHullID</key> <false/> <key>IsAvailableForPls</key> <false/> <key>NormNominalLength</key> <real>12.8</real> <key>NormPrice</key> <real>68114.43</real> <key>OptionActiveIndicator</key> <false/> <key>Service</key> <array> <string>imt.beta</string> <string>branding.imt.features.boats.display</string> <string>imt.product.boat</string> <string>imt.expiry</string> <string>imt.layout.newui</string> <string>export.yw</string> <string>account.type.broker</string> <string>soldboats</string> <string>yw.websites</string> <string>yw.mls</string> <string>yw</string> <string>branding.imt.bw</string> <string>imt.tracker.regular</string> </array> <key>GeneralBoatDescription</key> <array> <string><p>This world sailor has unprecedented qualities, designed by Alistair Hunter and built by the Hunt Worth Shipyard on the Isle of Wight.&nbsp; It is a perfect ship for rough weather, and it has already endured a hurricane without even a scratch. The steel hull has some slight chines&nbsp;in some places and the same applies to the deck, this gives the boat a rounded very strong ”egg-type” self-bearing construction. &nbsp;Similarly there are hardly any obstacles on deck that can be damaged. After&nbsp;many ocean crossings and long trips, the owner decided to renovate the ship completely. First he dealt with the outer skin and beams: the thinner beams were chiselled and re-inserted and trusses were replaced. After that, the ship was completely sandblasted and treated with 2-component paint which will preserve&nbsp;it for the coming 20 years.</p> <p>Furthermore, the entire interior was rebuilt by the yard and the outside cockpit again&nbsp;covered with teak. The layout of the ship remained unchanged, with a nice aft cabin with double bed of 2m x 1.80m, and two settees witch can be converted to beds in the main cabin, also equipped&nbsp;with galley and a centrally located wood stove. The cushions and matrasses&nbsp;are new. Up front is a shower / head and in the bow there is a workplace with storage for tools and spare parts, plus an extra bed. Also, the electrical system has been completely revamped, as well as all the equipment, the tanks and the (SS) anchor locker.</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>A safe working ship fit for making long trips and living aboard. This remodelled ship can serve for many years as the basis for World circumnavigation.</p> <p></p> <p>Deck and hull: Steel keel 6mm, 4mm flat, side 4mm, 3mm deck, deck features non-skid paint.</p> <p>Superstructure: Smooth deck with small deckhouse, steel</p> <p>Rudder: pierced helm, behind a skeg</p> <p>Control: Steering wheel, hydraulic</p> <p>Displacement: Ca. 10 tons, 12 tons loaded</p> <p>Ballast (kg): Approx. 4.9 tonnes (cast iron)</p> <p>Length: 42'&nbsp;loa, lod: 39.6', beam 11',&nbsp;depth 6.5'</p> <p>Clearance: Ca. 15 m</p> <p></p> <p>accommodation</p> <p>Material, colors: plywood, Mahogany</p> <p>Cabins: 2 cabins, 3 lounges</p> <p>Sleeping: 3 fixed, 2 extra</p> <p>Headroom: Ca.190 cm</p> <p>Toilet: 1x, with holding tank</p> <p>Shower: Yes</p> <p>Cooking / device: 3-burner diesel cooker</p> <p>Oven: Yes, diesel</p> <p>Refrigerator: Yes, with compressor</p> <p>Heating: Yes, Webasto diesel heater and wood stove</p> <p></p> <p>Engine, electrics, water</p> <p>Power: 20 horsepower</p> <p>Brand: Volvo Penta 2003T</p> <p>Year: 2003, revision 2016</p> <p>Hours: 1100</p> <p>Fuel: diesel</p> <p>Fuel capacity: 200L</p> <p>Cooling intercooling</p> <p>Propulsion: Fixed propeller</p> <p>No thruster</p> <p>Mains voltage: 12V</p> <p>Battery:&nbsp;2 x 120Ah</p> <p>Battery charger: yes</p> <p>converter: Yes</p> <p>Water pressure system: no</p> <p>Hot water: yes, by the engine</p> <p>Water tank: Ca. 300 liter</p> <p>Holding tank: yes</p> <p>Shore power: yes</p> <p>Voltmeter: Yes</p> <p>Tachometer: yes</p> <p>Fuel Meter: yes</p> <p>Wind generator, solar panels</p> <p></p> <p>Rigging</p> <p>Bermuda type cutter</p> <p>Winches 8 x</p> <p>mainsail 2007</p> <p>Mainsail reefing system Bind</p> <p>Genoa 2007</p> <p>Genoa reefing system</p> <p>Staysail ,trysail, storm jib</p> <p></p> <p>Navigation and electronics</p> <p>Navigation lights: yes</p> <p>Compass: yes</p> <p>Log / speed: yes, new</p> <p>Depth: yes, new</p> <p>Wind: yes, new</p> <p>Autopilot: yes</p> <p>Wind vane: yes, an Aries</p> <p>Radar: yes, new</p> <p>GPS plotter: yes, new</p> <p>VHF: yes, new</p> <p>SSB: yes, new</p> <p>Epirb: yes</p> <p></p> <p></p> <p>Equipment</p> <p>Anchor: 2x + 2 x 80m chain</p> <p>Windlass: yes</p> <p>Fenders, lines</p> <p>Life raft: Yes, approved in 2016</p> <p>Bilge pump: Manual and electrical</p> <p>Fire extinguisher: 2x&nbsp;</p> <p>Tarpaulins Winter cover and hood for mainsail and mizzen</p> <p>Sprayhood: yes</p> <p>Swimming ladder: yes</p> <p>Achilles dinghy with 3.5 hp Yamaha outboard</p> <p></p></string> </array> <key>BoatClassCode</key> <array> <string>Other</string> </array> <key>Images</key> <array> <dict> <key>Priority</key> <integer>0</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004733844_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>1</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004744938_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>2</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20161028071959392_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>3</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004748049_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>4</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004755518_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>5</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004806511_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>6</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004815612_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>7</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004824055_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>8</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004832060_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>9</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004840380_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>10</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004848701_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>11</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004857534_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>12</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004911936_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>13</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004920125_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>14</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004927880_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>15</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004935481_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>16</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004942361_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>17</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004949514_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>18</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502004955292_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>19</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502005001362_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>20</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502005008632_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>21</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502005015158_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>22</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170309014443217_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>23</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/61/81/5986181_20170502005208891_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> </array> <key>Marketing</key> <array> <dict> <key>OpportunityType</key> <string></string> <key>OpportunityMethod</key> <string>Offers wanted</string> <key>ProgramID</key> <string>TagLine</string> <key>ProgramDescription</key> <string></string> <key>ProgramOffer</key> <string></string> <key>PublicationID</key> <string></string> <key>MarketingID</key> <string></string> </dict> <dict> <key>OpportunityType</key> <string></string> <key>OpportunityMethod</key> <string>CUSTOM_CONTACT_SHOW_BROKER</string> <key>ProgramID</key> <string>PUBLIC</string> <key>ProgramDescription</key> <string></string> <key>ProgramOffer</key> <string></string> <key>PublicationID</key> <string></string> <key>MarketingID</key> <string></string> </dict> <dict> <key>OpportunityType</key> <string></string> <key>OpportunityMethod</key> <string>NAME_ACCESS</string> <key>ProgramID</key> <string>PUBLIC</string> <key>ProgramDescription</key> <string></string> <key>ProgramOffer</key> <string></string> <key>PublicationID</key> <string></string> <key>MarketingID</key> <string></string> </dict> </array> <key>BoatClassCodeNoCaseAlnumOnly</key> <array> <string>Other</string> </array> <key>AdditionalDetailDescription</key> <array> <string><strong>Disclaimer</strong><br>The Company offers the details of this vessel in good faith but cannot guarantee or warrant the accuracy of this information nor warrant the condition of the vessel. A buyer should instruct his agents, or his surveyors, to investigate such details as the buyer desires validated. This vessel is offered subject to prior sale, price change, or withdrawal without notice.</string> </array> </dict> <dict> <key>Source</key> <string>IMT</string> <key>DocumentID</key> <integer>6590372</integer> <key>SalesStatus</key> <string>Delete</string> <key>CoOpIndicator</key> <string></string> <key>NumberOfEngines</key> <integer>1</integer> <key>RegistrationCountryCode</key> <integer>0</integer> <key>Owner</key> <dict> <key>PartyId</key> <integer>58610</integer> </dict> <key>SalesRep</key> <dict> <key>PartyId</key> <integer>58611</integer> <key>Name</key> <string>Giorgia Bettin</string> </dict> <key>CompanyName</key> <string>G-Broker</string> <key>Office</key> <dict> <key>PostalAddress</key> <string>Marina di Punta Faro</string> <key>City</key> <string>Lignano Sabbiadoro</string> <key>State</key> <string></string> <key>PostCode</key> <string></string> <key>Country</key> <string>IT</string> <key>Email</key> <string>info.gbroker@gmail.com</string> <key>Phone</key> <string>+39 329 2114424</string> <key>Name</key> <string>G-Broker</string> </dict> <key>LastModificationDate</key> <string>2018-02-17</string> <key>ItemReceivedDate</key> <string>2018-01-23</string> <key>Price</key> <string>49750.80 USD</string> <key>PriceHideInd</key> <false/> <key>EmbeddedVideoPresent</key> <false/> <key>BoatLocation</key> <dict> <key>BoatCityName</key> <string>Lignano Sabbiadoro</string> <key>BoatCountryID</key> <string>IT</string> <key>BoatStateCode</key> <string></string> </dict> <key>BoatCityNameNoCaseAlnumOnly</key> <string>Lignano Sabbiadoro</string> <key>MakeString</key> <string>Elan</string> <key>MakeStringExact</key> <string>Elan</string> <key>MakeStringNoCaseAlnumOnly</key> <string>Elan</string> <key>ModelYear</key> <integer>2000</integer> <key>SaleClassCode</key> <string>Used</string> <key>Model</key> <integer>333</integer> <key>ModelExact</key> <integer>333</integer> <key>ModelNoCaseAlnumOnly</key> <integer>333</integer> <key>BoatCategoryCode</key> <string>Sail</string> <key>BoatName</key> <string></string> <key>BoatNameNoCaseAlnumOnly</key> <string></string> <key>BuilderName</key> <string></string> <key>DesignerName</key> <string></string> <key>CruisingSpeedMeasure</key> <string></string> <key>PropellerCruisingSpeed</key> <string></string> <key>MaximumSpeedMeasure</key> <string></string> <key>RangeMeasure</key> <string></string> <key>BridgeClearanceMeasure</key> <string></string> <key>BeamMeasure</key> <string>11.35 ft</string> <key>FreeBoardMeasure</key> <string></string> <key>CabinHeadroomMeasure</key> <string></string> <key>WaterTankCountNumeric</key> <integer>2</integer> <key>WaterTankCapacityMeasure</key> <string>100|liter</string> <key>WaterTankMaterialCode</key> <string>Stainless Steel</string> <key>FuelTankCountNumeric</key> <integer>1</integer> <key>FuelTankCapacityMeasure</key> <string>70|liter</string> <key>FuelTankMaterialCode</key> <string></string> <key>DryWeightMeasure</key> <string>11,464.04 lb</string> <key>BallastWeightMeasure</key> <string></string> <key>DisplacementMeasure</key> <string></string> <key>DisplacementTypeCode</key> <string></string> <key>TotalEnginePowerQuantity</key> <string>29 hp</string> <key>DriveTypeCode</key> <string></string> <key>BoatKeelCode</key> <string></string> <key>ConvertibleSaloonIndicator</key> <true/> <key>WindlassTypeCode</key> <string></string> <key>DeadriseMeasure</key> <string></string> <key>ElectricalCircuitMeasure</key> <string></string> <key>TrimTabsIndicator</key> <false/> <key>DoubleBerthsCountNumeric</key> <integer>2</integer> <key>CabinsCountNumeric</key> <integer>2</integer> <key>BoatHullMaterialCode</key> <string>Fiberglass</string> <key>BoatHullID</key> <string></string> <key>StockNumber</key> <string></string> <key>NominalLength</key> <string>34.45 ft</string> <key>MaxDraft</key> <string>6.23 ft</string> <key>TaxStatusCode</key> <string>Paid</string> <key>IMTTimeStamp</key> <string>2018-02-18T06:35:46Z</string> <key>HasBoatHullID</key> <false/> <key>IsAvailableForPls</key> <false/> <key>NormNominalLength</key> <real>10.5</real> <key>NormPrice</key> <real>54590.8</real> <key>OptionActiveIndicator</key> <false/> <key>Engines</key> <array> <dict> <key>Make</key> <string>Yanmar</string> <key>Model</key> <string>3gm30</string> <key>Fuel</key> <string>diesel</string> <key>EnginePower</key> <string>29|horsepower</string> <key>Year</key> <integer>2000</integer> <key>Hours</key> <real>1300</real> </dict> </array> <key>Service</key> <array> <string>export.cdb</string> <string>imt.beta</string> <string>branding.imt.features.boats.display</string> <string>imt.product.boat</string> <string>branding.imt.boatscentral</string> <string>imt.layout.newui</string> <string>boats.com.service.level.premium</string> <string>account.type.dealer</string> <string>boats.com.featured.boats</string> <string>imt.vbs</string> <string>boats.com.c2a.buy</string> <string>boats.com.c2a.more</string> <string>boats.com.c2a.brochure</string> <string>boats.com.c2a.appointment</string> <string>boats.com.c2a.tradein</string> <string>boats.com</string> <string>export.boats</string> <string>imt.tracker.regular</string> </array> <key>GeneralBoatDescription</key> <array> <string><p><strong>Elan 333, bellissimo , in piu' che eccellenti condizioni generali , interni perfetti , avvolgiranda , avvolgifiocco.</strong></p> <p><strong>&nbsp;</strong></p> <p><strong>-</strong><strong>Tagliandi regolari, alaggi invernali, la velocita di crocera a 2500 giri e di 6.7 nodi</strong></p> <p><strong>-</strong><strong>Due prese corrente 220 sia a poppa che a prua</strong></p> <p><strong>-</strong><strong>Una randa in dacron, due fiocchi un gennaker</strong></p> <p>&nbsp;</p> <p><strong>Rimessata d'inverno sempre a terra</strong></p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p><strong>&nbsp;</strong></p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p></string> </array> <key>BoatClassCode</key> <array> <string>Cruisers</string> </array> <key>BoatClassCodeNoCaseAlnumOnly</key> <array> <string>Cruisers</string> </array> <key>AdditionalDetailDescription</key> <array> <string><strong>Disclaimer</strong><br>La Societ&agrave; pubblica i dettagli di questa imbarcazione in buona fede e non pu&ograve; pertanto avvallare o garantire l'esattezza di tale informazione</string> </array> <key>Images</key> <array> <dict> <key>Priority</key> <integer>0</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062813083_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>1</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180123081703157_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>2</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062638282_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>3</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062753803_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>4</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062725795_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>5</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180127062711986_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>6</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062743549_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>7</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062715958_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>8</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062656996_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>9</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180123081719852_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>10</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062734832_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>11</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062705939_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>12</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180124062801848_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>13</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180127063012657_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> <dict> <key>Priority</key> <integer>14</integer> <key>Caption</key> <string></string> <key>Uri</key> <string>https://imt.boatwizard.com/images/1/3/72/6590372_20180127063613625_1_XLARGE.jpg</string> <key>LastModifiedDateTime</key> <string></string> </dict> </array> <key>Marketing</key> <array> <dict> <key>OpportunityType</key> <string></string> <key>OpportunityMethod</key> <string>CUSTOM_CONTACT_SHOW_BROKER</string> <key>ProgramID</key> <string>PUBLIC</string> <key>ProgramDescription</key> <string></string> <key>ProgramOffer</key> <string></string> <key>PublicationID</key> <string></string> <key>MarketingID</key> <string></string> </dict> </array> <key>TotalEngineHoursNumeric</key> <real>1300</real> </dict> </array> <key>facets</key> <dict> <key>price</key> <dict> <key>price<1000EUR</key> <integer>647683</integer> <key>price1000-40000EUR</key> <integer>1289785</integer> <key>price40000-90000000EUR</key> <integer>1030454</integer> <key>price>90000000EUR</key> <integer>425</integer> </dict> <key>make</key> <dict> <key>tracker</key> <integer>326543</integer> <key>sea</key> <integer>219908</integer> <key>ray</key> <integer>150520</integer> <key>sun</key> <integer>90626</integer> <key>lowe</key> <integer>68638</integer> <key>bayliner</key> <integer>61432</integer> <key>lund</key> <integer>61370</integer> <key>boats</key> <integer>61009</integer> <key>bennington</key> <integer>58211</integer> <key>crestliner</key> <integer>49035</integer> <key>yamaha</key> <integer>47759</integer> <key>beneteau</key> <integer>45735</integer> <key>yachts</key> <integer>40206</integer> <key>boston</key> <integer>39529</integer> <key>whaler</key> <integer>39502</integer> <key>craft</key> <integer>38939</integer> <key>chaparral</key> <integer>38109</integer> <key>nitro</key> <integer>35419</integer> <key>ranger</key> <integer>31223</integer> <key>jeanneau</key> <integer>31176</integer> <key>tahoe</key> <integer>29609</integer> <key>white</key> <integer>29460</integer> <key>grady</key> <integer>29018</integer> <key>gradywhite</key> <integer>28714</integer> <key>seadoo</key> <integer>28609</integer> <key>doo</key> <integer>28164</integer> <key>regal</key> <integer>28105</integer> <key>cobalt</key> <integer>24241</integer> <key>carver</key> <integer>24154</integer> <key>winns</key> <integer>23189</integer> <key>chris</key> <integer>23156</integer> <key>four</key> <integer>23080</integer> <key>catalina</key> <integer>22989</integer> <key>princess</key> <integer>22882</integer> <key>mako</key> <integer>22653</integer> <key>chriscraft</key> <integer>22285</integer> <key>harris</key> <integer>22114</integer> <key>malibu</key> <integer>21565</integer> <key>hurricane</key> <integer>21302</integer> <key>marine</key> <integer>21288</integer> <key>mastercraft</key> <integer>20334</integer> <key>pursuit</key> <integer>20186</integer> <key>hunter</key> <integer>19810</integer> <key>sweetwater</key> <integer>18969</integer> <key>wellcraft</key> <integer>18850</integer> <key>crownline</key> <integer>18822</integer> <key>princecraft</key> <integer>17883</integer> <key>monterey</key> <integer>17423</integer> <key>formula</key> <integer>17290</integer> <key>bavaria</key> <integer>16540</integer> <key>rinker</key> <integer>16496</integer> <key>cruisers</key> <integer>15974</integer> <key>3</key> <integer>15664</integer> <key>carolina</key> <integer>15656</integer> <key>key</key> <integer>15648</integer> <key>g</key> <integer>15577</integer> <key>hunt</key> <integer>15506</integer> <key>pro</key> <integer>15465</integer> <key>starcraft</key> <integer>15232</integer> <key>west</key> <integer>14795</integer> <key>bay</key> <integer>14476</integer> <key>tige</key> <integer>14352</integer> <key>nauticstar</key> <integer>14319</integer> <key>custom</key> <integer>14049</integer> <key>skeeter</key> <integer>13996</integer> <key>triton</key> <integer>13959</integer> <key>sunseeker</key> <integer>13919</integer> <key>skiff</key> <integer>13901</integer> <key>azimut</key> <integer>13767</integer> <key>alumacraft</key> <integer>13445</integer> <key>fairline</key> <integer>13411</integer> <key>tiara</key> <integer>13254</integer> <key>silverton</key> <integer>13040</integer> <key>maxum</key> <integer>12925</integer> <key>robalo</key> <integer>12823</integer> <key>glastron</key> <integer>12189</integer> <key>scout</key> <integer>11780</integer> <key>c</key> <integer>10641</integer> <key>larson</key> <integer>10608</integer> <key>nautique</key> <integer>10278</integer> <key>hatteras</key> <integer>10270</integer> <key>stingray</key> <integer>10204</integer> <key>sylvan</key> <integer>10120</integer> <key>grand</key> <integer>9864</integer> <key>fox</key> <integer>9672</integer> <key>sportsman</key> <integer>9591</integer> <key>viking</key> <integer>9517</integer> <key>xpress</key> <integer>9257</integer> <key>avalon</key> <integer>9037</integer> <key>line</key> <integer>8788</integer> <key>tidewater</key> <integer>8261</integer> <key>crest</key> <integer>8255</integer> <key>ocean</key> <integer>8179</integer> <key>sealine</key> <integer>8122</integer> <key>flotebote</key> <integer>8048</integer> <key>sports</key> <integer>7974</integer> <key>harbor</key> <integer>7737</integer> <key>south</key> <integer>7722</integer> <key>cc</key> <integer>7582</integer> <key>premier</key> <integer>7566</integer> <key>bertram</key> <integer>7554</integer> <key>polar</key> <integer>7424</integer> <key>cobia</key> <integer>7400</integer> <key>dufour</key> <integer>7332</integer> <key>mainship</key> <integer>7295</integer> <key>proline</key> <integer>7131</integer> <key>cranchi</key> <integer>7124</integer> <key>j</key> <integer>7100</integer> <key>axis</key> <integer>6949</integer> <key>baja</key> <integer>6889</integer> <key>pontoons</key> <integer>6860</integer> <key>banks</key> <integer>6834</integer> <key>kraft</key> <integer>6812</integer> <key>ferretti</key> <integer>6801</integer> <key>waverunner</key> <integer>6795</integer> <key>manitou</key> <integer>6730</integer> <key>luhrs</key> <integer>6574</integer> <key>parker</key> <integer>6534</integer> <key>hydra</key> <integer>6384</integer> <key>boat</key> <integer>6244</integer> <key>contender</key> <integer>6160</integer> <key>everglades</key> <integer>6110</integer> <key>cat</key> <integer>6107</integer> <key>fountain</key> <integer>6051</integer> <key>lagoon</key> <integer>5989</integer> <key>hydrasports</key> <integer>5983</integer> <key>moomba</key> <integer>5961</integer> <key>island</key> <integer>5874</integer> <key>cay</key> <integer>5867</integer> <key>cypress</key> <integer>5864</integer> <key>pearson</key> <integer>5753</integer> <key>sport</key> <integer>5653</integer> <key>zodiac</key> <integer>5427</integer> <key>regulator</key> <integer>5409</integer> <key>hallberg</key> <integer>5396</integer> <key>rassy</key> <integer>5391</integer> <key>century</key> <integer>5374</integer> <key>sailfish</key> <integer>5221</integer> <key>cape</key> <integer>5073</integer> <key>scarab</key> <integer>4919</integer> <key>edgewater</key> <integer>4915</integer> <key>donzi</key> <integer>4841</integer> <key>seaswirl</key> <integer>4799</integer> <key>hallbergrassy</key> <integer>4774</integer> <key>riva</key> <integer>4565</integer> <key>regency</key> <integer>4536</integer> <key>trojan</key> <integer>4493</integer> <key>supra</key> <integer>4461</integer> <key>hanse</key> <integer>4400</integer> <key>wave</key> <integer>4397</integer> <key>centurion</key> <integer>4385</integer> <key>pershing</key> <integer>4363</integer> <key>sabre</key> <integer>4270</integer> <key>blue</key> <integer>4224</integer> <key>misty</key> <integer>4206</integer> <key>pathfinder</key> <integer>4177</integer> <key>riviera</key> <integer>4042</integer> <key>stratos</key> <integer>4015</integer> <key>meridian</key> <integer>3986</integer> <key>trophy</key> <integer>3945</integer> <key>aqua</key> <integer>3799</integer> <key>sessa</key> <integer>3761</integer> <key>packet</key> <integer>3739</integer> <key>smoker</key> <integer>3734</integer> <key>bentley</key> <integer>3686</integer> <key>intrepid</key> <integer>3564</integer> <key>albin</key> <integer>3533</integer> <key>pajot</key> <integer>3498</integer> <key>moody</key> <integer>3496</integer> <key>fisher</key> <integer>3458</integer> <key>patio</key> <integer>3450</integer> <key>fountaine</key> <integer>3445</integer> <key>cabo</key> <integer>3416</integer> <key>westerly</key> <integer>3368</integer> <key>yacht</key> <integer>3306</integer> <key>quicksilver</key> <integer>3285</integer> <key>sanlorenzo</key> <integer>3283</integer> <key>world</key> <integer>3260</integer> <key>tartan</key> <integer>3249</integer> <key>seaark</key> <integer>3228</integer> <key>phoenix</key> <integer>3194</integer> <key>mercury</key> <integer>3158</integer> <key>dory</key> <integer>3144</integer> <key>morgan</key> <integer>3100</integer> <key>doral</key> <integer>3067</integer> <key>cantieri</key> <integer>3035</integer> <key>inflatables</key> <integer>2984</integer> <key>x</key> <integer>2972</integer> <key>dehler</key> <integer>2954</integer> <key>classic</key> <integer>2909</integer> <key>seacraft</key> <integer>2904</integer> <key>ericson</key> <integer>2901</integer> <key>correct</key> <integer>2893</integer> <key>suncatcher</key> <integer>2869</integer> <key>o</key> <integer>2855</integer> <key>tollycraft</key> <integer>2851</integer> <key>tugs</key> <integer>2827</integer> <key>berkshire</key> <integer>2805</integer> <key>day</key> <integer>2801</integer> <key>aquasport</key> <integer>2800</integer> <key>oday</key> <integer>2764</integer> <key>caravelle</key> <integer>2727</integer> <key>albemarle</key> <integer>2715</integer> <key>elan</key> <integer>2653</integer> <key>pioneer</key> <integer>2644</integer> <key>pacific</key> <integer>2593</integer> <key>alexander</key> <integer>2588</integer> <key>barletta</key> <integer>2579</integer> <key>eagle</key> <integer>2528</integer> <key>prestige</key> <integer>2512</integer> <key>s</key> <integer>2504</integer> <key>sunchaser</key> <integer>2494</integer> <key>chaser</key> <integer>2413</integer> <key>xyachts</key> <integer>2394</integer> <key>blackfin</key> <integer>2386</integer> <key>angler</key> <integer>2371</integer> <key>striper</key> <integer>2355</integer> <key>north</key> <integer>2324</integer> <key>trader</key> <integer>2306</integer> <key>mariah</key> <integer>2297</integer> <key>rodman</key> <integer>2281</integer> <key>egg</key> <integer>2275</integer> <key>hewescraft</key> <integer>2262</integer> <key>cal</key> <integer>2229</integer> <key>hinckley</key> <integer>2217</integer> <key>yellowfin</key> <integer>2207</integer> <key>ab</key> <integer>2199</integer> <key>godfrey</key> <integer>2193</integer> <key>bass</key> <integer>2189</integer> <key>apex</key> <integer>2121</integer> <key>jc</key> <integer>2104</integer> <key>war</key> <integer>2084</integer> <key>shamrock</key> <integer>2064</integer> <key>majek</key> <integer>2057</integer> <key>najad</key> <integer>2040</integer> <key>veranda</key> <integer>2039</integer> <key>2</key> <integer>2038</integer> <key>nautor</key> <integer>2031</integer> <key>pontoon</key> <integer>2018</integer> <key>nordic</key> <integer>2014</integer> <key>jupiter</key> <integer>2010</integer> <key>triumph</key> <integer>1999</integer> <key>ebbtide</key> <integer>1998</integer> <key>van</key> <integer>1997</integer> <key>bryant</key> <integer>1988</integer> <key>astondoa</key> <integer>1954</integer> <key>glacier</key> <integer>1948</integer> <key>kawasaki</key> <integer>1936</integer> <key>cove</key> <integer>1935</integer> <key>gibson</key> <integer>1932</integer> <key>sanpan</key> <integer>1932</integer> <key>excel</key> <integer>1930</integer> <key>soleil</key> <integer>1915</integer> <key>mirrocraft</key> <integer>1913</integer> <key>islander</key> <integer>1900</integer> <key>bristol</key> <integer>1890</integer> <key>mb</key> <integer>1883</integer> <key>sundance</key> <integer>1879</integer> <key>irwin</key> <integer>1864</integer> <key>allmand</key> <integer>1838</integer> <key>river</key> <integer>1814</integer> <key>gulfstar</key> <integer>1800</integer> <key>motor</key> <integer>1797</integer> <key>qwest</key> <integer>1794</integer> <key>vee</key> <integer>1790</integer> <key>suncruiser</key> <integer>1786</integer> <key>de</key> <integer>1782</integer> <key>leopard</key> <integer>1772</integer> <key>largo</key> <integer>1765</integer> <key>uniflite</key> <integer>1760</integer> <key>macgregor</key> <integer>1758</integer> <key>bluewater</key> <integer>1749</integer> <key>lee</key> <integer>1735</integer> <key>nimbus</key> <integer>1732</integer> <key>master</key> <integer>1728</integer> <key>galeon</key> <integer>1698</integer> <key>cheoy</key> <integer>1679</integer> <key>horn</key> <integer>1674</integer> <key>stamas</key> <integer>1647</integer> <key>californian</key> <integer>1641</integer> <key>tayana</key> <integer>1638</integer> <key>inc</key> <integer>1637</integer> <key>endeavour</key> <integer>1630</integer> <key>sportcraft</key> <integer>1622</integer> <key>rampage</key> <integer>1611</integer> <key>jet</key> <integer>1596</integer> <key>legend</key> <integer>1587</integer> <key>atlantis</key> <integer>1574</integer> <key>back</key> <integer>1536</integer> <key>epic</key> <integer>1533</integer> <key>beach</key> <integer>1525</integer> <key>jefferson</key> <integer>1520</integer> <key>cruiser</key> <integer>1517</integer> <key>cigarette</key> <integer>1515</integer> <key>shearwater</key> <integer>1499</integer> <key>benetti</key> <integer>1495</integer> <key>sanger</key> <integer>1466</integer> <key>hobie</key> <integer>1462</integer> <key>palm</key> <integer>1456</integer> <key>rio</key> <integer>1456</integer> </dict> <key>condition</key> <dict> <key>Used</key> <integer>1865397</integer> <key>New</key> <integer>1169545</integer> <key>Other</key> <integer>5647</integer> </dict> <key>radius</key> <dict> <key>radius<10kilometer</key> <integer>0</integer> <key>radius<200kilometer</key> <integer>69236</integer> <key>radius<300kilometer</key> <integer>104457</integer> <key>radius>300kilometer</key> <integer>1613828</integer> </dict> <key>length</key> <dict> <key>length<10meter</key> <integer>2267466</integer> <key>length10-20meter</key> <integer>693359</integer> <key>length>20meter</key> <integer>76922</integer> </dict> </dict> </dict> </plist>
wangszoo / Insulator DetectionDetection and missing positioning of high voltage insulators in aerial images
masoudshab / Smart Monitoring Of Deformations On Transformers Using Image Processing And UWB TransceiversIn this paper, a novel method based on image processing is proposed for detecting the presence and location of mechanical deformations on an actual power transformer winding. A vertical imaging setup is used to obtain a two-dimensional (2-D) image of the transformer winding using synthetic aperture radar (SAR) imaging method and Kirchhoff migration algorithm. The main goal of the image processing method is to detect the location of the radial deformation on the transformer high-voltage (HV) winding. Two different deformations are applied on the winding under the test in this paper. The first one is a modeled bulgymechanical deformation and the second one is an actual concave buckling made on the actual transformer HV winding. The experimental results for different cases show the effectiveness of the proposed method to detect the presence and location of the deformation on the transformer winding.
BholaHrishikesh / Psychic Rotary PhoneIf you like this build I’ve also written other posts on building a simple voice controlled Magic Mirror with the Raspberry Pi and the AIY Projects Voice Kit, and a face-tracking cyborg dinosaur called “Do-you-think-he-saurs” with the Raspberry Pi and the AIY Projects Vision Kit. At the tail end of last month, just ahead of the announcement of the pre-order availability of the new Google AIY Project Voice Kit, I finally decided to take the kit I’d managed to pick up with issue 57 of the MagPi out of its box, and put it together. However inspired by the 1986 Google Pi Intercom build put together Martin Mander, ever since I’ve been thinking about venturing beyond the cardboard box and building my own retro-computing enclosure around the Voice Kit. I was initially thinking about using an old radio until I came across the GPO 746 Rotary Telephone. This is a modern day replica of what must be the most iconic rotary dial phone in the United Kingdom. This is the phone that sat on everybody’s desk, and in their front halls, throughout the 1970’s. It was the standard rental phone, right up until British Telecom was privatised in the middle of the 1980's. The GPO 746 Rotary Telephone. While the GPO 746 is available in the United States it’s half the price, and there are a lot more colours to choose from, if you’re buying the phone in the United Kingdom. A definite business opportunity for someone there because it turns out that, on the inside, it’s a rather interesting bit of hardware. Gathering your Tools For this project you’ll need is a small Philips “00” watch maker’s screwdriver, a craft knife, scissors, a set of small wire snips, a drill and a 2 to 4mm bit, a soldering iron, solder, some jumper wires, female header blocks, a couple of LEDs, some electrical tape, a cable tie, and possibly some Sugru and heat shrink tubing, depending how neat you want to be about things. While I did end up soldering a few things during the build, it is was mostly restricted to joining wires together and should definitely be approachable for beginners. Opening the Box Ahead of the new Voice Kit hitting the shelves next month I managed to get my hands on a few pre-production kits, which fortunately meant that I didn’t have to take my cardboard box apart to put together a new build. The new AIY Project Voice Kit. The new AIY Voice Kit comes comes in a box very similar to the original kit distributed with the Mag Pi magazine. The box might be a bit thinner, but otherwise things look much the same. Missing from my pre-production kits the two little plastic spacers that keep the Voice HAT from bending down and hitting the top of the Raspberry Pi. I’m presuming they’ll include them in the production kits, without them the underside of the HAT tends to push downwards and the solder tails of the speaker screw terminal shorts out against the Raspberry Pi’s HDMI connector. I fixed this by adding some electrical tape to separate the two boards, but the spacers would have worked a lot better and added more stability. The only component swap was the arcade button, gone was the separate lamp, holder, microswitch and button—all four components have been replaced by a single button with everything integrated. Since it was somewhat fiddly to get that assembled last time, this is a definite improvement. While my pre-production kits didn’t include it, I’m told the retail version will have a copy of the MagPi Essentials AIY Projects book written by Lucy Hattersley on how to “Create a Voice Kit with your Raspberry Pi.” Other than that, things went together much as before. At which point I quickly put together the Voice Kit, this time however, I didn’t bother with the cardboard box. Opening the Phone Pulling the replica GPO 746 out of its box you’ll find it comes in two parts, the main phone with the dial, and a separate handset which plugs in underneath the base. The first thing I needed to do was take the base unit of the phone apart and figure out how it worked. Until I knew what I had to work with, it was going to be impossible to figure out a sensible plan to integrate the Voice Kit. Opening up the GPO 746. The main PCB is mounted on the base along with a steel weight to give the impression of “heft” to the replica phone. There’s also a large bell, which makes that distinctive ringing noise familiar to anyone that owned or used a GPO 746 back in the 1970's. The circuitry attached to the base of the GPO 746. To the left of the PCB is the jack socket where the telephone line is connected (two wires, red and green). To the top, two switches. One is for handset, and the other for ringer, volume. At the bottom another jack switch (four wires, red, black, yellow, and green) where the handset is attached. The only thing of real interest on the PCB is the Hualon Microelectronics HM9102D which is a switchable tone/pulse dialer chip, which we’re actually not going to use. In fact, since the line voltage in the UK is +50V, pretty much none of it was going to be any use to me. So after measuring the voltage on the cable connecting the dialer to the PCB, I snipped the wires to the switches and the jacks—leaving them in place with as much trailing wire as possible in case they were going to come in useful,—and then removed both the PCB and the bell. After that, I filed down the plastic moulding that held everything in place leaving me with a large flat area which was perfectly sized for the Raspberry Pi and the Voice HAT. The moulded top of the phone has two assemblies, a simple microswitch toggled using a hinged and sprung plastic plate when the phone handset is taken on and off the hook, and the dialer assembly which is connected to the base and the PCB using a ribbon cable. How the Dialer Works It was time to break out the logic analyser. While I’ve got a Saleae Logic Pro 16 on my desk, if you’re thinking about picking one up for the first time I’d really recommend the much cheaper Logic 8, or even the lower specification Logic 4, rather than splashing out on the higher end model. Either will take you a long way before you get the itch that you have to upgrade. Logic Analyser attached to the dial of the GPO 746 powered up using a Bench Power Supply. Stripping the connector from the cable that connected the dialer to the PCB and powering it up with a bench power supply to +5V—which is more-or-less what I’d measured on the cable and was something I could reasonably expect to get from the Raspberry Pi—I connected the rest of the cables to my logic analyser and started turning the dial confidently expecting to see something interesting going on. I found nothing, I had flat lines, there was no signal going down the wires at all. After playing around with the voltage for a few minutes, with no results, I stripped the dialer assembly out of the case for a closer look. Dialer assembly removed from the GPO 746. The back of the dialer assembly has two LEDs, which I thought was rather odd since there dial isn’t illuminated in any way, at least not from the outside. Interestingly these two LEDs flash briefly when the dial is turned all the way around to hit the stop. Cracking the case brings us to something else interesting, it’s a light box. Designed to keep the light from the LEDs inside, it has a hole which rotates around as you dial a number. Taking apart the dial assembly. The hole exposes one of twelve photoresistors to the light from the LEDs and the number (or symbol) you’re dialing determines which of the resistors will be under the hole when the dial stop is reached. The photoresistors inside the dial assembly. It was all passive circuitry. No wonder I hadn’t seen anything on the logic analyser, there wasn’t any logic to analyse. It was all analogue. Unfortunately for me, the Raspberry Pi has no built in analogue inputs. That means I’d have to pull a Microchip MCP3008, or something similar, from the shelf and build some circuitry. I’d also have to figure out how the resistance for twelve photoresistors ended up travelling down just eight wires, which sort of had me puzzled at this point. That all sounded like a lot of effort. Since I really only wanted to dial a single digit to activate the Voice Kit, and I didn’t care what that was, I decided to ignore the photoresistors and concentrate on the dial stop. The dialer mechanism showing the back of the dial stop (left) with microswitch. Unlike the original GPO 746, the dial stop on this replica moves. It drops when you hit it with the side of your finger when dialling a number. It turned out that it was connected to a microswitch, and when the microswitch was activated, this was the thing that briefly flashed the LEDs and exposed the appropriate photoresistor. It was actually all rather clever. A really neat way to minimise the build of materials costs for the phone. Startups thinking about building hardware could learn a lesson or two in economy from this phone. Using the logic analyser on the microswitch. Just to be sure I had this right, I dialled down the bench power supply to a Raspberry Pi friendly +3.3V and wired up the microswitch to the logic analyser. Applying +3.3V (middle trace) and “dialing” shows the microswitch toggling (lower trace). Dialling a number on the dialer assembly worked as expected. We could ignore the dial itself, and those photoresistors that would be a pain to use with the Raspberry Pi and just make use of the microswitch. In fact we could more-or-less just replace the arcade button with this switch. Integrating the AIY Project Kit Moving on, I really wanted to reuse both the speaker and the microphone already in the handset instead of the ones the came with the Voice Kit. Handset stripped of its speaker and micrphone, Taking apart the handset—the end caps holding the speaker and microphone just screw off—showed that there were four wires inside the curled cable. Two for the speaker, and two for the electret condenser microphone. The Voice Kit makes use of two InvenSense ICS-43434 MEMS microphones which use I2S to communicate. They’re a solid replacement for traditional 2-wire analog microphones like the one we in the handset of the GPO 746. The Voice HAT Microphone daughter board. Looking at the Voice HAT microphone daughter board, it has been designed so that you can break the two microphones away from the board at the perforations and then you can solder the wiring harness directly to the pads. So long as you keep the signals consistent you should be able to place the mics pretty much anywhere, and with a clock rate of ~3MHz, a longer cable should be fine. Unfortunately I2S uses more wires than I had available. Unless I wanted to replace the curled cable, and I didn’t really want to have to do that, I was in trouble. Putting that aside for a moment I decided to start with the dialer assembly. Refitting it to the case, I snipped the wires leading to the microswitch and, grabbing the wiring harness for the arcade button, I soldered the microswitch to the relevant wires in the harness. Soldering the Voice HAT button wiring harness to the phone’s microswitch. I then grabbed a ultra-bright LED and a 220Ω resistor from the shelves and soldered the resistor in-line with the LED. I then attached my new LED assembly to the other two wires in the arcade button wiring harness. At this point I had a replacement for the arcade button that came with the Voice Kit. Attaching a current limiting resistor to my LED. Giving up on putting microphones into the handset I pulled out a drill and measuring the spacing between the two microphones I drilled a couple of holes in the external shell of the phone. Drilling two holes in the shell of the phone. These weren’t going to be visible from the outside as there is a void between the top of the phone, where the handset rests. This is a carrying handle where you can tuck your hand in, and pick up the phone. In the old days this let you pick up the phone and wander around the room—well, so long as the cable tying you to the wall was long enough. Attaching the Voice HAT microphone board to the phone shell. I then went ahead and tucked the microphone board behind the spring which operated the hook mechanism. There was just enough room to secure it there with a cable tie, and some Sugru. After that I plugged the handset into the jack on the base and connected the two wires from the handset jack that were attached to the speaker to the screw terminals on the Voice HAT. The re-wired internals of the modified GPO 746. Microphone board and Voice Kit both fixed in place with Sugru. Stripping the jack out where the phone line originally ran left two upright pillars that used to go on either side of the jack. I threaded the end of a 2.5A micro-USB charger through the hole and tied it around the pillars for strain relief. Which completed the re-wiring. The arcade button had been replaced with the dial stop microswitch and an LED which I was going to tuck just ahead of the microphone board in a convenient clip-like part of the body moulding. The speaker had been swapped out directly with the one in the handset—fortunately the impedance match wasn’t too far off—and the microphone had been mounted somewhere convenient inside the main body of the phone. A Working Phone Screwing everything back together we have once again something that looks like a phone. The assembled phone. I booted the Raspberry Pi, logged in via SSH and went ahead and ran the src/assistant_library_with_button_demo.py script from the dev console. A working build, but it’s not quite there yet. Success. Picking up the handset and dialling a number, any number, let you talk to the Voice Assistant. But it wasn’t quite there yet. While it worked, it didn’t feel like a phone. Adding a Dial Tone What the phone needed was a dial tone. It needed to play when the handset was lifted and shut off when the phone was dialled, or the handset replaced. The phone hook works the opposite way that you might expect, when the handset is in the cradle the microswitch that simulates the hook is open as the bar below it is pushed down by the hook. When the handset is off the hook, then the microswitch is closed as the bar moves upwards. Conveniently the Voice HAT breaks out most of the unused GPIO pins from the Raspberry Pi, so at least in theory wiring the the microswitch attached to the the hook mechanism to one to the Voice HAT should be fairly simple. Available unpopulated connectors on the Voice HAT. (Image credit: Google) Thinking about how to approach this in software however left us with a bit of a quandary. While the underlying Python GPIO library allows us to detect both the rising and falling edge events when a switch is toggled, the AIY wrapper code doesn’t in the Voice Kit doesn’t. While I could have gone in and modified the wrapper code to add that functionality, I decided I didn’t want to mess around with that—perhaps I’ll get around to it later and send them a pull request—instead I decided to fix it in hardware and wire the hook switch into both GPIO4 and GPIO17. That way I could use one pin to monitor for GPIO.RISING, and the other for GPIO.FALLING. Wiring up the phone hook. It’s easy enough to do that using the aiy._drivers._button.Button class, and two callback methods. One called with the handset is taken off the hook, and the other called with it is replaced. All the additional wiring in place and working. We can then use the pygame library to play a WAV file in the background when the handset is lifted, and stop when it is replaced. We also have to add a stop command inside the _on_button_pressed() method so that the dial tone stops when the phone is dialled, and a call to stop_conversation() to stop the Voice Assistant talking if the handset is returned on hook while Google is answering our question. Adding a Greeting and a Hang Up Noise We’re not quite there yet, we can also use aiy.audio.play_wave() to add that distinctive disconnect noise when Google finishes talking and “hangs up” before returning to our dial tone. We can also use aiy.audio.say(‘…’) call to add a greeting when Google “picks up” the phone to talk to us. The final build. It’s surprising how much atmosphere just adding these simple sounds ended up making to the build, and how much the user experience was improved. It now doesn’t just look like a rotary phone, it sort of feels, and perhaps more importantly, sounds like one too. The Script The final version of the script has amazingly small number of modifications away from the original version distributed byGoogle. Which sort of shows how simple it is to build something that looks and feels very different from the original cardboard box with not a lot of effort, at least on the software If you want to replicate the build you can grab the two mono WAV files I used for the build from Dropbox. Although, if you’re outside the the United Kingdom, you might want to replace the standard British dial tone of 350Hz and 450Hz—which you hear any time you lift a phone off the hook—with something more appropriate. Available to Preorder The new kits are being produced by Google, and are available to pre-order at Micro Center and through their resellers like Adafruit, and SeeedStudio. The AIY Voice Kit is priced at $25 on its own, but you can pick one up for free if you order a Raspberry Pi 3 at $35 for in-store pickup from Micro Center. My new retro rotary phone build next to my original Voice Kit. The kit will be available in the United Kingdom through Pimoroni, and cost £25, and you can expect shipping dates for kits ordered in through them to be similar to those ordered from Micro Center.
