Machsupport Forum

Third party software and hardware support forums. => NC Pod => Topic started by: apollonono on December 20, 2011, 05:25:35 AM

Title: I have tested on several samples
Post by: apollonono on December 20, 2011, 05:25:35 AM
Results of the 2031 update

Installing the SD Memory
S/N Number power of USB_BUS RNumber Display character

S/N 1017  5V power jumper Error! try again update 28 0% NG
S/N 1035  5V power jumper Error! try again update 28 0% NG
S/N 1044  5V power jumper Error! try again update 28 0% NG
S/N 1038  5V power jumper Error! try again update 28 0% NG
S/N 1043  5V power jumper Error! try again update 28 0% NG

S/N 1678  R228 Error! try again update 25 41% NG
S/N 1642  R48 Error! try again update 25 50% NG

S/N 1641  R168 31 0% OK
S/N 1675  R204 31 0% OK
S/N 1667  R276 31 0% OK
S/N 1671  R168 31 0% OK
S/N 1672  R240 31 0% OK
S/N 1674  R240 31 0% OK

Title: Re: I have tested on several samples
Post by: apollonono on December 21, 2011, 02:48:14 AM
Conditions for successful firmware update

Background I tried to experiment further.

Had earlier firmware version from the following:.
2012,2014,2018,2020,2024,2025,2027,2031

There are also several versions of the USB driver
LibUSB-under the WIN32 Driver,
Removing an existing driver or ncPOD
Add Hardware in Control Panel
Adding new hardware, you may incorporate by.

Board update was successful, view on the S / N is avoided.
Numbers may appear different from the displayed number to the substrate.

It connects the USB-5V supply from VBUS.
Land there is a way to enliven the solder resistance to using the wire.
Red LED lights up when you connect a USB

The V2031 is a need to update two drivers ncPOD.

If you see a USB interface and send back an invalid -1
Good run.

Sometimes less than a 5V power supply failure.

If the red LED is not lit will show success by doing the following update.

Might fit into an older version of the MACH3.
The V2027 is a need to update drivers ncPOD one.
ncPOD DRIVER ROOT \ LIBUSEDVISES \ 0008
But in another window appears with failure and try again.
I could not actually update confirmed.
Have not confirmed compatibility with MACH3.

Best regards
Title: Re: I have tested on several samples
Post by: apollonono on January 08, 2012, 07:31:30 PM
firmware was up experiments ncPOD.

Greetings
Dedicated to the owner of the ncPOD curl results.

There are several different versions of the board.
There are things with and those with a red light,
Unrelated to the success of the update.
Five failed to succeed 11.

Requires two drivers for the USB device
"Libusb-Win32 Devices" required under the
One is "ncPOD" name is a hypothetical and does not disappear even if you disconnect.
One is "ncPOD" name is a practical, or appear and disappear through and out.

To monitor those provided by Microsoft,
Start the batch file "Show hidden devices over show" Please to ON.
"Set devmgr_show_nonpresent_devices = 1
cd \% SystemRoot% \ System32
start devmgmt.msc "

http://den-nekonoko.blog.so-net.ne.jp/2012-01-08-1
A virtual driver while connected to USB, as the image sequence,
Perform the hardware installation.
The image type is confusing because the Japanese would, please determined by analogy.

Driver installation is practical to install the device while connected to USB "ncPOD.inf" by showing the installation - you can file.

The virtual driver "Device Instance ID" is
Was active in the following two types.
"ROOT \ LIBUSBDIVICES \ 0008" "ROOT \ UNKNOWN \ 0000"

Practical instance of the driver is "USB \ VID_16C0 & PID_056F \ 0001"
The contents of the USB driver coming from the whole range examined were similar in OEMTEC.

The FDD is a hidden device known to the PC after connecting the USB,
Enables the update.

The firmware can be updated, "2031" and "2027" There are,
"2031" and can be updated, and if it is not a sign of success than the
Been successfully updated, can be operated from the MACH3.
"2027" not to work only, and can appear successful update
The other window is displayed as Coach No. Please try again and actually a failure,
Can be run from MACH3.

The problem is probably in the errata of the version of the MPU.
Once we hope to improve anyway.
Best regards