« 28 »  05  20 15 г.




Статус 1073 point blank что делать

The analog input ports are numbered from 0 to 7 starting from the left. Connect the LED by inserting the long LED wire into the digital output 7 and the shorter wire into Ground. Connect the power supply to the PhidgetSBC3 using the barrel connector. Connect the PhidgetSBC3 to your network with an Ethernet cable. Plug the wall adapter into an appropriate outlet. The red status indicator light located near the USB ports should be lit if the unit is receiving power. The green LED located above the red LED indicates boot status. The green LED will turn on and off once during boot and then turn back on when everything is running. Other Phidgets can also be connected to the 1073 using a USB cable. If you don't, follow these steps: Go to the Quick Downloads section on the Download and run the Phidget21 Installer 32-bit, or 64-bit, depending on your system You should see the icon on the right hand corner of the Task Bar. Running Phidgets Sample Program Double clicking on the icon loads Phidget Control Panel; we will use this program to ensure that your new Phidget works properly. Make sure that the PhidgetSBC3 is powered and properly connected to your network. Click the PhidgetSBC3 tab in the Phidget Control Panel. Double click on the PhidgetSBC3 device to bring up the PhidgetSBC3 configuration panel in your default web browser. You can differentiate multiple PhidgetSBC3s by their MAC address, which is printed on the sticker on the back of your board. This control panel view will tell you at the bottom : The link local address of the SBC called the mDNS addresshere it is phidgetsbc. Basic Use Basic use of the PhidgetSBC allows the opening of connected Phidgets over the network. Using another Phidget with the PhidgetSBC in this way is almost exactly like using Phidgets over USB, in respect to the API calls and behavior. However, some extra considerations need to be made when working with the PhidgetWebservice. Phidget Webservice Support for opening Phidgets over the network is made possible via the Phidget Webservice. This allows a user to write an application in a system and language of their choosing and then operate Phidgets connected to the PhidgetSBC. It is a socket based server that runs on the PhidgetSBC, and allows any attached Phidgets to be seen and opened directly over the network. Opening and controlling a Phidget over the network is nearly the same as opening one locally. The main differences are: Different open calls that include server information. New calls OpenRemote and openRemoteIP naming depends on language. Access to Webservice based properties: Server hostname, port and ID. Access to server connect and disconnect events, and network error events. Phidgets can be opened by more then one separate application at the same time. Reliability is more of a issue because network connections are easily broken Opening a Phidget over the network is asynchronous and pervasive, just like opening locally. This means that if a connection to the remote server cannot be established right away, it will keep trying indefinitely, and even survive the server being stopped and started, etc. Instances of the Phidget Webservice can be referred to either using hostname IP Address and port number, or by Server ID. In order to use a Server ID, the Bonjour utility also needs to be installed. Refer to the Programming Manual and the API manual for your language for more information about using the Phidget Webservice. Reliability Determining reliability needs can become important while opening Phidgets over the network, because the network connection can potentially be interrupted at any time. This can leave the network attached Phidget in an undesirable state. For example - if a motor controller is driving a motor and the connection is lost, there is no way to stop the motor until the connection is re-established. These issues are less important if you are just receiving sensor data from an Interface Kit. If reliability is important, you should consider writing a program to run locally on the PhidgetSBC, and communicate with it through the Dictionary interface. This way, if the connection is broken, the local application will notice and be able to take any appropriate actions. See the advanced chapter for more information. The Phidgets connected to the PhidgetSBC should be seen here and can be opened by double clicking its name in the menu. Network attached Phidgets can also be located programmatically with the Phidget Manager. The manager can also be used to find all Phidgets on any Webservice through Bonjour, by specifying a NULL Server ID. Testing Using Mac OS X The steps are very similar to the Windows process described above: Ensure you have OS X 10. Note down the address in the browser, as you will need this information for later if you will be working to perform tasks such as writing or running code. But for now, with the web interface open, we have a. Using Linux With Linux, you have many setup options, but all involve knowing the IP address or link local address of the SBC after you have plugged it in as described in. The IP address can be somewhat difficult to obtain, but the default link local address for all new Phidget SBCs is phidgetsbc. Wait at least three minutes after booting the SBC to make sure link local addressing is started. You'll also need some form of mDNS either avahi or mDNSResponder installed on your main computer. The avahi service is usually installed by default on most Linux machines, try which avahi-resolve to make sure. Then, try typing phidgetsbc. The should come up, starting with the screen. Note that some browsers i. If these steps do not bring you to the initial setup password screen as shown in theyou will probably need to read the. That section contains more than just troubleshooting information - it includes in-depth information on how the SBC starts its network, your initial network configuration options, and how to connect to the SBC without mDNS using both DHCP and static IP. If this is your sole intended use of the SBC, you can skip ahead to our example on using the. However, the SBC is much, much more than simply a way to get data from Phidgets over a network. You can use the SBC as an external Linux computer. You'll need to using the SBC web interface, and write down a network address of the SBC phidgetsbc. But after that, if no other sections in the basic section apply to you using the webcam, setting up wireless networking, or checking system parameters like memoryyou can skip ahead to the page. To test the InterfaceKit on your Linux computer over the network, you will need to install the Phidget libraries and the Phidget webservice if you haven't already. If you have used any Phidget via USB and over a network on your Linux computer, you have already done this. This process is described on the general page, so follow those installation instructions, with the following modifications to the : Instead of using a localhost 127. Note that any attached analog sensors in the black ports will not show up over the webservice as individual Phidgets. Rather, they will show up as part of the Interface Kit, through the port number that they are attached to on the SBC board. SBC Web Interface Using the operating system sections of this guide, you should have been able to open a web browser with a connection to the SBC using either: The Phidget Control Panel Windowsor The Phidget Preference Pane Mac OSor An mDNS connection Linux. Here we cover the basics on the tool that has been opened in the browser, known as the SBC Web Interface. Set the Password If this is your first time connecting to the SBC or after a complete factory resetyou will see a screen asking you to set a password: This password will be linked to the user admin if you use the web interface in the future, and to the user root if you choose to use SSH. These are actually the same user, and the SSH connection is covered in-depth on the. Remember this password, as you will need it to connect to the SBC in the future, and the only way to log in if you lose it is to perform a on the SBC. The next time you connect to the SBC after you log out or reboot the SBC, you will be asked to log in with a user name and password: Navigating The SBC Web Interface has a series of tabs and sub-tabs at the top, and by using these you can access the entire web interface. Note that the web interface only allows you to configure a very small portion of the SBC, please refer to the full page for an in-depth introduction on the SBC Linux operating system. The header also has information about how long the SBC had been powered on without a reboot, what the link local address of the SBC is here it is phidgetsbc, so the full link local address is phidgetsbc. This can be a bit misleading however. To get a better idea of the total memory usage go to the "Processes" subtab and look at memory usage on a per-process basis. The SBC can switch dynamically between Ethernet what it tries first and wireless via the. It is also able to dynamically handle both Ethernet and wireless being unplugged and then plugged back in. This is especially useful if you are designing a project where the SBC will operate without a network - when testing you can plug in and remove the network adapters to check on how the SBC is doing. Wireless The SBC can only access wireless networks using the. These do not necessarily have to be networks that are currently seen - you can add the SSID and password of your home network, for example, and the next time the SBC boots at home with wireless only it will connect to your home wireless network. These SSID settings are only for DHCP networks. Static IP If you do not have DHCP on your main network, and do not want to use link local addressing, you can set the network connection to be static. In the Ethernet settings, for example, you can specify network elements manually in the same way you would for a desktop computer: This setting is also useful to work entirely without mDNS and link local addressing. After setting it, the SBC will start using that static IP immediately, so if this is done improperly this can make the SBC very hard to re-connect to depending on the routing within the rest of your network. If you are not sure whether this will be a problem, it may help to read the in-depth for the SBC. It will also show any Phidgets plugged into the SBC's USB ports. On the right hand side of this screen not shown in the screenshot you will see the serial numbers of the attached Phidgets. If you want to use these Phidgets within your code over a network using the webservice, you can use these serial numbers in your programming project. Note that any analog or digital sensors will not show up here, as they are a 'part' of the Interface Kit and can be accessed through the ports in the Interface Kit API. Taking a look at the for the will show you a good example of how this works. Use the Webcam Using the webcam either the or another should be fairly straightforward. This stream can also be viewed with any compatible M-JPG viewer, such as VLC. To take pictures with the webcam within your code, see the on the main SBC operating system page. Multiple frame rates and resolutions are supported. If the video stream is to be exported over the internet, it is recommended that the password be enabled. However, it must be noted that this is a simple HTTP authentication, which is sent unencrypted, and is thus not highly secure. If multiple webcams are attached, they will all start up using the same settings, except that each additional webcam will run on the next higher port number. Multiple webcams will generally only work when the resolution and framerate are set to low levels. At this point, we have covered most of the common uses of the web interface. But the web interface offers many more configuration options. This reference section covers all of the available options. If you want to continue on to tasks such as writing and running code on the SBC, visit the page. Can I use multiple webcams? In theory you can connect multiple webcams to the SBC, however, the bandwidth of a USB1. Web Interface Reference This section provides a complete reference to all tabs and sub-tabs within the SBC web interface. Note that the web interface itself also includes help as text on the right side of most tab screens. Top Bar On loading the interface, you will see a tool bar along the top of the page. It holds some information across all the configuration pages. The information is as follows: Host Name The host name given to the PhidgetSBC on the network. Uptime Total time elapsed since the last reboot. Load The average CPU utilization in the last minute, 5 minute, and 10 minute durations. Version The current board and web interface version. Tab: Status The main tab Status has options for System, Network, Processes, USB, and Phidgets. System This is the first page you should see after loading the configuration Interface. It contains general information about the SBC. System Information Board Name Name of the device. Board Revision Board revision number. This tracks the hardware design. Webif Version The version of the web interface currently being used. Kernel Version The type and version of the loaded Linux kernel. These libraries are included with the firmware, and may need to be updated to use newly released Phidgets. A PhidgetSBC is uniquely identified by its MAC address shown here. This address is also printed on the label of the underside of the PhidgetSBC. Other Phidgets, including the integrated InterfaceKit, use a serial number to identify themselves. Memory Memory usage is shown. Processes This lists all running processes, along with their Process ID PIDUser, State, CPU usage and memory usage. Advanced users can use this to tell if any application is using too much memory, or has crashed. USB This lists all USB devices. Also listed are any mounted USB drives. All connected devices A list of all the USB devices present in the system. This includes the main USB, the built in 6 port hub, and all Phidget and non-Phidget devices. Mounted USB devices This area lists of all the USB based drives connected to the PhidgetSBC, and their mount points. Unmount Button Use this button before removing the device to safely disconnect it. Status General network status can be viewed on this page. Modifying these values are done on other pages. Network Adapter Abbreviated name and number of the network interface. Type Wired or wireless connection. Mode Network protocol used. IP Address The IP address of the network interface. Subnet Mask The subnet mask of the network interface. Gateway The IP address of your gateway. MAC Address The MAC address of the interface. Wireless State Connection status information for the Wireless link. This could be 'CONNECTED', 'INACTIVE', 'FAILED', etc. Wireless SSID The plaintext name of the wireless connection access point. Wireless Security Security protocol used for a wireless link. DNS Server s List of nameservers being used. This is also where SSH is enabled. In the absence of a DHCP server, Static should be used and filled in manually. DNS settings DNS can be set up automatically if DHCP is enabled. Under manual settings, up to two DNS servers can be specified. Note that DNS settings are system-wide and will apply to all interfaces. SSH Server This is where the SSH server can be enabled or disabled. Enabling SSH for the first time can take several minutes as the keys are generated. Wireless Wireless networking is supported via a. When an adapter is plugged in, this wireless configuration page will be available. Wireless networks are joined based on a list of saved networks. You can join, manually enable and disable, as well as delete these saved networks. To add a wireless network to this list, either choose from the list of detected networks, or enter the details manually. Supported security includes WEP, WPA 2 Personal and WPA 2 Enterprise. Saved networks will be joined first based on security and secondly based on best signal strength. Add a Wireless Network SSID The SSID of the access point that you wish to add. This is the plaintext name of the access point. Security The security system used by this access point. Remember this network If enabled, this network will be added to the list of saved networks permanently, and will be available to be automatically joined in the future. Otherwise, this network will remain in the list of saved networks until the board is reset, or another network is added. Manage saved networks Join This Network Joining a specific network will temporarily disable all other saved networks, so that the specific network will be joined, if available. The other networks will remain disabled until the board is reset, or another network is added. Delete This Network Delete a saved network. There is no confirmation and this cannot be undone. Disabled networks will never be joined. In the absence of a DHCP server, Static should be used and filled in manually. DNS settings Switch the DNS settings between Automatic and Manual. DNS can be set up automatically if DHCP is enabled. Otherwise, up to two DNS servers can be specified. Note that DNS settings are system-wide and will apply to all interfaces. Tab: Phidgets Status Library Version The version of the installed Phidget21 library. These libraries are included and are updated along with the firmware. List of attached Phidgets A list of all detected Phidgets connected to the PhidgetSBC. This includes the integrated PhidgetInterfaceKit and displays both the serial number and version. WebService The Phidget webservice is a simple server that allows Phidgets connected to the PhidgetSBC board to be opened over the network. This is enabled by default and starts with the SBC. This page lets you view and modify the Phidget webserice settings, as well as stop and start the server. Server ID Server ID is used when opening a connection to the PhidgetSBC using the mDNS based openRemote calls. This is by default the same as the PhidgetSBC hostname phidgetsbcbut can be set to anything up to 63 characters. Port Port is the port that the webservice runs on - default is 5001. Password The password is used for securing the webservice. By default, this option is disabled with a blank password. Note that while the authentication protocol and password is encrypted during authentication, all following data is sent in the clear. Tab: Projects This is where user projects are set up. Custom applications can be written in either C compiled to an ARM architecture or Java, and then set up to run on the PhidgetSBC at system startup. We offer an on creating applications in this manner using Java. Projects This sub-tab lists installed applications as well as the controls for creating a new application space. This is also where you can download the SBC-specific version of the Phidget Java libraries: phidget21. You can click on the application name to launch the Specific Project page. Create new app Button This button creates a new application space using the input field for its name. Application names should not contain spaces. Free space remaining on userspace partition The amount of free space remaining on the user partition in bytes. Specific Project On a specific application space page, there are controls to start and stop the program, as well as view the stdout and stderr from the most recent or current run. Starting a program will generate stdout and stderr logs. View stdout You can view the standard console output of your program through this link. View stderr In the event of an error that halts program execution, its corresponding error message is printed here. Filesystem Browser This allows viewing, editing and removal of application files, as well as the ability to upload new files. File upload size is limited to 5MiB per file. Startup Settings This section configures the application to start at boot. When this enabled, it will start at the end of the system boot process after things like bringing up the network, starting the Phidget WebService, etc. The startup order field specifies a start order among the custom applications, with lower numbers being started first. Executable name is the name of the file to execute. Video streaming can consume a lot of bandwidth depending on the settings used. Resolution The resolution of the capture in pixels. Only resolutions supported by the webcam are listed. Framerate The transmission frame rate of the capture. Available frame rates will depend on the selected resolution. Port The port that the video stream is sent to. Password Protect the webcam stream with a password. This will add a simple username and password prompt whenever you view the webcam stream - including on this page. The username is 'webcam'. Set to nothing to disable passwords. Tab: System System Settings Host name The system hostname. All PhidgetSBCs have a default hostname of phidgetsbc. When used as a link local address, the extension. Zoneinfo String Standard zoneinfo names are defined for different areas of the world. You can supply any zone from the official list as an alternative to selecting a predefined zone from the list. Logs This is where the kernel and system logs can be viewed. This also includes the ability to filter the text. We also have a special section on. Text Filter Text to Filter Insert a string that covers what you would like to see or exclude. Remove Filter Clears the filter being used Filter Messages Change the filter being used. Including a blank Text to Filter effectively removes the filter. Password Change This is where the system password can be changed. The system password is the which is the admin password for the web interface is also the root user password on the SBC when using. Changes here made will take effect immediately after being saved, without asking for confirmation. The new password must consist of alphanumeric characters and be at least 1 character long. Password Change New Password The first field for a new password. Confirm Password The second field for a new password. This must match the first field. Set Password This button will commit the changes to your password. File Editor This grants access to the full filesystem. Files can be uploaded, edited and deleted, and directories can be created. File upload is limited to a filesize of 5MiB. Note that this only backs up configuration files directly related to the web interface - such as network configuration, hostname, time settings, and user project setting but not including project files. For other methods of backup, including installed software, we have a. When restoring from a backup file, the system will check that it is a valid backup before asking the user to continue. Backup Configuration Name this configuration You can give the backup file an arbitrary name. The name is only shown during restore. Backup This button creates the backup. A download link to the backup will be provided and you will be prompted to save the file to an off-SBC location. The download link is not valid indefinitely, use it then. Restore Configuration Saved backup file Choose a backup file for this machine type. The restore system will check the file and ask for confirmation before running the restore. Restore This button applies the backup. The backup file will then be verified. Clicking restore again will commit the changes and take effect immediately. Reset Configuration Reset This will reset all of the web interface configuration files to their default states. This will not reset the system as a whole. Refer to our section on the for more information. Packages This is where package updates are performed. From time to time, updates will be made available. These will address any bugs and security issues, add new features, and update the phidget21 library and webservice. There are also some other package management options available. Note that this page can take quite a long time to load when 'Include full Debian Package Repository' is enabled. Upgradable Packages This lists all available package updates, if any. Upgrade All Packages This installs all available package updates. Selective updating can only be done via. Refresh Available Packages This runs to refresh the package list and check for new updates. Installable Packages This lists some package sets that be installed to add common features to the SBC. Java Support Button This installs 'libphidget21-java' and 'default-jre-headless' to support Java based projects. We also have a detailed walkthrough of installing and using C, Java, and Python. Settings Include full Debian Package Repository This enables the full Debian repository in the apt sources list. By default, only the Phidgets repository is included. When enabled, all system packages will show up in the updates list, rather then just Phidgets packages, allowing for full system updates. This also allows the user to install any packages they like, from the SSH interface. Reboot The board can be rebooted remotely from this page. The reboot should take 45-60 seconds depending on network conditions. It tries to shut down all running programs before restarting as opposed to the reset button. About The license information and credits for the configuration interface is displayed here. A link is provided to the original sources and the Phidgets web site. Advanced User's Guide This section describes use of the PhidgetSBC outside of the web configuration, and basic opening of Phidgets over the network. It is recommended that you have some experience with Linux before trying some of these tasks. Custom Applications The PhidgetSBC supports custom user application written in either Java or Custom applications are set up and managed using the configuration interface. This must include at least the executable file. Java applications must be compiled on a separate development machine, where they can also be tested before deployment. When coding, make sure to include the correct version of phidget21. You can use the link under Userspace: Applications page in the configuration interface to ensure that your Java program is synchronized with the version of phidget21 on the PhidgetSBC. When using Java packages, make sure to create the appropriate directory for them. The PhidgetSBC also supports. When your project is completed we recommend to compile the project as a. This reduces the number of extra flies created into a single package that is easier to manage and can be executed from the command line, or even by double clicking the file if your operating system environment is configured properly. Under the command line, you can use the jar utility from the Java SDK to package the. The process starts by going to the directory where your program is located and creating a manifest file. This manifest file tells the java jar compiler the version of the program and the name of the Main-Class which acts as the entry point for the application. The entry point is the class that contains the main method that is run when the program is started. You also want to add a line to specify the class-path which will point to the phidget21. First, compile the program to generate the. Now, create the manifest file MyProgram. Create the jar by running the following command from the command line: jar cmf MyProgram. You should now have an executable jar file called MyProgram. To run the executable jar file you can either type the following into the command line: java -jar MyProgram. Note: Some IDEs, such as Eclipse and Netbeans, automatically create jar files when you build your project. Simply look in your build output folders for your. Java applications can also be directly executed through SSH using jamvm. Use of a cross compiler is not strictly documented here, but it is possible to build one from the buildroot distribution available on our web site. Note that custom applications should not try to get user input, as stdin is closed before the application gets run. GCC The PhidgetSBC contains full GCC and associated build tools, as well as make and gdb for compiling C source. Use of these is the same as on full linux, just keep in mind that there is no swap space and userspace is limited. Compiling will also be slow for complicated programs. Simple programs are ideal for this environment. The C library used is uClibc. For most uses this should be similar to full libc, just much smaller. Also, when compiling a program that links with libphidget21. Otherwise, you will get segfaults. Phidget Dictionary Communication between a custom application on the PhidgetSBC and the outside world can be facilitated by using the dictionary interface of the Phidget Webservice. This could be used to post data or listen for commands over the network, while maintaining reliability and ultimate control on the PhidgetSBC itself in case of network failure. See the Phidget Programming manual for its use in your language of choice. SSH The built-in SSH Server can be enabled to allow console access to the PhidgetSBC. By default, this server is disabled. SSH access to the PhidgetSBC is enabled in the Network: Network configuration page on the PhidgetSBC. Enabling the server for the first time can take several minutes as the encryption keys are generated. Once SSH is enabled, connect to the PhidgetSBC using its hostname or IP address e. The password for the user account can be changed any time either through the unrestricted root account or directly through the user account. Files can be sent to the board using scp or by uploading through the web interface in Userspace: Userspace Browser. The SSH server does not support sftp. Text files source code, etc. On Windows, we recommend Putty for an SSH client. You can get this at. Customization If you wish to customize the root filesystem, you have two options: customize locally on the board, or build a custom kernel and filesystem from source. If you mess up the firmware while customizing, you can always perform a board reset and start again. You may also want to to add new libraries or kernel extensions, add new Unix tools, update certain aspects, delete others, change the boot process, etc. All of this is possible, but it is also completely unsupported by Phidgets. Custom Kernels and Filesystem You can build the complete filesystem and kernel from the same codebase as Phidgets Inc. The full Buildroot system can be downloaded from our website. However, this basic information should be enough to get started. Buildroot works by building a full cross-compiler for the PhidgetSBC and then using that to build a full set of tools to create a root filesystem from scratch. It also handles building the kernel. You can use the cross compiler that it produces to build your own applications for the PhidgetSBC independently of the system, or integrate your code into the process. Buildroot downloads all of the source code it needs from open-source repositories, so the Buildroot distribution itself is fairly small. Buildroot needs to be run on Linux. Building the full filesystem relies on some packages which you will need to install into your Linux distribution, including but not limited to: libacl1-dev, zlib1g-dev, kaffe, liblzo2-dev. If you make changes to config files, source, etc. Both Ethernet Port LEDs yellow-connectivity, green-activityand the green status LED will turn off. The reboot is done when all LEDs come back on in about 25 seconds. To reset the firmware, press and hold the button for 10 seconds until the green status LED begins to blink, then release. Both Ethernet Port LEDs will turn off yellow-connectivity, green-activity for 80 seconds; the green status LED will then turn off; then all LEDs will come back on in 20 seconds. All data will be lost and the operating system will be reset to a factory state. The recovery system allows for factory reset, full system upgrades and recovery of the main system. Entering the Recovery System The recovery system can be entered in two ways. By holding down the reset button for 20+ seconds - until the green light has switched from flashing slowly to flashing quickly. Upgrades Generally, you should not need to do a full system upgrade. Phidgets will not be creating these images with every release of phidget21 as we did with PhidgetSBC1, rather they will be released several times a year, as needed for major changes not easy to push out via packages. You can also flash your own custom kernel or root filesystem image. Factory Reset This restores the kernel and root filesystem from backup, overwriting any changes that may have been made. This is equivalent to holding down the reset button for 10 seconds. The recovery system runs an SSH server that you can loginto for console access. JTAG connector, for internal testing purposes only 1. This Ethernet port is used for network connectivity to the PhidgetSBC. This enables access to the PhidgetSBC as well as any connected Phidgets through the webservice. Alternatively, the USB Wireless adapter can be used for network connectivity. These USB ports can be used for connecting Phidgets, Wi-Fi adapters, flash drives, webcams, USB hubs, etc. These LEDs indicate the status of the PhidgetSBC. The Red LED indicates that the power supply is on and running properly. The green LED indicates boot status. The green LED will turn on and off once during boot and then turn back on when everything is running. This will reboot the board if pressed once. Note that this is a forced reboot. Any user programs that were running may leave their data in a inconsistent state, but this is safe for the base system. A soft reboot can be performed remotely from the configuration interface. If held for more then 10 seconds, the red LED will start to blink and enter emergency Reset mode. Once the button is released, the onboard memory will revert to a factory-fresh state. This includes overwriting the kernel and root file system, and erasing all configuration, user data, and applications. The PhidgetSBC can be powered from either the terminals or the barrel connector. Power Distribution The 12V power supply is stepped down to 5V and distributed in the following way: Each USB port has 500 mA available All analog inputs share a total of 500 mA The digital outputs, +5V terminals, USB controller, and pull-ups all share a total of 500 mA Power Over Ethernet Power over Ethernet can be used to provide both a network connection and power to a device when a power outlet is not available. This means that with the proper adapters, you can run the PhidgetSBC entirely off an Ethernet source. The PhidgetSBC does not draw power directly from a powered Ethernet line, but instead can use a setup where the power is split to a separate line again near the PhidgetSBC. The board has been tested and will work with Power Sourcing Equipment that can output 6-12VDC. Hardware Layout The PhidgetSBC is based around the i. This is an ARM926EJ-S based microprocessor from Freescale, which runs at 454MHz. The microprocessors USB Host port is connected to a 7-port USB 2. The kernel is 3. The root filesystem is created using debootstrap and is mounted in a ~924MiB nand partition using the UBIFS filesystem, in Read-Write mode. This is where all configuration that can be set through the website is located. The kernel is stored on bare Nand in it own 4MiB partition, in the uImage format. Date and Time The date and time are set using ntp network time protocol at boot. The ntp daemon continues to run in the background and will periodically update the clock, keeping it very close to real time. If power is unplugged suddenly, the real-time clock may not have the correct time. Wireless Networking System Wireless networking is supported using the available adapter and is configured through the configuration interface. These files should generally not be changed manually, but there is no reason why they could not be. Nand Layout The board contains 1GiB of Nand. Boot Process This describes the boot process from power on. The system has finished booting Drivers for USB to Serial adapters The SBC kernel contains driver support for the following USB to Serial Adapters. Please consult the kernel documentation for details into the driver support for the USB to Serial adapters. Company Product ConnectTech WhiteHEAT Keyspan USA-18X, USA-28, USA-28X, USA-28XA, USA-28XB, USA-19, USA-19W, USA-19QW, USA-19QI, USA-49W, USA-49WLC FTDI Single Port Serial Adapter Cypress M8 CY4601 Family Digi International AccelePort USB Serial Belkin USB Serial Adapter F5U103 MCT USB Single Port Serial Adapter U232 Inside Out Networks Edgeport Serial Adapter Prolific PL2303 Drivers for USB Wifi Adapters The SBC kernel contains driver support for the following USB Wireless Adapters. Please consult the kernel documentation for more details. Normal users will not need to use it. If you are connected to the serial port, you will see the U-Boot prompt shortly after power up. You can view the environment variables for information on how to properly boot Linux on the PhidgetSBC. Be very careful when modifying the u-boot partition. If it is damaged or overwritten, it is difficult to fix. Refer to U-Boot documentation here: for more information on using U-Boot. Ad-hoc Networks The SBC can be configured as a device in an ad-hoc network. For more information, visit the page. Further Reading Check the page for more details about using the Phidget SBC. Check the for more information about the InterfaceKit on this board. Check the for API details. Product History Date Board Revision Device Version Comment January 2013 0 300 Product Release January 2015 0 301 Changed flash and updated kernel This page was last modified on 24 March 2015, at 18:23. This page has been accessed 21,474 times. This work by Phidgets Inc.




Эльвира Щенникова

The program should report how long it takes for the level of water to reach the target level. The next time you connect to the SBC after you log out or reboot the SBC, you will be asked to log in with a user name and password: Navigating The SBC Web Interface has a series of tabs and sub-tabs at the top, and by using these you can access the entire web interface.