So in my testing, If the Data wires are not right the computer doesn’t detect the device at all. Regardless, that’s all very helpful, I’m going to resolder the cable and trace connections to the threads. Thanks.
maelstrom2001 I've been using AF on the Grus for over a year. I bought another one recently with the 2.0 chip but for some reason, it keeps saying "device too hot". I have tried changing temp to Int in settings but, it still says "device too hot". Any ideas?
Hmm, it is absolutely normal. But while using the temperature raises smoothly, or there is some random peaks? It seems that is 2.0 issue: https://nfeteam.org/forum/threads/l...btb-thelema-centaurus.4905/page-18#post-13679
Overheating of the MCU really bothers me. Int 170F is really too much. I can add option to switch off this protection at all. But... under your responsibility
I'll do some testing, I don't mind the risk! Is it something with the software not reading right or is it actually getting hotter? Also whats the difference between Ext and Int? Thanks again!
Ext channel is for thermistor placed on the PCB, Int is internal MCU temperature sensor. In your case Int is also getting hot. There should be no defference between MCU's used in old and newer revisions, so it looks like MCU really overheats.
Go to "Main Menu" -> "Settings" -> "Advanced" -> "Temp": short Fire button click - switch between Int and Ext, as earlier; long press Fire button - enable/disable (Off) sensor. Build removed for safety reason.
So I did some testing and it looks like the MOSFETs get hot and trigger the error. I tried the Ursa boot and it seemed to keep the board at 110 when firing. What's the difference between the Ursa and Grus boot? If the mod doesn’t overheat when on the Ursa firmware could that means its a software issue?
Thank you! Is your Grus 2.0 working correctly with Ursa boot? Early Grus and Ursa have different pinouts. I'll take a look for the OEM 2.0 firmware (post #341), maybe I missed something.
You're absolutely right, it is software issue. Thank you! Here is the difference between early and newer PCBs: Indeed, Grus 2.0 should be flashed with Ursa bootloader because of hardware changes.
Glad there's a solution, is there any need to edit the Ursa bootloader or should it work without issues?
Nope. Different bootloaders are intended for hardware identification in ArcticFox since it is unified. As Grus 2.0 have the same hardware as Ursa, the only issue is "wrong" device name in Firmware Updater. I can, of course, make a separate boot for the updated Grus and add it to the firmware, but is it worth it? P. S. For now I just added a warning about it.
Hey, Thanks for all your work in the firmware and your time. I was wondering if you knew if Lost vape thelema quest 200W can be flashed with red panda?Here it is implied it can be but not sure, Is it just a normal flash like a wismec or joyetech or anything else needs to be done? Thanks again,
