49 replies to this topic

[xavior38]

Yes, happy to help debug. Just lmk what I can do.

Thx

[DDH69]

No rush on this as I'm walking out the door in about 30 minutes and will be away for 4 days.

 

1. Delete DOFLinx.LOG
2. Set DEBUG=2 in DOFLinx.INI
3. Save your existing DOFLinx.EXE somewhere safe
4. Expand and copy in the attached version (it will produce BIG logs when FX3 is running)
5. Start FX3 and get the issue to occur as quickly as you can, don't worry about playing the game, etc
6. Immediately after it happens quit FX3, we want  a failed flipper hold to be the last flipper press in the log
7. Zip up the DOFLinx.LOG and send it to me along with any observations, sequence of what you had to do to get the error to occur, etc
8. Put your saved version of DOFLinx.EXE back in place

I'm not sure this will get me a resolution, but it should at the very least show me in detail what is happening.  Dependent on what we find I may put in some other logging and need to go again later.

Attached Files

•  DOFLinx v733 Beta 1.zip   414.64KB   1 downloads

[xavior38]

here is the file: https://pastebin.com/Ngg5m6cz
 
I was alternating holding the left flipper and right flipper for a couple seconds at a time. The end of the file is where the right flipper solenoid triggered itself again (only once).
 
16-Apr-21 16:39:51.955 - LEFTFLIPPER - 1 - 0 - 15216712 - 11022408 - 255 - 157876244
16-Apr-21 16:39:51.959 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
16-Apr-21 16:39:51.963 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
16-Apr-21 16:39:51.967 - Link is turning off device #1
16-Apr-21 16:39:52.175 - RIGHTFLIPPER - 0 - 1 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:52.178 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
16-Apr-21 16:39:52.183 - Link is turning on device #2 for 10000 milliseconds
16-Apr-21 16:39:52.189 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
16-Apr-21 16:39:52.193 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
16-Apr-21 16:39:52.197 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
16-Apr-21 16:39:52.211 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
16-Apr-21 16:39:52.215 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
16-Apr-21 16:39:52.898 - RIGHTFLIPPER - 1 - 0 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:52.902 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
16-Apr-21 16:39:52.907 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
16-Apr-21 16:39:52.910 - Link is turning off device #2
16-Apr-21 16:39:52.925 - RIGHTFLIPPER - 0 - 1 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:52.929 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
16-Apr-21 16:39:52.933 - Link is turning on device #2 for 10000 milliseconds
16-Apr-21 16:39:52.940 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
16-Apr-21 16:39:52.946 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
16-Apr-21 16:39:52.950 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
16-Apr-21 16:39:52.969 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
16-Apr-21 16:39:52.974 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
16-Apr-21 16:39:55.164 - RIGHTFLIPPER - 1 - 0 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:55.168 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
16-Apr-21 16:39:55.173 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
16-Apr-21 16:39:55.177 - Link is turning off device #2
16-Apr-21 16:39:55.213 - RIGHTFLIPPER - 0 - 1 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:55.217 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
16-Apr-21 16:39:55.222 - Link is turning on device #2 for 10000 milliseconds
16-Apr-21 16:39:55.226 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
16-Apr-21 16:39:55.229 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
16-Apr-21 16:39:55.234 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
16-Apr-21 16:39:55.248 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
16-Apr-21 16:39:55.254 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
16-Apr-21 16:39:56.606 - RIGHTFLIPPER - 1 - 0 - 15216712 - 11022408 - 255 - 157876252
16-Apr-21 16:39:56.610 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
16-Apr-21 16:39:56.613 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
16-Apr-21 16:39:56.618 - Link is turning off device #2
16-Apr-21 16:39:59.127 - There are no OFF actions for GAMEMODE
16-Apr-21 16:40:05.032 - Activating process disappeared so stopping things
16-Apr-21 16:40:05.039 - Stopping ROM
16-Apr-21 16:40:05.043 - Stopping DOF controllers due to 'Start Each Time' flag
16-Apr-21 16:40:09.241 - Shutting down
16-Apr-21 16:40:09.245 - Program close

Edited by xavior38, 16 April 2021 - 09:48 PM.

[DDH69]

I'm back!

 

Thanks for the test and additional information.  What I can see from the log is that FX3 is definitely triggering, then "releasing" the trigger for the flipper on / off.  What keyboard encoder are you using?  The sequence you are getting is On / Off / On then eventually Off.  The Off / On sequence seems very fast, but DOFLinx is still happy to process it.  This is why I am wondering about your keyboard encoder.  I am wondering if you are actually getting an Off / On that is so fast that FX3 doesn't visibly drop the flippers but DOFLinx detects it and  actions the solenoids.

 

I've yet again added some more logging.  Would you mind doing the same test again?

