Correct. V5 has a different, and very much faster method to convert to an xy grid that does not use UTM and convergence angle. V5 just ignores those upon opening.
But now that i think about it, if it was made in 4.3 and opened in v5, you should be able to open again in 4.3. Want to try that?
Ah, now this (i2c frequency) could be why I thought I’d got something slightly wrong when I implemented my own BNO085 code a while ago. Steer did at times seem jumpy. I tried math’s code a week or so ago and it actually made no difference.
So the wire.clockSpeed(400000) instruction is being overridden by the old school TWBR setting and could be omitted entirely.
I saw and liked that code. Confusingly Sparkfun and adafruit BNO085’s have differing addresses. Neat way of catching what could be a “but which BNO085 do you have?” DiscourseHub and telegram nightmare!
yes I have modified the ino for v5 to connect a 0-5v or 4-20 ma sensor using channel 3 of the ads115 the triggering threshold is adjustable by adjusting the encoder but something is wrong it worked fine in the old version
if (aogSettings.ShaftEncoder)
{
SteeringWheelPressureReading = ads.readADC_SingleEnded(3);
SteeringWheelPressureReading = (SteeringWheelPressureReading >> 3); //bit shift by 3 0 to 3320 is 0 to 5v
if ((pulseCount >= aogSettings.PulseCountMax)||(SteeringWheelPressureReading >=(aogSettings.PulseCountMax100)))
{
steerSwitch = 1;
currentState = 1;
previous = HIGH;
new verssion
if (steerConfig.ShaftEncoder)
{
adc1.setMux(ADS1115_REG_CONFIG_MUX_SINGLE_3);
SteeringWheelPressureReading =adc1.getConversion();
adc1.triggerConversion();//ADS1115 Single Mode
SteeringWheelPressureReading = (SteeringWheelPressureReading >> 3); //bit shift by 3 0 to 3320 is 0 to 5v
if ((pulseCount >= steerConfig.PulseCountMax)||(SteeringWheelPressureReading >=(steerConfig.PulseCountMax100)))
{
steerSwitch = 1;
currentState = 1;
previous = HIGH;
}
}
There seems to be something wrong with the GPS communication. “No GPS!, I’m Lost” rotates most of the time.
The are no problems with GPS in version 4.3.10.
I Tried “LogNMEA”, but “NMEA_log.txt” is empty.
I can’t write to the autosteer arduino nano inside agopen.
I loaded the autosteer_USB_20.ino with succes into nano. The com does connect in agio. The roll, heading and steer angle are coming through correct.
When I try to write any change (like invert WAS) from inside ageopen a screen pops up “autosteer port, module configuration”. What am I doing wrong, can’t find where I could set anything for standard usb connected autosteer module besides in agio which seems to work correct
Will it keep my boundry and ab lines intact from 4 to v5 ? I want to use those if I can
Edit
I can set up vehicle and implement, and save as. Now if I change settings in them, there is no save button. I have to save as again. If I switch vehicles by loading xml, then all unsaved setting are gone. Along with steer settings.
Can we have a save settings button that just saves to current vehicle ? Maybe save on exit with the green OK button in the bottom right as you close the page ?
If it is saying this, then the settings are sent. There is no confirmation from the Steer module anymore that it got the update you have sent. if the WAS reads the other way now, it worked. I should change the Text in the little info window to say Data has been sent, more accurately say what is going on.
ummmmm not sure, when you connect in the connection page, is nmea showing up in the text box in AgIO? Flashing by kind of quickly. Set high enough baudrate as well.
I mean the steer settings. I set up a vehicle and save it. Later today I have to adjust my left right offset, then add a little gain. Now if I don’t save vehicle as again and switch vehicles, I lose all the settings I put in today. If it would save to that vehicle on exit of the setup page would be best. Right now nothing is saved since the save as when you make a new vehicle. If you dont put that tablet in another tractor, I guess you would never know.
You have v5 set up so that I could grab the tablet, and go to any tractor, load vehicle, and load farm, and go, if it would save.
Thanks a lot for your reply! I have been “mislead” by the textbox then.
I will try it this evening!
I can’t find the “drive” button anymore, to set the steer angle sensor zero when hit the drive button on o degrees and drive a straigt path. What is the new method to exact zero it out?
GPS is simpleRTK2B-F9P V3. Baudrate is 115200.
At connection page, nmea messages are updating all the time whether there is “No GPS!” or not. Behavior is more or less random. Sometimes GPS stays on most of the time sometimes not.
Again there are no problems with other computer. There might be different USB serial driver.
I don’t know what kind of communication there is from AGIO. There are all kinds of services and programs running on this computer with the problem.
IT needs a good network card since it uses the loopback (internal) ip address 127.0.0.x to talk back and forth to aog. That might be an issue on that computer, so maybe try everything network related off?
It looks I have a communication problem too, because the gps doesn’t give accurate position in aog, while having stable rtk fix, simplertk2b f9p. The arrow on the right botom of the screen flickers red/purple very fast, when I toggle the steer switch it flickers purple/yellow. Baudrate set to 115200 . Also steer angle isn’t stable when standing stil (jumps 1 degree back and forth)
With exact the same system I just worked 3 hours without problem with V4.3.10
edit: tried different notebook, tried to set gps from 8 to 10Hz, tried different nano, all no difference.