Mindstorm nxt module programing guide trouble

hi there,
I have some trouble with the 'Labview mindstorms NXT Module programming guide'.
I develop an application on labview 2009 and i want to acces some properties like 'Overload and ActualSpeed' but i don't found anywhere in this guide how to acces to those propertie. btw i try to use some module in the toolkit like 'set output state' and 'get output state' in the NXT Direct I/O section but those properties are unable to found. When i open the vi called by those module, i see they called vi named 'Fantom'. All those vi are in driver folder. i try to search some help about this drivers but i find nothing.
If anyone can help me ;p
thanks

I Romain,
thank to
try helping me.
I'll be
more precise this time.
The guide I
use is this one: http://www.ni.com/pdf/manuals/372574c.pdf
The
properties i want to access is in use with the NXTInput and NXTOutput refnum.
I find how
to access to this refnum and how to see the propertie i want with the propertie
node in the Application Control palette.
But now i
don't know how to use this refnum and the propertie node with the other objet
of the toolkit
To be more
precise i want to create an object like those existant in NXT Direct I/O
palette, so i don't know how to create an ‘NXT Object’ or to scan, detect The
NXT Brick and create an nxt object like they do the object ‘FIND NXT’ and ‘CREATE
NXT OBJECT’ to implement the flow.
If i can do that, i'll really can create an object I can use
with the toolkit.
If you have
a solution or an exemple for me it’ll be fine because I find nothing.
(I hope you
understood me, cause I’m French and I think my English is not perfect )
Regards

