rsandage

Mint Ubuntu. Thanks

and after doing that, I have 57 int, i get the following output trying to run the .sh file after installing ./launch-escribe-suite 13:42:23.1049: System.IO.FileNotFoundException: Could not load file or assembly 'gdk-sharp, Version=2.12.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f' or one of its dependencies. File name: 'gdk-sharp, Version=2.12.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f' at A.GLL.PO () [0x00027] in <e86c68b7d5a148c3bcf9f4cb27453eae>:0 at A.GAI.CE () [0x00034] in <7f503517b0c24202b94c6c77ff97f7ca>:0 at A.GAI+<>c.SE () [0x00000] in <7f503517b0c24202b94c6c77ff97f7ca>:0 at A.GAI.TE (System.Boolean , System.String ) [0x0017b] in <7f503517b0c24202b94c6c77ff97f7ca>:0 HRESULT: 0x80070002 Unhandled Exception: System.PlatformNotSupportedException: Operation is not supported on this platform. at A.GAI.TE (System.Boolean , System.String ) [0x001b0] in <7f503517b0c24202b94c6c77ff97f7ca>:0 at A.BE.BE (System.String[] ) [0x00011] in <8e2979cefe5e41efada4eb30def4adb6>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.PlatformNotSupportedException: Operation is not supported on this platform. at A.GAI.TE (System.Boolean , System.String ) [0x001b0] in <7f503517b0c24202b94c6c77ff97f7ca>:0 at A.BE.BE (System.String[] ) [0x00011] in <8e2979cefe5e41efada4eb30def4adb6>:0

Any update of the install history you were looking up?

looking to see if there is an updated install/er for Linux Mint 22.1 6.8.0-55-generic kernel, Ubuntu/Deb Based. gtk2-sharp is a huge pain to install, if you can get it all to install. I have the sp57 int run file, but doesnt execute from the menu entry after install. any word on updating the install reqs?

so resoldering that spot, attempt it or wait on evolv's response?

so im wondering if we are thinking the board is fried or if it was a defective? so i have an idea of what is coming.

Wayneo, Yes i can push the positive pin from on top of the 510 (like an atomizer would be attached to it) and on the under side, it returns to flush when i let up pressure from a screwdriver. but i can't push up from underneath. I hope thats what you're having me do. EDIT : The board i purchased was to replace the board that came with my Hadron Pro. So the non-board soldering was not touched.

So using a pre-built coil to create the short in the output gnd connection, while watching Atomizer Analyzer, there was no change to the ohms. then using a screwdriver, and no change. so what's that mean

i know seeing my monitor in the background is a bit difficult, but you can see the ? in there (i think/hope). so with an atomizer attached i get the same thing.

this is what it shows

that's the thing. My battery (a 4S lipo) isnt being seen/read by the board. neither is any atomizer i attached. I have a secondary mod that reads the atomizer with no issue. the charger i have for my lipos is i believe dying, so im not able to charge my lipos there. I believe i have an ohm meter somewhere. so, right now the primary issue would be getting the board to read both an attached battery, and attached atomizer.

here are the best shot i can get of the 510 soldering points. am i the only one that thinks i can see a piece of solder that's laying a crossed the white line there

i will get some pictures of the area that im unsure on my soldering or that i think there might be a "short" possible. when i had the battery in and it was plugged in to my pc, just after that screenshot of the device monitor, i was smelling hot solder and see the temp get up to 102. give me a bit and i will add some pictures to let others see if they can help.

i believe i found the root problem, which i didnt check. so im chalking it up to being blond. I did not check to make sure that all my solder points and areas around such were clean and clear. if you look at the board temp, that give the first clue as to what is going on. I didnt check the soldering around the 510 pads at the top of the board. I took a few pictures with my phone, and i have a crossing connection. so it looks like ill be resoldering the top again. hopefully this will clear up some / or all of the issues.

so this is what i see when Device Monitor is active.