SiK firmware 1.8.1 released

[Andrew Tridgell]

Hi All,

Michael Oborne found an issue with changing settings with MP in the 1.8
release, so I have put out 1.8.1 with a workaround. Basically the "RTI5"
command was not working when MAX_WINDOW was small for low latency mode.

I've put in a workaround for now. The workaround involves a couple of
changes:

- removed the spaces in the ATI5 and RTI5 output, so the size of the
response is less than the 252 byte packet size limit

- added new syntax to dump ranges of register values. You can use
"RTI5:7:13" to dump registers 7 to 13. This will allow config tools
to re-fetch any missing register values is the command fails to get a
complete set (which will happen sometimes)

Michael, could you let me know if this is sufficient?

Cheers, Tridge

[Bill Bonney]

Hi,

If you are not running Mission Planner, you can also update the radios using a python script that is available. The instructions are as follows

wget http://firmware.diydrones.com/SiK/stable/radio~hm_trp.ihx

wget http://smaccmpilot.org/artifacts/sik_uploader.py #it’s also in the SiK github repo

sudo easy_install pexpect

python sik_uploader.py --port /dev/cu.usbserial-DN0019TF --baudrate 57600 radio~hm_trp.ihx 

The port here is for an radio connected to OSX, so will vary if you are on linux.

Hope that helps. 

I’m adding the updating as a feature to AP2, it should be ready for APM Planner 2.0 Beta-RC3

Bill

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Graham Dyer]

After upgrading my radios to v1.8.1 I was connecting fine, then I went from ACv3.1rc7 to 3.1 final and now I can't connect reliably anymore.

Loading settings in the 3DR Radio Config 1.3 gives this result which much of the info not populated, tried another radio, the same:

Any ideas? Tridge, where can I find the 1.7 hex file please?

[Graham Dyer]

After two hours of fiddling I found the radios work with v3.1rc8 but not with v3.1 final

How can that be?

[Kevin Hester]

Hi Graham,

That's really strange.  I can think of no reason they would work with rc8 but not the new final build.  Can you connect a serial terminal to each of the radios and capture the result of +++ (to enter command mode), then ATI5 (to dump parameters)?

Kevin

--

[ctech]

I am unable to connect with max window size of under ~75ms with MP.

The radios are connected, the green led is on solid...

MP connecting hangs on getting the first parameter for ever at 33ms and on an other parameters when 50ms....

[Kevin Hester]

Hi ctech,

Can you use a terminal program to capture the results of RTI5/ATI5 for the radios? 

Kevin

[ctech]

hmm...

I am not able to enter command mode with putty and these instructions

"If you connect with a serial console to a 3DR radio at the current serial baud rate, you can tell the radio to enter AT command mode by entering the sequence ‘+++’. To prevent data being seen as the command sequence there is a guard time required, so make sure you type nothing on the serial link for 1 second before and after you enter the sequence." http://copter.ardupilot.com/wiki/common-using-the-3dr-radio-for-telemetry-with-apm-and-px4/

are these correct?

Data bits: 8

Stop bits: 1

Party: None

Flow control: XON/XOFF

[Peter Plischka]

V1.8.1 works with and without low latency well with the current master trunk.

regards Peter

[Bill Bonney]

Turn flow control off for one (though it should not matter)

Also, make sure you are not typing +++ then <enter>. You need to wait for a second, type +++ and then wait for another second, you can then type ATI to see if it worked

Bill

PS: This is not a support forum, we should move this discussion to http://ardupilot.com/forum

[ctech]

ok got it, does not seem to work when the radios are connected to each other and sending data, here are the ATI5 outputs from both radios...and RTI5 does not do anything....

Radio Local:
OK
ATI5
S0:FORMAT=25
S1:SERIAL_SPEED=57
S2:AIR_SPEED=48
S3:NETID=25
S4:TXPOWER=20
S5:ECC=1
S6:MAVLINK=2
S7:OPPRESEND=1
S8:MIN_FREQ=415000
S9:MAX_FREQ=417000
S10:NUM_CHANNELS=20
S11:DUTY_CYCLE=100
S12:LBT_RSSI=0
S13:MANCHESTER=0
S14:RTSCTS=0
S15:MAX_WINDOW=33

remote:
OK
ATI5
S0: FORMAT=25
S1: SERIAL_SPEED=57
S2: AIR_SPEED=48
S3: NETID=25
S4: TXPOWER=20
S5: ECC=1
S6: MAVLINK=2
S7: OPPRESEND=1
S8: MIN_FREQ=415000
S9: MAX_FREQ=417000
S10: NUM_CHANNELS=20
S11: DUTY_CYCLE=100
S12: LBT_RSSI=0
S13: MANCHESTER=0
S14: RTSCTS=0
S15: MAX_WINDOW=33

--

[Andrew Tridgell]

> S2:AIR_SPEED=48

that's a lower airspeed than usual. Any reason why you dropped it from 64?

> S8:MIN_FREQ=415000
> S9:MAX_FREQ=417000

That's an unusual frequency range too. What sort of radios are these?

[Graham Dyer]

Hi Kevin

Not 100% sure how to do that, I have Terminal installed but get no response when I enter a command so am not sure if I'm doing it right.

Graham

[ctech]

@tridge