Attached Files

•  DOFLinx V733 Beta 2.zip   414.7KB   1 downloads

[xavior38]

Sure, will try to do this a bit later today (for my time zone, at least)

 

I am using joy2key to interpret keystrokes from my geeekpi encoder.

 

Note that I tried using just my keyboard (using left and right arrow as flippers) and got the same flipper retrigger result, so not sure it would be the encoder (but what do I know?)

 

Thanks again

[xavior38]

Here is the newest - same thing as above (alternating flipper, and the last activated flipper pulls the retrigger (right flipper): https://pastebin.com/3wQXcsNk

[DDH69]

Thanks again, some good information there.

 

I can see that DOFLinx is testing for FX3's view of the flipper button being held down every 13 - 16mS, a little slow, but its logging hard.  The solenoid lift is being caused by one read in there reporting that the flipper key has lifted, so about a 15mS gap ..... we may never know why.

 

I can add some coding to only release flippers after a set amount of time to stop false untriggering, the problem however is that this is artificial and would cause a delay from the release of the flipper button and reaction of the linked toys.  Having said that, if it was set to about 50mS I doubt you would really notice.  If this interests you I can have a look at coding this with the default being disabled adn enable the delay to be enabled via a parameter.

 

What you have seems quite unique, it may require a unique solution.

[Outhere]

I have mine set like this
This way they aren't on the hole time, Plus it may solve your problem

 

MAX_FLIPPER_ON=60

LINK_LF=101,50,60,255
LINK_RF=102,50,60,255

[xavior38]

Thanks again, some good information there.
 
I can see that DOFLinx is testing for FX3's view of the flipper button being held down every 13 - 16mS, a little slow, but its logging hard.  The solenoid lift is being caused by one read in there reporting that the flipper key has lifted, so about a 15mS gap ..... we may never know why.
 
I can add some coding to only release flippers after a set amount of time to stop false untriggering, the problem however is that this is artificial and would cause a delay from the release of the flipper button and reaction of the linked toys.  Having said that, if it was set to about 50mS I doubt you would really notice.  If this interests you I can have a look at coding this with the default being disabled adn enable the delay to be enabled via a parameter.
 
What you have seems quite unique, it may require a unique solution.

Yeah I'd try it for sure, thanks. What about a variable delay that I can maybe set?

Also, and I know this would be a hack, but what about adding a "double check" to see if the keyboard key press has been released or not before it turns the flipper device off? (Maybe that's what you were indicating, so in that case nevermind)

Anyhoo, happy to try. Thanks again

I have mine set like this
This way they aren't on the hole time, Plus it may solve your problem
 
MAX_FLIPPER_ON=60

LINK_LF=101,50,60,255
LINK_RF=102,50,60,255

Thanks I actually tried that as well. Problem is, even with those settings it will still retrigger.

Thanks though for the suggestion

[xavior38]

I finally got DOF working for VPX and tried the solenoids. No flipper trouble there that I could notice in a few minutes worth of trying to get it to re-trigger, so I am at least more confident it's not the solenoid hardware or the sainsmart, and somewhat more confident it's not the encoder.

Edited by xavior38, 23 April 2021 - 12:15 AM.

[DDH69]

I finally got DOF working for VPX and tried the solenoids. No flipper trouble there that I could notice in a few minutes worth of trying to get it to re-trigger, so I am at least more confident it's not the solenoid hardware or the sainsmart, and somewhat more confident it's not the encoder.

 

I'm confident too.  It is 100% the triggering input from FX3, definitely established that.  I've done some coding to help work around this.  Should get to testing it this weekend to ensure I haven't broken the standard stuff, ten you can test if we can sort out your issue.

[DDH69]

OK, so give this a try in the same way as before, except we'll do it two or three times.

 

Test #1 - Just use the new EXE and see if the problem persists (it should)

 

Test #2 - Set FX3_TRIGGER_RELEASE_DELAY=50 in your DOFLinx.INI - hopefully the problem stops.  Feel free to play with the value its in milliseconds

 

Test #3 - If test #2 works for you, do about a minute of play so I can see a longer log

 

Very happy to see 3 separate logs or one longer one.

 

The attached EXE version still has extra logging.  If this sorts out the issue I'll remove that and do a more formal release.

Attached Files

•  DOFLinx V733 Beta 5.zip   414.87KB   1 downloads

[xavior38]

Thanks for this. Just tried. It actually made the problem worse somehow. Now it retriggers every split second or so. Here's the log:

 

with FX3_TRIGGER_RELEASE_DELAY=50

 

23-Apr-21 14:55:37.306 - Setting FX3 process ID to :1292
23-Apr-21 14:55:37.326 - Activated by process name : 'Pinball FX3'
23-Apr-21 14:55:37.332 - Named process detected and startup commenced
23-Apr-21 14:55:37.334 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
23-Apr-21 14:55:37.338 - DOFLinx device:1 Pinscape setup with 22 outputs
23-Apr-21 14:55:37.342 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0
23-Apr-21 14:55:37.352 - DOFLinx device:2 LEDWiz setup with 32 outputs
23-Apr-21 14:55:37.541 - DOFLinx Device: 3 Initializing as FTDI (Sainsmart) #1 serial # AL03MDJM
23-Apr-21 14:55:37.547 - DOFLinx device:3 FTDI (Sainsmart) setup with 8 outputs
23-Apr-21 14:55:38.079 - FX3.EXE file exists, getting details
23-Apr-21 14:55:38.082 - FX3 EXE name=C:\Program Files (x86)\Steam\steamapps\common\Pinball FX3\Pinball FX3.exe Size=11303056 bytes, Dated 12/1/2020 6:03:29 PM
23-Apr-21 14:55:38.087 - Applying memory offsets for FX3 version circa 2/12/20
23-Apr-21 14:55:38.096 - FX3 full link active
23-Apr-21 14:55:39.105 - Loading FX3 configuration file C:\DirectOutput\DOFLinx_FX3\ALL_PRE.FX3
23-Apr-21 14:55:39.118 - Loading FX3 configuration file C:\DirectOutput\DOFLinx_FX3\WMSMedievalMadness.FX3
23-Apr-21 14:55:39.121 - Processing parameter 'FF_ROM' with data 'FX3_WMS_MMADNESS' in real-time
23-Apr-21 14:55:39.125 - Loading DOF 'Pinball' with ROM='FX3_WMS_MMADNESS'
23-Apr-21 14:55:39.129 - No DOF Global Config file supplied
23-Apr-21 14:55:39.135 - Processing parameter 'BACKGLASS_EXISTS' with data 'YES' in real-time
23-Apr-21 14:55:39.153 - Loading FX3 configuration file C:\DirectOutput\DOFLinx_FX3\ALL_POST.FX3
23-Apr-21 14:55:39.158 - B2S file not found : WMSMedievalMadness
23-Apr-21 14:55:39.191 - Using full colour palette
23-Apr-21 14:55:39.194 - 122 colours added to the palette
23-Apr-21 14:55:39.198 - Cabinet Mode = 0   Backglass Mode = 0
23-Apr-21 14:55:43.856 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
23-Apr-21 14:55:43.866 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FL,6,750,100,RANDOM'
23-Apr-21 14:55:43.874 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FL,6,750,100,RANDOM'
23-Apr-21 14:55:43.877 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FL,6,750,100,RANDOM'
23-Apr-21 14:55:43.880 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FL,6,750,100,RANDOM'
23-Apr-21 14:55:43.884 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FL,6,750,100,RANDOM'
23-Apr-21 14:55:43.887 - GAMEMODE mode=1 action #6 of 'FF_DOF,E424,-1'
23-Apr-21 14:55:43.902 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:43.908 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:44.746 - BALLIN_SENSOR mode=1 action #0 of 'FF_DEV,DV_MC,-1'
23-Apr-21 14:55:44.751 - Link is turning on device #6 for 50 milliseconds
23-Apr-21 14:55:44.764 - BALLIN_SENSOR mode=1 action #1 of 'FF_DOF,E311,-1'
23-Apr-21 14:55:44.815 - Link is turning off device #6
23-Apr-21 14:55:45.286 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
23-Apr-21 14:55:45.290 - Link is turning on device #2 for 10000 milliseconds
23-Apr-21 14:55:45.294 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
23-Apr-21 14:55:45.297 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
23-Apr-21 14:55:45.301 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
23-Apr-21 14:55:45.313 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:45.317 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:48.045 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
23-Apr-21 14:55:48.048 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
23-Apr-21 14:55:48.052 - Link is turning off device #2
23-Apr-21 14:55:48.064 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53748064.8586 -- 18.8586000055075 50
23-Apr-21 14:55:48.077 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53748077.859 -- 31.859000004828 50
23-Apr-21 14:55:48.092 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53748092.8603 -- 46.8603000044823 50
23-Apr-21 14:55:48.108 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
23-Apr-21 14:55:48.111 - Link is turning on device #2 for 10000 milliseconds
23-Apr-21 14:55:48.115 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
23-Apr-21 14:55:48.122 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
23-Apr-21 14:55:48.126 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
23-Apr-21 14:55:48.139 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:48.143 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:49.763 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
23-Apr-21 14:55:49.767 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
23-Apr-21 14:55:49.770 - Link is turning off device #2
23-Apr-21 14:55:49.782 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53749782.8595 -- 18.8595000058413 50
23-Apr-21 14:55:49.795 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53749795.8586 -- 31.8586000055075 50
23-Apr-21 14:55:49.811 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53749811.8591 -- 47.8590999990702 50
23-Apr-21 14:55:49.827 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
23-Apr-21 14:55:49.830 - Link is turning on device #2 for 10000 milliseconds
23-Apr-21 14:55:49.834 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
23-Apr-21 14:55:49.837 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
23-Apr-21 14:55:49.842 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
23-Apr-21 14:55:49.855 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:49.859 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:50.350 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
23-Apr-21 14:55:50.353 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
23-Apr-21 14:55:50.358 - Link is turning off device #2
23-Apr-21 14:55:50.370 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53750370.8601 -- 19.8601000010967 50
23-Apr-21 14:55:50.383 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53750383.8583 -- 32.8583000004292 50
23-Apr-21 14:55:50.397 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53750397.8595 -- 46.8595000058413 50
23-Apr-21 14:55:50.414 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
23-Apr-21 14:55:50.417 - Link is turning on device #2 for 10000 milliseconds
23-Apr-21 14:55:50.422 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
23-Apr-21 14:55:50.425 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
23-Apr-21 14:55:50.429 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
23-Apr-21 14:55:50.445 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:50.448 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:52.669 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
23-Apr-21 14:55:52.672 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
23-Apr-21 14:55:52.676 - Link is turning off device #2
23-Apr-21 14:55:52.689 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53752689.8585 -- 20.8585000038147 50
23-Apr-21 14:55:52.701 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53752701.858 -- 32.8580000028014 50
23-Apr-21 14:55:52.717 - RIGHTFLIPPER skipped due to FX3 Trigger Release Delay setting 53739189 53752717.8593 -- 48.8593000024557 50
23-Apr-21 14:55:52.732 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
23-Apr-21 14:55:52.736 - Link is turning on device #2 for 10000 milliseconds
23-Apr-21 14:55:52.739 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
23-Apr-21 14:55:52.743 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
23-Apr-21 14:55:52.747 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
23-Apr-21 14:55:52.759 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
23-Apr-21 14:55:52.762 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
23-Apr-21 14:55:53.232 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
23-Apr-21 14:55:53.235 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
23-Apr-21 14:55:53.240 - Link is turning off device #2
23-Apr-21 14:55:53.990 - There are no OFF actions for GAMEMODE

[DDH69]

My bad, I didn't get the release delay right  .  Leave it with me, working on it ........

[xavior38]

No problem. I thought perhaps we had accidentally discovered the root cause of the problem somehow since now it's consistently re-triggering every time

[DDH69]

So hopefully I got it right this time 

 

Still has extra logging, still looking for the three tests I explained the first time.  Let me know.

Attached Files

•  DOFLinx V733 Beta 7.zip   414.94KB   1 downloads

[xavior38]

For some reason DEBUG=2 did not log anything

 

Anyways, I tried this newest build. Strangely enough, the delay worked properly this time, but the retriggering still happens. Even when I set the delay ridiculously high (500ms), it sometimes retriggers before 500ms.

 

A very elusive anomaly indeed. I'm happy to try any other builds you may have!

 

Sincerely,

[DDH69]

Nothing has changed with the DEBUG options so need you to check your setup (location, format, not commented, etc) of DEBUG=2, I will need the log files.  DOFLinx always produces the first part of the log file, so if your cannot find any log file then you may be looking in the wrong spot.

 

I've updated the code again, its possible that it was only suppressing the first false untrigger.  Not being able to reproduce this makes it very hard.  Let me know.

Attached Files

•  DOFLinx V733 Beta 8.zip   414.96KB   1 downloads

[xavior38]

Now we're talking! I only got it to retrigger once at 20ms after a minute or 2 of trying. At 50ms I wasn't able to get it to retrigger at all (yet).

 

Here is my log at 25ms.. it retriggers on the last flipper hold I believe: https://pastebin.com/WHAUKC7f

 

My main issue is that now there's a slight delay when FX3 activates the solenoid. I thought the fix was to delay the de-activation of the solenoids, not the activation? Anyways, a definite improvement!

 

Edit: additional observation: there seems to be a rare random amount of input delay on flipper solenoid activation whenever FX3_TRIGGER_RELEASE_DELAY is on. Usually there's no problem, but sometimes it feels more like 100-150ms or so, rather than 50ms (when it's set to 50). Again, not sure if the intention was to delay solenoid activation.. if it wasn't, then this shouldn't be an issue I guess.

Edited by xavior38, 27 April 2021 - 12:41 AM.

[DDH69]

Progress, good.  Let me look at the activation vs deactivation.  I've probably made this a simple change in state, not a one-way change in state.