PLEASE NOTE: If you had an account with the previous forum, it has been ported to the new Genetry website!
You will need to reset the password to access the new forum. Click Log In → Forgot Password → enter your username or forum email address → click Email Reset Link.
8 hours ago, Tim said:but what about Bluetooth and thumb drive for updates?.
There is no USB controller support on the WiFi board; all of the processors involved are way too simple to support something that fancy.
The processor on the WiFi board DOES support Bluetooth (as yet untapped)...
I am planning to provide an add-on (for those that don't mind voiding their GS inverter warranty to open it up and solder it in!) to provide an isolated RS-485/MODBUS port on the inverters; that'll also come standard on GS inverters after I get it done. It will make reading stats/controlling the inverter super-easy.
Could you elaborate a bit on the use-case? A whole lot of things are possible, but I'm just trying to figure out exactly what is needed...or if there's already a solution for the problem.
1 hour ago, Sid Genetry Solar said:There is no USB controller support on the WiFi board; all of the processors involved are way too simple to support something that fancy.
The processor on the WiFi board DOES support Bluetooth (as yet untapped)...
I am planning to provide an add-on (for those that don't mind voiding their GS inverter warranty to open it up and solder it in!) to provide an isolated RS-485/MODBUS port on the inverters; that'll also come standard on GS inverters after I get it done. It will make reading stats/controlling the inverter super-easy.
Could you elaborate a bit on the use-case? A whole lot of things are possible, but I'm just trying to figure out exactly what is needed...or if there's already a solution for the problem.
Only thing I can see in useing bluetooth would be for a app connection, sort of like Make Sky blue and Dayly BMS. Which does the same as you already have on WiFi, which just thinking now, MSB already uses Wifi, but, it has a draw back, as it cuts you off the network to connect to it, unless your useing a phone with LTE. With Bluetooth, it would allow to stay on a network and pull updates and such.
But, really, I would just stay with WiFi, since bluetooth can be unsecured more so then WiFi.
Just my thoughts. I'm not the Expert 😛 Thought with bluetooth and two GS inverters they could talk to each other, which I wouldn't know what benfits that would give.
Thought with bluetooth and two GS inverters they could talk to each other, which I wouldn't know what benfits that would give.
We have considered that functionality. Probably a lot more trouble than it's worth, though...
Only thing I can see in useing bluetooth would be for a app connection, sort of like Make Sky blue and Dayly BMS. Which does the same as you already have on WiFi, which just thinking now, MSB already uses Wifi, but, it has a draw back, as it cuts you off the network to connect to it, unless your useing a phone with LTE. With Bluetooth, it would allow to stay on a network and pull updates and such.
If two GS inverters could talk to each other, they'd plot against us. ( Watched " Colossus: The Forbin Project" when it came out 😁)
So Sid, how much codeing you got done thus far? Looks like you goi ng to have time to put in the easy mode for me :P.
12 minutes ago, The Blind Wolf said:So Sid, how much codeing you got done thus far? Looks like you goi ng to have time to put in the easy mode for me :P.
Ha. Nice try. Coding isn't about how fast I can type, but a lot of brainpower into solving issues...or delving into the assembler output to figure out in what way the compiler messed up what I wrote. Oftentimes I'm surprised at how little I've managed to accomplish in one day.
Gotta love it when the compiler does an unsigned comparison on an explicitly declared signed variable, and all along I've been wondering why it isn't working right...figured THAT one out after digging into the compiled output. Why I don't like compilers. But with a project of this scale, it's not really feasible to do in assembler.
Getting a lot of very necessary infrastructure work done--all the stuff that nobody really sees, but you're mighty glad it's there.
Spent the last 2 days characterizing the frequency adjustment code, figuring out how much resolution is possible...and then revamping the rest of the system for the new high-resolution output frequency control. Required for grid-tie-master, not to mention better slave AC sync.
Just got the "grid-tie master auto throttle" implemented this morning (and found that the tranny in my house inverter was wired with reversed polarity), building on the past 2 days' work. I'm currently trying to figure out why the "grid tie slave frequency throttle" doesn't seem to be working. Always reads 0...which obviously isn't right, 'cause the AC input frequency is at 60.06Hz.
After figuring that problem out (and getting the "grid tie slave throttle" tied to output current regulation)...then on to some real battery charge tests (I've done preliminary tests, but not connected to an actual set of batteries).
Sean's raring to test the 12kw prototype in battery charge mode from grid power, so that will be a good test bench.
58 minutes ago, Sid Genetry Solar said:Ha. Nice try. Coding isn't about how fast I can type, but a lot of brainpower into solving issues...or delving into the assembler output to figure out in what way the compiler messed up what I wrote. Oftentimes I'm surprised at how little I've managed to accomplish in one day.
Gotta love it when the compiler does an unsigned comparison on an explicitly declared signed variable, and all along I've been wondering why it isn't working right...figured THAT one out after digging into the compiled output. Why I don't like compilers. But with a project of this scale, it's not really feasible to do in assembler.
Getting a lot of very necessary infrastructure work done--all the stuff that nobody really sees, but you're mighty glad it's there.
Spent the last 2 days characterizing the frequency adjustment code, figuring out how much resolution is possible...and then revamping the rest of the system for the new high-resolution output frequency control. Required for grid-tie-master, not to mention better slave AC sync.
Just got the "grid-tie master auto throttle" implemented this morning (and found that the tranny in my house inverter was wired with reversed polarity), building on the past 2 days' work. I'm currently trying to figure out why the "grid tie slave frequency throttle" doesn't seem to be working. Always reads 0...which obviously isn't right, 'cause the AC input frequency is at 60.06Hz.
After figuring that problem out (and getting the "grid tie slave throttle" tied to output current regulation)...then on to some real battery charge tests (I've done preliminary tests, but not connected to an actual set of batteries).
Sean's raring to test the 12kw prototype in battery charge mode from grid power, so that will be a good test bench.
Will that 60.06 drop down to 59.9Hz under load? That is the one thing I have noticed with every meter we have ever had was that none of them ever read 60Hz when measuring the actual line frequency if they can go down to a tenth of a Hz.
Will that 60.06 drop down to 59.9Hz under load?
It shouldn't. The only way the output frequency can change is if the CPU's internal oscillator changes--while not directly dependent on the output load, the output load might have a minute chance of affecting it...by temperature or other means.
Still tracking down bugs...the line frequency offset measurement routine is working, but somehow it's broken between that and the temperature throttling. Had to fix a dumb bug preventing me from turning down the (brand new) frequency adjustment feature...my house was running at 62.8Hz there for a bit 😉. Fixed that bug, and messed up the GUI in that area--yeah, I'm having fun...
So how is the coding coming along Sid? Looks like you going to have time to make everything work for me :P.
If they keep this delayin' on, I might just be able to get all of it ready for you ;-). Don't like the delays, but hey, we didn't pick 'em. And certainly won't ever use Frontline Freight again.
It's one thing to delay. It's another to lie to the customer.
If they keep this delayin' on, I might just be able to get all of it ready for you ;-). Don't like the delays, but hey, we didn't pick 'em. And certainly won't ever use Frontline Freight again.
Front Line? More like the Back door Freight. "We Like it a Lot, thats Why We Lie, to give you the Best, Of our Rear Back Door Dock, to show, we will Take it all, and Give you None, cause We are a Lie Endless Void of a Company."
😛
We've got the factory pushing them from the one end, and Sean & I hounding them from the other end.
Probably won't make much of a difference, but at least they know that nobody involved is happy.
I half wonder if that's why the tracking now indicates "delivered" with some very suspicious times--because the factory had just had their CA warehouse ask Backline Freight where the shipment was. Then *poof* it says "delivered."
Sleazy alright. Unfortunately it also makes Genetry Solar look bad.
If they aren't there on Monday, it is time for a lawyer to get involved. With it marked as Delivered, they could face fraud charges.
56 minutes ago, Waterman said:If they aren't there on Monday, it is time for a lawyer to get involved. With it marked as Delivered, they could face fraud charges.
Yep, that what I ment. Break out the big guns, we sue, and get remembusted, and sean can order another round on their dime 😛 while we get free inverters lol. . . I'm all for Class Action!!!
Yep, that what I ment. Break out the big guns, we sue, and get remembusted, and sean can order another round on their dime 😛 while we get free inverters lol. . . I'm all for Class Action!!!
Class Action...well, think months and months of delays plus lawyer fees. I think in this case we will get through this mess, and then just never use them again. We're small peanuts.