M3005 Firmware
Clara Vanliere
The Model 3005 is a durable, lightweight instrument with an internal energy-compensated GM detector for radiation survey. It features a large, easy-to-read LCD screen and audible alarms and is controlled using a simple five-button interface. The unit body is made of high-impact plastic and splash-resistant construction allows the instrument to be used outdoors.
Three modes of operation are available - RATE, MAX, and COUNT - which can be selected by pressing the MODE button. Measurements can be collected in two sets of units (primary and secondary) for RATE and MAX modes in cps, cpm, mR/h, or Sv/h units. The user can switch between the two sets of units by pressing the UNITS button. When enabled with the optional Lumic Data Logger Kit (see Options), data can be logged in any of the operational modes using the LOG button on the handle. Up to 1000 data points can be stored internally.
Instrument setup can be done either through the front-panel controls or via the Lumic Calibration Kit (see Options). The Model 3005 is shipped ready to use with batteries and a calibration certificate.
In order to use the latest Lumic Calibration Software*, you may need to update the firmware on your instrument. (All new instruments will be compatible with the latest software version.) Use the table below to determine the firmware requirement for your instrument.
The decoder needs usernames and passwords to the cameras to access the video streams. The decoder can have multiple credentials saved. It will try to access all cameras using all of the stored credentials.
IP address: Enter a unique IP address for the device. Static IP addresses can be assigned at random within isolated networks, provided that each address is unique. To avoid conflicts, we recommend you contact your network administrator before you assign a static IP address.
Assign DNS automatically: Select to let the DHCP server assign search domains and DNS server addresses to the device automatically. We recommend automatic DNS (DHCP) for most networks.
HTTPS is a protocol that provides encryption for page requests from users and for the pages returned by the web server. The encrypted exchange of information is governed by the use of an HTTPS certificate, which guarantees the authenticity of the server.
HTTP port: Enter the HTTP port to use. The device allows port 80 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning.
HTTPS port: Enter the HTTPS port to use. The device allows port 443 or any port in the range 1024-65535. If you are logged in as an administrator, you can also enter any port in the range 1-1023. If you use a port in this range, you get a warning.
LLDP and CDP: Turn on to allow automatic discovery on the network. Turning LLDP and CDP off can impact the PoE power negotiation. To resolve any issues with the PoE power negotiation, configure the PoE switch for hardware PoE power negotiation only.
You can use a CA certificate to authenticate a peer certificate, for example to validate the identity of an authentication server when the device connects to a network protected by IEEE 802.1X. The device has several pre-installed CA certificates.
IEEE 802.1x is an IEEE standard for port-based network admission control providing secure authentication of wired and wireless network devices. IEEE 802.1x is based on EAP (Extensible Authentication Protocol).
To access a network protected by IEEE 802.1x, network devices must authenticate themselves. The authentication is performed by an authentication server, typically a RADIUS server (for example, FreeRADIUS and Microsoft Internet Authentication Server).
When using a certificate, in Axis' implementation, the device and the authentication server authenticate themselves with digital certificates using EAP-TLS (Extensible Authentication Protocol - Transport Layer Security).
Key agreement connectivity association key name: Enter the connectivity association name (CKN). It must be 2 to 64 (divisible by 2) hexadecimal characters. The CKN must be manually configured in the connectivity association and must match on both ends of the link to initially enable MACsec.
Key agreement connectivity association key: Enter the connectivity association key (CAK). It should be either 32 or 64 hexadecimal characters long. The CAK must be manually configured in the connectivity association and must match on both ends of the link to initially enable MACsec.
New password: Enter a password for the user. Passwords must be 1 to 64 characters long. Only ASCII printable characters (code 32 to 126) are allowed in the password, for example letters, numbers, punctuation, and some symbols.
Firmware upgrade: Upgrade to a new firmware version. New firmware releases can contain improved functionality, bug fixes, and completely new features. We recommend you to always use the latest release. To download the latest release, go to axis.com/support.
Motion JPEG, or MJPEG, is a digital video sequence that is made up of a series of individual JPEG images. These images are then displayed and updated at a rate sufficient to create a stream that shows constantly updated motion. For the viewer to perceive motion video the rate must be at least 16 image frames per second. Full motion video is perceived at 30 (NTSC) or 25 (PAL) frames per second.
H.264 can, without compromising image quality, reduce the size of a digital video file by more than 80% compared to the Motion JPEG format and by as much as 50% compared to older MPEG formats. This means that less network bandwidth and storage space are required for a video file. Or seen another way, higher video quality can be achieved for a given bitrate.
Axis offers device software management according to either the active track or the long-term support (LTS) tracks. Being on the active track means continuously getting access to all the latest product features, while the LTS tracks provide a fixed platform with periodic releases focused mainly on bug fixes and security updates.
Using AXIS OS from the active track is recommended if you want to access the newest features, or if you use Axis end-to-end system offerings. The LTS tracks are recommended if you use third-party integrations, which are not continuously validated against the latest active track. With LTS, the products can maintain cybersecurity without introducing any significant functional changes or affecting any existing integrations. For more detailed information about Axis device software strategy, go to axis.com/support/device-software.
AXIS OS determines the functionality of our devices. When you troubleshoot a problem, we recommend that you to start by checking the current AXIS OS version. The latest version might contain a correction that fixes your particular problem.
If the firmware upgrade fails, the device reloads the previous firmware. The most common reason is that the wrong firmware file has been uploaded. Check that the name of the firmware file corresponds to your device and try again.
If the IP address intended for the device and the IP address of the computer used to access the device are located on different subnets, you cannot set the IP address. Contact your network administrator to obtain an IP address.
If you receive: Reply from : bytes=32; time=10... this means that the IP address may already be in use by another device on the network. Obtain a new IP address from the network administrator and reinstall the device.
The static IP address in the Axis device is used before the DHCP server sets a dynamic address. This means that if the same default static IP address is also used by another device, there may be problems accessing the device.
IP addresses obtained from a DHCP server are dynamic and may change. If the IP address has been changed, use AXIS IP Utility or AXIS Device Manager to locate the device on the network. Identify the device using its model or serial number, or by the DNS name (if the name has been configured).
While using the SD-card is the simplest way to flash a new firmware, it is usable mostly in cases where the drone works properly before update. If the drone cannot properly communicate with some of its modules, they will not be affected by the update. This means if a module stopped working after an update, further updates will not affect it in any way (it is still possible that the module works properly, just using its older firmware - in that case a downgrade of the whole drone could bring it back to life, by downgrading all other modules to the version which can communicate with the problematic module).
The official way of flashing the firmware is by inserting an SD-card with firmware package file into the drone camera. The camera will extract modules from the package and distribute them to proper target components. It requires the firmware in bin form to exist in root directory of the SD-card.
If the SD-card contains a file named _FW_DEBUG, where is a short code name of the drone, then firmware package file on SD-card will be used to update the drone even if its version is lower or equal the current version. Any checks whether downgrade is allowed are skipped, and firmware modules are flashed to appropriate components.
During the update, log files will be created and stored internally. After the upgrade, two logs will be copied to the SD-card. The more verbose log will be in a MISC/LOG folder which has the hidden attribute set. It is best to check that log for a result information.
The camera can also upgrade specific modules of the drone if properly named files are found on the SD-card. The firmware module file needs have 1st encryption level removed - the one which comes with xv4 container file. Some modules have only one encryption level and thus will be unencrypted, others have multiple levels, so the flashed data will still be encrypted.
4a15465005