- Posts: 8
Strange behavior of DEVO 10
- Serg_S
- Topic Author
- Offline
I updated my DEVO10 from the build 24f4cf6 from 27/03/2017 to the last night build e292f38.
Now I observe the strange behavior of the transmitter.
On the main page, instead of the virtual channel values, the transmitter shows nonsense (contents of boxes with real channels, timers, battery voltage, etc.).
In the attached video:
On the left side of the video the transmitter with the old firmware, on the right side - with the new firmware.
On the left side of the tranmitter's display are boxes that show the values (output) of virtual channels.
On the right side of the tranmitter's display are boxes that show the output of real channels or timers.
When changing the value of the source of the virtual channel mixer, then to the corresponding box (on the left of the tranmitter's display) instead of the virtual channel output shows the value from the boxes on the right or the battery voltage.
The channel monitor shows the virtual channel values correctly.
The transmitter works this way on any of the latest available night build.
If I restore build 24f4cf6, then the transmitter again works correctly.
The model.ini file is attached.
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- Serg_S
- Topic Author
- Offline
- Posts: 8
Please Log in or Create an account to join the conversation.
- Serg_S
- Topic Author
- Offline
- Posts: 8
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- Serg_S
- Topic Author
- Offline
- Posts: 8
[gui-128x64]
V-trim=0,11,1
Toggle=5,11,0,72,0,RUD DR
Toggle=14,11,0,5,0,ELE DR
Toggle=23,11,0,65,197,MIX
Toggle=32,11,0,69,0,AIL DR
Toggle=41,11,0,64,194,FMODE
Big-box=4,23,Ch1
Big-box=4,36,Ch2
Small-box=4,50,Ch3
H-trim=4,60,3
Battery=51,11
TxPower=51,17
Bargraph=52,24,Ch6
Bargraph=57,24,Ch1
Bargraph=62,24,Ch4
Bargraph=67,24,Ch3
Bargraph=72,24,Ch2
Big-box=76,11,Timer1
Small-box=76,26,Timer2
Small-box=76,38,Timer3
Small-box=76,50,Timer4
H-trim=75,60,4
V-trim=124,11,2
quickpage1=Channel monitor
quickpage2=Telemetry monitor
But with virtual channels, the emulator will crash.
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
sprintf(tempstring, val_format, val_raw/val_scale); => division by 0 and emulator will crash.
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
[channel3]
display-scale=1000
display-scale=1000
display-format=%2d%%
template=simple
[mixer]
src=THR
dest=Ch3
Why "display-scale=1000" appears twice???
I recommend revert this commit.
github.com/DeviationTX/deviation/pull/328
Please Log in or Create an account to join the conversation.
- FDR
- Offline
I've informed him in the thread, which was about that change:
www.deviationtx.com/forum/6-general-disc...custom-display-units
Please Log in or Create an account to join the conversation.
- nknotts
- Offline
- Posts: 7
With regards to "display-scale" showing up multiple times in the model, I have witnessed this behavior but have also seen it with other options as well. Since this issue didn't impair the loading of the model, I did not investigate further.
I can investigate the duplicate entries but am not quite sure where to begin. Looking at github.com/DeviationTX/deviation/pull/32...05f5b2a6ac9e31fR1231 , I see nothing special about the entries that I added. Any suggestions would be welcome.
I apologize for any grief I've caused.
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
static const struct struct_map _seclimit[] = {
{CHAN_LIMIT_SAFETYSW, OFFSET_SRC(Model.limits[0], safetysw), 0},
{CHAN_LIMIT_SAFETYVAL, OFFSETS(Model.limits[0], safetyval), 0},
{CHAN_LIMIT_MAX, OFFSET(Model.limits[0], max), DEFAULT_SERVO_LIMIT},
{CHAN_LIMIT_SPEED, OFFSET(Model.limits[0], speed), 0},
{CHAN_SCALAR, OFFSET(Model.limits[0], servoscale), 100},
{CHAN_SCALAR_NEG, OFFSET(Model.limits[0], servoscale_neg), 0},
{CHAN_SUBTRIM, OFFSETS(Model.limits[0], subtrim), 0},
//{CHAN_DISPLAY_SCALE, OFFSETS(Model.limits[0], displayscale), DEFAULT_DISPLAY_SCALE},
};
I get at modelXX.ini
[channel3]
display-scale=1000
display-format=%2d%%
template=simple
[mixer]
src=THR
dest=Ch3
And it looks like all work as before.
Please Log in or Create an account to join the conversation.
- nknotts
- Offline
- Posts: 7
All entries in _seclimit are de/serialized via the write_int / assing_int functions. To prevent the duplications, I removed the additional de/serialization code for 'display-scale'.
Please Log in or Create an account to join the conversation.
- Serg_S
- Topic Author
- Offline
- Posts: 8
Thanks, now the transmitter works correctly.FDR wrote: Merged, it will be in tomorrow's nightly builds...
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Builds
- Strange behavior of DEVO 10