SkyRC — IFA 2014 — MC3000 charger-analyzer

[Ravel]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Have you lost your programming after the update?

Yes, indeed (as expected)

 

[TinderBox (UK)]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I reset my charger to default settings before and after the flash just in case, though this seems not to be needed.

John.

 

[ilgrank]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

W10 x64: updated without any problem.
Now how just do I stop the not-so-hidden game?(edit: I mean the breakout-style 'screensaver' with a ball making a beep every time it hits the brick) It makes continuous beeps whenever I leave the charger powered up doing nothing...

 

[tjh]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

W10 x64: updated without any problem.
Now how just do I stop the not-so-hidden game?(edit: I mean the breakout-style 'screensaver' with a ball making a beep every time it hits the brick) It makes continuous beeps whenever I leave the charger powered up doing nothing...

Read the updated manual for how to turn it off?

 

[light-wolff]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

... I brought it up as an example for the reduced starting charge current if a battery is below certain voltage(3.2v on the MC3000 vs 3.0v on the xtar VC4).

I second that. Full charge current should be applied at least from 3.0V onwards, not 3.2V.
It takes forever on a discharged high-current ("IMR") 26650 to reach 3.2V and finally go to full charging current.

 

[ilgrank]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Read the updated manual for how to turn it off?

Yes, I've read the updated manual, and I don't want to turn off system beeps, just the 'game' ones. I don't want my idle charger to be beeping all the time.
I've missed some part?

 

[tjh]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Yes, I've read the updated manual, and I don't want to turn off system beeps, just the 'game' ones. I don't want my idle charger to be beeping all the time.
I've missed some part?

Yeah.
Turn off the screen saver.

 

[tjh]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Yeah.
Turn off the screen saver.

I haven't updated mine yet, I should point out.
But if the screensaver BEEPS every time it's in use, that is the stupidest thing I have ever, ever heard of. I can't believe that krisel would have signed that off...
I hope I misunderstand your post

 

[Curetia]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

No the screensaver beeps every few seconds when the screensaver is activated
But while you charge or discharge the display won't go into the screensaver mode.

 

[DeJaVu]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I second that. Full charge current should be applied at least from 3.0V onwards, not 3.2V.
It takes forever on a discharged high-current ("IMR") 26650 to reach 3.2V and finally go to full charging current.

Ohhh, as i dont use 26650(but plan on getting few soon) didnt even think of that group of people.*
Must be even more dissapointing charger feature for 26650 than with charging 18650.
But im sure(at very least hope) theyll address this limitation for IMR/INR users.

@kreisl, you probably missed it, but in my previuos post i asked you about some info about the charger terminals.
I know you mentioned in one of your posts that SkyRC is improwing the design/materials of the charger with every revision/batch.
So i would like to know did SkyRC solve/planing to solve the problem with the terminals? By which i mean the terminals not being able to make propper contact with many flat top cell models(in my case more than 50% i own), and being forced to use magnets or raising the battery.**

Even though this isnt mentioned here much as i suppose most of the flashaholics use button top batteries, or panasonic flattops(do they all have bit raised + as my 18500 panasonic?).

I might be the only one writing here about it, but im sure that im not the only one that has this issue and finds this as a minus for the charger.

 

[Albert_]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Windows 10 reinstalled. and nope. No dice, same issue. I don't know how you guys manage to get it to work with Windows 10. It is not working for me. I willing to bet that this will work on Windows 8

Your USBView report appears nearly identical to mine under Windows Vista 64-Bit.

I did find a few differences.

Windows 10:____________________________________

Device Description : USB Input Device
Driver : C:\Windows\System32\drivers\hidusb.sys (Version: 10.0.10240.16384 Date: 2015-07-10)

Windows 10 additionally includes:
a "--------------- Connection Information V2 -------------"

Location IDs : PCIROOT(0)#PCI(1D00)#USBROOT(0)#USB(2), ACPI(_SB_)#ACPI(PCI0)#ACPI(USB0)#USBROOT(0)#USB(2)
Container ID : {979c59fa-3a88-11e6-9bc4-2c8158e5a3c0}

Windows Vista:__________________________________

Device Description : USB Human Interface Device
Driver : C:\Windows\system32\DRIVERS\hidusb.sys (Version: 6.0.6002.18005 Date: 2009-04-10)

_______

Differences found within USB MC3000 connection reports Windows 10 vs Windows Vista

Device description "USB Input Device" (Windows 10) vs "USB Human Interface Device" (Windows Vista)

The hidusb.sys Driver versions are different (Version: 10.0.10240.16384 Date: 2015-07-10)-(Windows 10) vs (Version: 6.0.6002.18005 Date: 2009-04-10)-(Windows Vista)

Windows 10 also includes V2 Connection Information, a Location IDs and Container ID
__________________________

There are a few things you can try:

1. In device manager under "Universal Serial Bus Controllers" there will be several "Root Hubs". You need to go into the properties power management tab of each "Root Hub" and turn off "Allow computer to turn off this device" and/or deselect any power options for the root hub.

Unless you know which root hub usb port is being used for the MC3000 you need to deselect power functions for all the root hubs.

2. You can try up or down grading USB drivers but requires some knowledge of the history versions of Windows 10 USB drivers.

3. Sometimes powering down your PC and the USB device then repowering the usb device, making a connection to the PC and then repowering the PC helps to establish a USB connection to a USB device that's having problems or isn't recognized by the OS.

 

[ilgrank]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I haven't updated mine yet, I should point out.
But if the screensaver BEEPS every time it's in use, that is the stupidest thing I have ever, ever heard of. I can't believe that krisel would have signed that off...
I hope I misunderstand your post

You got it perfecty right: the screensaver beeps every time the ball hits the logo, ie every 2-3 seconds.
And yes, one of the most annoying things I ever seen
I've found the menu to disable the screensaver tho.. it would be nice to just disable the screensaver SOUND instead of disabling the screensaver altogether.

 

[gyzmo2002]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

Yes, indeed (as expected)

Thank you. Update done in less than a minute on Windows 7 Pro 64bits via usb2.

 

[MarioJP]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I don't know what to do. Fresh installed Windows 10. Windows sees that some HID device is detected. This can't be this hard. Just plug and flash lol. I am coming to the conclusion that the program is not really compatible with Windows 10. If PC link can't detect the charger. I highly doubt that the flash program can detect it either. I did came up with a workaround. I could Boot Winpe 8 and flash from there. Just not sure how safe would that be since WinPE is a stripped down version of windows and it is custom, but at least the firmware program sees the charger. Or i could dual boot with Windows 8 or 7. For those that got it to work on Windows 10. Must be a special driver that i am not aware of because from a fresh install. No dice lol.

USB Device Tree Viewer on Win8PE. Ignore why Windows is on X drive lol, but it works.





=========================== USB Port1 ===========================


Connection Status : 0x01 (Device is connected)
Port Chain : 6-1
Properties : 0x01
IsUserConnectable : yes
PortIsDebugCapable : no
PortHasMultiCompanions : no


======================== USB Device ========================