>> S2:AIR_SPEED=48
>that's a lower airspeed than usual. Any reason why you dropped it from 64?

Yeah I keep dialing it down until i see problems to increase range

>> S8:MIN_FREQ=415000
>> S9:MAX_FREQ=417000
>That's an unusual frequency range too. What sort of radios are these?

haha they are the 433mhz radios V1.3 from 3dr

I have access to a license for some channels in that range, for testing I just picked them at random...no telecom for 300km hehehe

@graham

check that your using the correct com port and that the terminal is configured right

looks to me if the radio is not transmitting you don't see anything until you hit +++, then you should get "ok"

[Tom Coyle]

Hi Tridge,

You might want to take a look at a member's problem using firmware v1.8.1: firmware issue

Regards,

Tom C

[Jesus Alvarez]

Maybe a misconfiguration?

Both my copter and plane works great with 1.8.1

[Bill Bonney]

I think there maybe an issue with the settings getting messed up on upgrade. I had what seemed to be a similar issue.

The fix is to restore factory settings to bot radio and then see if you can reconnect

AT&F - Set the factory Settings
AT&W - Write those settings to EEPROM
ATZ - reboot the radio
to connect to the radio on OSX I use screen /dev/cu.usbserial-XXXXXXXX 57600  use ctrl-a,ctrl-\ and pres Y to quite screen when done

XXXXXXXX is the unique identifier for your radio

Bill

[Graham Dyer]

I asked on the v1.8 thread but got no response, what is low latency mode and how does it affect/benefit us, the end user? Also is it a recommended update? I've reverted back to v1.7 as I couldn't get v1.8.1 to work. I have not yet tried Bill's subsequent solution though.

[Craig Elder]

Here, let me google that for you.

The best place to find answers is to look in the wiki.

http://copter.ardupilot.com/wiki/common-using-the-3dr-radio-for-telemetry-with-apm-and-px4/#Low_latency_mode

On Sun, Dec 22, 2013 at 11:26 AM, Graham Dyer <graha...@gmail.com> wrote:

I asked on the v1.8 thread but got no response, what is low latency mode and how does it affect/benefit us, the end user? Also is it a recommended update? I've reverted back to v1.7 as I couldn't get v1.8.1 to work. I have not yet tried Bill's subsequent solution though.

--

[Kevin Hester]

Sorry ya'll I was away from this list for a few days:

I just replied to the forum post, here's my reply:

Hi - I wrote most of these changes, but haven't managed to reproduce the problem you describe.  Would you switching into terminal mode and then doing:

Pause one sec

Type +++ (with a short pause between each plus) 

Pause one sec

then type AT and press return

You should see a "OK" response (if you don't try the procedure above until you do - the timing is a bit finicky)

Then type ATI5 and press return

It will print a bunch of stuff

Then type RTI5 and press return

It will print more stuff

Could you post the stuff these two commands print?

On Sun, Dec 22, 2013 at 11:26 AM, Graham Dyer <graha...@gmail.com> wrote:

I asked on the v1.8 thread but got no response, what is low latency mode and how does it affect/benefit us, the end user? Also is it a recommended update? I've reverted back to v1.7 as I couldn't get v1.8.1 to work. I have not yet tried Bill's subsequent solution though.

--

[Kevin Hester]

Actually - I just had an idea.  For those that are having problems, do you have your mavlink streaming rates set to a non default value.  On the Mission Planner config screen what do you see here:

[Graham Dyer]

Actually that should be "let me wiki that for you" except the wiki wasn't updated when I asked, anyway thanks, it answers a question.

[Graham Dyer]

Kevin, sorry I haven't tried to get it to work again, I got no response apart from 'OK' using the terminal program I was using but I was probably doing something wrong. The radio's are working fine with v1.7 so for the moment I'm not going to mess with them.

[Marco Robustini]

I've found a problem, dunno if there's something wrong with the latest Planner or with this SIK firmware.
I'm not able to change the frequence of the remote adapter via wireless, i force the new range, i push the button "Copy required items to remote", then "Save Settings" and then i loose the link, the frequency in the remote is always "414000 - 415000" Mhz.

Marco

[Marco Robustini]

I've found a solution, but it is just a way to circumvent the problem, not solve it.
Before changing the frequencies in the remote module and I click "Save Settings", then I do the same thing on the module connected to the PC, so I think it's a bug of the Planner, sending AT commands in the wrong order, you can tell it to Michael?
The version is "1.2.90.3".

Marco

[Michael Oborne]

MP has always sent remote radio commands first, before doing local. And have verified this morning as well. Could you provide the ArdupilotPlanner.log file, as this will show the full radio command history

 

Michael

[Marco Robustini]

Thanks Michael for reply, ok, then i think there's something wrong in the new SIK firmware... only happens to me this thing?

Marco

[Bill Bonney]

Hi Kevin,

I had a similar problem when I upgraded that my radios that they would not connect. The fix was to do the AT&F AT&W ATZ and then it was fixed. The FW is good, the upgrade of the eeprom values may be an issue. Is reading the new value on upgrade taking a random value from the eeprom. (random guess) But something is not quite right (hunch) with that stage.

The outcome is that I fixed it with a factory reset. And like all the best intermittent defects, I cannot reproduce. I did make sure the APM Planner 2.0 did the fcatory reset properly.

Hope that helps :)

Bill