Wismec Sinuous V80 and V200

Discussion in 'Suggestions' started by clarkem, Jan 8, 2019.

Tags:
  1. clarkem

    clarkem New Member

    Joined:
    Mar 27, 2018
    Messages:
    10
    Likes Received:
    2
    I see a new mod is on pre-release from Wismec - the Sinuous V80. Does anyone know about this - does it use the STM Microcontroller, for instance? Wondering if there's any prospect for Arctic Fox support?
    It looks similar in shape to the P80, except that it has conventional buttons.
     
    dampfan likes this.
  2. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    Probably, Nuvoton, judging by the VID and PID

    USB\VID_0416&PID_5020\A02014090304
    USB\VID_0416&PID_5020\A02015081302

    You need to wait for the firmware from the manufacturers, or at least understand that with the charge controller
    I have devices.
     
  3. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Added support for Nuvoton-based V80, test build: 190221

    Added support for Nuvoton-based V200, test build: 190301

    P. S. Added V200 to the topic name as well.
     
    #3 maelstrom2001, Feb 21, 2019
    Last edited: Mar 1, 2019
    LoLaTiOn likes this.
  4. clarkem

    clarkem New Member

    Joined:
    Mar 27, 2018
    Messages:
    10
    Likes Received:
    2
    Thanks for that, must buy one now!
     
  5. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    LoLaTiOn likes this.
  6. LoLaTiOn

    LoLaTiOn New Member

    Joined:
    Mar 7, 2019
    Messages:
    4
    Likes Received:
    0
    My v80 Waiting for device...

    L'appareil HID\VID_0483&PID_5750\7&350780d5&0&0000 n’a pas été migré à cause d'une correspondance partielle ou ambiguë.

    Dernier ID d'instance d'appareil : USB\VID_046D&PID_C016\5&2301df1d&0&4
    GUID de classe : {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
    Chemin d'accès d'emplacement :
    Rang de la migration : 0xF000FFFFFFFFF120
    Présent : false
    Statut : 0xC0000719
     
  7. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    [​IMG]
     
    LoLaTiOn likes this.
  8. LoLaTiOn

    LoLaTiOn New Member

    Joined:
    Mar 7, 2019
    Messages:
    4
    Likes Received:
    0
    Thank you for the quick reply
    I told myself that if it's not good it must be because it's based on STM32
    I find it disappointing that some v80 works on Nuvoton and other STM32
    It's even frustrating for anyone interested in artic fox I'm out of luck
    The official update works on both Nuvoton and STM32 version

    No future support for STM32?

    Continue your good work
     
  9. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Hello!
    Apparently, we have to decide on STM support. The first supported box should be Pico X or Espion Tour - as they are STM only and there is a guarantee that we'll get STM32 inside.
    If there are enough people who want to see ArcticFox on at least 4 listed boxes (2 above and 2 in this thread), we'll announce a fundraising for purchase one or two boxes.
     
    Anx.07 and LoLaTiOn like this.
  10. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    maelstrom2001

    What is this? On the oscillogram test for Nickel. Why does a voltage break occur, I guess at the moment Boost turns on?

    [​IMG]

    There is no such thing on the stock firmware. And the resistance is measured by one voltage.

    [​IMG]

    And note that the stock firmware 0 is below. This is because at ArcticFox I discovered that the voltage in idle mode is ~ 118 mV. I thought it was my problem with the device and I put 0 on it. It turned out that there were no problems with the device. You for some reason always have 118mV on the connector.

    If interested, I have waveform records from the latest firmware and from Arcticfox to V80. There are still many strange moments. You should have looked at them. It will be necessary to put the program free.
    Where to find me you know :)
     
    spado likes this.
  11. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Flash recent build 190310 and add CSV data from Device Monitor in both modes (TC and VW). Oscillogram of the output voltage is not enough to clarify the causes of problems.
     
    #11 maelstrom2001, Mar 12, 2019
    Last edited: Mar 12, 2019
  12. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    spado likes this.
  13. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Thank you! It's hard to say what exactly goes wrong, but there is a suspicion on improper buck-to-boost mode transition. Tomorrow will take this part from newer firmwares and upload test build. It seems that starting from Pico S DC-DC converter management was changed significantly.
    As for the small constant voltage on the connector in the standby mode, this will be postponed a bit.
     
  14. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    ArcticFox: 190313, 190314, 190315
    Affected boxes: V80, V200, Ultex, CB-80, Pico S, Primo Fit, Active, Squeeze 2, probably Luxotic MF.

    RedPanda: 190313, 190315
    Affected boxes: both.
     
    #14 maelstrom2001, Mar 13, 2019
    Last edited: Mar 15, 2019
    spado likes this.
  15. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    maelstrom2001
    It will be easier if I understand exactly what and where to check.
    Since I practically cannot work on this forum, I can write on ecigtalk, or https://vk.com/25o3o2o9
     
    spado likes this.
  16. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Do the same Nickel test on V80, and that's enough.
     
  17. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    spado and maelstrom2001 like this.
  18. maelstrom2001

    maelstrom2001 Developer
    NFE Team

    Joined:
    May 4, 2017
    Messages:
    1,082
    Likes Received:
    993
    Nice, thank you for figuring out and pointing to this issue.
    Noise in the boost mode is terrific, but I don't want to do some experiments on it now, just using OEM BBC routines. If JWEI will do something with it in firmware updates, I just keep eye on it. In most cases the manufacturer know best.

    P. S. By the way, in V200 firmware found code that prevents sleep mode until charge end, using signal from external hardware charger. Did the same trick for Luxotic DF, probably now it should charge correct without "USB No Sleep" option (starting from 190301 build).
     
    #18 maelstrom2001, Mar 15, 2019
    Last edited: Mar 15, 2019
    spado likes this.
  19. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    V200 I plan to start seriously testing on Monday, if I have time to write a review SMOK on Sunday.
    But the first tests of charge, which I did immediately after receiving, I really did not like.
    Let's see, maybe fixed in the new firmware.
     
  20. Janishewskiy

    Janishewskiy Active Member

    Joined:
    May 17, 2017
    Messages:
    142
    Likes Received:
    26
    maelstrom2001

    Now started testing the V200.
    SC8922A charge controller detected on board
    https://datasheet.lcsc.com/szlcsc/Southchip-Semicon-SC8922QDLR_C252426.pdf
    On the Wismec firmware, there is such a beautiful charge curve (I haven’t yet built my own charge chart, it will be in review)
    [​IMG]
    And the charge is not interrupted and ends completely.

    On your firmware before testing, I plan to fully balance the cells in external charging, because the algorithm still does not depend on you.

    Question: What is Device too Hot? I could not even take 25 voltage measurements in pulses of 2-3 seconds at a time, I had to take a break. I thought it was a stock firmware feature, but the same behavior on Arcticfox.
    The device did not even heat up, it seems to me that this restriction should be increased. And Wismec I will write about it, because under normal use this message will appear constantly.

    P.S. Remove restrictions, I wanted to write it yesterday and could not