[sanelss]

1 - Your CAN Talons don't move at all? Are they blinking orange or solid orange? What does the web-based config self-test says? Check the mode and throttle as well.

they are blinking red and green. Well one blinks red, one blinks green. I was not aware the web interface provides this information so I'll take a look

2- Your PWM Victor 888s dont' move at all? Are they blinking orange or is the led solid orange?

this only happens on occasion but is still a problem, forgot the LED status when it happens

3-Your PWM channels 8 and 9 are nonzero when they should be zero? What are the Victor LEDs doing?

i don't know if they should or shouldn't be "zero". i just know 9 always works without issue and as expected but 8 which is programmed in the exact same way and just gets a mirror value sent to it sometimes goes to position i never send it and gets stuck there. it certainly is some kind of default position but it's not "zero" as far as i'm aware. I believe I have found a solution to this particular issue although I don't like it since i'm constantly getting the servo ref and writing the same value to it in code which to me is unnecessary.

[4] What does your driver station messages list say?

on initialization a lot, too much to keep up. Most of them seem like non issues. for example I get some i2c errors but don't have any errors with the i2c device so not sure where they come from, among other messages i'm not sure the meaning of.

[5] I assume you are creating motor controllers in Begin.vi. Are you wiring safety-config? If so I would set it to 'disable' to rule out watchdog events.

yes i set it up in begin.vi. no safety config on anything.

[6] Anything in the DS log when this problem occurs?

as mentioned in another question there is a lot of stuff on the DS, and only when it initially powers up and first code upload.

Might be easier to just post your project somewhere. I can try deploying on my bot and see what happens.

i may be able to skim out the relevant section, you REALLY don't want to have to deal with the spaghetti that labview tends to make

[7] What's with all the posting? What does 'X-post' mean? Your just confusing the forum members.

it stands for cross-post, and i posted all over since i didn't know where i would get the best(or for that matter just any) answer. pretty standard forum jargon

I believe i have determine what the problem is and why other teams don't experience them. Still need to verify. I have seemed to have fixed the issue with the servos I was having though. The way my code works is that in teleop it sets function modes in global variable, then in periodic task i check for a change of function modes and only send the motors a value once on each change. I mean why keep sending a motor the same value over and over? I also tried only getting the motor ref prior to loop and using a shift register&/or tunnel to set value which i think part of the problem lies with. If i get the motor ref every loop execution and keep sending it values the issues seem to be mitigated.

From what I can find online there does seem to be some kind of issue with initializing motors(perhaps some kind of race condition?) so you need to send it a value after a certain point for it to work. Still needs investigating though.

Although not tested for long, our competition bot didn't seem to suffer from these issues, the roborio on our practice bot seems to be having a lot more issues for whatever reason. we simply can't have these kinds of glitches happen at competition and considering how sporadic and seemingly random it happens i don't see how it could be a code issue. But i'm aware it very well may be so will need more testing/investigating.