Similar Messages

  • Need assistance installing MindStorm NXT module on my desktop with Win XP and also my laptop which runs Win 7, software does not want to install?

    I need assistance to install LabView MindStorm NXT module in a Desktop system with Win XP and a Laptop with Win7. Both are 32 bit with all service packs applied. I purchased the academic version from a company called On-The-Hub.
    Attempted to install but seems to reject my serial number?

    Hi Rob,
    Thats really strange because the NXT Module 2010 and the NXT Module 2011 are free and don't require serial numbers. Where did you obtain the installer? The core LabVIEW installer requires a serial number but if you already have that installed, the NXT Module is just a free addon. Here are the links to the module for LabVIEW 2010 & 2011
    NXT Module 2011 : http://joule.ni.com/nidu/cds/view/p/id/2637/lang/e​n
    NXT Module 2010: http://joule.ni.com/nidu/cds/view/p/id/2551/lang/e​n

  • NI LabVIEW 2009 LEGO MINDSTORMS NXT Module Released!

    This software allows users to run code on their computers to control LEGO® NXT Bricks and compile, download, and run LabVIEW code directly to the NXT.  The new NXT Module 2009 represents a considerable improvement in features and usability over past versions.
    Totally redesigned APIs
    Full access to LabVIEW debugging tools
    Control NXT bricks either by running code in LabVIEW or compiling and deploying code to the NXT brick
    VIs for TETRIX kits are available out of the box
    Support for all LEGO® MINDSTORMS NXT 2.0 sensors.
    NXT Applications  Data Viewer, Piano Player, NXT Multimeter, Remote Control, and Scope
    The module can be downloaded here. 
    Please feel free to ask questions and provide feedback to NI R&D.
    Thanks,
    Mark
    Product Support Engineer - LabVIEW R&D
    Mark
    LabVIEW R&D

    Nice! But I guess that doesn't mean that you will be releasing a free version any time soon... does it. 
    Oh! BTW (slightly off topic) you should remove the "Select Your Operating System" block on the Student edition cd order form. It just gets peoples hopes up that they might get a mac version. 
    Andrew 
    Message Edited by AndrewDudney on 10-22-2009 10:27 PM

  • Updated LV NXT programming guide?

    I see that there exists the "LabVIEW Lego Mindstorms NXT Module Programming Guide" for 2009.  Does anyone know if there is a comprable manual with maybe a different title for LabVIEW 2013?  Among other things I'm hopping for a complete list of Direct Mode Commands.  I am not sure if I've upgraded/updated properly.  I was expecting to see in my Direct Mode Pallet:  "Creat NXT Object" and "Destroy NXT Object".  Are these still part of the newer versions of LV NXT pallets?
    Thank you for looking at my post
    Solved!
    Go to Solution.

    Hi dunnor,
    Your best bet for getting code executing correctly the first time is starting from one of the examples in the Example Finder. Please note that all those examples will work for NXT or EV3.
    I wrote a program to find direct mode VIs, and found 176 direct mode VIs from the palettes. The palettes are logically organized in a way that is probably more instructive than this list. I doubt this is exactly what you're looking for, but I am just trying to be as helpful as I can be, recognizing that the documentation for the module is lean. The most thorough and up to date documentation is the context help. Open the context help window using ctrl+H, and hover over a subVI or palette item to get a detailed description of its usage.
    Attached is the program that creates a list of direct mode VIs available to you, along with VI description and icon. You can find the VIs by VI name using search (ctrl+s) or quick drop (ctrl+.), or navigate to them using the palettes. The VI takes a couple minutes to run.
    If you encounter any difficulties in your project, do not hesitate to post them here. 
    Attachments:
    Complete List of Direct Mode VIs.vi ‏31 KB

  • Labview 2009 Module Mobile And Lego Mindstorms NXT

    Hi
    I've installed the mobile toolkit in labview 2009 but when I created a new mobile project I didn't find the NXT Programmings category on menu.....
    are they not supported?
    I would like to control my nxt with my PDA through bluetooth.
    Thanks in advance for help 

    Hi,
    which NXT software did you exacly installed? LabVIEW Module for LEGO MINDSTORMS NXT or LabVIEW Toolkit?
    I would like to be sure to have corretcly understood: in a mobile project, the function palette of a VI under a PDA target does not have the NXT palette, correct?
    Bye!
    Licia

  • MythTV Program Guide Slow/No Composite Effects On Dual Monitor

    Hello all,
    I am not entirely sure where this would belong, so I put it here.
    I am running Arch64 with an NVidia 8600GTS and dual monitors as seperate X screens. The second monitor is actually a TV not a monitor, and is using the S-Video output on the video card, but I'm not sure that that's relevant at all.
    On my primary monitor the program guide in MythTV runs fairly decent, however on the TV it runs unbearably slow. Pushing up on the remote a time or two will take a minute or so to happen. I have it set to the least demanding level possible.
    I originally thought that this was just a MythTV issue but I noticed that XCompmgr and Compiz-Fusion effects do not work at all on the TV either, so I think these issues are related.
    Also, I do not currently have a composite window manager installed, I am using Gnome with Metacity.
    Here is a copy of my xorg.conf:
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder62) Tue Jan 6 09:44:34 PST 2009
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder62) Tue Jan 6 09:43:54 PST 2009
    # Auto-generated by Archie mkxcfg
    # Auto-generated by Archie mkxcfg
    Section "ServerLayout"
    # Serial Mouse not detected
    # USB Mouse not detected
    Identifier "Xorg Configured"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "PS/2 Mouse" "CorePointer"
    EndSection
    Section "Files"
    # Additional fonts: Locale, Gimp, TTF...
    # FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
    # FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    FontPath "/usr/share/fonts/cyrillic"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    # Load "synaptics"
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    Option "AutoAddDevices" "False"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    Section "Monitor"
    # Warning: This may fry old Monitors
    # Very conservative. May flicker.
    # VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -hsync +vsync
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -hsync +vsync
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -hsync +vsync
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -hsync +vsync
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -hsync +vsync
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -hsync +vsync
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -hsync +vsync
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
    Option "DPMS" "true"
    # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 55.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "All"
    BoardName "All"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 16
    Option "TwinView" "0"
    Option "metamodes" "DFP: 1680x1050 +0+0; DFP: 800x600 +0+0; DFP: 640x480 +0+0"
    SubSection "Display"
    Depth 16
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 16
    Option "TVStandard" "NTSC-M"
    Option "TVOutFormat" "SVIDEO"
    Option "TwinView" "0"
    Option "metamodes" "TV: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 16
    EndSubSection
    EndSection
    It's a bit of a mess at the moment. Last time I reinstalled I was having trouble with the keyboard and mouse not working in Gnome, so I've been hesitant to mess with it too much.
    On my previous install my xorg.conf looked like this:
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder58) Wed Oct 1 15:13:37 PDT 2008
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jul 17 18:39:00 PDT 2008
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    # RgbPath "/usr/lib/X11/rgb"
    EndSection
    Section "Module"
    Load "dbe"
    Load "extmod"
    # Load "type1"
    Load "freetype"
    Load "glx"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "keyboard"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    # Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "RenderAccel" "True"
    Option "NoRenderExtension" "False"
    Option "AllowGLXWithComposite" "True"
    Option "XvmcUsesTextures" "True"
    Option "LoadKernelModule" "True"
    Option "DamageEvents" "True"
    # Option "LogoPath" "/home/theavataroftime/Pictures"
    Option "NoLogo" "True"
    Option "TwinView" "0"
    Option "metamodes" "DFP: 1680x1050 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "RenderAccel" "True"
    Option "NoRenderExtension" "False"
    Option "AllowGLXWithComposite" "True"
    Option "XvmcUsesTextures" "True"
    Option "LoadKernelModule" "True"
    Option "DamageEvents" "True"
    Option "LogoPath" "/home/theavataroftime/Pictures"
    Option "NoLogo" "True"
    Option "TVStandard" "NTSC-M"
    Option "TVOutFormat" "SVIDEO"
    Option "TwinView" "0"
    Option "metamodes" "TV: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER" "Enable"
    EndSection
    I had the same issues with composite managers and that MythTV guide using this xorg.conf too.
    Has anyone had any similar issues? I am at a total loss here, so any help is greatly appreciated. Thank you.

    No one else has had troubles with the program guide or composite effects on dual monitors?

  • Connecting LEGO mindstorms NXT to my computer

    I am trying to learn Labview using the LEGO mindstorms NXT robot. I installed Labview 2009 and started working, but when I open the NXT terminal in the NXT module it claims that the NXT is not connected although it is (via USB). Any ideas ? Could this have to do with the fact that I am using Windows Vista ?
    Thanks

    This article is intended to indicate the installation and configuration process between LabVIEW and educational robot Lego Mindstorms NXT wirelessly, this will enable LabVIEW developers in having a mobile platform for the development of projects and autonomous robots, we need to install some programs the computer:
    https://decibel.ni.com/content/docs/DOC-32448    
    Atom
    Certified LabVIEW Associate Developer

  • Download LabVIEW Code to NXT Module

    HI
    I want to know how to download a *.vi file to my NXT Lego Mindstorm Robot. I,ve tried to make a simple VI and it doesn't give me any errors but I can't find it on my NXT.
    Can someone take a look?
    There's three different kinds of people, those who can count, and those who can't.
    Attachments:
    Download.vi ‏15 KB

    Hi Klump The solution for your problem is very easy!  you only have to do this:
    1.  Open the LabVIEW VI you want to run on the NXT.
    2. Launch the NXT Terminal by selecting Tools»NXT Module»NXT Terminal. The VIs you currently have open automatically appear in the PC VI Files listbox.
    3. To connect the NXT Terminal to an NXT device, use one of the following options:
    • Plug in an NXT through USB and it will automatically connect.
    • Click the Find NXT button and choose an NXT connected through USB or scan for available NXTs using Bluetooth.
    4. After you connect the NXT Terminal to an NXT device, select the VI you want to run from the PC VI Files listbox, and use one of the following options.
    and that's all !!!!!  click in download and enjoy your program
    I don't know if you heve been tried to do this before but I have one problem with this.  when I download a program to the NXT the time is 5-8 minutes, I don't know what happend can anyone Help ME?
    thanks..   David

  • LabVIEW Toolkit for LEGO MINDSTORMS NXT bugs

    When you find bugs in the toolkit, post them to this message thread.
    This board will be regularly monitored by both NI Application Engineers and members of the development team.
    Thanks for helping us create a better toolkit going forward.
    John Field
    MINDSTORMS Software Group Manager
    LabVIEW R&D

    Hi John,
    Problem: Unsupported case structure values in NXT Toolkit VIs.
    I think the problem is, that the VIs of the NXT Toolkit do not follow the restrictions of the Programming Guide of the NXT Toolkit. The programming Guide says at page 6 (Structures, Case Structure) that
    “Only one specific value (or "Default) is allowed in the case selector lable for each subdiagram."
    But for example the "PortSemaphore.AccessSemaphores.vi", which is part of the NXT Toolkit (and which is a Sub VI of "NXT_SyncUnlimited.vi") uses a Case Structure with the values “0, Default”, “1”, and “2”. This is only one example. I found many VIs in the NXT Toolkit which are using case structures with more than one specific value or with a “0, Default” value.
    Why does the NXT Toolkit include VIs whitch are not programmed according to the Programming Guide of the NXT Toolkit?
    How can I solve the problem? Do I have to modify each NXT-Vi with incorrect case structure values?
    I am using LabVIEW 7.1 and NXT Firmware 10.3.
    Regards
    Manfred

  • System Identification and Transfer Function of the LEGO MINDSTORM NXT Robot

    Can anybody please help with the below question.
    Using your LabView interface, input different values of power and record the output value of the number of wheel rotations. You can convert the latter into speed by measuring the diameter of the wheel. Then, type ‘ident’ in the command line of Matlab to launch a graphical user interface for system identification. Using the data collected for input power and recorded speed, you can derive the transfer function for your robot in the Laplace domain.
    You will notice that it is possible to approximate the transfer function to a first order system.
    Add disturbance to your system such as wind drag, road profile or friction. You might want to model the disturbance as a sinusoidal waveform.
    Analyse the system response in LabView in order to tune the response.
    Finally, write a LabView program to test your controller.
    Set both Integral and Derivative to 0
    Increase the value for Proportional controller to 0.5, 0.8, 1, 1.1, 1.3, and 1.5
    Select a suitable simulation stop time.
    Compare each simulation results and draw some conclusions.
    Record the steady-state error. Has it dropped to near zero?
    Record the rise time. Has it decreased to less than 0.5 second? And for what values of Kp?
    Check whether this response is realistic i.e. a real cruise control system generally cannot change the speed of the vehicle from 0 to 10m/s in less than 0.5 second.
    Adjust the gain (Kp) to give a reasonable rise time and add an integral controller to eliminate the steady-state error.
    Change both Kp and Ki and see what happens to the response. When you adjust the integral gain Ki, start with a small value since a large Ki can destabilise the response. (Ki =0.001, 0.002, 0.003, 0.004).
    Then you need to adjust both the proportional gain Kp and the integral gain Ki to obtain the desired response. Record the values of Kp and Ki that can meet all the design criteria.
    Write the PID-feedback control LabVIEW program as described above.
    Does it work? Quantify! Show us it is working
    Hand in a short report on the PID project on the cruise control of the LEGO MINDSTORM NXT Robot. Your report should contain an introduction to cruise control and uses of PID controllers, a brief explanation of how PID feedback control works. The printout of the Block Diagram and Front Panel of your LabVIEW program should be attached at the end of your report.
    Put it all together. There are many questions that can be explored and written up in the result section. Be creative.
    Here are some things that may be addressed: Check whether your system can stabilise speed to within 1%. What are the optimal PID parameters that you have found? Can you choose PID parameters to both reach the set speed quickly and also maintain the speed within good accuracy once the system has reached the set speed? Can you control the speed of small steps? Explain your results?

    Thanks for that.
    DanHarryman wrote:
    HI ToolMonkey
    You should be able to build control system to do this using PID control VIs. The following paper is a good place to start when working with PID systems. 
    http://www.ni.com/white-paper/6440/en
    Let me know how you get on using some of the functions in this. 
    Thanks 
    Dan.H
    UKAE

  • Modlue programming guide!

    Need some help in module pool programming guide !

    Hi,
    MODULE POOL PROGRAMMING (MPP):
    These are type M programs in SAP.
    These programs cannot be executed directly.
    Transaction Codes (Tcodes) are used to execute MPP programs.
    Graphical Screen PAinter is the tool used to create GUI in MPP (SE51).
    MPP programs are created using the transaction code SE80.
    MPP programs should start with the naming convention SAPMZ or SAPMY.
    EVENTS ASSOCIATED WITH SELECTION-SCREEN:
    INITIALIZATION
    AT SELECTION-SCREEN
    START-OF-SELECTION
    TOP-OF-PAGE
    END-OF-PAGE
    END-OF-SELECTION.
    EVENTS ASSOCIATED WITH MPP:
    1. PROCESS BEFORE OUTPUT (PBO) - Used to specify initial attributes for the screen.
    2. PROCESS AFTER INPUT (PAI) - Used to specify
    event functionalities for the components of the screen.
    COMPONENTS OF MPP PROGRAM:
    1. ATTRIBUTES - It holds description about the screen.
    2. FLOW LOGIC - This is an editor for MPP programs to specify event functionality for the screen components.
    3. ELEMENT LIST - This provides description about the components created in the screen.
    TYPES OF SCREEN IN MPP:
    1. NORMAL SCREEN - A screen which has maximizing, minimizing and closing options
    is referred to as normal screen.
    2. SUBSCREEN - A screen within a normal screen with either of above three options
    is referred to as subscreen.
    3. MODAL DIALOG BOX - A screen with only closing option which is used to provide
    information to the end user is referred to as modal dialog box.
    NAVIGATIONS TO CREATE A SIMPLE MPP PROGRAM:
    SE80 -> Select Program from the dropdown list -> SPecify program name starting with SAPMZ or SAPMY (eg. SAPMYFIRSTMPP) -> Press Enter -> Click on Yes to Create object -> Opens another dialog box -> Click on Continue to create Top Include File for the program -> Opens another dialog box specifying TOP INCLUDE FILE name (MYFIRSTMPPTOP) -> Click on Continue -> Opens Program Attributes screen -> Enter short description -> The default program type is M -> Save under a package -> Assign Request number -> A folder with specified program name(SAPMYFIRSTMPP) is created with Top Include File.
    To create a screen, right click on program name -> Create -> SCreen -> Opens dialog box
    -> Specify Screen number (100) -> Continue -> Opens an interface -> Enter short description
    -> Select Screen type as Normal -> Click on LAYOUT pushbutton from appn. toolbar
    -> Opens Graphical Screen painter -> Drag and drop two input fields, two pushbuttons and
    two text fields -> Double click on each component to specify attributes as follows:
    INPUT FIELDS: IO1, IO2
    FIRST PUSHBUTTON : PB1, PRINT, PRINT
    SECOND PUSHBUTTON : PB2, EXIT, EXIT
    TEXT FIELDS : LB1 (ENTER NAME), LB2 (ENTER CITY)
    -> Save -> Click on Flowlogic Pushbutton from appn. toolbar -> Opens Flow Logic editor
    with two events (PA1 and PBO).
    To specify event functionalities for screen components,
    decomment PAI Module name (USER_COMMAND_0100)
    -> Double click on module name -> Click on Yes to create object -> Opens an interface
    -> Select Program name from the list -> Continue -> Click on Yes to save the editor
    -> Opens PAI module and specify following code:
    CASE SY-UCOMM.
    WHEN 'PRINT'.
    LEAVE TO LIST-PROCESSING.
    WRITE :/ IO1, IO2.
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    ENDCASE.
    In TOP INCLUDE FILE, declare input fields as follows:
    DATA : IO1(20), IO2(20).
    Save -> Activate -> Right click on Program name -> Activate (to activate all inactive objects).
    To execute MPP program, right click on program name -> Create -> Transaction
    -> Opens an interface -> Specify Tcode starting with Z or Y (zfirstmpp) -> Enter short description -> Continue -> Specify Main program name (SAPMYFIRSTMPP) and initial Screen number (100) -> Save under a package -> Assign a request number -> Execute.
    TOP INCLUDE FILE is an area to declare variables for the program, and the variables declared here becomes globally accessed.
    SCREEN VALIDATION USING MPP:
    SCREEN is a predefined structure used to make MPP screen validations dynamically. SCREEN has following components:
    GROUP1
    INVISIBLE
    REQUIRED
    INPUT
    OUTPUT
    INTENSIFIED
    IF SCREEN-INVISIBLE = 0 - Sets the input field values as visible.
       SCREEN-INVISIBLE = 1 - Sets the input field as password field.
       SCREEN-REQUIRED = 0 - Not a mandatory field.
       SCREEN-REQUIRED = 1 - Sets input field as mandatory one.
    Eg. code to perform validation dynamically for a login screen:
    1. Create an MPP program.
    2. Create a Normal Screen like initial login screen.
    3. Assign IO1, IO2 to group GR1, IO3 to GR2.
    4. In Top Include file, declare variables.
    5. In PBO, specify following code:
    LOOP AT SCREEN.
    IF SCREEN-GROUP1 = 'GR1'.
    SCREEN-REQUIRED = '1'.
    ENDIF.
    IF SCREEN-GROUP1 = 'GR2'.
    SCREEN-INVISIBLE = '1'.
    ENDIF.
    MODIFY SCREEN.  * to update the changes made to the predefined             structure.
    ENDLOOP.
    6. In PAI, specify following code:
    CASE SY-UCOMM.
    WHEN 'LOGIN'.
    CALL TRANSACTION 'SE38'.
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    ENDCASE.
    7. Create a Tcode -> Activate all -> Execute.
    INSERTING RECORDS FROM MPP SCREEN INTO DATABASE TABLE:
    1. Create an MPP program.
    2. In Top Include File, declare an internal table as follows:
         DATA IT_KNA1 LIKE KNA1 OCCURS 0 WITH HEADER LINE.
    -> Save -> Activate.
    3. Create a screen -> In Screen Painter, click DICTIONARY/PROGRAM FIELDS (F6)
    pushbutton from appn. toolbar -> Opens an interface
    -> Specify internal table name -> Click on GET FROM PROGRAM pushbutton
    -> Select required fields -> Continue -> Paste on Screen Painter
    -> Create two pushbuttons (INSERT, EXIT) -> Save -> Flow logic.
    4. In PAI, specify following code:
    CASE SY-UCOMM.
    WHEN 'INSERT'.
    INSERT INTO KNA1 VALUES IT_KNA1.
    IF SY-SUBRC = 0.
    MESSAGE S000(ZMSG).
    ELSE.
    MESSAGE W001(ZMSG).
    ENDIF.
    WHEN 'EXIT'.
    *LEAVE PROGRAM.
    SET SCREEN 0.
    ENDCASE.
    5. Create a Tcode -> Activate all -> Execute.
    LIST OF VALUES:
    Adding dropdown facility to the input fields is called as LIST OF VALUES.
    VRM is a predefined type group which has the following structure and internal table:
    VRM_VALUE is a structure with the components KEY and TEXT.
    VRM_VALUES is an internal table declared for the above structure without header line.
    The above type group is used to fetch values from the internal table declared with user-defined records and insert into the input field in the screen.
    'VRM_SET_VALUES' is a function module used to carry the records from the internal table and populate in the input field.
    NAVIGATIONS TO CREATE DROPDOWN FACILITY FOR INPUT BOX:
    1. Create MPP program.
    2. Create a screen.
    3. Add a input box -> Double click -> Specify name (IO1) -> Select LISTBOX from the dropdown list -> A dropdown facility is added for the input field in the screen.
    4. Create two pushbuttons (PRINT, EXIT).
    5. In Top Include File, specify following code:
    TYPE-POOLS VRM.
    DATA IO1(20).
    DATA A TYPE I.
    DATA ITAB TYPE VRM_VALUES. * To create an internal table of an existing type
    DATA WA LIKE LINE OF ITAB. * To create a temporary structure of sameline type of internal table.
    6. In PBO, specify following code:
    IF A = 0.
    WA-KEY = 'ABAP'.
    WA-TEXT = 'ADVANCED PROGRAMMING'.
    APPEND WA TO ITAB.
    WA-KEY = 'BW'.
    WA-TEXT = 'BUSINESS WAREHOUSING'.
    APPEND WA TO ITAB.
    WA-KEY = 'EP'.
    WA-TEXT = 'ENTERPRISE PORTAL'.
    APPEND WA TO ITAB.
    CALL FUNCTION 'VRM_SET_VALUES'
      EXPORTING
        ID                    =  'IO1'
        VALUES                =   ITAB.
    A = 1.
    ENDIF.
    7. In PAI, specify following:
    CASE SY-UCOMM.
    WHEN 'PRINT'.
    LEAVE TO LIST-PROCESSING.
    WRITE :/ IO1.
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    ENDCASE.
    8. Create a Tcode -> Activate all -> Execute.
    CREATING TABSTRIPS IN MPP:
    In a normal screen, we can add only maximum of 40 components.
    To make a screen hold more than 40 components, we can use tabstrip controls.
    NAVIGATIONS TO CREATE TABSTRIP CONTROL:
    1. Create an MPP program.
    2. Create a normal screen (100)
    -> Add Tabstrip Control component from toolbar
    -> By default, a tabstrip control is created with 2 tab buttons
    -> Double click on tabstrip control
    -> Specify name (TBSTR) in Attributes box
    -> Click on First tab button
    -> Add Subscreen Area from toolbar to first tab button
    -> Double click on subscreen area
    -> Specify name (SUB1)
    -> Click on Second tab button
    -> Repeat same process for adding subscreen area (SUB2)
    -> Double click on First tab button
    -> Specify attributes (TAB1,FIRST,TAB1)
    -> Double click on Second tab button
    -> Specify attributes (TAB2, SECOND, TAB2)
    -> SAve
    -> Flowlogic.
    3. Create two subscreens (10, 20) -> Add required components in each subscreen.
    4. In Top Include File, specify following code:
    DATA : IO1(10), IO2(10), IO3(10), IO4(10).
    CONTROLS TBSTR TYPE TABSTRIP.
    DATA A LIKE SY-DYNNR.
    'CONTROLS' statement is used to allocate a memory area for the tabstrip created in the normal screen. 'TABSTRIP' itself is a data type for the tabstrip control. Whenever a tabstrip is created, SAP creates an object called 'ACTIVETAB' which is used to call the corresponding subscreens for each tab button in PAI.
    5. In Flowlogic editor, write following code to initiate the subscreens to the corresponding subscreen areas of each tab button when the main screen is called:
    PROCESS BEFORE OUTPUT.
    MODULE STATUS_0100.
    CALL SUBSCREEN SUB1 INCLUDING 'SAPMZTABSTRIP' '10'.
    CALL SUBSCREEN SUB2 INCLUDING 'SAPMZTABSTRIP' '20'.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0100.
    CALL SUBSCREEN SUB1.
    CALL SUBSCREEN SUB2.
    6. In PAI, specify following code for click events on each tab button:
    CASE SY-UCOMM.
    WHEN 'TAB1'.
    A = '10'.             * calls specified subscreen during PAI     
    TBSTR-ACTIVETAB = 'TAB1'.  * makes entire tab button in active status
    WHEN 'TAB2'.
    A = '20'.
    TBSTR-ACTIVETAB = 'TAB2'.
    WHEN 'DISPLAY'.
    LEAVE TO LIST-PROCESSING.
    WRITE :/ IO1, IO2, IO3, IO4.
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    ENDCASE.
    7. Create a Tcode -> Activate all -> Execute.
    TABLE CONTROLS:
    Table Control component is used to view the internal table contents in the screen.
    Navigations to create Table control component:
    1. Create an MPP program.
    2. In Top include File, declare variables as follows:
    DATA ITAB LIKE KNA1 OCCURS 0 WITH HEADER LINE.
    DATA ITAB1 LIKE KNA1 OCCURS 0 WITH HEADER LINE.
    CONTROLS TBCL TYPE TABLEVIEW USING SCREEN 100.
    DATA CUR TYPE I VALUE 5.
    -> Save -> Activate.
    3. Create a Screen (100) -> Select Table control component from toolbar -> Double Click and specify name (TBCL) -> Press F6 and specify internal table name (ITAB) -> Select required fields -> Paste on the Table control -> To separate the fields, use Separators option in Table control Attributes -> Specify labels if necessary -> Create pushbuttons (FETCH, MODIFY, PRINT, EXIT) -> Save -> Flowlogic.
    4. In PAI module, specify following code:
    CASE SY-UCOMM.
    WHEN 'FETCH'.
    SELECT * FROM KNA1 INTO TABLE ITAB.
    TBCL-LINES = SY-DBCNT.  * To create Vertical Scrollbar
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    WHEN 'PRINT'.
    GET CURSOR LINE CUR.
    READ TABLE ITAB INDEX CUR.
    LEAVE TO LIST-PROCESSING.
    WRITE :/ ITAB-KUNNR, ITAB-NAME1, ITAB-ORT01, ITAB-LAND1.
    WHEN 'MODIFY'.
    LOOP AT ITAB1.
    MODIFY KNA1 FROM ITAB1.
    IF SY-SUBRC = 0.
    MESSAGE S002(ZMSG).
    ELSE.
    MESSAGE E003(ZMSG).
    ENDIF.
    ENDLOOP.
    SELECT * FROM KNA1 INTO TABLE ITAB.
    TBCL-LINES = SY-DBCNT.
    ENDCASE.
    5. In FlowLogic editor, specify following step loops:
    PROCESS BEFORE OUTPUT.
    MODULE STATUS_0100.
    LOOP AT ITAB CURSOR CUR WITH CONTROL TBCL.
    ENDLOOP.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0100.
    LOOP AT ITAB.
        MODULE NEW.     * New module to move records from ITAB to                 ITAB1. Double click on Module Name (New)                 to create a new one.
    ENDLOOP.
    6. Specify following code in the NEW module:
       MODULE NEW INPUT.
         APPEND ITAB TO ITAB1.
       ENDMODULE.                
    7. Create a Tcode -> Activate all -> Execute.
    USING TABLE CONTROL WIZARD:
    This is a predefined SAP-specific component to create table control using predefined navigations.
    1. Create an executable program (Z_TABLEWIZARD) in SE38 editor. Write the following code:
    CALL SCREEN 200.
    -> Save -> Activate.
    2. Goto SE51 -> Specify program name created earlier (Z_TABLEWIZARD) -> Specify Screen number (200) -> Layout -> Select Table Control (Wizard) component from toolbar -> Opens Table control Wizard -> Follow the navigations -> Save and Activate the table control.
    3. Execute the program (Z_TABLEWIZARD).
    Regards,
    Priya.

  • NI LabVIEW Toolkit for LEGO MINDSTORMS NXT

    Labview 7.1.0と一緒に、タイトルのtool kitを使って、
    LEGO MINDSTORMS NXTを動かそうとしているのですが、
    一括コンパイル、nxt tool kit 1.0.1 patchコピーを終え、
    "Getting Started with the LabVIEW toolkit for LEGO MINDSTORMS NXT"(添付)
    の最初の"Building a LabVIEW VI that Runs on the NXT"に従って、
    作成したVIをNXT上で動かそうとしたのですが、
    Debugボタンを押すと、コンパイル、ダウンロードまではうまくいくのですが、
    ダウンロードされたプログラムがNXT上で動作せず、動かそうとすると、
    NXT本体のディスプレイにFILE ERROR!と表示されます。
    NXTのバージョンは、1.03で、
    "LabVIEW Toolkit for LEGO® MINDSTORMS® NXT"を
    一括コンパイルした際には、次のようなメッセージが表示されました。
    #### Starting Mass Compile: 2008年7月2日 18:41:42
      Directory: "C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons"
    Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.GetRelevantContexts_8_0.vi)
    Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.OpenVIRefInContext_8_0.vi)
    Failed to load (C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\NXTToolkit\shared\NXTToolkit.RemoveScrollbars_8_0.vi)
    #### Finished Mass Compile: 2008年7月2日 18:42:58
    Labview 7.1では関係ないのかなと思っているのですが、関係あるでしょうか?
    その他でも、不具合原因について、心当たりのある方がいらっしゃいましたら、
     アドバイス頂ければ幸いです。
    小松崎
    添付:
    LabVIEW_Toolkit_for_LMS_NXT_Getting_Started_Guide.pdf ‏201 KB

    I do know of this one software where you can simulate the NXT, but it might only be for NXT-G programs.
    SimplySim at The NXT Step
    Other than that I don't think there's any way.
    As for the difference between the two, there's a whole ton. Those are two different programs with very different syntaxes. Lego NXT-G is the basic software that comes with the NXT kit. It's a very scaled down version of LabVIEW and is pretty nice. LabVIEW is much more advanced and you can do much more with it, but you are restricted to using the LabVIEW NXT Toolkit and the NXT's cababilities. (no float, only so much RAM, etc.). But you can still do a ton more with it. Yes, you can data log with LabVIEW in, like, many ways.
    Hope that helps!

  • Difference​s between LabVIEW Education Edition and LabVIEW 2009 + NXT Module

    Recently saw the announcement regarding LabVIEW Education Edition.
    From the information available at this time it's hard to tell the difference between this product and just adding the NXT module to standard LabVIEW 2009 if your only interest in LabVIEW is for NXT  programming.  Anymore details about this new product would be appreciated as well as info on how it's different from the alternative.  Are there some unique VIs not present in the standard NXT module?  Obviously the pricing is very different, but for a student the academic version of LabVIEW is actually lower cost than this new Education Edition.

    Inh-
    LabVIEW Education Edition (LVEE) includes the NXT Module and the API to interface with Vernier products.    LVEE is geared towards middle school and high school classrooms to get students interested in math and science.  It includes curriculum for teachers that may not be familiar with programming and LabVIEW in general to use the NXT bricks and the LabVIEW environment. 
    LabVIEW with the NXT module only has the NXT API and not the Vernier API.  It will not include the course work and as extensive example programming useful for teaching. 
    For additional information on LVEE, please take a look at the Getting Started with LabVIEW Education Edition or go to ni.com and search for “labview education edition”. 
    Regards,
    Mike S
    NI AE

  • New Program Guide - unusable

    I want to be tactful about this - what would be the best way to characterize your new program guide - Sick Joke? In what sense is it an improvement over the previous one?  It is in fact immeasurably WORSE.  How could anyone at Verizon have signed off on this?
    The biggest problem is that it is now unacceptably, absurdly, SLOW.  Was that the intention?  I asked Verizon Phone Tech support if  they slowed it down intentionally , because maybe the network traffic volume was too costly for Verizon and they wanted to cut expenses.  Amazingly, he did not give a flat denial to this.  As I recall he said He didn't have any knowledge that that was the case.
    The way it used to work is for example you would hold down the right arrow button, and it would as expected just briskly scroll through  all the programming selections for that day for whatever channel you happened to be looking at, scrolling through all subsequent shows on the channel that day.  (And also as a recall when scrolling through subsdequent days).
    Now you hold down the right arrow button, and it scrolls forward just one show, and then just freezes, doing nothing.  If a few seconds later you lift your finger off the right arrow button,  it immediately jumps to say 8 hours in advance.  This makes this feature unusable.  How could you not understand that, Verizon?
    The same situation exists when scrolling to different channels with the up or down arrows.  Press and hold down  the down arrow, and it does in fact scroll through the subsequent channel icons, but it does NOT,  as it did with the previous program guide, scroll through all the  program DESCRIPTIONS in real time.  So why was that feature ditched? 
    The fastest it can scroll in real time now either left/right or up/down  is 1 entire second.  So, iow, hit the down arrow, and...one one thousand two ...OK NOW it switches.  What is up with that? 
    For the record, this is not the high-def Verizon box.  The TV on the high-def box seem to work a little better.  Does Verizon only support high-def now?
    And I haven't even mentioned the bizarre color scheme and other bizarre design decisions for the new Program Guide layout.  So, how is it better to reduce the size on the screen where the actual program info is, and surround it with a a lot of unused white space (or shoud I say unused sickly pale blue space)?  Just as far as the aesthetics of the new guide, there is not a single aspect of it that is not drastically worse than it was previously.  (e.g.hitting the info button during a show and it covering a third of  the screen.) 
    But disregard the complaints about  the colors, etc.  - just go wild with that if you want.  Just please restore the SPEED of the programming guide to what it was previously.  Because the way it is now its unusable. 
    Is there any way to go back to the old guide?  There is in fact an option in the Menu for the Classic Guide, but it does not do anything except rearrange the new guide a little bit to make it even worse.
    What is going on with you people (Verizon).

    I'm sorry to hear your frustration with the new guide. There is no way to go back to the old style guide. If unplugging the power cord to the box and plugging it in doesn't speed up the guide maneuvering, please send me a private message.
    Anthony_VZ
    **If someones post has helped you, please acknowledge their assistance by clicking the red thumbs up button to give them Kudos. If you are the original poster and any response gave you your answer, please mark the post that had the answer as the solution**
    Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or plan

  • Applescript to automatically update the EyeTV DVB EPG program guide

    For EyeTV users in Europe and Australia with DVB EPG access, you will all know that EyeTV will not keep that database automatically updated.
    So I wrote this bit of Applescript will update EyeTV's free to air DVB EPG database.
    Paste it into the ApplesScript Editor, and save it as an application somewhere like in Applications.  On first run you will get a dialog saying it need access to Accessibility.  Navigate to System Preferences > Security and Privacy > Accessibility and you will see your app listed there.  Enter your password, click the checkbox, and then try again.  It should then work fine.
    To automate the launching of the script, set it to run at at daily a convenient time using either Lingon (or some similar launch agent configuration utility), or using iCal as per this tip: http://www.maclife.com/article/howtos/how_make_your_ical_alarm_perform_action
    Running it daily (or as often as you like) will keep your EyeTV EPG database up to date always.  No more missed recordings because the EPG was not up to date!  Yay!
    This is the basic script, I'm sure it can be better.:
    tell application "EyeTV"
              activate
    end tell
    tell application "System Events"
              tell process "EyeTV"
                        keystroke "g" using command down
                        delay 1
                        click (pop up button 1 of window 1)
                        delay 1
                        click menu item "Update DVB Program Guide" of menu 1 of pop up button 1 of window "EyeTV Programs"
              end tell
    end tell
    Cheers
    Chris.

    Good morning Frank
    OK....
    I too have the same issue (didn't notice it at first).  Having wasted several hours, I found no way around it.
    But there are tools like clicclick that can click anywhere on the mac screen.  So... get it from here:
    http://www.bluem.net/en/mac/cliclick   (big thank you to Carsten Blüm)  :-)
    install as recommended (I put it in usr/bin/ as I had no usr/local/bin).  Check it works via the terminal by pastingcliclick c:28,11 into terminal and pressing return.  If that opens the apple menu, then it is installed and working.
    Then try this script, which first puts the EyeTV window to a specific location on the screen, then instead of using UI scripting to click the silly pop up button 1, uses clicclick to clik at the location of the button.  This opens the menu, and then UI scripting can click it.  You may want to change the EyeTV window location from the value I chose, if so put it into your prefered position then use the Accessibility Inspector to get the location of the button, then add some pixels either side of that.
    For me this now works perfectly every time, I hope it will for you.  Annoying to have to install clicclick but there you go. 
    tell application "EyeTV"
      activate
      set the position of window 1 to {30, 60}
    end tell
    tell application "System Events"
      tell application process "EyeTV"
      keystroke "g" using command down
      delay 4
      do shell script "cliclick c:170,70"
      delay 1
      click menu item "Update DVB Program Guide" of menu 1 of pop up button 1 of window "EyeTV Programs"
      end tell
    end tell
    I have found that the delay after the keystroke g is essential otherwise I get an invalid index error, I think because it is not ready to accept the click.  You may need to change the delay.
    Also when using Lingon to launch the Applescript App, the path needs to be to the applet file inside the contents of it.  ie something like mydirectory/myappname.app/contents/MacOS/applet.  name your app without spaces.
    cheers
    Chris

Maybe you are looking for

  • Unable to connect to MySQL database in Dreamweaver CS3

    I have been working on this problem for hours and am getting very frustrated. I hope someone can help me out. My FTP server and MYSQL server have to use two different hosts. I will be using false information in this post but hopefully someone can hel

  • Mail: How To Get Mail Headers To Show "Read"

    How can I get the mail headers to "gray" out or be colored when they've been read? Right now, ALL messages in the list are bold black. Once I read an email, it still shows bold and black. I need some sort of identification to show what is NEW and wha

  • To use my class files in my applications

    Hi all! public class Count private int serialNumber; private static int counter=0; public static int getTotalCount() return counter; public Count() counter++; serialNumber=counter; public class TestCounter public static void main(String args[]) Syste

  • Macbook Pro (Leopard v10.5.8) connectivity problems

    Computer: Unibody Macbook Pro 13" from August 2009 (running OS X 10.5.8) Problem: Randomly, my AirPort card will turn off and occasionally the computer will freeze up. This issue arose after Apple replaced the Logic Board for a faulty audio-out port.

  • HT1711 rest of the songs

    when i search a album and lets say theres 24 songs.. it only shows like 12-17 of them. how do i see the rest. imac user