+++++++++++++++++ Device Information ++++++++++++++++++
Device Description : USB Input Device
Device Path : \\.\usb#vid_0000&pid_0001#5&2a0ad64e&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Device ID : USB\VID_0000&PID_0001\5&2A0AD64E&0&1
Driver KeyName : {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0000 (GUID_DEVCLASS_HIDCLASS)
Driver : X:\Windows\System32\drivers\hidusb.sys (Version: 6.3.9600.16384 Date: 2013-08-22)
Driver Inf : X:\Windows\inf\input.inf
Legacy BusType : PNPBus
Class : HIDClass
Class GUID : {745a17a0-74d3-11d0-b6fe-00a0c90f57da} (GUID_DEVCLASS_HIDCLASS)
Interface GUID : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
Service : HidUsb
Enumerator : USB
Location Info : Port_#0001.Hub_#0006
Location IDs : PCIROOT(0)#PCI(1D00)#USBROOT(0)#USB(1), ACPI(_SB_)#ACPI(PCI0)#ACPI(USB0)#USBROOT(0)#USB(1)
Container ID : {5e0ac713-3afd-11e6-824c-0024beac9d44}
Manufacturer Info : (Standard system devices)
Capabilities : 0x84 (Removable, SurpriseRemovalOK)
Problem Code : 0
Power State : D0 (supported: D0, D2, D3, wake from D0, wake from D2)
Child Device 1 : HID-compliant device
Device ID : HID\VID_0000&PID_0001\6&36931F7A&0&0000
Class : HIDClass


---------------- Connection Information ---------------
Connection Index : 0x01 (1)
Connection Status : 0x01 (DeviceConnected)
Current Config Value : 0x01
Device Address : 0x01 (1)
Is Hub : 0x00 (no)
Number Of Open Pipes : 0x02 (2)
Device Bus Speed : 0x01 (Full-Speed)
Pipe0ScheduleOffset : 0x00 (0)
Pipe1ScheduleOffset : 0x02 (2)


--------------- Connection Information V2 -------------
Connection Index : 0x01 (1)
Length : 0x10 (16 bytes)
SupportedUsbProtocols : 0x01
Usb110 : 1 (yes)
Usb200 : 0 (no)
Usb300 : 0 (no)
ReservedMBZ : 0x00
Flags : 0x00
DevIsOpAtSsOrHigher : 0 (Is not operating at SuperSpeed or higher)
DevIsSsCapOrHigher : 0 (Is not SuperSpeed capable or higher)
DevIsOpAtSsPlusOrHigher : 0 (Is not operating at SuperSpeedPlus or higher)
DevIsSsPlusCapOrHigher : 0 (Is not SuperSpeedPlus capable or higher)
ReservedMBZ : 0x00


------------------ Device Descriptor ------------------
bLength : 0x12 (18 bytes)
bDescriptorType : 0x01 (Device Descriptor)
bcdUSB : 0x200 (USB Version 2.00)
bDeviceClass : 0x00 (defined by the interface descriptors)
bDeviceSubClass : 0x00
bDeviceProtocol : 0x00
bMaxPacketSize0 : 0x40 (64 bytes)
idVendor : 0x0000
idProduct : 0x0001
bcdDevice : 0x0200
iManufacturer : 0x01 (String Descriptor 1)
Language 0x0409 : "STMicroelectronics"
iProduct : 0x02 (String Descriptor 2)
Language 0x0409 : "STM32 Custm HID"
iSerialNumber : 0x03 (String Descriptor 3)
Language 0x0409 : "Uÿop?SI(g" *!*CAUTION contains character below 0x20 *!*CAUTION contains character above 0x7E
bNumConfigurations : 0x01


------------------ String Descriptors -----------------
------ String Descriptor 0 ------
bLength : 0x04 (4 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language ID[0] : 0x0409 (English - United States)
------ String Descriptor 1 ------
bLength : 0x26 (38 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "STMicroelectronics"
------ String Descriptor 2 ------
bLength : 0x20 (32 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "STM32 Custm HID"
------ String Descriptor 3 ------
bLength : 0x1A (26 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "Uÿop?SI(g" *!*CAUTION contains character below 0x20


---------------- Configuration Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x02 (Configuration Descriptor)
wTotalLength : 0x0029 (41 bytes)
bNumInterfaces : 0x01
bConfigurationValue : 0x01
iConfiguration : 0x00 (No String Descriptor)
bmAttributes : 0x80
D7: Reserved, set 1 : 0x01
D6: Self Powered : 0x00 (no)
D5: Remote Wakeup : 0x00 (no)
D4..0: Reserved, set 0 : 0x00
MaxPower : 0x20 (64 mA)


---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x00
bAlternateSetting : 0x00
bNumEndpoints : 0x02 (2 Endpoints)
bInterfaceClass : 0x03 (HID - Human Interface Device)
bInterfaceSubClass : 0x01 (Boot Interface)
bInterfaceProtocol : 0x02 (Mouse)
iInterface : 0x00 (No String Descriptor)


------------------- HID Descriptor --------------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x21 (HID Descriptor)
bcdHID : 0x0101 (HID Version 1.01)
bCountryCode : 0x00 (00 = not localized)
bNumDescriptors : 0x01
Descriptor 1:
bDescriptorType : 0x22 (Class=Report)
wDescriptorLength : 0x001B (27 bytes)
Error reading descriptor : ERROR_GEN_FAILURE


----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x81 (Direction=IN EndpointID=1)
bmAttributes : 0x03 (TransferType=Interrupt)
wMaxPacketSize : 0x0040 (64 bytes)
bInterval : 0x0A (10 ms)


----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x01 (Direction=OUT EndpointID=1)
bmAttributes : 0x03 (TransferType=Interrupt)
wMaxPacketSize : 0x0040 (64 bytes)
bInterval : 0x10 (16 ms)

 

[Albert_]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I don't know what to do. Fresh installed Windows 10. Windows sees that some HID device is detected.

I assume you have 1. tried connecting to other USB Ports? 2. disconnect all other usb devices from the PC while attempting to perform the update?
3. Tested other USB 2.0 devices under Windows 10, possibly a USB device such as a cell phone, etc. that needs to talk / communicate bidirectionally to the PC ?

Other things to try. Boot to Windows 10 safe mode and initiate a USB connection. If usb connection is available initiate the firmware upgrade under Safe Mode. If successful then test the MC3000 usb connection using the PC-Link software.

Try booting to another Windows version if possible. If you have a Windows XP version that can be booted from another partition or drive?

Upgrading firmware instructions:

1. Remove all batteries, disconnect all USB cables and power cables, deactivate Bluetooth
everywhere, close and exit all software and hardware on your Windows PC which access the
USB communication. Connect the device to its power supply.

2. Use the PC Link premium USB data cable to connect the device to your Windows PC. In
many cases no further device drivers or USB drivers need to be installed. Launch the official
PC Link software and test the functionality of the software.

3. (N/A)

4. Depending on the firmware version the updating process may conclude with an automatic
soft reset, or not. The user is at liberty to check the update success and, if needed, perform a
manual Factory Reset on top, see GSV.

*Additional* instructions for applying the 1.11 firmware update:

0. Application of this firmware updater *.EXE has been approved on WinXP SP3. All other Windows PC
operating systems have not been approved for the application of this firmware updater *.EXE

 

[gyzmo2002]

Someboby has tried to disable the bip sound?

If I set the key bip off, the key bip is disabled, that is correct but it disable also the system beep too even if the System Beep is set to ON...??

The System Beep is when a status is completed and when there is a system alarm? I think so.

Key Beep OFF and System Beep ON, I don't have the 10 beeps when the charge is completed...

 

[MarioJP]

Yaaaayy!! Finally. Ended up dual boot with Windows 8.1 after all, and that worked! Firmware successfully updated on both my chargers. The thought of trying different OS's just for this is a bit too much bit at last. lol



Ok, i can see how the screensaver can get annoying really fast because of the beep. For now, i turned off the screensaver.

 

[Sharkie]

Re: SkyRC — IFA 2014 / CES 2016 — MC3000 charger-analyzer

I finally was able to update with Windows prof. Service pack 1. Downloaded and used the USB view software and a few tries. Had error 1 but at a point it just started and worked.

I had bricked my charger but the enter button information helped.

Thanks for all the information, without the help and hints here i was really sure I had to buy a new one !

 

[Ravel]

Re: http://tinyurl.com/mc3k-list

The below comprises a redacted filtered list of reasonable realistic feasible likable serious strong or urgent suggestions, nothing too distant from the present state of things. ...

[h=2]List quoted above at http://tinyurl.com/mc3k-list[/h] Hello,

Here is a FW improvement request to be seconded please (or questionnned/challenged).
AFAIK not yet discussed.
Lets call it OnCapacityNextJump
Thanks. Regards


WHAT
Jump to next step (during refresh or cycle) when a userset capacity (OnCapacityNext)
is reached during charging.
For NiMH. Not thought of the needs on other chemistries.
By the way if criterion deltaVPeak is reached first, charger would continue as in today FW.

WHY
a) Dealing with old NiMH that do not stop on delta V peak.
b) Healthy batteries that I do not want to fully cycle, to increase lifetime, or be quicker (shorten charging cycle)
c) A way to implement early charging termination-continuation, for whatever reasons.


HOW
In advanced mode obviously, as a program option.
Some suggestions, in SPV, either:


1) When the actual CAPACITY parameter is set to off.
A new line just below with a parameter called OnCapacityNext becomes available for edit.
(same ranges of mAh as CAPACITY, unless somebody see a safety issue).
Safety capacity cutoff possibly disabled in this implementation.
Maybe easier to update FW code this way.


2) The actual CAPACITY parameter is set to a user value, normally.
Then a new line just below with a parameter called OnCapacityNext
becomes available for edit, only two choices possible {OFF | ON} or
it could display {OFF | CAPACITY - 100 mAh} where CAPACITY - 100 would be
calculated automatically. This way cuttoff on capacity may still be implemented.
I assume a 100 mAh difference is enough.
If only ON was displayed, the manual would explain that
OnCapacityNext = CAPACITY - 100 mAh
Would work only from 200 mAh then.


3) The capacity parameter could be set to a positive, OFF, or negative value.
Would be confusing and negative CAPACITY would have here a different meaning.
In this implementation one could use
capacity as a safety cutoff only if there was a hardcoded
CAPACITYcutoff = Abs(CAPACITY)+100
This implementation only suggested as a way to save one line in SPV if ever needed.

 

[tjh]

Re: http://tinyurl.com/mc3k-list

Firmware v1.11 update went fine on Windows 10 x64.

I plugged the charger directly into my laptop, checked with MC3000, loaded up the Update app and it went without a hitch.

Thanks all!