Question regarding Extra Devices #1394
Replies: 11 comments 7 replies
-
|
A question, not a bug report (Issue), so I moved it to a Discussion item. |
Beta Was this translation helpful? Give feedback.
-
Modules (incl. the VINT HUBs) are assigned in order of their serial number.
Never good to mix several topics into one. This one you reported already as an issue and it was closed. Raising it again without additional information will not have much chance to go much further. Must be a hardware issue on your side or an issue with the Phidget driver. Artisan does not detach modules on ON besides that the VCPs are just sensors and not modules and thus cannot be detached. Just the HUB device channel can be detached.
For a lack of those modules and sensors I don't see a way to help here. Did you look into the Artisan phidget.log as adviced in #1379? |
Beta Was this translation helpful? Give feedback.
-
|
Modules (incl. the VINT HUBs) are assigned in order of their serial number. Does that mean the highest serial number connects last? I still don't understand.
Which Vint HUB Extra Device is Artisan seeing, 1) or 2)? LOG |
Beta Was this translation helpful? Give feedback.
-
|
Could you please attach the full artisan.log file here (rename to .txt and attach via drag-and-drop to a Github browser window). There is obviously a bug during data gathering here which might be the reason channels get detached. Artisan is "seeing" all channels provided by connected Phidgets. Assignment, attach/detach is by channel not by module. First all available channel are discovered, next they are sorted by serial number (either of the module or the HUB). In a second phase, Artisan is assigning those channels in order. First the main device (if a Phidget is selected) is attached to the first matching channel of the discovered and sorted list of device channels, next all extra device channels of type Phidget are assigned with the same strategy in order. |
Beta Was this translation helpful? Give feedback.
-
|
Sorted by serial number? Low to high number? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the log. There was an (typing) issue with async IO channels which was not reported by our type checkers for unknown reasons. Fixed now. You can deactivate device and debug logging again (they produce large output) and update to the next continuous build which should be online within the next hour. Sorting should be low to high. |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic. Thank you so much. |
Beta Was this translation helpful? Give feedback.
-
|
Will that be 2.10.2 ? |
Beta Was this translation helpful? Give feedback.
-
|
The fix will be part of the next release. However, the fix is also in the current beta Continuous Release |
Beta Was this translation helpful? Give feedback.
-
|
No change. Still detaching for no reason. Found this in the LOG: 01-09 11:33:31 MainThread artisanlib.main DEBUG : message: Alarm 1 triggered |
Beta Was this translation helpful? Give feedback.
-
|
Can you please turn device logging on (under Config >> Device) again, activate debug logging (hold OPTION/COMMAND on macOS or ALT/CTRL while clicking on the plus icon until "debug logging ON" appears in the message line), connect your devices, press ON and attach your |
Beta Was this translation helpful? Give feedback.
-
|
Oh, that error message must be related to one of your alarms or script button actions. Obviously the script file specified cannot be found. Not sure if this is related to the detach. |
Beta Was this translation helpful? Give feedback.
-
|
Should I re-install the Phidgets library? |
Beta Was this translation helpful? Give feedback.
-
|
Always use the latest and use (after updating) the Phidget Control Panel to update the firmware of all your modules. |
Beta Was this translation helpful? Give feedback.
-
|
Will do thanks. Some just won't update though, get a long error message.
…On Tue, 9 Jan 2024 at 13:50, Marko Luther ***@***.***> wrote:
Always use the latest and use (after updating) the Phidget Control Panel
to update the firmware of all your modules.
—
Reply to this email directly, view it on GitHub
<#1394 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBEHJB2Y64AAKKXXMO7WRLDYNUVJLAVCNFSM6AAAAABBSTYFO6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANRUHE3TM>
.
You are receiving this because you authored the thread.Message ID:
<artisan-roaster-scope/artisan/repo-discussions/1394/comments/8064976@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
All firmware should be update. If not contact Phidget. However, I would first try to just connect one individual model via one HUB for updating and don't update while all modules are connected to ensure you do not run into any USB power issues during update. I couldn't spot any further Artisan issue in the logs. However, I can see that some Phidget detached and later re-attched, but then did not communicate well (lots of communication errors). The troubles starts here: You might want to send this log to Phidgets asking for help, but I fear you have a EMV or power issue on your system due to the many issues (and maybe motors nearby). Nothing that can be solved on the Artisan side. Sorry. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you for all your efforts. Will get some advice from Phidgets,
they are very helpful.
I am also going to look at the USB cables, the USB hub and USB to mini
cables.
…On Tue, 9 Jan 2024 at 14:14, Marko Luther ***@***.***> wrote:
All firmware should be update. If not contact Phidget. However, I would
first try to just connect one individual model via one HUB for updating and
don't update while all modules are connected to ensure you do not run into
any USB power issues during update.
I couldn't spot any further Artisan issue in the logs. However, I can see
that some Phidget detached and later re-attched, but then did not
communicate well (lots of communication errors).
The troubles starts here:
2024-01-09T11:33:57.719 <ERROR> phidget22usb[PhidgetUSBReadAsyncPacket()] : GetOverlappedResult() in PhidgetUSBReadAsyncPacket failed with error code: 0x0000001f - A device attached to the system is not functioning.
2024-01-09T11:33:57.719 <Info> phidget22[PhidgetUSBReadThreadFunction()] : HUB0001 (6-Port USB VINT Hub Phidget) v116 S/N:687340: ReadThread exiting normally (Phidget detach detected in PhidgetDevice_read)
2024-01-09T11:33:57.725 <Info> phidget22usb[PhidgetUSBCloseHandle()] : Closing USB Device: 0x1674
2024-01-09T11:33:57.725 <Info> phidget22[deviceDetach()] : (Detach) DAQ1000 (8x Voltage Input Phidget) v114 -> HUB0001 Port:0 S/N:687340
2024-01-09T11:33:57.726 <Info> phidget22[deviceDetach()] : (Detach) DCC1000 (DC Motor Phidget) v206 -> HUB0001 Port:1 S/N:687340
2024-01-09T11:33:57.726 <Info> phidget22[deviceDetach()] : (Detach) HUB0001 (6-Port USB VINT Hub Phidget) v116 S/N:687340
2024-01-09T11:33:57.982 <Info> phidget22usb[AttachUSBDevice()] : Attaching Phidget | Path: \\?\usb#vid_06c2&pid_0043#687340#{ddc0b225-2263-4835-aa6e-55f8b77788fe} | PDO Name: \Device\USBPDO-3 | Hub Port: 2
2024-01-09T11:33:57.987 <Info> phidget22[deviceAttach()] : (Attach) HUB0001 (6-Port USB VINT Hub Phidget) v116 S/N:687340
2024-01-09T11:33:57.989 <Info> phidget22[deviceAttach()] : (Attach) DAQ1000 (8x Voltage Input Phidget) v114 -> HUB0001 Port:0 S/N:687340
2024-01-09T11:33:57.990 <Info> phidget22[deviceAttach()] : (Attach) DCC1000 (DC Motor Phidget) v206 -> HUB0001 Port:1 S/N:687340
2024-01-09T11:33:57.998 <Debug> phidget22vint[PhidgetHubDevice_initAfterOpen()] : TXBUFFERSTATUS: 0|127, 0|127, 0|127, 0|127, 0|127, 0|127
2024-01-09T11:33:57.998 <Info> phidget22vint[PhidgetHubDevice_setPortMode()] : Setting Port: 0 mode to VINT on HUB0001 (6-Port USB VINT Hub Phidget) v116 S/N:687340
2024-01-09T11:33:57.998 <Info> phidget22[PhidgetUSBReadThreadFunction()] : HUB0001 (6-Port USB VINT Hub Phidget) v116 S/N:687340: USB read thread started: 0x0000024c
2024-01-09T11:33:59.009 <Warn> phidget22[waitForPendingPacket()] : Packet tracker waitForPendingPacket timeout (1000ms), Port 0
2024-01-09T11:33:59.009 <ERROR> phidget22vint[PhidgetVINTDevice_bridgeInput()] : Failed to send VINT_PACKET_TYPE_PHIDGET_RESET message: 0x03 - Timed Out
You might want to send this log to Phidgets asking for help, but I fear
you have a EMV or power issue on your system due to the many issues (and
maybe motors nearby). Nothing that can be solved on the Artisan side. Sorry.
—
Reply to this email directly, view it on GitHub
<#1394 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBEHJB3WIWBRN2IU3IB6CBLYNUYATAVCNFSM6AAAAABBSTYFO6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANRVGQ2TM>
.
You are receiving this because you authored the thread.Message ID:
<artisan-roaster-scope/artisan/repo-discussions/1394/comments/8065456@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Adding Extra Devices
How does Artisan know what Extra Device is connected when there is more than one Vint Hub?
In my case, I have 2 Vint hubs. If I select Phidget HUB IO 45, how does Artisan know which Vint hub it is? Surely this would cause a conflict.
When I connect 2 x VCP4114 (current transducer) and I press ON the Phidget detaches and the PC requires a computer restart or unplugging of the Vint hub USB to re-attach it.
I have the choice of either connecting the two VCP4114 to Vint HUB ports or a DAQ1000, (8 channel voltage input). I also then assign a Phidgets device 2 and 3 (voltage input)
Both ways detach the Phidget when I press ON
Note: All work fine in the Phidgets control panel, no detaching occurs.
Any help or advice on this issue would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions