Open GoogleCodeExporter opened 8 years ago
Hi there,
Yes - I have had issues with the scripts since upgrading to Windows 10 as well.
Note: None of the issues appear to be with the scripts themselves - rather
changes to Windows. The issues appear to be related to Bluetooth driver issues
in Windows 10 and also the Windows Task scheduler. Here are some things I have
done to get the scripts working again:
I have been connecting to my inverter seamlessly until upgrading to W10 and now
I struggle to connect on a regular basis. Mind you, over the past week it has
been pretty good so I think Microsoft are getting that part sorted out. If
connection to the inverter itself appears to be the issue then try updating the
Bluetooth drivers.
To test Bluetooth - open Sunny Explorer directly and see if you can connect.
Task Scheduler.....what a mess that has been! That 'Open With' box was driving
me nuts but I figured out what was going on.
When you create the task, under the 'Action' you put the full path to the VBS
file. Putting this in quotes should hold all the path together but I discovered
that Windows doesn't quite cope with it. If you open your documents folder and
go to the SMA folder, I bet you have a Sunny.txt file sitting there. Stupid
Windows is dropping the end of your path (Explorer/Pvupload_Live.vbs) and
finishing at documents/SMA/Sunny.
That is what the 'Open With' dialog box is for.
To get around it, I have Changed the way the 'Action' tab works in scheduler.
In Program/Script, just put PVupload_Live.vbs
Then in the Start in field put the rest of the path - C:\Users\<
>\Documents\SMA\Sunny Explorer\
That should sort those issues out.
But that's not the end of it.
Once you get it running for a bit, have a look at Task Manager. I found that
the C# compiler (csc.exe) and also the Console Host weren't terminating
correctly and just create task after task....which will obviously grind Windows
to a halt after a while.
Let me know if that is the case for you as well and I'll send you the code I
added to stop that from happening!!
Still get the odd VBscript error pop up but nothing that stops the scripts from
running.
Let me know how you go.
Cheers,
Gary
Original comment by gazgl...@picknowl.com.au
on 20 Aug 2015 at 11:02
Gary,
Thanks for replying.Not had chance to try your suggestions.Attatched are two screen shots of pop ups that occurr after leaving box open for minutes.Am also running V3.1 of your script not V4.0 as I previously stated.
Regards,
Dave
Original comment by dave.hay...@gmail.com
on 22 Aug 2015 at 1:48
Attachments:
Original issue reported on code.google.com by
dave.hay...@gmail.com
on 20 Aug 2015 at 4:41