Show us the battery temperature!
P.S. As this is the OVMS technical discussion thread, the reason I ask is because support for the Think EV Zebra battery required a change in OVMS from 8bit signed integer for battery temperature.
jim3cantos
Member
Show us the battery temperature!
P.S. As this is the OVMS technical discussion thread, the reason I ask is because support for the Think EV Zebra battery required a change in OVMS from 8bit signed integer for battery temperature.
Now, it will fit but when driving it rises to 275°C or so, so the temp. value would overflow with only one byte...
Seriously.
Molten salt battery - Wikipedia, the free encyclopedia
P.S. That was the exact same reaction when I first learned of this, and our -128 to +127 celcius range was overflowing. We switched to 16bit integers.
thefortunes
Active Member
dhrivnak
Active Member
Nvbob
Roadster 1256
Texting "GPRS?" to my OVMS returns:
GPRS:
APN:ATT.MVNO
User:
Password:
GSM:AT&T
GPRS: OK
Server: Connected OK
So, maybe the web server just needs a restart?
GPRS:
APN:ATT.MVNO
User:
Password:
GSM:AT&T
GPRS: OK
Server: Connected OK
So, maybe the web server just needs a restart?
I've found this not working for over a day now.
I've really been meaning to set up my own server.
Pulling out my network administrator hat. I think they have bad problems.
The web server is also out, but something strange. Connections get to TCP's ESTABLISHED state but data does not flow. That seems to imply some network configuration issue. There may be some network device which is accepting the connection and forwarding stuff which isn't working. Maybe there is a cloud instance which needs rebooting. The IP address is now of a HK based cloud provider which might be part of the problem.
I've really been meaning to set up my own server.
Pulling out my network administrator hat. I think they have bad problems.
The web server is also out, but something strange. Connections get to TCP's ESTABLISHED state but data does not flow. That seems to imply some network configuration issue. There may be some network device which is accepting the connection and forwarding stuff which isn't working. Maybe there is a cloud instance which needs rebooting. The IP address is now of a HK based cloud provider which might be part of the problem.
hjr
#1291
Problem here too - looks like the server is out. I sent an email to mark directly - will advise if I get an answer tonight.
hjr
#1291
Texting "GPRS?) returns different answer - mine answers not connected:
GPRS:
APN:ISP.CINGULAR
User:
Password:
GSM:AT&T
GSM/GPRS: Not connected (0x0042)
hjr
#1291
dpeilow
Moderator
AEdennis
Active Member
- Jul 23, 2013
- 2,712
- 937
Ok
I have h2owireless and now have the following too:
GPRS: APN:att.mvno User: Password: GSM:AT&T GSM/GPRS: Not connected (0x0040)
GPRS: APN:att.mvno User: Password: GSM:AT&T GSM/GPRS: Not connected (0x0042)
hmmm... That points to something more than just the server, right?
Sorry guys. Seems like our upstream ISP had a routing issue causing high packet loss that affected some connections.
Our average server response time is normally about 270ms (global average). In the past few hours it has been >3,000ms at times. But not bad enough for Pingdom to raise an alert.
Issue has been resolved already, and things seem better now. If still not working for you, please let me know by the [email protected] email address.
Our average server response time is normally about 270ms (global average). In the past few hours it has been >3,000ms at times. But not bad enough for Pingdom to raise an alert.
Issue has been resolved already, and things seem better now. If still not working for you, please let me know by the [email protected] email address.
Nvbob
Roadster 1256
Similar threads
