Mitchell Guzik

The project is a high speed data mover (files and/or folders) tested up to a 10G fiber optic line with speed capabilities of line speed (1.1 GB/s with low CPU usage).

We started off using software from one vendor, but that product was not up to the challenge, high CPU usage and inconsistent speeds only sometimes approaching line speed. I worked with two other engineers on the project. I was a Linux system admin in the first phase of the project.

I created 802.3ad port bonding on… Show more

The project is a high speed data mover (files and/or folders) tested up to a 10G fiber optic line with speed capabilities of line speed (1.1 GB/s with low CPU usage).

We started off using software from one vendor, but that product was not up to the challenge, high CPU usage and inconsistent speeds only sometimes approaching line speed. I worked with two other engineers on the project. I was a Linux system admin in the first phase of the project.

I created 802.3ad port bonding on CENTOS and Brocade Big Iron RX4 switch using dual 10G fiber optic cable. Later, we bypassed the Brocade switch and just ran a cable directly between the two systems through another box, which simulated load at various latencies.

We switched software vendors, which was daemon based. The daemon worked to specification with low CPU sage and consistent line speeds without data compression (1.1 GB/s). I worked directly with the creators of that software to create the full featured FTP line GUI application, which I did on my own. Think Smart FTP or equivalent. Users could run the software directly off of one of the CENTOS servers or from a third party desktop.

I interfaced to the daemon using REST XML calls. The release single jar runs seamlessly on Windows, Linux, or Macintosh supporting both 32-bit and 64-bit Java. The jar embeds all resources sans the image for the desktop shortcut.

Key features include a real time graphs (Nebula), implemented custom file and folder browse similar to Smart FTP, OEM branding using a setting in the ANT build XML build file, and multi transfer capabilities, multilink capabilities, and multi-server capabilities. The GUI offers import and export capabilities for link and server lists.

I was involved in the team that tested and implemented the service into JMR's products, and created the tuning parameters for different latencies.

Environment: Java, SWT, ANT, Eclipse, Java libraries (many), regex (regular expressions), Visual Studio, CENTOS (Linux) Show less

Towards the end of the 3G SAS/SATA expander project, described separately, we started work on the 6G SATA/SATA expander for all JMR expander products. We introduced a new BlueStor 24 bay expander. The 24 bay uses a single code base with the other expanders.

The boards used the Maxim MAX72018C SAS/SATA 6G expander (which uses a MIPS 4KEc processor) utilizing ThreadX OS. Maxim developed the 6G SDK separately from the Vitesse 3G SDK. Still, there were overlaps. I used Visual Studio as the… Show more

Towards the end of the 3G SAS/SATA expander project, described separately, we started work on the 6G SATA/SATA expander for all JMR expander products. We introduced a new BlueStor 24 bay expander. The 24 bay uses a single code base with the other expanders.

The boards used the Maxim MAX72018C SAS/SATA 6G expander (which uses a MIPS 4KEc processor) utilizing ThreadX OS. Maxim developed the 6G SDK separately from the Vitesse 3G SDK. Still, there were overlaps. I used Visual Studio as the IDE. The underlying tool chain was a bit different than the 3G Cygwin. I built the project both from the command line and from with Visual Studio.

I continued to use the SerialTek BusXpert Pro 3G/6G SAS Analyzer for debugging as well as the onboard serial port. Thankfully, the serial port operated at the faster 38400 baud rate compared to the 9600 that the Vietesse VSC7153 expander supported.

Like with the 3G expander, I had to get our boards working with both the ATTO and LSI SAS/SATA RAID adapters. I continued to work directly with ATTO Technologies to debug their adapters.

PMC Sierra purchased the Maxim products with many personnel moving over to PMC Sierra. PMC Sierra already had 12G expander software and basically discontinued the Maxim SDK. I started developing a 12G solution, but the project stopped at the early stages.

Environment: C#.Net (v4.51), Visual Studio 2013, TFS Show less

I started the project, which as part of the radar system, at Design Catapult for the U2. The board plugged into a VME backplane. The final shippable unit that Raytheon shipped was a standard sized chassis that plugged into the Lockheed Marin Marietta U2. The project and I moved over to JMR Electronics.

The original design utilized a Philips XA chip using a homespun round-robin operating system. Raytheon requested a complete overhaul with new functionality. I got to choose the main chip… Show more

I started the project, which as part of the radar system, at Design Catapult for the U2. The board plugged into a VME backplane. The final shippable unit that Raytheon shipped was a standard sized chassis that plugged into the Lockheed Marin Marietta U2. The project and I moved over to JMR Electronics.

The original design utilized a Philips XA chip using a homespun round-robin operating system. Raytheon requested a complete overhaul with new functionality. I got to choose the main chip, an Intel 80386EX embedded processor. The compiler was Intel CAD-UL. I kept the home spun operating system, but rewrote everything else. I talked either directly to the chip or to an FPGA, originally a CPLD. The CPLD originally implemented the I2-C functionality, but I later rewrote that once supporting the ASTOR and Northrop Global Hawk got added to the mix.

All three aircraft use the same source code base with a configuration file setting, configured from the console, determining the aircraft type. The Northrop Global Hawk had had two different CCM boards in one chassis.

I upgraded the header files for compiling under Visual Studio. Final built was always using the Intel CAD-UL Workstation IDE, which was able to build from the same Visual Studio C++ class based object oriented code. I wrote the software and was co-developer on the boot loader.

The board had I2C bus, LM-35/75 sensors, RS232, SPI, SCI, VME, sensors, JTAG, fans, heaters, VME backplane, and many other elements. Software and hardware complied with IEEE 9001, Six Sigma, and CMMI Level 2 standards along with applicable military specifications including RTCA DO-178B and Software Considerations in Avionics and RTCA DO-254, Design Assurance Guidance for Airborne Electronic Hardware. I had to use HP logic analyzers and naturally an embedded RS232 serial port (9600 baud). Early on, I also had an ICE (in-circuit emulator).

Environment: OO C++, Visual Studio, VSS, Intel CAD-UL, HyperAccess Show less