#21

@tehn Thanks for doing this - teletype remote for ansible could be a big thing. I just did the upgrade and found two things while testing it with a simple 1 CY.RES 3 script line:

  1. every now and then it still skips commands and does not reset.

  2. After a while cycles suddenly changes the direction while everything else seems to to stay as it was set

#22

can you give an approximation of frequency? i’ve witness very rare packet drops, though rare is still frustrating and i’ll track it down hopefully soon.

you’re saying, while sending CY.RES 3 you get a direction reversal? (the equivalent of CY.REV) do all cycles reverse, or just number 3?

#23

@tehn [quote=“tehn, post:22, topic:5807”]
can you give an approximation of frequency? i’ve witness very rare packet drops, though rare is still frustrating and i’ll track it down hopefully soon.
[/quote]

I tested it with a Metro Script (M: 250) and one command is skipped per minute. I already posted another pattern with an audio example on the earthsea thread some weeks ago:

Yes, that’s what is happening. Though I am not sure that it happens exactly at the time the CY.RES 3 is sent. All cycles get reversed then and it happens slightly less frequentliy than the skipped reset command.

It is indeed frustrating, especially when it is about something sequence related since you get unwanted phase shiftings then.

Also the cycles are severely stepped in voltage again and somehow irrgeluar - I’ll see if I can post an example.

#24

Here we go - first you hear cycle voltage to osc pitch to demonstrate the stepped voltage, then I activate the Metro Script with the reset command and it does not take long till the first skipped reset. Plus you hear a beating rhythm as if the cycle is not reset to the same point everytime or the Metro tempo is shaky:

https://soundcloud.com/salz-peter-zucker/ansible-cycle-bugs

#25

First time using Ansible as a Teletype expander; everything freezes up when I send a command. Requires a restart.

Ansible 1.0
#26

I can’t make any of the commands work.
It works as a TT expander so i guess it’s all wired correctly. But no luck with the Arc.
Simply ‘CY.RES 0’ should reset call cycles, shouldn’t it ?

#27

Sorry !
i updated TT only, and not the Ansible. Should be working now !

#28

Unless i am wrong, the values for CY.POS are 0-127, and not 0-255 as stated.

#29

@tehn

I just tried the new remote functions again and either teletype or both teletype and ansible are constantly freezing after a short time with Cycles as well as with Kria.

While they are working for example cycles looks like this - CY.POS 1 affects Cylce 2 too:

https://youtu.be/yu8ceZ7Gfk8

EDIT: Just found that on Levels LV.POS also from time to time alters the start position of a pattern!

It seems that Ansible reacts quite randomly to teletype remote commands…
:disappointed:

#30

ok i’m seeing the glitch, but it seems like an LED glitch, not actually messing up the CV output.

can you confirm this?

#31

I tried - on the first trial Ansible and Teletype instantly froze. On the second trial I cannot replicate the behaviour. This fits with some of my observations that the state is not always the same on power on. I had it for a short time in a state where cycles have been continuous instead of stepped voltage but it froze then…

#32

how many modules are on your II ribbon chain?

which commands are freezing?

i can confirm that parameter reads inside M scripts will bring it down. are you seeing others?

#33

Earthsea, Ansible and Meadowphysics are on my i2c bus. I think all are on the latest firmwares.

I did not find any special commands by now that are freezing the modules, I used reset and position mostly to try by now for all Ansible apps. Teletype/Ansible is reacting absolutely erratic.

#34

for the time being during testing, can you switch your ii cable to ansible and limit the setup to just tt and ansible?

#35

@tehn Yes I disconnected MP and ES now. When I powered on the case today I found Cycles being stepped again and CY.POS range is definitely 0 - 64 with 16 at east, 32 at south and 48 at west…

…And teletype just froze again while doing this M CY.POS 1 63 with M = 250

:neutral_face:

EDIT: Okay, it freezes when you forget the Cycle channel on the command - CY.POS 63 outputs 27 a few times then freezes teletype or both.

#36

it sounds like you’re repeatedly running into a known bug which is param reads inside the metro.

is this on a fresh flash of ansible?

#37

I am not sure what you mean: fresh flash of ansible?

#38

apologies-- newest firmware update, with default settings

#39

Ah, yes, fresh flesh - I am just scaling the output range down. teletype the same, nothing saved and just single or two line scripts or live mode commands.

#40

@tehn Now with i2c running better I did a short video exploring the range behaviour of cycles.

This script pushes cycle 1 forward from 0 - 64 which is one full cycle and puches cycle 2 forward by the read value of cylce 1 which is four cycles as cycle one read values have a range from 0 - 255 (to clarify, the movement is just the metro script, cycles it self are setup to move very slow/stand still as you see on three and four):

X ADD 1 MOD X 64
CY.POS 1 X
CY.POS 2 CY.POS 1

Also mind the pattern of the LED glitch - it’s always one cycle doing it after the other. On the first two cycles it is masked by the programmed positions.

I am happy that i2c remote has made a step forward and hope this does help on debugging Ansible.

:+1: