Jump to content


Full Members
  • Content Count

  • Joined

  • Last visited

Everything posted by Inductores

  1. Not sure if you're developing it, but I am...
  2. I learned some VHDL some years ago, but just the basics... I was thinking about using icestudio: https://github.com/Jesus89/icestudio
  3. Just what the title says. I'm interested to know which DC/DC converter they're using for the >100V Gotway EUC's. Thank you!
  4. Sorry, I didn't provide any info for almost two months... but I'm planning to program it by myself using a FPGA. Just saw a paper using one: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=2ahUKEwi2mtb046LkAhVCDuwKHS7mAWEQFjAAegQIABAC&url=https%3A%2F%2Fwww.mdpi.com%2F2079-9292%2F8%2F2%2F198%2Fpdf-vor&usg=AOvVaw0IquFUWfvusVHp1WeGwe3z I have to do the board layout, but first I need to define all the schematics...
  5. Open the lid and put the magnet in the inner side if the battery allows it (or maybe a thinner magnet)
  6. They're just patching a board instead of doing a new and proper layout, that way they save money using old boards. Like adding an external air conditioner to your car (yes, it works, but not so reliable and poorly aesthetic, right?)
  7. Wait wait wait! Don't tell me they just added an additional board to the old MSX board... Are you serious???
  8. It seems like they also modified the DC/DC converter... you can see it doesn't use a high-frequency transformer anymore. Anyway, I can still see lots of possible improvements to this board.
  9. Welcome to the club. Al least in the spanish group we're quite a lot of people with the same problem (I guess it's a FW problem) The RW Firmware doesn't seem to be quite debugged anyway...
  10. As I say in the title, I'm looking for a cheap-ish damaged EUC board to test and continue with this project: A Ninebot board would be great (as I already have the original FW in my computer), but also opened to other boards. Preferably in Europe (because of shipping costs).
  11. I'm thinking about getting the schematics from a Ninebot One S2 (mine). The problem? Multi-layer board and (probably) need to destroy the board to access to the inner layers Does anybody have a Ninebot One S2 damaged board just to test?
  12. PDF attached. Not very clean but the connections are the same. RockWheel_sch.pdf
  13. I'm sorry, I had no time to update it! I will do it today, I promise
  14. Let me finish the schematic, I can post it at the end of the week. Actually it's already finished, but I need to order the symbols.
  15. STM32F103C8T6 https://www.st.com/en/microcontrollers-microprocessors/stm32f103c8.html
  16. It was a possibility, but as I'm not an expert in programming, I just want the programmer feel comfortable In any case, I would look for a uC with more pins than the used in the Rockwheel board (it's running out of free pins to add extra peripherals like the handle switch, fan control, an external memory for logs...)
  17. Great! So tell me what microcontroller you are comfortable with (STM32F103 or another one) and I can update the board and add more outputs
  18. The original MOSFET driver integrated on the GT16 board is this one: http://fortiortech.com/zh-cn/productshow.asp?id=125&i=3 But I don't like it because: 1) It's a chinese company and I found nothing in the usual european sellers (Farnell, Digikey, Mouser...) 2) The datasheet is incomplete, I don't even know the pinout! So I took a look to different well-known manufacturers and I found these ones: http://www.ti.com/product/DRV8350R http://www.ti.com/product/DRV8353R I already ordered samples and I got them, so I can integrate them in a custom board.
  19. Oh yes, a MSV3 would be a great base to test, and if the batteries are still OK, then it will for sure become alive again. According to the FW, I guess the first thing to be programmed should be the basics: BLDC motor control and data acquisition from the gyroscope (implementing a Kalman filter might be more tricky, but maybe someone can help). I would suggest to use a bigger uC than the STM32F103C8T6, I think the new board should need extra I/O pins to add new functionalities (what about the one implemented on the One Z10?). So the one(s) programming the uC should choose for a proper uC, I'll adapt it to the board.
  20. Hi to all, sadly I couldn't extract the original firmware and no one helped me with the firmware yet. So I was wondering if someone has a damaged board from a Ninebot, Kingsong or Inmotion, due to their FW is available from the manufacturer...
  21. Layout is finished: Yes, I know, some copper traces are different (and the MOSFET capacitors aren not tied to GND in the photo) and I didn't respect the clearance between high potential nets, but I got the complete netlist to get the original schematic. And if you are wondering, yes, this PCB is (if some changes related to the clearance are made) 100% compatible with the original board. I didn't place the silkscreen properly, but is already on my design. So from now we need to decide if we want to implement the same uC (which I think it should because of the lack of free pins for new add-ons) and extras (e.g. an external EEPROM or similar to store data even without power, or a kill switch installed on the EUC handle). Let me some days to organise the schematic (right now it's a bit chaotic).
  22. I attach a photo with the current status of the board layout. I would say 90% done:
  23. The problem with Teensy 3.5 is that the uC comes in a BGA package, being quite more difficult to be soldered...
  • Create New...