#linuxcnc-devel Logs

Mar 26 2023

12:46 AM linuxcnc-build: build #9009 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/9009 blamelist: Hans Unzner <hansunzner@gmail.com>
12:54 AM linuxcnc-build: build #7622 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/7622 blamelist: Hans Unzner <hansunzner@gmail.com>
03:49 AM linuxcnc-build: build #9827 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9827 blamelist: Hans Unzner <hansunzner@gmail.com>
05:01 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:40 AM -!- #linuxcnc-devel mode set to +v by ChanServ
11:29 AM -!- #linuxcnc-devel mode set to +v by ChanServ
02:31 PM andypugh: So, is there a more PC phrase for the modbus slave address?
02:42 PM pcw--home: oppressor/oppresee?
02:45 PM andypugh: “the enslaved device” ? If something else is coming into use then I would prefer to use that.
03:45 PM rmu: in SPI i've seen Peripheral In, Controller Out
03:45 PM rmu: so maybe in modbus "peripheral address" could make sense?
04:06 PM JT-Shop: the collective
04:07 PM JT-Shop: resistance is futile
05:01 PM andypugh: I am using “node address” for the moment.
06:31 PM seb_kuzminsky: pcw--home: i've got a 7i93 where i'm trying to switch the LED mode from "debug" to "hostmot2", and i'm not having any success, i may be misunderstanding the manual here...
06:32 PM seb_kuzminsky: i'm looking at the 7i93 manual, v1.2, p31 (p35 of the pdf)
06:33 PM seb_kuzminsky: i send a single packet with these contents: 01d91a00 065a 01d91400 0000
06:37 PM seb_kuzminsky: i believe that's "write 16 bits to space 6, address 0x001a = 0x5a06 (write enable space 6)", followed by "write 16 bits to address space 6, address 0x0014 = 0x0000 (LEDMode = 0, meaning hostmot2)"
06:38 PM seb_kuzminsky: the leds turn off, but do not appear to be under hm2 control
06:38 PM seb_kuzminsky: and if i powercycle the board, they go back to "debug" mode where they count received packets
06:39 PM seb_kuzminsky: I see there's a field in space 2 that also talks about the LED mode (0x0028 DEBUG LED Mode), should i set that too?
06:39 PM seb_kuzminsky: or instead?
06:42 PM seb_kuzminsky: setting both of them to 0 does not give hm2 access to the leds
06:43 PM seb_kuzminsky: but the board goes back to debug leds after a power cycle so maybe i'm not writing the registers correctly :-/
06:45 PM Tom_L: i think similar came up in the main channel on a 7i96s a few days back
06:47 PM Tom_L: Mar 13 21:12:28 <pcw-home> Tom_L: it should be pretty easy, all the functions are there
06:47 PM Tom_L: Mar 13 21:12:52 <Tom_L> would they map like a regular io pin then?
06:47 PM Tom_L: Mar 13 21:13:14 <Tom_L> 7i96s.0.led1 or such
06:47 PM Tom_L: Mar 13 21:18:21 <Tom_L> is that LEDMode? 0014
06:47 PM Tom_L: Mar 13 21:19:23 <pcw-home> yes
06:47 PM seb_kuzminsky: did you get it working?
06:47 PM Tom_L: i never tried to but he indicated setting that up with mesaflash wouldn't be a big deal
06:48 PM Tom_L: maybe you can coax him...
06:48 PM seb_kuzminsky: yeah, i'm working on a mesaflash patch to switch the leds back and forth between debug and hm2 mode
06:48 PM Tom_L: then you just address the pins the normal way
06:48 PM Tom_L: mode 13
06:48 PM Tom_L: 14 sry
06:48 PM seb_kuzminsky: i'm used to "old" boards where there was no debug mode, and yeah, the leds show up as pins in hal and you use them any way you like, it's super convenient
06:50 PM seb_kuzminsky: pcw--home: for reference, after the commands above, i also tried 01d91a00 025a 01c92800 0000 ("write-enable space 2, write 0x0000 to 0x0028")
06:52 PM Tom_L: http://tom-itx.no-ip.biz:81/~tom-itx/irc/logs/%23linuxcnc/2023-03-13.html
06:52 PM Tom_L: i think it's in there
06:52 PM Tom_L: nothing really on how to set it up
06:56 PM Tom_L: 09:15 PM pcw-home: its just that the default EEPROM contents select the RXPacketCount option
06:56 PM Tom_L: that's about all that was mentioned
06:56 PM Tom_L: so aparently you change a bit or so in the eeprom
06:57 PM seb_kuzminsky: yeah, that's what my packets above are trying to do... i'm probably just doing something stupid, i'll wait to hear what pcw thinks
06:58 PM Tom_L: if you read those contents does it return the RXPacketCount option?
06:58 PM Tom_L: should tell you if you're in the right place
06:58 PM Tom_L: not sure what 0x value that would be..
07:03 PM seb_kuzminsky: both seem right: space 2 addr 0x0028 is 0x0000 (meaning LEDs owned by HM2), space 6 addr 0x0014 is 0x0000 (meaning LEDs driven by HM2)
07:04 PM seb_kuzminsky: but the LEDs are definitely counting packets and ignoring hm2 register 0x0200
07:04 PM Tom_L: powercycle?
07:04 PM Tom_L: yeah.. you said that
07:04 PM seb_kuzminsky: this is after a powercycle
07:04 PM seb_kuzminsky: fw "bug" (in a feature that not many care about), or a bug in my understanding of how this stuff works...
07:06 PM rmu: i probably don't know what i'm talking about, but what makes you think this parameter is persisted? page 30 says space 6 is "status control area" and the other values are packet counters and similar ephemeral data
07:07 PM Tom_L: because it's an eeprom?
07:09 PM rmu: I'm pretty sure those addresses don't point to eeprom
07:10 PM Tom_L: i gather from what pcw said that's where the values are stored (in eeprom)
07:11 PM rmu: 0000 to 0012 are counters and error registers, 0018 "can be used for sequence numbers", 001c lets you reset the firmware, 001e allows some low level fpga manipulation
07:11 PM Tom_L: whether ^^ that's the right address or not i have no idea
07:12 PM rmu: page 25
07:16 PM rmu: space 2 0x0028 seems to be eeprom
07:16 PM seb_kuzminsky: yeah, maybe they're not persisted. i'd guess the 0x0028 field in space 2 is persisted (space 2 is where the ip address is stored), but maybe space 6 is not?
07:19 PM rmu: i would assume that space 6 0014 is initialized with space 2 0028
07:20 PM Tom_L: have you tried setting 0028 to 0 then power cycle to see if it changes space 6 0014?
07:22 PM Tom_L: also what about space6 0016?
07:27 PM Tom_L: as i see it, that would switch address to hm2
07:27 PM Tom_L: variable
07:35 PM seb_kuzminsky: i would think space6 0016 is a pointer in space6 that's used when 0014 is set to debug mode
07:35 PM seb_kuzminsky: i would think 0016 is ignored if 0014 is 0
07:35 PM seb_kuzminsky: bbl
07:37 PM Tom_L: could be
08:49 PM linuxcnc-build2_: Build [#643](http://buildbot2.highlab.com/buildbot/#builders/14/builds/643) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
08:50 PM linuxcnc-build2_: Build [#643](http://buildbot2.highlab.com/buildbot/#builders/7/builds/643) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
08:50 PM linuxcnc-build2_: Build [#648](http://buildbot2.highlab.com/buildbot/#builders/11/builds/648) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
10:08 PM troglodi1o is now known as troglodito