-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Applications are not coming up #63
Comments
The last message in your attached log shows that it was still in the process of receiving the implements' pool:
Try keeping the terminal open for a few minutes to allow the pool to transfer. Normally you'd expect a loading indicator of some sort, there is an issue open for that: #4 |
Started the process on 9:50, waited 15 minutes till 10:05. In the meantime, the New rx session was started multiple times but not succesfull. Somewhere halfway i saw one icon on the screen (see attament). Once again uploaded the logs. Keeps coming back with missing language or country code (which is true, country code is empty in settings, but i tried with different codes). And Received an abort (reason=3) for an rx session for Node to terminal. (PGN E700) In total with all the versions en this set-up I think I have tried around 30 times with different settings, ECU's, and sequences of starting things. Still no luck. |
For me the Müller ECU takes a a long time to load. Sometimes over 15 minutes... |
I looked over the logs, and our VT is definitely getting stuck.... after one of the big groups of ETP packets we just stop sending all messages for a little bit, then send out a bunch all at once as if they were stuck in the transmit queue.... it kind of looks to me like a mutex staying locked or something but it's kind of hard to tell.... So it's definitely a bug of some kind. We'll have to dig into it... though it may be a bit tricky without the same equipment here. |
If there is anything I can help you with, please let me know. I can send
you the OPs, another canlog via external tool or anything.
Knowing that there is a sort of bug, i will also try different ecu’s.
Untill now always used just 2 different types of ECUs.
Op ma 30 dec 2024 om 00:11 schreef Adrian Del Grosso <
***@***.***>
… I looked over the logs, and our VT is definitely getting stuck.... after
one of the big groups of ETP packets we just stop sending all messages for
a little bit, then send out a bunch all at once as if they were stuck in
the transmit queue.... it kind of looks to me like a mutex staying locked
or something but it's kind of hard to tell....
So it's definitely a bug of some kind. We'll have to dig into it... though
it may be a bit tricky without the same equipment here.
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5LAVXZFX5PCM23NS3KSIL2IB6RDAVCNFSM6AAAAABUDCBZ22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUHA3DEMZWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ESP32 example OP working fine Kuhn M310 additional try After +/- 10 minutes the AGISO VT shut down fully, so I was not able to save logs. I add the logs of a new session, where the same behavior occurs, but created after a few minutes, so I can make logs. [I know that this session is still open/active at the moment of log] After a new try, it again crashed after a certain amount of time. AgISOVirtualTerminalLogs_2_Jan_2025_11_51_52am.zip I later on created a video of 17 minutes. Video starts already during Rx ression, After more then 15 minutes: [VT Server]: An ecu at address 140 transferred 183132 bytes of object pool data to us. No activity for 2 seconds and AGISOVT totally disappears. ISARIA module working partly However, I can click the buttons, and command is shown in log, but the active masks are not changed. I can only see the mask that is in the screenshot. Please see the logs of clicking buttons below: AgISOVirtualTerminalLogs_2_Jan_2025_12_11_11pm.zip Hmm, after a few more attempts, it looks like the application is loaded, but after a few seconds get an error and gets offline. I see a difference with loading in the CCI 1200, where another red icon alarm is shown at the bottom left. This indicator is a time-out indicator for serial communication, and of course the AGISO VT cannot check for serial connection i guess. The alarm icon above is on CCI1200 appearing after a few seconds, just around the same time that the application gets offline in AGISOVT. |
I am using CANPEAK adapter to ISOBUS network with RAUCH and or KUHN ECU and CCI1200.
Whenever I am trying to connect a machine to the AGISO VT, I see activity in the text shown, but next to some buttons I have never seen the OP shown as expected on the system.
Might be I am doing something wrong, might be settings, might be compatibiliy.
Attached the log of trying to connect the RAUCH ISO ECU on the network.
AgISOVirtualTerminalLogs_23_Dec_2024_2_17_21pm.zip
The text was updated successfully, but these errors were encountered: